non-reversible case conversion

• What is the current behavior?

>>> from graphene.utils.str_converters import to_snake_case
>>> from graphene.utils.str_converters import to_camel_case

>>> to_camel_case("my_variable_1")
'myVariable1'

>>> to_snake_case("myVariable1")
'my_variable1'

• What is the expected behavior?

>>> from graphene.utils.str_converters import to_snake_case
>>> from graphene.utils.str_converters import to_camel_case

>>> to_camel_case("my_variable_1")
'myVariable1'

>>> to_snake_case("myVariable1")
'my_variable_1'

• What is the motivation / use case for changing the behavior?

Being able to convert objects/properties back and forth between server and client.
Also useful for introspecting and debugging use cases.

In my particular case, I receive an object on my server that the client got from the api and I want to associate it with the source which I now need an extra mapping for since the conversion is one-directional.

• Please tell us about your environment:

Version: graphene-django 2.10.0

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

This is where in graphene it is happening: https://github.com/graphql-python/graphene/issues/1204

My current workaround is to add an underscore in case of trailing numbers:

input = re.sub(r'(.*)(\d+)$', r'\1_\2', input) 

I have 2 solution suggestions:

1. Adding an underscore in case of trailing numbers.
2. Not removing the underscore in case of trailing numbers (like _1).

Bắt đầu trong graphene.utils.str_converters và tái hiện các ví dụ được ghi lại cho to_camel_case và to_snake_case. So sánh hai cách xử lý được đề xuất đối với các số ở cuối, sau đó xác định hành vi round-trip mong đợi và xác minh rằng việc chuyển đổi giữ nguyên dấu gạch dưới trước số cuối cùng.