Skip to content

Conversation

@timgrohmann
Copy link

Fixes #22267

Tagging the committee as stated in the checklist: @TiFu @akehir @petejohansonxo @amakhrov @davidgamero @mkusaka @joscha

Change Description

Externalise the query parameter assignment into a separate mustache script and call it in the original place as well as while setting a exploded: true, non-container param.

PR checklist

  • Read the contribution guidelines.
  • Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
  • Run the following to build the project and update samples:
    ./mvnw clean package || exit
    ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
    ./bin/utils/export_docs_generators.sh || exit
    
    (For Windows users, please run the script in WSL)
    Commit all changed files.
    This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
    These must match the expectations made by your contribution.
    You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
    IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
  • File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
  • If your PR solves a reported issue, reference it using GitHub's linking syntax (e.g., having "fixes #123" present in the PR description)
  • If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

@wing328
Copy link
Member

wing328 commented Nov 3, 2025

Thanks for the PR but your commit (as shown in the Commits tab) is not linked to your Github account, which means this PR won't count as your contribution in https://github.com/OpenAPITools/openapi-generator/graphs/contributors.

Let me know if you need help fixing it.

Ref: https://github.com/OpenAPITools/openapi-generator/wiki/FAQ#how-can-i-update-commits-that-are-not-linked-to-my-github-account

@wing328
Copy link
Member

wing328 commented Nov 3, 2025

@timgrohmann timgrohmann force-pushed the fix/22267-date-formatting-request-parameter branch from e492c1f to f00dc1b Compare November 3, 2025 08:35
@timgrohmann timgrohmann force-pushed the fix/22267-date-formatting-request-parameter branch from f00dc1b to 5f0a518 Compare November 3, 2025 08:58
@timgrohmann
Copy link
Author

Thanks for the advice @wing328, I adjusted the whitespace in the templates so the samples do not change. Also I tried correctly setting the commit author, lmk if that worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] [typescript-fetch] Regression While Exploding Non-Primitive Types in Request Parameters

2 participants