-
-
Notifications
You must be signed in to change notification settings - Fork 355
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
RequestsMock.add() and .upsert() parameter names are different #734
Comments
That would be great. We can't remove the |
and add deprecation notice + update readme + changelog |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
I'm finally getting a few cycles to work on it |
It's just a little pain point, but
.add()
usesmethod
while.upsert()
usesmethod_or_response
for the HTTP method parameter name. Both can use the same actual values, but the formal names are different.Why is this a problem (at least for me)? I will sometimes send in the inputs by applying
**
to a dict. If the formal parameter names are different, it's a PITA to change the dict keys if I have to swap.add()
vs..upsert()
.If you think it's worthwhile I can create a little PR to change it.
The text was updated successfully, but these errors were encountered: