swagger-api / swagger-api/swagger-codegen-generators
Question: how to extend CodegenConstants for a codegen change in this repo
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 299
- Forks
- 439
- PR merge metrics
- No merged PRs in 30d
Description
I'd like to make a PR change in this repo which will mirror the existing PR change that I've already made that targets the v2 master branch of swagger-codegen.
As part of this new v3 change I need to make a change to CodegenConstants and it looks like CodegenConstants is imported and compiled into the code in this repo at build time.
I see (at the time of writing), that https://oss.sonatype.org/content/repositories/snapshots/io/swagger/codegen/v3/swagger-codegen/3.0.25-SNAPSHOT/swagger-codegen-3.0.25-20210207.055740-17.jar is downloaded at mvn clean package build time and I imagine that this .jar is https://github.com/swagger-api/swagger-codegen/tree/3.0.0 tagged and built code.
What is the process for getting new CodegenConstants values into swagger-codegen 3.0.0 which will then enable me to make a change in this repo that depends on the newly introduced CodegenConstants values ?
Is the process that I first need to make a PR over in swagger-codegen 3.0.0 which will eventually be merged in and then subsequently will make its way into a oss.sonatype.org v3 swagger-codegen built snapshot in the future?
Thanks for any help, Joe
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running mvn clean package and inspect how the build obtains the snapshot JAR containing CodegenConstants; the issue names no source file or test. Confirm the required upstream swagger-codegen 3.0.0 change and snapshot or release handoff, then document the steps needed before this repository can consume the new values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100