FEATURE: Allow access to properties that are deeper down the object tree #81
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.
The current implementation only allows the user to access a row's first-level properties.
For example, if you have some underlying objects that look like this
and you want to display the street on the table, you will first have to map them to something like this
before you can assign this to
ngTable
'srows
input. It's becauserows[0]['address.number']
will returnundefined
.I propose we allow users to access properties that are deeper than the first-level properties.
For example, to display the street name, one can simply set the
column.name
to'address.street'
. This notation will work for array too. For example, to show the first phone number, just setcolumn.name
to'phones.0.number'
.