-
-
Notifications
You must be signed in to change notification settings - Fork 400
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
[Bug] "defaultClassNamePrefix" set to undefined in production #901
Comments
thanks for the report |
So instead of undefined let's just use an empty string or would this break something as well? |
I think it would be fine, wanna send a PR? |
This should already be fixed: 1e9ba74#diff-15944e28391ef80a3f4e34ea8a2193f4R99 |
true, @VintorezVS subscribe #795 for notifications when v10 will be published |
Why is it even undefined in the first place? I mean, why in production is We want the same classnames generated in dev and prod. |
@airtonix my understanding is that |
From @VintorezVS on October 23, 2018 6:0
Custom "classNamePrefix" concatenated with "defaultClassNamePrefix" in production gives "customprefix-undefinedXXX" class names.
Copied from original issue: cssinjs/react-jss#304
The text was updated successfully, but these errors were encountered: