-
Notifications
You must be signed in to change notification settings - Fork 4
I'm sharing: Context API and Cleanup, really not ready #1
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
base: master
Are you sure you want to change the base?
Conversation
Support for: - new Context API - static getDerivedStateFromProps
…Context.Consumer)
createContext() vs. React.createContext() made no difference - I just choose the latter because of personal preference
e.g. "now" and "formatters"
|
Hey, |
|
Update of current code is wasting by time by my own experience. I tried this. |
|
@DragonRaider5 what is the status on your New Context API branch ? is is ready to use ? |
WARNING: You don't want merge this :-)
Please, do not take this seriously, you can checkout my current version which I'm using now.. many of features are disabled
For example I completely drop
<FormattedHTMLMessage />and other apis are not really ideal..My goal is
Translatorclass which can be used with ease outside of React……and I know that I will need
TranslatorManagersingleton on client which will be feeded automatically by Webpack generated code…Also note my rewrite of
babel-plugin-react-intl(published on npm as@langpavel/babel-plugin-react-intl)