Uploaded image for project: 'Aesh'
  1. Aesh
  2. AESH-306

@GroupCommandDefinition tab completion improvements

    Details

    • Type: Enhancement
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.0.0.RC1
    • Component/s: None
    • Labels:
      None

      Description

      A mix of @GroupCommandDefinitions and normal commands are a little hard to use with tab completion.

      1.) Consider differentiating @GroupCommandDefinitions somehow? Append ":", "->", etc?

      2.) Tab completion doesn't kick in, unless the group has a space after it. Example:

      artificer> storedQuery<TAB>
      artificer> storedQuery <TAB>
      storedQuery create   storedQuery execute  storedQuery list     
      storedQuery delete   storedQuery get      storedQuery update
      artificer> storedQuery 
      

      Instead, consider:

      artificer> storedQuery<TAB>
      storedQuery:create   storedQuery:execute  storedQuery:list     
      storedQuery:delete   storedQuery:get      storedQuery:update
      artificer> storedQuery:
      

      Essentially, if you hit <TAB> and the buffer contains only one possible command (a group), immediately display all the group's commands. Currently, it "completes" the group name by adding a space and forcing you to hit tab again.
      Also, consider using ":" between the group and commands, rather than a space.

      3.) The listing of all possible commands is confusing, since groups and commands are not differentiated from each other. Example – here's Artificer's full tab-completion:

      artificer> 
      addComment       clear            echo             man              refreshMetaData  updateMetaData   
      alias            connect          exit             maven            showMetaData     uploadArtifact   
      archive          createArtifact   export           ontology         status           
      audit            delete           getContent       property         storedQuery      
      classification   disconnect       getMetaData      query            unalias
      

      Several of those are groups (ontology, storedQuery, maven, etc.). Multiple Artificer users mentioned being confused.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  stalep Stale Pedersen
                  Reporter:
                  brmeyer Brett Meyer
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: