Btw we've recently bumped Graphene version and now Graphene supports setting deprecation messages for enums. I think we have our own wrapper for that which I think isn't required anymore. See the changelog and these changes.

That's a separate issue but this version also added the implementation of Decimal scalar so we should be able to drop our own implementation.

Btw we've recently bumped Graphene version and now Graphene supports setting deprecation messages for enums. I think we have our own wrapper for that which I think isn't required anymore. See the changelog and these changes.

Our wrapper is converting our custom enums that have the CHOICES fiels into a GraphQL enum, it's meant to avoid repetitive [(k, v.upper()) for k, v in cls.CHOICES.items()].

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Adding good first issue label. If anyone wants to pick this up, it's best to work on this in smaller batches and provide pull requests for each module separately. Reviewing and improving is easier than a big PR with changes in many modules.

I am available to work on this, please provide an example, I see some enums already have @proprerty def description() created, is this what the issue is referring to?