If you select a row, then filter it out, the row remains selected. Not sure if this is actually a bug, but it does not seem to be intuitive default behaviour.
For example, you select a number of rows, then set a field which causes them to be filtered. Then, later you select some other rows, and delete them. This will also delete the non visible rows.
This has the added effect of making getSelectedRows() unusable when using filtering, instead you must use getSelectedGridRows(), and filter out the visible rows, then map to a list of entities.
In my current project I have added a row processor to remove selections when rows become non-visible. I suggest this should be default behaviour, or have some additional documentation.
If you select a row, then filter it out, the row remains selected. Not sure if this is actually a bug, but it does not seem to be intuitive default behaviour.
For example, you select a number of rows, then set a field which causes them to be filtered. Then, later you select some other rows, and delete them. This will also delete the non visible rows.
This has the added effect of making getSelectedRows() unusable when using filtering, instead you must use getSelectedGridRows(), and filter out the visible rows, then map to a list of entities.
In my current project I have added a row processor to remove selections when rows become non-visible. I suggest this should be default behaviour, or have some additional documentation.