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
In this scenario, it's a small typo, where I accidentally added an extra r when naming the imported value, and when I was typing the background color I just hit tab to autocomplete.
I've somewhat worked around this variation of the issue by using editor plugins such as All Autocomplete.
However, the other scenario in which it fails is when you're refactoring. There's no easy way of confirming that a value is no longer being used anywhere. On the other hand, if deleting a value from colors.css caused compilation to fail, I could follow the errors and update all references.
Would it be feasible to implement this kind of behavior?
The text was updated successfully, but these errors were encountered:
It would be extremely useful to get errors when you import a value which doesn't exist.
I've been using module values for a couple months now, and silent failures have definitely been one of my bigger pain-points.
(In the following example, the components folder would be symlinked to
node_modules/components
.)For example:
components/styles/colors.css
components/Foo/Foo.css
In this scenario, it's a small typo, where I accidentally added an extra r when naming the imported value, and when I was typing the background color I just hit tab to autocomplete.
I've somewhat worked around this variation of the issue by using editor plugins such as All Autocomplete.
However, the other scenario in which it fails is when you're refactoring. There's no easy way of confirming that a value is no longer being used anywhere. On the other hand, if deleting a value from
colors.css
caused compilation to fail, I could follow the errors and update all references.Would it be feasible to implement this kind of behavior?
The text was updated successfully, but these errors were encountered: