-
Notifications
You must be signed in to change notification settings - Fork 113
Add support for hot deployment of OpenAPI files in development mode #1106
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
Add support for hot deployment of OpenAPI files in development mode #1106
Conversation
|
Hi @omatheusmesmo thank you for this great contribution. Could you add test for this code? |
Hi @mcruzdev ! It's done. =D |
mcruzdev
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot @omatheusmesmo, I tested here and it is great!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry @omatheusmesmo I have tested an scenario:
- When the user adds the following
quarkus.openapi-generator.moqu.resource-dir=openapiproperty (not in resources dir) the hot reload does not work.
The Quarkus Roq extension does something similar (watching directory from project root dir).
There's no need to apologize. I'm working on fixing this—thanks for the reference! |
moqu/deployment/src/main/java/io/quarkiverse/openapi/generator/MoquProjectProcessor.java
Outdated
Show resolved
Hide resolved
moqu/deployment/src/test/java/io/quarkiverse/openapi/generator/MoquProjectProcessorTest.java
Outdated
Show resolved
Hide resolved
mcruzdev
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@omatheusmesmo for now I think we can guarantee that when I change just the file content the live reload will work as expected. We can solve the live reload dir changes in another pull request, what do you think?
c3b7c79 to
4277a9c
Compare
Sounds good to me, I can also open a new issue about this bug. |
|
Thanks a lot for this pull request @omatheusmesmo! ould you set for review and squash all commits? So we can merge this! |
|
Sorry, IDNK why this was closed |
28eaa3c to
699d955
Compare
Done! 😄 |
mcruzdev
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great!
|
@ricardozanini @hbelmiro we need to add EDIT: We already have. |
|
@all-contributors please add @omatheusmesmo for code |
|
I've put up a pull request to add @omatheusmesmo! 🎉 |
Many thanks for submitting your Pull Request ❤️!
Please make sure that your PR meets the following requirements:
[0.9.x] SubjectFixes #1071
How to backport a pull request to a different branch?
In order to automatically create a backporting pull request please add one or more labels having the following format
backport-<branch-name>, where<branch-name>is the name of the branch where the pull request must be backported to (e.g.,backport-quarkus2to backport the original PR to thequarkus2branch).Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.