Add prefix to distinguish multiple auth variants of builders #265
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.
Following the previous change, code may now be generated for endpoints with multiple authentication types. If an endpoint with multiple authentication types generates a
Builder, this causes a naming collision and compilation error as we attempt to generate multiple builders with the same nameThis change uses the existing prefix that was already applied to the
Requestsclasses toBuilders to avoid this issueIt is a breaking change for existing consumers though the effect is minimal as it only affects places where the calling code makes explicit reference to the builder's type