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.
Fixes #5799
References to other Issues or PRs
Have you read the Contributing Guidelines?
Yes
Brief description of what is fixed or changed
Prevents unnecessary package prefixes in OpenAPI definition names when using
packageorsimplenaming strategies.Problem: The generator was adding package prefixes (e.g.,
foo.Foo) even when no actual naming collision existed in the generated spec. This happened because collision detection used ALL messages from the registry, including unreferenced imports.Solution: Filter the name set before collision detection to only include:
google.*packagesThis ensures only real collisions trigger prefixes while maintaining backward compatibility.
Example:
Before:
"definitions": { "foo.Foo": {...} }After:
"definitions": { "Foo": {...} }Other comments