anchor.diff:  
   == Dependency Injection
   === Spring Boot
  -The below example shows how to use picocli with Spring Boot:
  +When your command is annotated with `@org.springframework.stereotype.Component`, Spring can autodetect it for dependency injection. The below example shows how to use picocli with Spring Boot:
   
   [source,java]
   ----
  
positive.code: ----
  
  === Completion Candidates
  Picocli can deduce completion candidates for parameters of certain types. For example, `File`, `Path`, `InetAddress` and `enum` types allow picocli to generate completion candidates from the current directory, your `/etc/hosts` file, and the enum values, respectively.
  
  Additionally, you can specify `completionCandidates` for an option. For example, in the `CheckSum` application, we can get completion for the `--algorithms` option parameter by defining the option as follows:
  
  
negative.code: java -cp "${CP}" 'picocli.example.CheckSum' $@
  ----
  
  You probably want to `chmod 755 checksum` to make the script executable. Try calling it on the command line with `./checksum --version` to see if the script works.
  
  To generate a completion script, we call `picocli.AutoComplete`, and give it the name of the class and the name of the command:
  [source,bash]
  ----
  java -cp "checksum.jar:picocli-3.9.5.jar" picocli.AutoComplete -n checksum picocli.example.CheckSum
  ----
  
  This will generate a file called `checksum_completion` in the current directory.
  
  === Installing the Completion Script
  Simply source the completion script to install it in your current bash session:
  
  [source,bash]
  ----
  . checksum_completion
  ----
  Now, if your type `checksum [TAB]` the bash shell will show the available options for this command.
  
  To install the completion script permanently, add it to your `.bash_profile`. Below is a one-liner that adds all completion scripts in the current directory to your `.bash_profile`. It will not create duplicate entries, so it can be invoked multiple times.
  
  