Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-90

don't require escaping special characters where they are not expected in argument values

    Details

    • Type: Feature Request
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.0.0.Alpha6
    • Component/s: CLI
    • Labels:
      None

      Description

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  aloubyansky Oleksiy Lubyanskyy
                  Reporter:
                  aloubyansky Oleksiy Lubyanskyy
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: