v6: Nested object properties #477
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.
This PR extends data type support to include
objectandobject[]properties.The following is possible:
objectis allowed to be a Map or a customrecord(leveraging our ORM) and and the containerobject[]can be represented either a List or an Array.Where
AddressandApartmentare records defined according to the existing "ORM"-rules (e.g.@Propertyannotation sets custom names for properties, etc). 📍📍 Limitation: At the moment nested properties aren't supported in the higher-level ORM objects, e.g. it's not possible to do:
This should be trivial to implement, but is probably not needed for GA.