[
https://issues.jboss.org/browse/WFCORE-3489?page=com.atlassian.jira.plugi...
]
Erich Duda updated WFCORE-3489:
-------------------------------
Description:
When you use control flow constructs consisting of more commands (e.g. {{for-done}}) CLI
completion helper should offer commands based on the current context. So if you type
{{for}} command, CLI completion should offer {{done}} command. The same applies for other
constructs like {{if-else}}, {{try-catch-finally}} and so on.
However if you use these composite operations inside of other composite operations, the
following situation occurs.
{code}
[standalone@embedded /] for var in :read-resource
[standalone@embedded /] try
[standalone@embedded /] <TAB>
: cd connect deployment-overlay
help module read-attribute set
undeploy
alias clear connection-info done
history patch read-operation stop-embedded-server
unset
attachment command deploy echo if
pwd reload try
version
batch command-timeout deployment-info echo-dmr ls
quit run-batch unalias
{code}
As you can see the completion helper offers a {{try}} command although it should offer
{{catch}} command.
This issue is caused by design limitation of CLI. When you type some commands inside of
for loop block, they are just added into internal list and they are not evaluated until
{{done}} command is called. The same applies also for other control flow commands.
was:
The issue appears when you write following commands into the CLI.
{code}
[standalone@embedded /] for var in :read-resource
[standalone@embedded /] try
[standalone@embedded /] <TAB>
: cd connect deployment-overlay
help module read-attribute set
undeploy
alias clear connection-info done
history patch read-operation stop-embedded-server
unset
attachment command deploy echo if
pwd reload try
version
batch command-timeout deployment-info echo-dmr ls
quit run-batch unalias
{code}
As you can see the completion helper offers a {{try}} command although it should offer
{{catch}} command.
This issue is caused by design limitation of CLI. When you type some commands inside of
for loop block, they are just added into internal list and they are not evaluated until
{{done}} command is called.
The same applies also for other control flow commands such as {{if-else-endif}}
CLI completion does not work correctly inside of control flow
commands
----------------------------------------------------------------------
Key: WFCORE-3489
URL:
https://issues.jboss.org/browse/WFCORE-3489
Project: WildFly Core
Issue Type: Bug
Components: CLI
Affects Versions: 4.0.0.Alpha5
Reporter: Erich Duda
Assignee: Jean-Francois Denise
When you use control flow constructs consisting of more commands (e.g. {{for-done}}) CLI
completion helper should offer commands based on the current context. So if you type
{{for}} command, CLI completion should offer {{done}} command. The same applies for other
constructs like {{if-else}}, {{try-catch-finally}} and so on.
However if you use these composite operations inside of other composite operations, the
following situation occurs.
{code}
[standalone@embedded /] for var in :read-resource
[standalone@embedded /] try
[standalone@embedded /] <TAB>
: cd connect deployment-overlay
help module read-attribute set
undeploy
alias clear connection-info done
history patch read-operation stop-embedded-server
unset
attachment command deploy echo
if pwd reload try
version
batch command-timeout deployment-info echo-dmr
ls quit run-batch unalias
{code}
As you can see the completion helper offers a {{try}} command although it should offer
{{catch}} command.
This issue is caused by design limitation of CLI. When you type some commands inside of
for loop block, they are just added into internal list and they are not evaluated until
{{done}} command is called. The same applies also for other control flow commands.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)