-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Fix x-spring-provide-args handling. Pass arguments to delegates. Use JavaParser. #24071
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
Open
wilx
wants to merge
1
commit into
OpenAPITools:master
Choose a base branch
from
wilx:fix-x-spring-provide-args-with-java-parser
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
P2: Duplicated complex leading-comma logic for optional injected args across multiple Mustache template sections
Prompt for AI agents
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.
Well, what do you suggest we do with it? Mustache templates suck by design.
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.
@wilx Yeah, fair enough — Mustache is fundamentally bad at this kind of conditional formatting. The logic-less design means you end up with these
{{#hasParams}}, {{/hasParams}}chains everywhere, and there's no good abstraction mechanism.A few practical options:
1. Pre-format in the Java generator. Instead of splitting
springProvideArgsNamesinto individual items and handling commas in the template, store a pre-joined string (including leading comma) in the vendor extension. The template section becomes a simple insert:{{{vendorExtensions.springProvideArgsCommaJoined}}}That collapses all the
{{#-first}}{{#hasParams}}...noise into one{{{.}}}. The comma logic moves toSpringCodegen.javawhere it's justString.join(", ", names)with proper prefix handling.2. Mustache partials. Extract the repeated leading-comma block into a shared partial, e.g.
>provideArgComma:Then each insertion point becomes:
Not great, but at least the comma logic lives in one file.
3. Template lambdas. The Samskivert Mustache library supports lambdas. You could register a
leadingCommalambda on the context that handles the logic based on preceding sections. But that adds indirection and may be overkill.I'd go with option 1 for this PR — it's the clearest win and keeps the templates simpler. The Java side already has
ProvideArgsParamsset up, so adding a pre-formatted string field there is straightforward. Want me to look at what that'd look like in practice?Tip: get faster answers by chatting with cubic’s review copilot in the review UI