Vaadin 8.0.6 Grid missing addRow

[nickza]

Vaadin 8.0.6 Grid missing addRow, in version 7 there was a way to addrow. Could this come back ?

[Legioth]

addRow in Vaadin Framework 7 was based on the old Container API where each row was an Item that consisted of a set or Property instances.

With the new data API in Vaadin Framework 8, the corresponding functionality would instead be in the form of addItem(T item) that would take one single object that represents the entire row.

[hesara]

One issue with adding a generic addItem() is that not all data providers are modifiable. In fact, unlike the old Container API that tried to handle modifications often in a suboptimal way, the DataProvider API itself does not attempt to directly support such modifications nor notifying the component about modifications.

Simple in-memory data providers (ListDataProvider) could support such operations, but having the API on Grid might mislead users to believe that it always works.

[jomach]

I have the sample Problem. My Example: I have a grid that needs to be build on the fly. I cannot have a type on it. then I need to build the grid based on database response. The addItem does not appear on my Vaadin 8.0... The only thing related is addItemClickListener....

[hesara]

You should probably use/write a DataProvider that supports such an operation - that is much simpler with Vaadin 8 than writing a Vaadin 7 Container. You can also use a more generic type such as e.g. Map as the type of the rows of the Grid to be able to have an arbitrary set of values, though you'd also want to configure the columns so that the values are shown in a sensible way.

The method adding data to the data provider may need to call AbstractDataProvider.refreshAll().

[jomach]

@hesara I was thinking about this and I found Out I can achieve the same just by extending the TextRenderer.

[stale[bot]]

Hello there!

It looks like this issue hasn't progressed lately. There are so many issues that we just can't deal them all within a reasonable timeframe.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

• Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
• Provide more details how to reproduce the issue.
• Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
• Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
• Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
• If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!