[jboss-jira] [JBoss JIRA] (WFCORE-90) don't require escaping special characters where they are not expected in argument values

Alexey Loubyansky (JIRA) issues at jboss.org
Mon Sep 8 17:03:59 EDT 2014


     [ https://issues.jboss.org/browse/WFCORE-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Loubyansky updated WFCORE-90:
------------------------------------
    Fix Version/s: 1.0.0.Alpha6


> don't require escaping special characters where they are not expected in argument values
> ----------------------------------------------------------------------------------------
>
>                 Key: WFCORE-90
>                 URL: https://issues.jboss.org/browse/WFCORE-90
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: CLI
>            Reporter: Alexey Loubyansky
>            Assignee: Alexey Loubyansky
>             Fix For: 1.0.0.Alpha6
>
>
> Besides having this feature in place being nice in general, it will help avoid confusions in some cases and will make determining the problem with the parsed command line easier.
> Examples of special characters in argument values are: {, [, =. Each of these is a legal character in a value by itself. But the CLI reacts to them differently:
> { is a beginning of a DMR OBJECT value;
> [ is beginning of a DMR LIST value;
> = is a name value separator.
> The same for the corresponding closing } and ].
> At the moment the CLI parsing is not smart enough and requires escaping {, }, [, ] and = if they have to be a part of the value.
> This feature request is to make the parsing a bit smarter by taking into account the context where these characters appear and require escaping them in places where they obviously don't have the special meaning.
> E.g. { and [ are significant from the parsing point of few if they appear at the very beginning, i.e. before the parameter value, not in the middle.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


More information about the jboss-jira mailing list