Repository navigation
feat: Use Vite dev server for Hilla projects by default - #15768
Conversation
5c8367a to
4b6b209
Compare
|
|
||
| return prefix + url; | ||
| } | ||
|
|
There was a problem hiding this comment.
Definitely the wrong class for this
There was a problem hiding this comment.
Found nothing better than EndpointRequestUtil, not maybe a good choice either.
1656b37 to
e594b60
Compare
|
Tested with a starter project having Flow + Hilla, triggers hotdeploy mode by default as expected. Removing all related to Hilla triggers the express build mode by default as expected. |
| // This class belongs to fusion-endpoint and is not available in | ||
| // Flow projects. By checking for its availability, we can show the | ||
| // right project name in the Vaadin devmode gizmo | ||
| Class.forName("dev.hilla.EndpointController", false, |
There was a problem hiding this comment.
Is there any need for more than Class.forName("dev.hilla.EndpointController") if you moved it to the flow-server package?
There was a problem hiding this comment.
Probably not, changed.
|
Tested that it works correctly with start.vaadin.com |
Co-authored-by: Artur <artur@vaadin.com>
…e-hotdeploy-for-hilla
|
Kudos, SonarCloud Quality Gate passed! |
|
This ticket/PR has been released with Vaadin 24.0.0.alpha10 and is also targeting the upcoming stable 24.0.0 version. |








No description provided.