feat(quasar): add docsUrl to API definition

[lucasfernog]

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change? (check one)

• Yes
• No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• It's submitted to the dev branch and not the master branch
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• It's been tested on a Cordova (iOS, Android) app
• It's been tested on a Electron app
• Any necessary documentation has been added or updated in the docs (for faster update click on "Suggest an edit on GitHub" at bottom of page) or explained in the PR's description.

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

The quasar docs command receives a Quasar component/directive/plugin and opens the docs page. It also supports app extensions. It also has a --api option, which uses the API table anchor as URL.

Credits to @hawkeye64 for the idea.

EDIT: added options to open sections (components, plugins, directives and extensions), e.g. quasar docs components

[nothingismagick]

Wow. Congrats on this!!! Great job

[lucasfernog]

Thanks. Will adjust it to support quasar docs components/plugins/directives.

[nothingismagick]

Just a dumb question: how hard would it be to have $ quasar api search ${search_term}

[lucasfernog]

Just a dumb question: how hard would it be to have $ quasar api search ${search_term}

That's a VERY nice idea, and not hard at all. Just a matter of reading all API file names (quasar/dist/api/*.json) and string filtering them. If it will be another command, I can make another PR.

[nothingismagick]

Oh please, do it.

…

On Sun, 5 May 2019, 00:13 Lucas Fernandes Nogueira, < ***@***.***> wrote: Just a dumb question: how hard would it be to have $ quasar api search ${search_term} That's a VERY nice idea, and not hard at all. Just a matter of reading all API file names (quasar/dist/api/*.json) and string filtering them. If it will be another command, I can make another PR. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4045 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIM4G6AYSEDHOFXRIWKGEWLPTYDAZANCNFSM4HKZYORA> .

[lucasfernog]

Another thing that is missing here: can this command read the Quasar build config and get the user preferred browser? I've tried but couldn't do it.

[lucasfernog]

Another thing that is missing here: can this command read the Quasar build config and get the user preferred browser? I've tried but couldn't do it.

Fixed with latest commits. Also fixed running with app extension API. This PR is now done unless you want something else.

[lucasfernog]

TODO: move default "docs" values to the build command.

[rstoenescu]

Let's use one prop only "docsUrl" with full URL. For now, point to https://v1.quasar.dev. Example:

meta: {
  docsUrl: 'https://v1.quasar.dev/......'
}