8000
We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Graphene Django's documentation on ordering exposes the orderBy filter:
orderBy
query { group(id: "xxx") { users(orderBy: "-created_at") { createdAt } } }
Since the created_at Django field is actually exposed in GraphQL as createdAt, shouldn't the ordering filter follow a consistent style by default?
created_at
createdAt
query { group(id: "xxx") { users(orderBy: "-createdAt") { createdAt } } }
The workaround I've found is to do:
order_by = OrderingFilter( fields = ( ('created_at', 'createdAt') ) )
but the casing conversion probably be handled by the framework itself, to avoid the unnecessary noise / maintenance bloat.
The text was updated successfully, but these errors were encountered:
Allow to use camel case in order by field
4c9eefd
Fixes graphql-python#1008
Allow to use camel case in order by field (#1054)
a51c2bf
Fixes #1008
Successfully merging a pull request may close this issue.
Graphene Django's documentation on ordering exposes the
orderBy
filter:Since the
created_at
Django field is actually exposed in GraphQL ascreatedAt
,shouldn't the ordering filter follow a consistent style by default?
The workaround I've found is to do:
but the casing conversion probably be handled by the framework itself, to avoid the unnecessary noise / maintenance bloat.
The text was updated successfully, but these errors were encountered: