-
Notifications
You must be signed in to change notification settings - Fork 83
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
IDE | Autocomplete for web-components and their prop names and types #2056
Comments
Hello @Darkavid, honestly I've never used vue yet, I can give you a solution which worked for react and solid, If you need more help, you can reach out to me :) Christopher EDIT: Check this out, |
Hello team, Hi @christopherGdynia, I have found it: We can use this output in VSCode to get autocompletion for your custom webelements. Could you add this option to your stencil config for builds? Thanks in advance! |
An investigation with @christopherGdynia lead us to the following conclusions:
This makes this issue rather a bug than a support ticket. Can you please fix this issue in your next release? |
will close in favor of #2302 |
Scale Version
3.0.0-beta.56
Framework and version
Web-components with Vue3 and Vite.
Additional context
Hi!
The documentation says:
That is true, however, I think we can all agree that developer experience is not only about how cool something under the hood.
Proxy packages were really great because they provided the autocomplete suggestions for components and props in the IDE (e.g.: WebStorm). Without them, all I have is custom web-components added run-time, totally unknown by the IDE. Meaning, I have to rely only on basically pure text when using your components, which makes the frontend code hard to maintain and to refactor.
Please, help me, if you remove the proxy packages, what alternatives do I have to avoid losing autocomplete functionality for your package? How am I going to have type-check and autocomplete for components & props?
Maybe I'm just missing something here 😃
Many thanks!
Dave
The text was updated successfully, but these errors were encountered: