You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, nested selectors are not supported, or at least not fully. When you create a nested selector in a CSS file, the extension shows it as not-existing in the JS(/JSX/TS):
As you can see on the left side of the screenshot, my JSX file has a yellow line under the secondParagraph, because (as you can see on the right) the style is defined as a nested style. But if I remove the nesting, the extension recognizes the selector just fine:
To Reproduce
Steps to reproduce the behavior:
Create a nested selector
Reference that selector in JSX
See VS Code add a yellow squiggly line to the selector reference
Remove the nesting of the selector
See VS Code not add a line under the selector (now)
Expected behavior
It doesn't matter if the selector is nested or not; under the React CSS Modules standard the selector should be reference-able from the JSX.
Screenshots
See above
Desktop (please complete the following information):
I assume this is irrelevant, but
OS: Mac OS Sonoma 14.3
The text was updated successfully, but these errors were encountered:
Describe the bug
The library's own readme states:
However, nested selectors are not supported, or at least not fully. When you create a nested selector in a CSS file, the extension shows it as not-existing in the JS(/JSX/TS):

As you can see on the left side of the screenshot, my JSX file has a yellow line under the

secondParagraph
, because (as you can see on the right) the style is defined as a nested style. But if I remove the nesting, the extension recognizes the selector just fine:To Reproduce
Steps to reproduce the behavior:
Expected behavior
It doesn't matter if the selector is nested or not; under the React CSS Modules standard the selector should be reference-able from the JSX.
Screenshots
See above
Desktop (please complete the following information):
I assume this is irrelevant, but
The text was updated successfully, but these errors were encountered: