[
https://issues.jboss.org/browse/WFCORE-2974?page=com.atlassian.jira.plugi...
]
Vratislav Marek commented on WFCORE-2974:
-----------------------------------------
[~jdenise] If it is too risky to fix this issue because of CLI parser skip all whitespaces
and then malformed command is unrecognize e.q.:
{code:java}
[standalone@localhost:9990 /] /subsystem=logging/logging-profile=myapp:add
{"outcome" => "success"}
{code}
{code:java}
[standalone@localhost:9990 /] /sub ystem=logging/logging-profile=myapp:add
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0030: No resource definition is
registered for address [
(\"subystem\" => \"logging\"),
(\"logging-profile\" => \"myapp\")
]",
"rolled-back" => true
}
{code}
What about fix this with modify Tab Completion to verify if number of characters is same
as number of characters in trimed string e.q.:
{code:java}
"/sub ".length = 5;
"/sub".length = 4;
{code}
Tab Completion must contains number of entred character, or not?
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.12.1#712002)