Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
The pull request must only fix one issue, or add one feature, at the time.
The pull request must update the test suite to demonstrate the changed functionality.
After you create the pull request, all status checks must be pass before a maintainer reviews your contribution. For more details, please see CONTRIBUTING.
Building our own local image and using that over the global one. We likely will also do that, however, I felt contributing the change back upstream may be beneficial, at least to consider that at least 8 months of changes have been released.
Possible Drawbacks
It appears the resulting output files are building with 6.0.0-SNAPSHOT over 5.0.1-SNAPSHOT of current release, which introduces a lot of changes to resulting files.
Verification Process
Docker build successfully completes
Local code generates, and, us using the stringEnum flag correctly in output code
The code hasn't introduced regressions in my code paths, however, I do understand that I am not building for every language
Additional Notes
It appears the resulting output files are building with 6.0.0-SNAPSHOT over 5.0.1-SNAPSHOT of current release
Release Notes
Review checklist (to be filled by reviewers)
[ ] Feature or bug fix MUST have appropriate tests (unit, integration, etc...)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have one changelog/ label attached. If applicable it should have the backward-incompatible label attached.
[ ] PR should not have do-not-merge/ label attached.
[ ] If Applicable, issue must have kind/ and severity/ labels attached at least.
Requirements for Contributing to this repository
What does this PR do?
Updating image for access to stringEnum in typescript-fetch output (https://github.com/OpenAPITools/openapi-generator/pull/11976) as it would fix a lot of our usage issues
Description of the Change
Updated the dockerfile to pull a recent version of openapi-generator-cli to allow usage of a new flag. In order to do this I pointed the dockerfile to the newer dockerhub repo of https://hub.docker.com/layers/openapitools/openapi-generator-cli using the latest sha as of today which was https://hub.docker.com/layers/openapitools/openapi-generator-cli/latest/images/sha256-bda9ca9b2d4ad50a41e1b2cdfbb84d7c21ce0e4d9e9b0061718315d9a7321443?context=explore
Alternate Designs
Building our own local image and using that over the global one. We likely will also do that, however, I felt contributing the change back upstream may be beneficial, at least to consider that at least 8 months of changes have been released.
Possible Drawbacks
It appears the resulting output files are building with 6.0.0-SNAPSHOT over 5.0.1-SNAPSHOT of current release, which introduces a lot of changes to resulting files.
Verification Process
stringEnumflag correctly in output codeAdditional Notes
It appears the resulting output files are building with 6.0.0-SNAPSHOT over 5.0.1-SNAPSHOT of current release
Release Notes
Review checklist (to be filled by reviewers)
changelog/label attached. If applicable it should have thebackward-incompatiblelabel attached.do-not-merge/label attached.kind/andseverity/labels attached at least.