Unset used but not imported for required multi-body endpoints - #1478
Open
rolandgeider wants to merge 1 commit into
Open
Unset used but not imported for required multi-body endpoints#1478rolandgeider wants to merge 1 commit into
rolandgeider wants to merge 1 commit into
Conversation
rolandgeider
force-pushed
the
fix/unset-required-endpoints
branch
from
August 11, 2026 16:06
a00efe8 to
95e15ff
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #1451
We ran into this while generating a client from our spec. The multi-body branch of the
argumentsmacro readbody_requiredbefore it was ever assigned, so| Unset = UNSETwas appended to thebodyannotation even for a required request body.