diff --git a/RELEASE-NOTES.md b/RELEASE-NOTES.md index e84131a71..b6a4c1ee0 100644 --- a/RELEASE-NOTES.md +++ b/RELEASE-NOTES.md @@ -16,7 +16,7 @@ Picocli follows [semantic versioning](http://semver.org/). * [Potential breaking changes](#3.2.0-breaking-changes) ## New and Noteworthy -### JLine Tab-Completion Support +### JLine Tab-Completion Support This release adds support for JLine Tab-Completion. @@ -59,7 +59,7 @@ public class PicocliJLineCompleter implements Completer { } ``` -### Completion Candidates +### Completion Candidates From this release, `@Options` and `@Parameters` have a new `completionCandidates` attribute that can be used to generate a list of completions for this option or positional parameter. For example: ```java @@ -76,7 +76,7 @@ class ValidValuesDemo { This will generate completion option values `A`, `B` and `C` in the generated bash auto-completion script and in JLine. -### `${DEFAULT-VALUE}` Variable +### `${DEFAULT-VALUE}` Variable From picocli 3.2, it is possible to embed the default values in the description for an option or positional parameter by specifying the variable `${DEFAULT-VALUE}` in the description text. Picocli uses reflection to get the default values from the annotated fields. @@ -99,7 +99,7 @@ Usage:
-f= -f, --file= the file to use (default: config.xml) ``` -### `${COMPLETION-CANDIDATES}` Variable +### `${COMPLETION-CANDIDATES}` Variable Similarly, it is possible to embed the completion candidates in the description for an option or positional parameter by specifying the variable `${COMPLETION-CANDIDATES}` in the description text. @@ -130,7 +130,26 @@ Usage:
-l= -o=