Localized Field about prime HOT 9 OPEN

I am probably going to include this in 0.3.0 in the form argument on each field.

query {
  Blog {
    title
    titleNL: title(locale:"nl")
    body(locale:"is")
  }
}

Would this work for you? To reduce bloat this could be configurable by schema or field.

from prime.

Well, I doubt we will replace it completely, but we may implement them somehow. Contentful does this very well, so I may end up model it after them

from prime.

Ok. But how is that different from what we already have?

query {
  Blog(locale:"nl") {
    title
    body
  }
}

I am starting to think that this ticket is more about UI rather than API, am I correct?

from prime.

GraphCMS is also doing this on field level:

 query page($id: ID, $locale: Locale) {
      page(where: { id: $id }) {
        updatedAt
        createdAt
        id
        title
        slug(locale: $locale)
     }
 }

@birkir do you still plan to implement this in 0.3?

from prime.

from prime.

I don't have a strong opinion on how Localization is implemented, but I'm glad to see it will be released on 0.3.0 or soon enough

Keep up the great work, thanks for open sourcing! 👍 💯

from prime.

The way Cockpit CMS does it is with a URL query parameter. If the parameter is not provided the localized fields get a locale suffix. So far this is the setup that has worked best for me.

from prime.

That would indeed work, of course. I brought up the other approach just in case it might give you more ideas.

My concern is more towards multilingual sites using gatsbyjs.

from prime.

My only question with translated documents - how do you connect two documents?

For example, we have city tour website. We have a list of cities and a list of places for each city). So titles/descriptions suppose to be translated, but geo-location, open/closing times, price range are all the same across the languages. What I do now is that I have same entities in DB, but translate fields.

from prime.