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
We are looking to be able to use custom file extensions with Vue to differentiate some of our components between other components we have. Our compiler chain works fine with custom file extensions other than .vue, but the Volar extension has a few places where this is hard coded. I did a quick test and dropped in our custom extensions in a couple places and everything seems to work.
Would you be open to a pull request that adds a new configuration setting that would pass along these custom file extensions to the underlying services?
This would just be to make Volar's internals treat these other file extensions the same as if they were .vue. It would not automatically add file associations (unless I can find a way to do that dynamically instead of in package.json) - but VS Code already has support for that.
The text was updated successfully, but these errors were encountered:
We are looking to be able to use custom file extensions with Vue to differentiate some of our components between other components we have. Our compiler chain works fine with custom file extensions other than
.vue
, but the Volar extension has a few places where this is hard coded. I did a quick test and dropped in our custom extensions in a couple places and everything seems to work.Would you be open to a pull request that adds a new configuration setting that would pass along these custom file extensions to the underlying services?
This would just be to make Volar's internals treat these other file extensions the same as if they were
.vue
. It would not automatically add file associations (unless I can find a way to do that dynamically instead of in package.json) - but VS Code already has support for that.The text was updated successfully, but these errors were encountered: