-
Notifications
You must be signed in to change notification settings - Fork 113
Support GAV coordinates for client generation #1340 #1343
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
Conversation
|
@ricardozanini have a look at it. of couse i will add docu for it if its is ok in your opinion. |
.../quarkiverse/openapi/generator/deployment/codegen/GAVCoordinateOpenApiSpecInputProvider.java
Outdated
Show resolved
Hide resolved
.../quarkiverse/openapi/generator/deployment/codegen/GAVCoordinateOpenApiSpecInputProvider.java
Outdated
Show resolved
Hide resolved
...se/openapi/generator/deployment/codegen/YamlOrJsonGAVCoordinateOpenApiSpecInputProvider.java
Show resolved
Hide resolved
|
Can you also please take a look on the CI? |
…& tests simplicity & add config options to GlobalCodegenConfig
…spec mapping to ensure that config key is right
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
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 work! Do you need a minor release?
thank you 😃 should i raise another feature req. for addjng the JarGavCoordinateReader? i dont want to add it to this one. maybe i have some time in the next weeks... |
Please do! You can open an issue and implement it once you have the time ;) |
|
@ricardozanini when do you plan releasing it? |
Once we have a meaningful pack of PRs merged. I think we can release one patch version this week. |
* Support GAV coordinates for client generation #1340 * Support GAV coordinates for client generation #1340 * avoid star imports * SUPPORTED_EXTENSIONS refactored for better use * add filter for artifactIds & improved config naming(singular/plural) & tests simplicity & add config options to GlobalCodegenConfig * windows problem with colon in filename & extended test with specific spec mapping to ensure that config key is right * use verify phase to store artifacts to local mvn repo to get website / codeql action green * renaming and javadoc * use package phase for artifact installation to get codeql action running --------- Co-authored-by: Michael Sonnleitner <[email protected]>
* Support GAV coordinates for client generation #1340 (#1343) * Support GAV coordinates for client generation #1340 * Support GAV coordinates for client generation #1340 * avoid star imports * SUPPORTED_EXTENSIONS refactored for better use * add filter for artifactIds & improved config naming(singular/plural) & tests simplicity & add config options to GlobalCodegenConfig * windows problem with colon in filename & extended test with specific spec mapping to ensure that config key is right * use verify phase to store artifacts to local mvn repo to get website / codeql action green * renaming and javadoc * use package phase for artifact installation to get codeql action running --------- Co-authored-by: Michael Sonnleitner <[email protected]> * Apply suggestion from @ricardozanini * Apply suggestion from @ricardozanini --------- Co-authored-by: Michael Sonnleitner <[email protected]> Co-authored-by: Michael Sonnleitner <[email protected]> Co-authored-by: Ricardo Zanini <[email protected]>
adds feature #1340
Many thanks for submitting your Pull Request ❤️!
Please make sure that your PR meets the following requirements:
[0.9.x] SubjectHow 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.