Skip to content

Bad object expression created when using anonymous import & runtime resolution #14

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 14, 2016 · 1 comment

Comments

@PCreations
Copy link
Contributor

When using dynamic resolution with anonymous import, the generated object expression by createObjectExpression.js does not return a valid AST since the generated property name is prefixed by random- and the hypen is not "escaped" by quotes.

PCreations added a commit to PCreations/babel-plugin-react-css-modules that referenced this issue Dec 14, 2016
PCreations added a commit to PCreations/babel-plugin-react-css-modules that referenced this issue Dec 14, 2016
This was referenced Dec 14, 2016
@PCreations PCreations changed the title Bad object expression created when using anonymous import & dynamic resolution Bad object expression created when using anonymous import & runtime resolution Dec 16, 2016
gajus pushed a commit that referenced this issue Dec 18, 2016
…#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
@gajus
Copy link
Owner

gajus commented Dec 18, 2016

Fixed in #12. Thank you @PCreations

@gajus gajus closed this as completed Dec 18, 2016
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 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
None yet
Projects
None yet
Development

No branches or pull requests

2 participants