Preserve values from being formatted #420
Merged
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.
Fixes #313
Description of the Change
According to Json API Spec should only field names (hence the name
JSON_API_FORMAT_FIELD_NAMES
) be specifically named resp. formatted. The value itself may contain any json value though and we should keep it as is.With the option
JSON_API_FORMAT_KEYS
all keys (incl. value keys) are formatted though. This leads to underscored keys of a attribute value in Django code (or even on the database when using JSONField)To fix this I have introduced
JSON_API_FIELD_NAMES
setting which preserves value from being formatted.JSON_API_FORMAT_KEYS
still works as before though for backwards compatibility but is marked deprecated.Checklist
CHANGELOG.md
AUTHORS