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

Missleading tab completion for edit-batch-line command

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 3.0.0.Alpha6
    • None
    • CLI
    • None

    Description

      Tab completion for edit-batch-list command suggest to use --line-number as a command option, but that is not how the command works.

      command usage

      [standalone@localhost:9990 /] batch 
[standalone@localhost:9990 / #] :read-resource
[standalone@localhost:9990 / #] list-batch 
#1 /:read-resource
[standalone@localhost:9990 / #] edit-batch-line 1 :read-attribute(name=launch-type)
#1 :read-attribute(name=launch-type)
[standalone@localhost:9990 / #] list-batch 
#1 :read-attribute(name=launch-type)

      actual

      [standalone@localhost:9990 / #] edit-batch-line <TAB>
[standalone@localhost:9990 / #] edit-batch-line --<TAB>
--help  --line-number
[standalone@localhost:9990 / #] edit-batch-line --line-number=1 :read-attribute(name=launch-type)
Failed to parse line number '--line-number=1': For input string: "--line-number=1"

      --line-number shouldn't be offered by tab completion for the command.
      Misleading tab completion ends up with syntax error.
      expected

      [standalone@localhost:9990 / #] edit-batch-line <TAB>
--help

      The issue is a regression against EAP 7.0.0 release.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-5473 Missleading tab completion for edit-batch-line command

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is caused by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-4270 (7.0.z)(revert) Include indexed properties in the suggestion list if no completer exists

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFCORE-1487 Include indexed properties in the suggestion list if no completer exists

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-5313 (7.1.0) Include indexed properties in the suggestion list if no completer exists

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-5599 [GSS](7.0.z) patch rollback should suggest installed patch ids

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jdenise@redhat.com Jean Francois Denise
              pkremens@redhat.com Petr Kremensky (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: