feat: add headers support to RedirectionException for redirect handling #226
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 #214
Problem
When a GitHub repository is moved/renamed, the GitHub API returns a 3xx redirect response with a
Locationheader pointing to the new repository's API URL. However, theRedirectionExceptionraised by gidgethub doesn't provide access to the response headers, making it impossible for users to programmatically follow redirects.Solution
HTTPExceptionbase class to accept an optionalheadersparameterdecipher_response()function insansio.pyto pass headers to exceptionsMappingimport to support the new headers parameter typeChanges
gidgethub/__init__.py: Addedheadersparameter toHTTPException.__init__()and importedMappingfrom typinggidgethub/sansio.py: Modifieddecipher_response()to pass headers when raising exceptionsUsage
Users can now access redirect information from
RedirectionException:Testing
This enhancement enables proper handling of repository moves/renames in GitHub API clients built with gidgethub.