You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, the cli has a describe subcommand which is great for quickly checking the docs for a specific component. The problem is that there is currently no way for the users to know which components they can describe without going to the docs site.
Describe the solution you'd like
A new subcommand, list, would allow users to list available components/directives/etc.
quasar list components
quasar list directives
This new subcommand is needed less for efficiency but more for uniformity of the cli UX. In other words, the describe command is point-less without the docs site. This leads users to switching focus constantly between the cli and the browser. The list command would then allow users to stay inside one "environment". Examples of a more encompassing UX in a cli are: docker and kubernetes. Each one provides commands, which by themselves are extremely useful but as a whole provide a uniform (in terminal) experience for users.
The text was updated successfully, but these errors were encountered:
Enhancement for the "quasar describe" command will be available in "@quasar/app" v3.1.7
Example:
$ quasar describe list
The complete list of API elements:
• AddressbarColor
• AppFullscreen
• AppVisibility
• BottomSheet
• Cookies
• Dark
......
$ quasar describe list storage
The list of API elements that match "storage":
• LocalStorage
• SessionStorage
Is your feature request related to a problem? Please describe.
Currently, the cli has a
describe
subcommand which is great for quickly checking the docs for a specific component. The problem is that there is currently no way for the users to know which components they candescribe
without going to the docs site.Describe the solution you'd like
A new subcommand,
list
, would allow users to list available components/directives/etc.This new subcommand is needed less for efficiency but more for uniformity of the cli UX. In other words, the
describe
command is point-less without the docs site. This leads users to switching focus constantly between the cli and the browser. Thelist
command would then allow users to stay inside one "environment". Examples of a more encompassing UX in a cli are:docker
andkubernetes
. Each one provides commands, which by themselves are extremely useful but as a whole provide a uniform (in terminal) experience for users.The text was updated successfully, but these errors were encountered: