-
-
Notifications
You must be signed in to change notification settings - Fork 468
test: usage with css-loader and composes #208
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
test: usage with css-loader and composes #208
Conversation
@avaly Sry for the delay based on your description this sounds like a bug in |
The CI is also failing but it seems this is intentional for demonstration? |
@michael-ciniawsky I'm not sure where the issue is between |
@michael-ciniawsky Sorry for opening the PR here, but I tried adding this type of failing tests for the |
I also need to take a deeper look at it first aswell 😛, yep please open an issue in Is this PR for demonstration purposes only or subject to eventually merge in the future ? 🙃 |
I was looking into the I've updated my branch and tests seem to pass. Feel free to merge it or not, though I feel it might be helpful for others who might run into this. |
What kind of change does this PR introduce?
Test cases: passing and failing
Did you add tests for your changes?
Yes, only tests.
Summary
Using
style-loader
andcss-loader
with local scoped identifiers andcomposes
works as expected.However when adding
css-loader
sgetLocalIdent
option, only some identifiers are properly passed through the customgetLocalIdent
, while the identifiers from the composed files are still using thelocalIdentName
option.See the failing test
local scope, composing, custom getLocalIdent
I submitted this PR here, because this is not reproducible when using only the
css-loader
.