-
Notifications
You must be signed in to change notification settings - Fork 8
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
Autocomplete stops working before a nested selector #107
Comments
Syntactically That's how nested CSS works, syntactically. Properties are identified by following semi-colon. Any other chain of tokens Properties are not suggested via auto-completions, within selectors. That's working as expected. |
That's absolutely correct, I can see Stylelint processing it as a selector instead of a property. However, when writing scss, I would expect it to be handled as a property. Having to add properties between existing ones in order to use autocomplete feels clunky. If anyone else is running this issue - I've switched to LSP-css autocomplete for now, as they work as I would expect. |
Resolves #107 Suggest properties also within `meta.selector` as this is the most likely scope in front of a nested selector, if a property is not yet terminated by semi-colon.
Maybe removing |
When adding a new css property to the end of a property list, autocomplete stops working if there's a nested selector immediately following the new property. The type of nested selector doesn't seem to matter, it could be an
&
, a mixin, class, etc.Tested in Windows and MacOS on the current stable build of ST4. Also tested in a clean install with only the Sass package installed with the same results.
Here's an example of autocomplete not working:
And here's an example of autocomplete working as normal, when adding a property to the top of the list:
The text was updated successfully, but these errors were encountered: