-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
Update vscode extension to support new nesting syntax #1007
Comments
Hi @equinusocio, Thank you for reaching out. Which VSCode extension? Did you also try the native CSS support in VSCode, we contributed improved support for standard CSS nesting there and it landed in the latest release of VSCode. |
https://marketplace.visualstudio.com/items?itemName=csstools.postcss Assuming this is coming from this team since it says
Nope, not yet. But I'll give it a try |
sorry, pasted the wrong link: |
I've never personally contributed to that package/repo and it doesn't seem maintained anymore :/ I've been focussing my efforts on making sure that VSCode itself has really good support for CSS as that helps more people :) The main difference at this point is likely support for |
By reading the extension reviews, there are issues with vs code intellisense, so it may be a good idea to remove the extension from the marketplace or deprecate it. |
I agree but beyond my control here :) |
It's also beyond my control for what is worth. Only Jon can do it |
Who me ‘Jon’? VSCode extension? I can definitely ask about that. |
I also opened this issue in that repo to map out what can be ported to the builtin VSCode support for CSS : csstools/postcss-language#16 |
Going to close this here, we can follow up in the extension's repo. |
What would you want to propose?
Currently the vscode extension doesn't support the new nesting syntax which make
@nest
obsolete.Before with
@nest
:Now:
Suggested solution
nested code is highlighted correctly without
@nest
Additional context
No response
Validations
Would you like to open a PR for this feature?
The text was updated successfully, but these errors were encountered: