Change the way of injecting Intl

[Jiri Tomasek]

It may be worth investigating if it would be possible to pass intl prop without having to wrap every component with injectIntl(Component). IIUC this is used to make intl prop available for the component.

Maybe we could wrap just injectIntl(App) and make App provide intl in context:

class App extends React.Component {
  getChildContext() {
    return {intl: this.props.intl};
  }
  ...
}
App.childContextTypes = {
  intl: React.PropTypes.object
};

Any component would then grab intl from context as 'this.context.intl'

class AnyComponent extends React.Component {
...
this.context.intl.formatMessage
...
}
AnyComponent.contextTypes = {
  intl: React.PropTypes.object
};

See https://facebook.github.io/react/docs/context.html for more info on how context works

[Jason E. Rist (jason-rist)]

I'm nervous about doing this. At least with injectIntl, it's extremely clear what's happening.

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE