I have an older JSON-API backend which for compatiblity reasons cannot change that has everything in kebab-case, including attribute names. This was the norm pre https://github.com/json-api/json-api/issues/1255. Keeping those around in JavaScript or TypeScript access is no fun and I think the most desireable usage pattern is that they are converted to camelCase and vice-versa on (de)serialization.
Would it be acceptable to add an option to do this on deattribute, serialiseAttr and bubble up that option? This would be in line with the current option for resource type names.
I would be open to work on this, however I'm hesisant because of TypeScript rewrite?
I have an older JSON-API backend which for compatiblity reasons cannot change that has everything in kebab-case, including attribute names. This was the norm pre https://github.com/json-api/json-api/issues/1255. Keeping those around in JavaScript or TypeScript access is no fun and I think the most desireable usage pattern is that they are converted to camelCase and vice-versa on (de)serialization.
Would it be acceptable to add an option to do this on deattribute, serialiseAttr and bubble up that option? This would be in line with the current option for resource type names.
I would be open to work on this, however I'm hesisant because of TypeScript rewrite?