fix(vue): support attribute autocomplete in WebStorm - #31419
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
OS-jacobbell
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue number: internal
What is the current behavior?
The
web-types.jsonfile provides autocomplete information for Ionic-Vue component attributes to the JetBrains WebStorm IDE. The autocomplete does work, but only when the component has not been imported into the source.vuefile. Once imported, the IDE replaces types provided byweb-types.jsonwith types from@ionic/vue/dist/types/proxies.d.ts, which it fails to understand, and ceases providing attribute autocomplete.What is the new behavior?
Setting
priority: "highest"on each component inweb-types.jsontells WebStorm to keep these types over imported ones. Autocomplete information persists after importing the Ionic-Vue component.Does this introduce a breaking change?