Simple select Rendering fail after filter about grid-renderers-collection-addon HOT 7 CLOSED

That sounds pretty strange. There should not be any specific impact with filtering. That happens in data model level, and renderers are and should be generally unaware of any filtering. Also I found this. It is about the different renderer, but it is about last column, and maybe filtering. So there is probably something common here.

vaadin/framework#10359

from grid-renderers-collection-addon.

I notced somethink else. Consider this senario,

1. I add a new dto to my DataProvider. The Dto has a field "year" with an empty string as initial value .
2. A SimpleSelectRender with values 2017,2018,2019.

On initial display we will have the render showing 2017 and the dto underneath it with value of an empty string. And this is a case were the render is inconsistent to the model.

from grid-renderers-collection-addon.

That is a case which is not supported, i.e. that value set in data source and value set in selection being different. They must be the same. So in order to work in the case you mentioned, you would need to have empty value also added in set you put into SimpleSelectRenderer.

from grid-renderers-collection-addon.

I already did.

from grid-renderers-collection-addon.

I did find major flaw in the SimpleSelectRenderer, which apparently has been there a while. The migration to Vaadin8 was not completed properly.

from grid-renderers-collection-addon.

Version 2.2.2 can be found in library. Thanks for noticing this issue.

from grid-renderers-collection-addon.

thanx for responding so fast!

from grid-renderers-collection-addon.