-
Notifications
You must be signed in to change notification settings - Fork 388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: optionally pass request to before_record_response #556
Comments
My use case for this is: One of the endpoints I work with returns a list of data in arbitrary order - I'd like to sort that in |
+1 This would be really useful. There are some requests it would be handy to filter the responses of (based on the URI) but because this is inaccessible in the response, we can't do anything In principle I'd be happy to look at implementing it if the feature would be accepted |
There's related discussion in #527 about working around not having access to |
Closes kevin1024#556 kevin1024#527 Co-authored-by: Edward Delaporte (@edthedev) Co-authored-by: David Riddle (@ddriddle) Co-authored-by: Michelle Pitcel (@mpitcel) Co-authored-by: Zach Carrington (@zdc)
Closes kevin1024#556 kevin1024#527 Co-authored-by: Edward Delaporte (@edthedev) Co-authored-by: David Riddle (@ddriddle) Co-authored-by: Michelle Pitcel (@mpitcel) Co-authored-by: Zach Carrington (@zdc217)
Closes kevin1024#556 kevin1024#527 Co-authored-by: Edward Delaporte (@edthedev) Co-authored-by: David Riddle (@ddriddle) Co-authored-by: Michelle Pitcel (@mpitcel) Co-authored-by: Zach Carrington (@zdc217)
It would sometimes be useful to know which endpoint we're working with during
before_record_response
- but I think that's not currently possible.What do you think to allowing
before_record_response
to have an optionalrequest
argument, and passing the request dict if it's present?The text was updated successfully, but these errors were encountered: