Current behavior

Both locale: and fallbackLocales: arguments can be passed to multi-locale fields, but both arguments are completely ignored:

query {
  allBlogPosts {
    _allTitleLocales(locale: it_IT, fallbackLocales: [it, en]) {
      locale
      value
    }
  }
}

Similarly, the fallbackLocales: argument can be passed down to meta fields, but it's ignored:

query {
  _allBlogPostsMeta(fallbackLocales: [it, en]) {
    count
  }
}

Improved behavior

Both the locale: argument in multi-locale fields, and the fallbackLocales: argument in meta fields are removed, as they make no sense.

The fallbackLocales: argument in multi-locale fields is now taken into consideration when a value for a particular locale is missing:

1
query {
2
  allBlogPosts {
3
    noFallbacks: _allTitleLocales {
4
      locale
5
      value
6
    }
7
    withFallbacks: _allTitleLocales(fallbackLocales: [en]) {
8
      locale
9
      value
10
    }
11
  }
12
  _allBlogPostsMeta {
13
    count
14
  }
15
}

1
{
2
  "allBlogPosts" {
3
    noFallbacks: [
4
      { locale: "it", value: "" },
5
      { locale: "es", value: "Título" },
6
      { locale: "en", value: "Title" },
7
    ],
8
    withFallbacks: [
9
      { locale: "it", value: "Title" },
10
      { locale: "es", value: "Título" },
11
      { locale: "en", value: "Title" },
12
    ],
13
  },
14
  "_allBlogPostsMeta": {
15
    "count": 3
16
  }
17
}

Who is affected by this change?

This change will apply to all brand new DatoCMS projects created from today onwards. If you have an existing project that you'd like to update, you can manually do so in the Environment Settings.

Please note that this change cannot be undone, so we strongly recommend testing the effects in a sandbox environment before applying the change to your primary environment.