Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Add support for Quasar Framework #865

Merged
merged 2 commits into from
Aug 9, 2018
Merged

feat: Add support for Quasar Framework #865

merged 2 commits into from
Aug 9, 2018

Conversation

rstoenescu
Copy link
Contributor

No description provided.

@@ -21,6 +25,20 @@ export const bootstrapTagProvider = getExternalTagProvider('bootstrap', bootstra
export const buefyTagProvider = getExternalTagProvider('buefy', buefyTags, buefyAttributes);
export const vuetifyTagProvider = getExternalTagProvider('vuetify', vuetifyTags, vuetifyAttributes);
Copy link
Member

@octref octref Aug 9, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NVM, see the other comment.

@@ -68,6 +71,22 @@ export function getTagProviderSettings(workspacePath: string | null | undefined)
if (packageJson.dependencies['vuetify']) {
settings['vuetify'] = true;
}

const quasarPath = ts.findConfigFile(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Follow the pattern above

  • Check if dependencies have quasar-framework
  • If so, call into the function getQuasarTagProvider, which should encapsulate the code for finding package.json, etc
  • If that returns null, do nothing
  • If that returns the tagProvider, set settings to true and push it to allTagProviders.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is best for all the ways Quasar can be consumed (through Quasar CLI, vue-cli-plugin-quasar, etc etc). Explained on private.

@octref
Copy link
Member

octref commented Aug 9, 2018

Need to fix Travis which uses node 6, as Quasar depends on Node 8.

This is fine for Vetur since in next release of VS Code we jump to Node 8.9.3 with Electron 2.

@octref octref merged commit ea599ed into vuejs:master Aug 9, 2018
@TonyPythoneer
Copy link

What is it beneficial for this?

@octref
Copy link
Member

octref commented Aug 14, 2018

@TonyPythoneer When you install quasar dependency, you get IntelliSense for its components:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants