-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add support for code completion after @debug
and @error
#186
Comments
Thank you for opening this issue. Just in case I'll add that the at-rule Another case I found was: @use './test' as test;
$test: "#{test.}"; // it won't show the autocomplete here after the dot
.#{test.} {} // it won't show the autocomplete here after the dot // settings.json
{
"somesass.suggestFunctionsInStringContextAfterSymbols": " (+-*%{"
} I have a question regarding the option Please let me know if I'm doing something wrong and/or if you would like me to open another issue about this. P.S. The example repo has been updated with the new test cases. |
Sounds like a related issue, so we can track it here 👍 There's some handling of string interpolation here, but I guess there are some cases where it doesn't work correctly. |
Thanks for testing and reporting so thoroughly 🙌 $test: "#{test.}"; For this case it seems like VS Code is not asking for code suggestions when I type inside the quotes, even after this change, which I believe should make it so VS Code asks for completion items again. A workaround is to manually ask for suggestions. By default it should be Ctrl + Space. Another option is to skip the quotes. |
Apart from what I mention above, the bugs describe in this issue should be fixed in 3.1.11. I opened a new issue for that, so I'll close this one. |
About In your case inside the quotes you end up here, and |
Perfect, thanks for all the information! I will update the extension, do more testing and get back to you in the new issue if needed. |
From #184
It's likely the
do-complete
feature gets confused by the at-rule statements. See if the completion context can be extended to support code completions in these two scenarios (@debug
and@error
).The text was updated successfully, but these errors were encountered: