Feature Request: Different transformation methods for different marshaling types #84
Open
Description
I propose enhancing enumer to allow specifying different transformation methods for different marshaling types.
Our team currently implements custom GraphQL and JSON marshaling methods based on UPPER_SNAKE_CASE and snake_case representations, respectively. It'd be extremely helpful if enumer can generate both for us while keeping the current representations.
I suppose the feature will accept a transformation method via the value of each marshaling flag as shown below.
-gqlgen=snake-upper -json=snake
If this sounds like a good feature to add, I am ready and willing to contribute to its implementation.
Metadata
Assignees
Labels
No labels