refactor(add): show description for template positional arg

[shinGangan]

🔗 Linked issue

resolved #317 .

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

When I ran the nuxi add —help command, the description of the type: positional option was not displayed, as shown below.

Create a new template file. (nuxi add v3.10.0)                                

USAGE nuxi add [OPTIONS] <TEMPLATE> <NAME>

ARGUMENTS

  TEMPLATE    
      NAME    

OPTIONS

       --cwd    Current working directory
  --logLevel    Log level                
     --force    Override existing file

So we displayed the explanation as follows.

Create a new template file. (nuxi add v3.10.0)                                                                                                                                                 

USAGE nuxi add [OPTIONS] <TEMPLATE> <NAME>

ARGUMENTS

  TEMPLATE    Scaffold template. 
              Possible values: api, plugin, component, composable, middleware, layout, page
      NAME    Generated file name                                                                                            

OPTIONS

       --cwd    Current working directory
  --logLevel    Log level                
     --force    Override existing file

Contents not supported by this PR

• Addition of explanation for mode options such as —client, —server.
• Addition of explanation for —method option.

For user convenience, --client, --server, --global, and --method would like to displayed. However, it requires a slight modification of the existing implementation and should be discussed in a separate issue.
(It would be easier to add options for each Template if it were a subcommand, but it would increase maintenance costs.)

Note

This PR is not urgent.
Therefore, you can lower the priority of the review (if you have another reviewer, we would appreciate it if you could assign it to them, also low priority is not a problem).

📝 Checklist

• I have linked an issue or discussion.
• I have added tests (if possible).
• I have updated the documentation accordingly.

[shinGangan]

Hi, @pi0 (I wasn't sure who to request a review from).

We would appreciate your review and approve the workflows when you have time.

Note

This PR is not urgent.
Therefore, you may lower the priority of your review

Thank you for your ❤️ action.

[pi0]

Thanks (updated with citty fix that shows valueHint for positional as well. nice spot!)

[shinGangan]

Thank you for merging this PR. 🙏