feat: support context unwrapping #736
Merged
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.
This PR is an alternative to #699 which enables unwrapping a
huma.Contextback into its router-specific request/response object or router-specific context, effectively escaping Huma and giving back full control to the user. It's generally recommended to not do this, but there are legitimate use-cases where this could be handy to have as an option. Example:This implementation does not modify any interfaces in Huma itself, nor does it require manually casting
anyor things like that. Each adapter simply provides a convenienceUnwrap()function that returns the underlying data.This should also make it fairly simple to switch routers as you can find/replace the router-specific package (e.g.
humachi→humago) and things will just work or provide a compile-time error if the return types changed, making it easy to fix, instead of waiting for a runtime error.