-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for the Vaadin UI Framework #24794
Comments
This would be best implemented as a JHipster Blueprint. Having it separate from the core should make it easier to maintain. Would you just be using Vaadin for the frontend or for the backend, too? Also, please keep in mind that creating it is the easy part. Maintaining it for years to come is a lot harder. |
@josiahhaswell are you willing to contribute? |
Thats big news to have the Vaadin team on board. Looking forward to the first result. Do you want us to create a repo under the jhipster org or do you want to start elsewhere? |
The first step is to generate a working sample project. |
Hi @atomfrede -- we'd love to have a repo under the JHipster org. I can try to get an initial sample project here shortly. I'm currently traveling so I wouldn't expect much progress on this before February |
This issue is stale because it has been open for too long without any activity. |
Overview of the feature request
As a Vaadin user, it would be nice if JHipster supported the Vaadin UI framework
Motivation for or Use Case
Related issues or PR
I see an old issue related to this request (from 2018)
I'm happy to work on contributing this feature if it seems like there's agreement that it should be implemented.
Vaadin does have commercial features (components, support, etc.)--does that pose a problem? The core framework and many components are completely open-source.
Scope
Before I embark on submitting a PR, are there any comments or considerations I may be missing?
The text was updated successfully, but these errors were encountered: