allow roots-contentful to be configured to pull localized entry

[rmfarrell]

hack:

request = http_sync.request({
        method: 'GET',
        protocol: 'https',
        host: 'cdn.contentful.com',
        path: "/spaces/#{contentful_config.space_id}/entries/#{entry_id}?access_token=#{contentful_config.access_token}&locale=#{locale}"
      })

unsure what the config interface would look like...

[rmfarrell]

https://github.com/carrot/roots-contentful/blob/master/lib/index.coffee#L98 is where we need to pass in the locale obj per the documentation right here: https://github.com/contentful/contentful.js#search-examples (get localized content)

[hhsnopek]

@rmfarrell what are you thinking the outputted filename out be? view-br or br-view or would this be folder based?

[kylemac]

the filename would be whatever is defined in the path configuration, like the current extension configuration. i'm just imagining that you can also set a locale key to get it's language's response

[rmfarrell]

An entry can have multiple languages per field, the idea is to get an entry's fields in languages other than the default from any given file.

[hhsnopek]

oh I was thinking that it would compile all the locales request, but you're thinking it'll compile just one?

[hhsnopek]

Use Case:

• you provide locale(s) for each entry or locale(s) for all entries
• contentful returns with content in each locale + default local
• roots renders all content per locale based on multi-compile

Interface:

contentful = require 'roots-contentful'

module.exports =
  ignores: ["**/_*", "**/.DS_Store"]
  extensions: [
    contentful(
      access_token: 'YOUR_ACCESS_TOKEN'
      space_id: 'aqzq2qya2jm4'
      locale: 'en-ES' # or ['lang-1', 'lang-2'] Global scope, all entries
      content_types: [
        {
          id: '6BYT1gNiIEyIw8Og8aQAO6'
          locale: 'en-ES' # Entry scope, overrides global scope
        }
        {
          id: '7CDlVsacqQc88cmIEGYWMa'
          locale: 'en-ES'
        }
      ]
    )
  ]

[kylemac]

outstanding ☝️

[hhsnopek]

Also going to add a way to map a locale to a prefix for each template path so that you may use different templates depending on the locale, unsure the key name atm but the object looks like this:

{
  "en-ES": "english-",
  "en-ca": "french-",
  "locale-name": "foobar-"
}

[AdamPflug]

What's the status of this? Is this project just dead?