checkout_index_index.xml file code improvement.

[sanganinamrata]

Description (*)

Removed sortOrder from messages, authentication, progressBar, estimation, and sidebar checkout components as they are already been rendered without those sortOrders and individual getRegions at app/code/Magento/Checkout/view/frontend/web/template/onepage.html

Related Pull Requests

Fixed Issues (if relevant)

1. This is code improvement.

Manual testing scenarios (*)

N/A

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)

Resolved issues:

1. resolves [Issue] checkout_index_index.xml file code improvement. #30550: checkout_index_index.xml file code improvement.

[m2-assistant]

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

[rogyar]

@magento run all tests

[lenaorobei]

@magento give me test instance

[magento-deployment-service]

Hi @lenaorobei. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @lenaorobei, here is your Magento Instance: https://cdb368462778ff5928172ee147e93fbe.instances.magento-community.engineering
Admin access: https://cdb368462778ff5928172ee147e93fbe.instances.magento-community.engineering/admin_d91d
Login: 72897994
Password: 5462b2420ced

[sidolov]

@magento create issue

[rogyar]

@magento run Integration Tests

[ptylek]

Currently it gives wrong impression that changing sortOrder could have any impact for changing those checkout components order. Adding Auto-Tests: Not Required label as removing these sortOrders doesn't change anything - components are displayed with getRegion().

[magento-engcom-team]

Hi @ptylek, thank you for the review.
ENGCOM-8370 has been created to process this Pull Request
✳️ @ptylek, 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

[sanganinamrata]

@ptylek, Will you please add hacktoberfest-accepted label to this PR? This event is about to finish. Without this label to my PR, I'll be eliminated from that challenge. :)

[ptylek]

@sanganinamrata all approved/merged PRs should be counted for the hacktoberfest, afaik label is only added if they can't be approved/merged before the end of October

[engcom-Alfa]

✔️ QA Passed

This is code improvement. The order of sorting components has not been changed.
Everything work as previously (expected).

[m2-assistant]

Hi @sanganinamrata, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.