Not able to use camelCase in `orderBy` field

[innateessence]

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

• What is the current behavior?

I execute a query with these arguments:

{
  "first": 50,
  "kind": "QXNzZXRLaW5kOjMzZGYxZmNhLWI0NTAtNDcyZS05ZmYzLWI5NzcxZmYxMzlkMZ==",
  "after": null,
  "search": null,
  "orderBy": "fuelType"
}

and fuelType (which is fuelType as a JSON column in a Django DB)
gets converted to fuel_type before it reaches django's ORM.

The culprit is here: /usr/local/lib/python3.11/site-packages/graphene_django/filter/fields.py (line: 99) resolve_queryset()
On the version of graphene_django that I'm currently using (3.2.0).

• If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via
  a github repo, https://repl.it or similar (you can use this template as a starting point: https://repl.it/@jkimbo/Graphene-Django-Example).

execute a query where orderBy has a value that is in camelCase

• What is the expected behavior?
  I'd expect the naming convention not to cause such weird sorting behavior. (Or, at the least, give me an error telling me what is wrong and why I cannot use camelCase)

• What is the motivation / use case for changing the behavior?
  Please either add errors or fix the bug

• Please tell us about your environment:

  • Version:
  • Platform:

graphene-django = "==3.2.0"

• Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow)

[innateessence]

Looks like this is indeed expected behavior, based on previously merged PRs addressing this in the past
#1054

[kiendang]

From a quick look there doesn't seem to be a quick fix for this.
One workaround is if you have access to and can change model class you can do

fuel_type = JSONField(..., db_column="fuelType")

[innateessence]

From a quick look there doesn't seem to be a quick fix for this. One workaround is if you have access to and can change model class you can do

fuel_type = JSONField(..., db_column="fuelType")

In my case, I believe this won't work as the key fuelType is dynamically provided from a key from a JSONB field, which is pushed from an external codebase in charge of the data.

Any ideas in regards to bypassing the resolve_queryset function from executing?
I don't mind explicitly writing my own order_by functionality in Django's ORM outside of graphene-land.

Alternatively, it'd be nice if we could provide an optional override somehow to prevent this kind of behavior for codebases that have data that expect to perfor an order_by using a value in camelCase, possibly as a kwarg somewhere?