-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Auto-detection for Hilla's endpoints #18800
Labels
Comments
Can we also prevent running |
Yeah, it would be reasonable to skip it. Let's also check if skipping it has any side effects. |
This was referenced Nov 27, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Describe your motivation
Vaadin Flow adds endpoints generation Node Tasks (see
NodeTasks::addEndpointServicesTasks
) if Hilla's views are present and base Hilla class is in class path.This, however, doesn't take into account a presence of endpoint classes marked by
AtEndpoint
orAtBrowserCallable
, which leads to wrong detection and not generating the endpoints in the end.Describe the solution you'd like
Vaadin Flow can check:
frontend/generated/openapi.json
file (if this file exists at the point where we need to take a decision in Flow about starting the generator), specifically the "tags" json array.AtEndpoint
orAtBrowserCallable
annotations in the project.Additional context
Vaadin 24.4.
The text was updated successfully, but these errors were encountered: