-
Notifications
You must be signed in to change notification settings - Fork 1
Replaced: /orders -> /shipments #2
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
base: master
Are you sure you want to change the base?
Conversation
a69028e to
fae2874
Compare
| }, | ||
| "units": [ | ||
| { | ||
| "shippable": { |
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.
What's the reason for this shippable array?
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.
This is actually product variant. But from shipments POV it called shippable
We need it (or at least link to product variant endpoint) just to know what exactly unit we have.
| { | ||
| "shippable": { | ||
| "id": @integer@, | ||
| "code": "red-mug", |
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.
This has the same code as the previous. We would have to ask Peter from lagersystem.dk if that is desirable
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.
We can put id/code and link to product variant endpoint rather than inject all info to shippable field.
No description provided.