Make ReactLocalization the value of FluentContext #446
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The value of
FluentContext
is now an instance ofReactLocalization
which gained theparseMarkup
method.I also exposed
FluentContext
as part of the public API in case someone prefers to use it viaFluentContext.Consumer
or theuseContext
hook. In fact, I think we should declare these methods as preferrable to thewithLocalization
decorator, which suffers from not hoisting static members of the inner component, if any are present. #430 has a fix for it but perhaps we could live with this shortcoming ofwithLocalization
if other methods are available.