Provide more variants of getColumn

[amahdy]

• Vaadin version: 8.1.x

• Description of the bug: (Feature Request)
  Provide better API to retrieve already generated columns.

• If possible, minimal reproducible example:
  Sometimes I use the Grid initializer API that generates all the columns:
  Grid<Bean> grid = new Grid<>(Bean.class);
  But at this point, I'm unable to retrieve and modify those columns. The only available getColumn API takes columnId as a parameter.
  Alternatively, I have to manually create all the columns manually. I want a combination of both features.

Thanks!

[tsuoanttila]

When you use the Grid constructor with bean class, the columns are initialised with id being the property name. So Person with a String fullName and related getter and setter will produce a Grid containing a column with id fullName. grid.getColumn("fullName") will return the generated column.

What variants would you need in addition to that for your feature request to be considered done?

[amahdy]

I don't know if that was documented somewhere, buy still I feel that it's not intuitive enough.
So I'd request:

• Update the API documentation.
• Add one more API that accepts let say Bean::getFirstName.

[tsuoanttila]

The Bean::getFirstName in this particular case is shortened from:

new ValueProvider<Bean, String>() { 
    public String apply(Bean bean) { 
        return bean.getFirstName(); 
    } 
}

Which is a new instance that can't be reliably matched to another instance of ValueProvider. It's a nice idea and if it worked, it would be there already.

For the documentation on the topic, please take a look at Grid - Automatically Adding Columns

[amahdy]

I still believe it's a nice to have feature. One of the major updates in the new Grid was not to rely on any String constants. Guessing and using the member variable of the Bean as a String is not nice.

For documentation, I meant JavaDoc for the method, especially the getColumn(). Right now it gives no clue how to find the identifier called columnId.

[stale]

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!

[amahdy]

Still a valid issue.

[stale]

Hello there!

We are sorry that this issue hasn't progressed lately. We are prioritizing issues by severity and the number of customers we expect are experiencing this and haven't gotten around to fix this issue yet.

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!

[amahdy]

Still an issue.