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
Currently, replaceSymbols only accepts a mapping of values. This is problematic because the same value may need to be represented differently in different contexts (reference, and there's no way to do that right now.
An API that would solve this, would be something like:
What usecase do you have in mind where that is necessary?
At least for the composed-class-name issue that shouldn't be necessary, as the correct formatting is dependent entirely on where the identifier appears (class names cannot appear in rule declarations, and vice versa).
Not really, when we receive something (It can bee selector/value/media query) from another file, we do not know whether it is, so we should keep context where we get value before, we should change :import('file.css') { test: test from selector } (just idea) it will not fundamentally solve the problem, but rather a hack
Currently,
replaceSymbols
only accepts a mapping of values. This is problematic because the same value may need to be represented differently in different contexts (reference, and there's no way to do that right now.An API that would solve this, would be something like:
The text was updated successfully, but these errors were encountered: