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
This is a bug report, not a question on how to use the grid.
Use Stack Overflow or Gitter for questions.
You have searched the open issues to see if this bug has been filed before. We don't want duplicate issues.
You have reviewed the tutorials and documentation to ensure you are using the grid correctly. ui-grid.info
You are using the latest version of the grid. Older versions are not patched or supported.
You have provided steps to recreate your bug. A plunkr is even better.
When using the grid with an array of primitives (as in the top example here: http://ui-grid.info/docs/#!/tutorial/323_more_binding) getSelectedRows no functions correctly returning no rows.
This can be seen in the following demonstration plunk: https://plnkr.co/edit/peULRxkeZy0QtYbE5rga?p=info where the selected items list is empty when any of the string items are selected, though works fine for the non-primitives.
The breaking change appears to be here: 0e83225 as primitive types such as strings cannot have properties such as $$hashkey and will not retain them if they are set.
The text was updated successfully, but these errors were encountered:
StrangelyTyped
changed the title
getSelectedRows broken when using ENTITY_BINDING with primitive options
getSelectedRows broken when using ENTITY_BINDING with primitive entities
Apr 26, 2018
Use Stack Overflow or Gitter for questions.
When using the grid with an array of primitives (as in the top example here: http://ui-grid.info/docs/#!/tutorial/323_more_binding) getSelectedRows no functions correctly returning no rows.
This can be seen in the following demonstration plunk: https://plnkr.co/edit/peULRxkeZy0QtYbE5rga?p=info where the selected items list is empty when any of the string items are selected, though works fine for the non-primitives.
The breaking change appears to be here: 0e83225 as primitive types such as strings cannot have properties such as $$hashkey and will not retain them if they are set.
The text was updated successfully, but these errors were encountered: