[
https://issues.jboss.org/browse/WFCORE-2974?page=com.atlassian.jira.plugi...
]
Jean-Francois Denise commented on WFCORE-2974:
----------------------------------------------
[~soul2zimate], I checked and that is an old wrong behaviour. This is caused by the CLI
parser to ignore the space that exists in an operation: e.g.: / subsystem = xxx / name =
zzz : read-resource()
The side effect is that all whitespaces are skip, so having an invalid whitespace in the
middle of a type or name is treated the same way.
That is really a corner case and I would not fix it for 7.1.
CLI completion after one or more spaces gives confusing result
--------------------------------------------------------------
Key: WFCORE-2974
URL:
https://issues.jboss.org/browse/WFCORE-2974
Project: WildFly Core
Issue Type: Bug
Components: CLI
Affects Versions: 3.0.0.Beta26
Reporter: Chao Wang
Assignee: Jean-Francois Denise
Priority: Minor
CLI completion after one or more spaces gives confusing result.
{noformat}
[standalone@localhost:9990 /] /sub[space]TabKey Here
above completion returns result:
[standalone@localhost:9990 /] /sub ystem=
It seems the space before TabKey is recognized as character 's'.
Go on for a second TabKey, it will not list any subsystem candidates.
{noformat}
I think the first completion is not necessary as the {{sub}} with a following space is
not a valid path. It'd better stop there rather than return completion result {{/sub
ystem=}}. But this is a minor case.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)