When building REST APIs that follow the HAL/Hateoas spec it is common for metadata fields that aren't directly attached to the resource to be prefixed with an underscore eg. _links. Currently running this example through the renderer results in the first character being capitalised (Pascal case).
_links => Links
We could cater for this either by:
changing the default behaviour to preserve the first character if it's an underscore.
providing a settings option to enable this preserve behaviour.
I'm leaning to number 2 to avoid breaking the current behaviour if people are relying on that. However thinking about it I can't think of a use-case where you would want the Pascal case behaviour. Either way I'm happy to make a contribution, @jozo do you have any thoughts on this?
When building REST APIs that follow the HAL/Hateoas spec it is common for metadata fields that aren't directly attached to the resource to be prefixed with an underscore eg.
_links
. Currently running this example through the renderer results in the first character being capitalised (Pascal case)._links
=>Links
We could cater for this either by:
I'm leaning to number 2 to avoid breaking the current behaviour if people are relying on that. However thinking about it I can't think of a use-case where you would want the Pascal case behaviour. Either way I'm happy to make a contribution, @jozo do you have any thoughts on this?