[WIP] Add config option to globally format JSONAPI type. #1122
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a response to #974. The idea is that client-side libraries have different conventions on the format of the
type
attribute, which this PR offers to set globally as a lambda.I'm interested in opinions on the best way to offer a good experience with this. A few leads:
pluralize_dasherize
,singularize_camelize
, etc)[ :pluralize, :underscore, -> (x) { ... } ]
This is also related to #1029 (although the solution here is to globally handle the formatting, where #1029 offers to set it at the serializer level).