Given a local fallback of en-GB => [en-GB, en] - I would expect that inspecting a model instance with Block1 defined in en-GB and Block1 and Block2 defined in en - that when the en-GB locale is queried that the results would contain content from Block1 in en-GB and Block2 from en.
Gatsby GraphQL query
query MyQuery {
datoCmsStringTable(locale: {eq: "en-GB"}) {
id
locale
application {
__typename
... on DatoCmsShippingAddress {
id
lineOne
locale
}
... on DatoCmsConfirmation {
id
success
failure
locale
}
}
_allApplicationLocales {
locale
value {
__typename
... on DatoCmsShippingAddress {
id
lineOne
}
... on DatoCmsConfirmation {
id
success
failure
}
}
}
}
}
results - merging does not occur - secondly - it would be fantastic if the "failure" key of 'en-GB' would also fallback to 'en' as well.
Given a local fallback of en-GB => [en-GB, en] - I would expect that inspecting a model instance with Block1 defined in en-GB and Block1 and Block2 defined in en - that when the en-GB locale is queried that the results would contain content from Block1 in en-GB and Block2 from en.
Gatsby GraphQL query
results - merging does not occur - secondly - it would be fantastic if the "failure" key of 'en-GB' would also fallback to 'en' as well.