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
Tons of workspace/configuration requests #2062
Labels
Comments
This is on v1.0.16 with many vue files open:
|
johnsoncodehk
added a commit
that referenced
this issue
Dec 23, 2022
But I don't know why |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Volar requests configuration through
workspace/configuration
very frequently. For example here we have 8 requests in succession.It's not an issue in itself but it seems quite inefficient.
I think Volar could cache the configuration and rely on
didChangeConfiguration
to invalidate the cache.Note that my suggestion wouldn't work for cases where Volar asks for configuration for specific URI but I'm not really sure that needs to be supported and that people really expect to be able to override configuration per URI.
Also note that the requests that fetch configuration for specific URIs pass the URI of virtual/generated file (for example
../pages/index.vue.js
) and not of the actual file (..pages/index.vue
) so it's even less likely that anyone is relying on that functionality right now.The text was updated successfully, but these errors were encountered: