Skip to content

[Reorder] #30686 - Allow developers to filter order items for reorder #30687

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

Closed

Conversation

PierreLeMaguer
Copy link
Contributor

@PierreLeMaguer PierreLeMaguer commented Oct 28, 2020

Description (*)

The new reorder feature is hard to customize for developers.
The idea here is to allow developers to filter order items to reorder thanks to a plugin on the new method app/code/Magento/Sales/Helper/Reorder.php::canReorderItem .

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes [Reorder feature] Feature very hard to customize #30686

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 Oct 28, 2020

Hi @PierreLeMaguer. 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

@BarnyShergold
Copy link

@magento run all tests

@BarnyShergold
Copy link

@PierreLeMaguer - It would be useful, as this may not be your only PR in this code area, to add a small description of the change made and how you envisage developers utilising the change - I'm assuming you'd expect them to create a plugin on your new method and manipulate the return? Good for searching at a later date

@BarnyShergold BarnyShergold self-requested a review October 28, 2020 16:22
@BarnyShergold BarnyShergold self-assigned this Oct 28, 2020
@PierreLeMaguer
Copy link
Contributor Author

hello @BarnyShergold , thanks for the review. I add a small description to the PR area.

Copy link

@BarnyShergold BarnyShergold left a comment

Choose a reason for hiding this comment

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

The Reorder.php is causing a fail on two B2B static tests. Not sure why but this is for existing code. Will need to be addressed.

Once functional tests have completed check for errors.

*
* @SuppressWarnings(PHPMD.UnusedFormalParameter)
*/
public function canReorderItem($item, $product)
Copy link

@BarnyShergold BarnyShergold Oct 28, 2020

Choose a reason for hiding this comment

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

Missing return type on prototype

Suggested change
public function canReorderItem($item, $product)
public function canReorderItem($item, $product): bool

@PierreLeMaguer
Copy link
Contributor Author

@mbvb1223
Copy link

mbvb1223 commented Oct 29, 2020

Hello @BarnyShergold ,

I pushed a new commit to fix static tests.

I checked the functional tests : no error here https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/30687/33fbb0a2d1da4801a0d5971f86715e31/Functional/allure-report-ee/index.html#behaviors but one error here https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/30687/c3bb69a2652167d4e479a67f5eaee4cf/Functional/allure-report-ce/index.html on the test Magento\FunctionalTestingFramework.functional\MediaGalleryUiSuite ... Not sure that it's linked to my PR.

It seems the same my PR (#30660).
I also got an error
Magento\FunctionalTestingFramework.functional\MediaGalleryUiSuite
https://studio.cucumber.io/projects/131313/test-plan/folders/1320712/scenarios/4951848: Used in pages link

@PierreLeMaguer
Copy link
Contributor Author

@magento run all tests

@BarnyShergold
Copy link

@magento run Functional Tests CE

@sidolov sidolov added Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”. labels Oct 29, 2020
@BarnyShergold
Copy link

@magento run Functional Tests B2B

@BarnyShergold
Copy link

@magento run Integration Tests

@BarnyShergold
Copy link

@magento run Functional Tests B2B

1 similar comment
@mbvb1223
Copy link

mbvb1223 commented Nov 4, 2020

@magento run Functional Tests B2B

@romainruaud
Copy link
Contributor

can you please guy tag this PR with "Partner : Smile" ?

I used to be able to do so previously but it seems it's not the case anymore.

Regards

@PierreLeMaguer
Copy link
Contributor Author

@magento run Functional Tests B2B

@PierreLeMaguer
Copy link
Contributor Author

Hello @BarnyShergold , is it ok now ?
Also, is it possible to add the label Parter: Smile ?
Thanks

@BarnyShergold BarnyShergold added the Partner: Smile Pull Request is created by partner Smile label Nov 17, 2020
Copy link

@BarnyShergold BarnyShergold left a comment

Choose a reason for hiding this comment

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

All tests have passed! I've added Smile

@magento-engcom-team
Copy link
Contributor

Hi @BarnyShergold, thank you for the review.
ENGCOM-8470 has been created to process this Pull Request
✳️ @BarnyShergold, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

@PierreLeMaguer
Copy link
Contributor Author

@BarnyShergold any news about this PR ? Does it lack anything ?

@BarnyShergold
Copy link

@PierreLeMaguer I did some checking and currently the feedback is - "This PR is prioritised as P4, we are not able to process P4 PRs currently"

@engcom-Delta engcom-Delta added the Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it label Mar 8, 2024
@engcom-Dash
Copy link
Contributor

@magento run all tests

@engcom-Dash
Copy link
Contributor

Hello @PierreLeMaguer,

Thanks for your contributions!

Moving this PR to on hold since it’s a feature request and we need PO approval for it. Once we get approval, we will proceed accordingly.

Thanks.

@engcom-Dash
Copy link
Contributor

Hello @PierreLeMaguer,

Thanks for your contributions!

Moving this PR to on hold since it’s a feature request and we need PO approval for it. Once we get approval, we will proceed accordingly.

Thanks.

Hello @PierreLeMaguer,

Thanks for your contributions!

We've received feedback from the PO, and the requested functionality—overriding the reorder feature in customizations—wasn't intended to work that way. As a result, we can't proceed further with this PR.

Thank you again for your understanding and for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Sales Partner: Smile Pull Request is created by partner Smile Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Release Line: 2.4 Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”. Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Reorder feature] Feature very hard to customize
8 participants