Skip to content

No className generated when styleName is resolved at runtime #18

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

Closed
PCreations opened this issue Dec 16, 2016 · 5 comments
Closed

No className generated when styleName is resolved at runtime #18

PCreations opened this issue Dec 16, 2016 · 5 comments
Labels

Comments

@PCreations
Copy link
Contributor

PCreations commented Dec 16, 2016

When using runtime resolution to find the actual styleName, no className attribute is added to the component, making it unstyled.

@gajus
Copy link
Owner

gajus commented Dec 18, 2016

@PCreations Is still still an active issue?

@gajus gajus added the bug label Dec 18, 2016
@PCreations
Copy link
Contributor Author

@gajus Yes it is, do you understand it or do you want me to rephrase it ?

@PCreations
Copy link
Contributor Author

@gajus I'm actually trying to solve this one, PR should come today.

PCreations added a commit to PCreations/babel-plugin-react-css-modules that referenced this issue Dec 19, 2016
@PCreations
Copy link
Contributor Author

@gajus Should be fixed by #19

gajus pushed a commit that referenced this issue Dec 19, 2016
* fix: added escape hatch when testing attribute that do not have a name property (#11)

* fix: object expression generated on dynamic resolution now use quote to escape properties' name (#14)

* fix: getClassName now works as expected when multiple file use runtime resolution

* fix: getClassName now works as expected when multiple file use runtime resolution

* fix: className attribute is now correctly generated when using runtime resolution (#18)
@gajus
Copy link
Owner

gajus commented Dec 19, 2016

Thank you!

p.s. I saw your email. To follow up is on my list of things to do.

@gajus gajus closed this as completed Dec 19, 2016
gajus pushed a commit that referenced this issue Jan 6, 2017
* Make syntax parser configurable
* Make syntax parser configurable
* fix:  handle multiple file import with dynamic resolution (fixes #7 #11 #13 #14 #17) (#12)
* fix: added escape hatch when testing attribute that do not have a name property (#11)
* fix: object expression generated on dynamic resolution now use quote to escape properties' name (#14)
* fix: getClassName now works as expected when multiple file use runtime resolution
* fix: getClassName now works as expected when multiple file use runtime resolution
* fix: generate className when using runtime resolution (#18) (#19)
* fix: added escape hatch when testing attribute that do not have a name property (#11)
* fix: object expression generated on dynamic resolution now use quote to escape properties' name (#14)
* fix: getClassName now works as expected when multiple file use runtime resolution
* fix: getClassName now works as expected when multiple file use runtime resolution
* fix: className attribute is now correctly generated when using runtime resolution (#18)
* feat: improve error messages (#21)
* Make syntax parser configurable
* Merged upstream
* Updated the configuration section of the readme file
* docs: improve wording
* fix: add a missing comma

BREAKING CHANGE:

If your installation is using CSS, now you need to manually install scss-loader and configure it. https://github.com/gajus/babel-plugin-react-css-modules#configurate-syntax-loaders
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants