[
https://issues.jboss.org/browse/WFCORE-1723?page=com.atlassian.jira.plugi...
]
Jean-Francois Denise commented on WFCORE-1723:
----------------------------------------------
[~spyrkob], I think this one can be closed, the CommandArgument#canAppearNext is not the
right choice to develop CLI commands, aesh API is the way to go.
OperationRequestCompleter ignores CommandArgument#canAppearNext in
choosing ValueCompleter when there's more then one indexed arguments
---------------------------------------------------------------------------------------------------------------------------------------
Key: WFCORE-1723
URL:
https://issues.jboss.org/browse/WFCORE-1723
Project: WildFly Core
Issue Type: Bug
Components: CLI
Affects Versions: 3.0.0.Alpha5
Reporter: Bartosz Spyrko-Śmietanko
Assignee: Bartosz Spyrko-Śmietanko
If there are two or more indexed CommandArguments that can be used to complete user entry
at the same index, the first one will always be chosen - even if it clashes with previous
arguments.
For example:
{{patch rollback ..<TAB>}}
produces a list of directories - this is because PatchHandler registers multiple
CommandArguments with index 1 and in this case a completer for patch apply is the first
one matched.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)