Adding incorrect value to one_allowed_collections
relations through schema endpoint breaks graphql endpoint without any visible errors.
#22520
Labels
Describe the Bug
A member on my team accidentally added an incorrect value to a M2A relations value (through the schame apply) in the
one_allowed_collections
field where they used a-
instead of_
. This caused our graphql to return a 500 error for all queries being made. There was no error message outside ofINTERNAL_SERVER_ERROR
.A more descriptive error message would have been helpful.
To Reproduce
M2A
relationship.one_allowed_collections
value to include a non-existent collection in the schema.Directus Version
v10.11.0
Hosting Strategy
Directus Cloud
Database
PostgresQL 13.8
The text was updated successfully, but these errors were encountered: