quarkus-quinoa - infinite loop with openapi generation #45541
Unanswered
akil-rails
asked this question in
Q&A
Replies: 4 comments 1 reply
-
/cc @EricWittmann (openapi), @MikeEdgar (openapi), @phillip-kruger (openapi) |
Beta Was this translation helpful? Give feedback.
0 replies
-
@ia3andy ^^^ |
Beta Was this translation helpful? Give feedback.
0 replies
-
I would recommend creating an issue in the Quinoa project with a reproducer: https://github.com/quarkiverse/quarkus-quinoa/issues |
Beta Was this translation helpful? Give feedback.
0 replies
-
@akil-rails I'm having the same issue. Did you manage to find a solution or open a GitHub issue I might have missed? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
If i follow the guide - quarkus.live-reload.exclude-paths, the openapi gets generated in the webui folder, and that triggers reload of the UI (expected) but also the quarkus app (unexpected), and which then again creates the openapi file, and its an infinite loop
Why do changes in the webui folder result in a start of the quarkus app ? Is this the expected behavior?
Also, in case it is relevant, i have an OpenApiFilter as described here ..
Beta Was this translation helpful? Give feedback.
All reactions