You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request => Please do not submit support request here
Current behavior
When you specify a "deep" property as the prop for a column:
On either the "Expressive: Cars" tab or the "Templated: Cars" tab, try to sort by Formation
See that the sort does not work.
On either the "Expressive: Cars" tab or the "Templated: Cars" tab, try to sort by Color
See the the sort does work
What is the motivation / use case for changing the behavior?
I need to sort on deep properties,
Since its trivial (from the usage standpoint) to display these properties using the prop input, it seems like sorting by them should be supported by the default sort
Please tell us about your environment:
Windows
VSCode
Node
Webpack Dev Server
Table version: 0.7.x
0.9.2
Angular version: 2.0.x
@angular/core@2.0.1
Browser:
Only tried in Chrome
Language:
TypeScript@2.0.3
The text was updated successfully, but these errors were encountered:
I'm submitting a ...
Current behavior
When you specify a "deep" property as the
prop
for a column:or
Sort malfunctions, the entire data set is not sorted.
Expected behavior
All rows are sorted based on the value for the column. This is the behavior for rows that use a "shallow" property
Reproduction of the problem
http://plnkr.co/edit/9Eug63qi775HVCMe3BhO?p=preview
What is the motivation / use case for changing the behavior?
I need to sort on deep properties,
Since its trivial (from the usage standpoint) to display these properties using the
prop
input, it seems like sorting by them should be supported by the default sortPlease tell us about your environment:
Windows
VSCode
Node
Webpack Dev Server
0.9.2
@angular/core@2.0.1
Only tried in Chrome
TypeScript@2.0.3
The text was updated successfully, but these errors were encountered: