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
Use pascal case for global namespace #873
Conversation
This will make jss be accessed with |
Damn, checked old exports from jss
|
Also react-jss was using "reactJss"
|
I think it's okay for breaking change. Let's go with it? |
Its just confusing that Jss is a namespace but its not a constructor, I think React isn't either. |
Then we need to provide an explicit globals object. And convert |
I wonder when will be the next time we have same problem with some peer, we can't actually decide globally what global namespace any of the peer dependencies may use. |
We can actually. Just take a look at peer umd |
updated to use for jss packages camel case, but for peers - pascal case |
jss is also peer dependency, isn't it? |
On react-jss not. On most of the plugins yes.
…On 1. Oct 2018, 12:51 PM +0200, Bogdan Chadkin ***@***.***>, wrote:
jss is also peer dependency, isn't it?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Should be on react-jss too. |
Shit :) |
Any ideas how to do this without maintaining a whitelist? |
No way. Lib authors may not follow only one pattern. |
It's not so big list. react, react-dom and jss. Am I miss something? |
Ok, at least we should build a warning when there is an unknown peer dependency. |
Ok, whitelist with a warning it is now |
* use pascal case for global namespace * docs for new dist files * use camel case without pascal for jss packages globals * whitelist for peer deps and warning
No description provided.