Skip to content

Conversation

@chrisgarrity
Copy link
Contributor

Since #3431 GUI includes its own Intl provider (react-intl supports nested intl providers) that works within the www intl provider.

This PR restores the app-state-hoc intl provider for the stand-alone gui so that IE can function enough to put up the unsupported browser.

This will permit adding localization to things outside what's exported by GUI. We should be very careful about adding localization to any GUI wrapper component because it will work in playground (because of this PR), but possibly break in www.

GUI includes its own Intl provider (react-intl supports nested intl providers) that works within the www intl provider.

Restore the app-state provider intl provider and app-stat-hoc for the stand-alone gui so that IE can function enough to put up the unsupported browser.
@paulkaplan
Copy link
Contributor

@rschamp @benjiwheeler could you review this? I'm not familiar with the context from #3431 but you two reviewed that one.

@chrisgarrity chrisgarrity changed the base branch from develop to smoke October 29, 2018 13:53
@benjiwheeler
Copy link
Contributor

This LGTM!

@chrisgarrity chrisgarrity merged commit 0785ffa into scratchfoundation:smoke Oct 29, 2018
@chrisgarrity chrisgarrity deleted the issue/fix-ie-intl branch October 29, 2018 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants