-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
no property autocomplete in JSX(related with an empty space) #40941
Comments
@jrieken For the case: const z = <div c> where the user has just typed
where |
Any update on this? The Ctrl-Space works and provides the correct autocomplete options for props with associated type. Would be nice if I didn't have to do that each time. |
@kevinmlong Have the same problem, but wonder about: "... autocomplete options for props ...". Is VS Code capable to autocomplete my custom |
Fixes #40941 **Bug** Suggestions not auto triggered when you `x` in `const z = <div x>`. See #40941 (comment) for explaination of root cause **Proposed fix** In the case where suggestions are triggered at the boundary between two languages, I believe we should trigger. This change adds special logic to handle that case by making sure we check the word at the previous character position instead of at the current character positon when at language boundaries
Fixes #40941 **Bug** Suggestions not auto triggered when you `x` in `const z = <div x>`. See #40941 (comment) for explaination of root cause **Proposed fix** In the case where suggestions are triggered at the boundary between two languages, I believe we should trigger. This change adds special logic to handle that case by making sure we check the word at the previous character position instead of at the current character positon when at language boundaries
Fix #40941 - Suggest trigger at language boundaries
VSCode Version: Version 1.19.1 (1.19.1) 0759f77
OS Version: macOS, 10.12.6
Steps to Reproduce:
TypeScript React, and https://twitter.com/jiyinyiyong/status/946642303950626817
Reproduces without extensions: Yes.
The text was updated successfully, but these errors were encountered: