Skip to content
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

MC-34298: Introduce separate POST and PUT API for carts/mine/items #31018

Open
wants to merge 6 commits into
base: 2.5-develop
Choose a base branch
from

Conversation

engcom-Echo
Copy link
Contributor

@engcom-Echo engcom-Echo commented Nov 23, 2020

Description (*)

Related Pull Requests

https://github.com/magento/partners-magento2ee/pull/458
https://github.com/magento/partners-magento2b2b/pull/541

Fixed Issues (if relevant)

  1. Fixes Introduce separate POST and PUT API for carts/mine/items #28162

Manual testing scenarios (*)

  1. See: Introduce separate POST and PUT API for carts/mine/items #28162

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Nov 23, 2020

Hi @engcom-Echo. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@m2-community-project m2-community-project bot added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Nov 23, 2020
@engcom-Echo
Copy link
Contributor Author

@magento run all tests

Copy link
Contributor

@ihor-sviziev ihor-sviziev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @engcom-Echo ,
Your change is definitely backward incompatible in the interface marked with @api tag that is prohibited in minor releases and will create a lot of issues for upgrade.

Could you do following things:

  1. create new interface with your suggested changes
  2. add implements in the repository
  3. mark old interface as @deprecated due to issues listed in the related issue
  4. add to the old interface new tag @see with new interface

@ihor-sviziev
Copy link
Contributor

@magento run all tests

@engcom-Echo
Copy link
Contributor Author

@magento run all tests

@engcom-Echo
Copy link
Contributor Author

@magento run all tests

@engcom-Echo
Copy link
Contributor Author

@magento run WebAPI Tests

@engcom-Echo
Copy link
Contributor Author

@magento run WebAPI Tests

@gabrieldagama
Copy link
Contributor

@magento run all tests

2 similar comments
@engcom-Echo
Copy link
Contributor Author

@magento run all tests

@engcom-Echo
Copy link
Contributor Author

@magento run all tests

@engcom-Echo
Copy link
Contributor Author

@magento run WebAPI Tests

@@ -177,13 +177,13 @@
</resources>
</route>
<route url="/V1/carts/:quoteId/items" method="POST">
<service class="Magento\Quote\Api\CartItemRepositoryInterface" method="save"/>
<service class="Magento\Quote\Api\AddCartItemInterface" method="execute"/>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about Guest carts? I suppose should be same logic there

@@ -29,6 +29,11 @@ public function getList($cartId);
* @throws \Magento\Framework\Exception\NoSuchEntityException The specified cart does not exist.
* @throws \Magento\Framework\Exception\CouldNotSaveException The specified item could not be saved to the cart.
* @throws \Magento\Framework\Exception\InputException The specified item or cart is not valid.
*
* @deprecated Post and put endpoint should be separated
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why its deprecated? It widely used in code (I mean implementation of this method) not only for API

use Magento\Quote\Api\Data\CartItemInterface;

/**
* Interface UpdateCartItemInterface
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please provide meaningful description for interface

use Magento\Quote\Api\Data\CartItemInterface;

/**
* Interface AddCartItemInterface
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please provide meaningful description for interface

@ihor-sviziev
Copy link
Contributor

@engcom-Echo will you be able to update your PR?

@ihor-sviziev ihor-sviziev added this to the 2.5 milestone Feb 19, 2021
@m2-community-project m2-community-project bot added this to Changes Requested in 2.5 Milestone PRs Dashboard Feb 19, 2021
@m2-community-project m2-community-project bot removed this from Changes Requested in High Priority Pull Requests Dashboard Feb 19, 2021
@zakdma zakdma removed their assignment May 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Award: advanced Award: bug fix Component: Quote Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: needs update Release Line: 2.5 Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

Introduce separate POST and PUT API for carts/mine/items
5 participants