-
Notifications
You must be signed in to change notification settings - Fork 123
autocomplete not working on windows #401
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
Comments
@Proantagonist this is most likely because the extension failed to find |
Certainly. Here is the output:
|
I should add that this VSC workspace is an Nx workspace with multiple The target app is consuming components from |
Ahh ... please open a TS file first, then the HTML. This shall be fixed before the next release. |
Could you please try "Go to definition" for |
"Go to definition" navigates to it correctly. I looked at #402 but I'm not sure I know what to do from here. Thank you for all your help! |
Thanks @andrius-pra, I'll cut another beta release this week with all the fixes. |
Closing this, v0.900-.0-next.1 is released. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
@kyliau I followed the instructions to install v0.900.0-next.0, however there are no auto-complete suggestions for anything (e.g component selectors, properties, events, etc).
Originally posted by @Proantagonist in #335 (comment)
The text was updated successfully, but these errors were encountered: