You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently upgraded from 0.4.9 to 1.0.0, since we are upgrading our application to Django 4.2. Suddenly my tests for filters that happen to be on enum fields, which assert the query results is the expected result, are failing. The query result is including all results and not doing any filtering.
I can get around this by casting the fields to a string and then adding a resolver to uppercase the string, but then we lose the graphql features associated with enums.
The text was updated successfully, but these errors were encountered:
Actually I just realized this workaround could break downstream clients if they are using enums for these filters in the query. So yeah, I don't actually have a workaround.
I recently upgraded from 0.4.9 to 1.0.0, since we are upgrading our application to Django 4.2. Suddenly my tests for filters that happen to be on enum fields, which assert the query results is the expected result, are failing. The query result is including all results and not doing any filtering.
I can get around this by casting the fields to a string and then adding a resolver to uppercase the string, but then we lose the graphql features associated with enums.
The text was updated successfully, but these errors were encountered: