You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A fairly common abstraction I've encountered is something that needs both a Request and the request's path or host. The way things currently stand now with the opaque Request type there is no way to nicely implement these kinds of abstractions. You have to pass both the Request and the path, but that is more error prone since the Request contains the path. Exposing more (all?) of the Request internals would admit the nice solution in these cases.
The text was updated successfully, but these errors were encountered:
It's high time this got some love. I'll look into it this week. The trouble I have with all of this class of request is that the whole point of hiding internals is so that special (required) things can be done correctly. If there are use cases we're not supporting well (and there are) then we really need to rethink the API as a whole.
A fairly common abstraction I've encountered is something that needs both a Request and the request's path or host. The way things currently stand now with the opaque Request type there is no way to nicely implement these kinds of abstractions. You have to pass both the Request and the path, but that is more error prone since the Request contains the path. Exposing more (all?) of the Request internals would admit the nice solution in these cases.
The text was updated successfully, but these errors were encountered: