-
Notifications
You must be signed in to change notification settings - Fork 0
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
Implement Waybiller client #1
base: master
Are you sure you want to change the base?
Conversation
Live waybiller does not validate some of the data that waybiller responds with.
506bacc
to
210803d
Compare
Makes mypy happier
8a0eaf5
to
e893009
Compare
Currently, it uses the staging server to generate schema Potentially it might cause issues if staging has a different schema from live, is it a problem? Probably not a problem that we reveal the staging server to public |
Could you please explain the pipeline, don't have much experience with packages Let's say WB adds a new endpoint to add comments to waybills Then we would need to regenerate the client, and release it with a newer version, right? And then use that version in the projects where this package is used |
Pretty much what you wrote. Once Waybiller schema changes, things may break, usually in couple of ways:
|
e893009
to
ded38ca
Compare
Add manual test command to test against waybiller data dump. Run manual test for waybills (list and detail) and fix any issues that cause real data from waybiller to not validate with the schema.
Waybiller schema has origin_id mistakenly using optional int, while in reality it is a mapped id which is optional string
Inspired by pyEVR package with similar purpose, extracted from some of the projects where we already used this.