New design file should provide a name field for the Java companion file

[stefanuebe]

Currently, when creating a new design file with a companion file, I can only edit the Java source folder and package, but not the companion file name. That file is generated based on the component's tag name.

That might make sense for most cases, but there might be companies or projects, where special name conventions have to be taken into account. With the current dialog, the user has to manually go to the companion file after creating the design file and rename it. That is cumbersome.

It would be user friendly, when there would be a separate Java file name field. The field should auto update, when the web component's name change to match it (respecting Java naming conventions, but that is already the case, so shouldn't be a problem).

Alternative solution to the autoupdate: A checkbox, that allows editing the Java file name. If checked, the Java file name becomes editable and does not update any more when the component's name change.

IDE, Designer and OS version

IntelliJ 2020.1, Designer 4.5.0, Windows 10

[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 few 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 many duplicates in our issue tracker, so it is possible that the issue is already tackled.
• 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.
• 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!