Draft: #as_json should be API-ready #238
Closed
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.
Work In Progress - Not Ready for Merge
#as_json should return objects for API serialization, and be different than #as_extended JSON.
The general rules for
#as_json
are (in order of precedence):Map directly to a native JSON type if it is possible to do so. Examples:
Where ActiveSupport defines
#as_json
behavior for a Ruby object, follow the same. Examples:"(?-mix:dsfsd|dsf)"
"1234"
For the remaining types not mentioned above, we need to decide whether we go with:
(a) alias to
#as_extended_json
(b) compound object (Hash)
(c) compacted (lossy) single value representation
type
scope
ref
(collection)"$maxKey"
"$minKey"