Adds support for nested models and array elements in DisplayLookup #140
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 #86.
I found a simple way to implement a deep lookup in the object via a path without adding additional dependencies.
The syntax looks like this:
fieldName
for a plain (not-nested) lookup.arrayField.0
for looking up the 1st element of the array stored inarrayField
. Can take.x
for looking up thex
-th element.nested.attribute_1
for looking up the (nested) fieldattribute_1
in the top-level attributenested
.nested.arrayField.1.attribute_1
Also, added an example to the demo page for the Users table.