-
-
Notifications
You must be signed in to change notification settings - Fork 206
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
Inconsistent Props completion in namespaced component #2202
Comments
Thanks for the fix @jasonlyu123, it's very much appreciated! 😄 I cloned this repo to test out the changes and noticed 1 issue. The prop completions don't show correctly when you trigger them when you're 1 space out. It seems like it only triggers when you're two spaces out, as shown here: With that in mind, I've tested out all of the scenarios where it previously didn't work and they all seem to work now! Edit: Here's a reproduction to demonstrate the cases where it does and does not work: https://github.com/AdrianGonz97/inconsistent-namespace-props-repro |
I can't reproduce it with the reproduction. Are you sure the build succeeded? Or maybe you have the |
@jasonlyu123 Aha, you're correct! After deleting the my local repo and recloning, building and testing again, it seems to be working now. Sorry about that!! Everything looks to be working beautifully. 😄 Thanks for the help! |
Describe the bug
I'm noticing that the autocomplete works only if a known prop comes before you attempt to trigger Intellisense.
Here's an example of trying to trigger Intellisense before the prop:
Then if you try to trigger Intellisense after the prop, the correct result is displayed:
But if you try to use an expression, it also breaks:
Without the expression, all good:
Reproduction
Create a component:
Export it
Attempt to get Intellisense to work when using it:
Expected behaviour
Once a space has been inserted after the
.Root
, Intellisense should display the props.System Info
Which package is the issue about?
No response
Additional Information, eg. Screenshots
No response
The text was updated successfully, but these errors were encountered: