-
Notifications
You must be signed in to change notification settings - Fork 30
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
Fix#22 #24
Conversation
Can you merge master into this branch? Only changed formatting stuff. Also, don't forget to re-install the pre-commit hook with |
# Conflicts: # routingpy/client_default.py # routingpy/routers/google.py # routingpy/routers/graphhopper.py # routingpy/routers/heremaps.py # routingpy/routers/mapbox_valhalla.py # routingpy/routers/openrouteservice.py # routingpy/routers/osrm.py # routingpy/routers/valhalla.py # tests/test_base.py
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the first shot! Left a few todos, call me if anything unclear.
smth is not quite right with the linting still.. tons of formatting changes in this PR. don't sweat it though, could also be a mismatch of CI and local stuff: your latest commit passed but it shouldn't have. we'll figure that out after we merged this PR, as long as CI is happy. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Almost there;) there's quite a few unrelated changes which didn't make sense. best you go through the diff here on github and revert all those.
Other than that, three more things:
- please go through the docstrings a final time and update them where you changed things (lots of
request_kwargs
still there) - let's remove the
client_kwargs
arg to_request()
entirely. I explained why in the comment. - the tests are still failing, but all with the same error. See if you can get the reason, else we'll look into tmrw morning together.
…g in responses (since it didn't pick up on our bug before the last PR's packages updates)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
found the bug: wasn't your doing. apparently we had a small bug in the tests where it called the wrong URL. and then there was another bug in responses
which caused our bug to not be detected. What's weird there: I updated the dependencies in the last PR (which must've caused that it failed now), but CI went through..
Anyways, I quickly updated that, for me this is good to go. Thanks @chrstnbwnkl
client
argument withClient
as default valueCaveats: