-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
docs(generator): log file path collision warnings with detailed message #24951
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
Merged
wing328
merged 1 commit into
OpenAPITools:master
from
Mattias-Sehlstedt:log-solution-to-file-path-collision
Sep 17, 2026
+7
−1
Merged
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
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: Using
once()to emit the single primary warning does not reliably produce one warning per run. OnceLogger's cache is JVM-global and expires after 2 seconds (default), so in a generation that runs longer than 2s the primary message is re-emitted whenever a new collision appears, and in a JVM that runs several generators it is suppressed entirely after the first one while every later collision still logs 'see log FILEPATH_COLLISION' pointing at a primary that may not be present. Consider replacingonce()with an instance-level flag so the primary is emitted exactly once per DefaultGenerator run.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.
The
once()call is currently the preferred way of forwarding information to the client in a less noisy way. Having it bound to an instance-level flag comes with its own flaws, and leaves us to reason about whether the Generator should become stateful and to what degreeprocessTemplateToFileis to be invoked.Having it tied to
once()is better currently in my opinion, and an accidental omission ofFILEPATH_COLLISIONin uniquely executed workflows is still a better pointer than nothing.