You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pretty self-explanatory, but this would be a feature to allow clients to specify field name normalization/denormalizations on a per-endpoint basis. This would be useful in cases where (for instance) one endpoint picks PascalCase for their field names and another picks camelCase, and you want to standardize on one or the other in your code.
This could be worked-around using a responseTransformer and per-request denormalizers, but that feels pretty heavy for this specific type of transformation.
I have code for this and can submit a PR for it.
The text was updated successfully, but these errors were encountered:
Pretty self-explanatory, but this would be a feature to allow clients to specify field name normalization/denormalizations on a per-endpoint basis. This would be useful in cases where (for instance) one endpoint picks PascalCase for their field names and another picks camelCase, and you want to standardize on one or the other in your code.
This could be worked-around using a responseTransformer and per-request denormalizers, but that feels pretty heavy for this specific type of transformation.
I have code for this and can submit a PR for it.
The text was updated successfully, but these errors were encountered: