- Unique fields are currently broken due to a unique constraint applied in the database for localized content. We will issue a fix for this next week, the plan being to remove the unique constraint from the database layer and moving it to the application layer** *
We have run into this issue when trying to update a filled in version of the default locale, updating the default locale seems to work fine. Odd thing is that our component had no unique fields that it is failing for, so it must be related to something with the localisations, having rolled everything back to 3.5.3 and removing any localisations entries in the database everything is back to normal.
We also managed to get filtering working by using gatsby-source-graphql and using a where clause.
I guess we will wait for the stable release before taking it further than staging for the moment