Investigate Converting TemplateWrapper to Component that extends React.Component

[mccrodp]

From Gatsby i18n plugin I've brought over the TemplateWrapper to this repo from here.

Whereas the "Using Contentful" repo uses a React.Component as shown here.

I've used the TemplateWrapper from the i18n plugin as I need to pass those arguments for the i18n strings. There's probably a way I can do this with the Component method?

Also, this method has issue as it's designed to work with the static pages, not dynamic content from a CMS that uses templates, so in that way, our dynamic content: Products and Categories that use templates do not pass the i18n strings, so I need to do a hack for them here: https://github.com/mccrodp/gatsby-contentful-i18n/blob/master/src/layouts/index.js#L21

if (i18nMessages === undefined) {
    if (langKey === 'de') {
      i18nMessages = messagesDe
    } else {
      i18nMessages = messagesEn
    }
  }

[romeboards]

Seeing the issue with dynamically created pages not getting the i18n strings - this seems like an issue where gatsby-plugin-i18n isn't applying the specialized layout (e.g. src/layouts/en-US.js) to a dynamically created path?

Should that be something accounted for by the plugin, then?

[mccrodp]

Hey @romeboards, thanks a lot for chipping in here. Yes, I think you're right. I think it is related to what I mention on this issue on the plugin, but I don't know so much about it other than that at the moment. Would be great if you had anything to share on that, would love to address it. angeloocana/gatsby-plugin-i18n#12 (comment) Cheers

[mccrodp]

Completed this for Gatsby v2 when adding a custom Layout component: b861f86