i18n and context in components

[tomitrescak]

I have made i18n library available through context. As a result, I have to pass context to every single component via props. Is this the correct approach you reckon? Or should I just make i18n available through global space? Does not seem clean.

[achtan]

read this #44

[tomitrescak]

I know about this discussion :/ My problem is that now context has to be inserted into every single component manually via props. Was wondering whether there would be some other way, some way of auto-injecting context to components. But thanks for the pointer.

[achtan]

ifaik context is passed by mapper to every component (if you dont override it)

[tomitrescak]

It's not. Only to containers. Components need to be passed context manually.

[arunoda]

@tomitrescak you can have a common composer which does that.

[fermuch]

is there a problem creating dummy containers just for passing the context to the component?

[tomitrescak]

Thanks for the comments guys. I'm too lazy to do both of these things even though they are probably the cleanest. This is probably not the smartest solution, but I have extended the React.Components class which holds the context as a class property. Now all the components are children of this extended context-enriched component. I'm experimenting with it now and looks ok. Is this a real blasphemy?

import Context from "/client/config/context"

class MantraComponent extends React.Component {
   constructor() {
      base();
      this.context = Context;
   }
}

class MyComponent extends MantraComponent {
   render() {
     <div>{ this.context.i18n('key')}</div>
   }
}

[arunoda]

Closing this and continue the discussion here: #164