-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[API] shipping shipment with tracking code + minor fixes #11231
Conversation
AdamKasp
commented
Mar 16, 2020
Q | A |
---|---|
Branch? | api |
Bug fix? | no |
New feature? | yes |
BC breaks? | no |
Deprecations? | no |
License | MIT |
Thanks, Adam! 🎉 |
Scenario: Shipping a shipment with tracking code from shipments index | ||
When I browse shipments | ||
And I ship the shipment of order "#00000001" with "AWDDXS-SAAQQ-SEFFX-CCDSE" tracking code | ||
Then I should be notified that the shipment has been successfully shipped | ||
And an email with the shipment's confirmation of the order "#00000001" should be sent to "donald@duck.com" | ||
|
||
@ui @api @email |
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.
Why have you deleted this tag?
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.
in this PR I fixed comment from #11230, here I added by mistake @email
tag so now i have removed it (this scenario does not have any email-related steps)
@@ -32,8 +32,6 @@ | |||
<itemOperation name="get" /> | |||
</itemOperations> | |||
|
|||
<collectionOperations /> |
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.
Why have you removed this?
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.
Because we have it inline 29 - i fixed mistake after merge :( (btw i will move it above itemOperations
i next PR :) )
Part of #11250 |