Repository navigation
feat: Call copilot init feature when starting from an empty app - #18749
Conversation
c3bb19f to
3b61c2b
Compare
|
mcollovati
left a comment
There was a problem hiding this comment.
I tested both Flow and Hilla view generation and got source code generated, but I noticed the following (perhaps expected?):
- starting application from the IDEA, after creating Flow view, the server is restarted, browser page is reloaded, and I can see the new view
- starting application from the IDEA, after creating Hilla view the server is not restarted, the browser page reloads, but still
NoRoutesError_dev.htmlis shown. After manual restart, I can see the view. - starting application with
mvnfrom terminal, server is not restarted neither for Flow nor for Hilla view. After manual restart, I can see the view
Sounds like this is working as it should
There might be several cases here and I am not sure which one you had or what project you started from:
This also depends on the case. If you don't have any IDE running, then nothing will compile the files and no restart will take place. |
|
I created a test project with |
|
Starting with an application without a theme and creating a Hilla view works, but it took three restarts. |
|
Indeed, it is not optimal but a start |
|
It would be nice to improve |
|
Yes, but I think those changes should go on the copilot side. Similarly to how it adds a message if you don't have spring boot dev tools in the project |



No description provided.