Skip to content

Clean code and remove whitespace in markup layered navigation filters #30333

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

Conversation

mrtuvn
Copy link
Contributor

@mrtuvn mrtuvn commented Oct 4, 2020

Description (*)

This pr aim to clean whitespace in some inline elements inside layered filter items. Also update use $escaper instead $block in template

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes magento/magento2#<issue_number>

Manual testing scenarios (*)

  1. ...
  2. ...

Questions or comments

Luma theme
Results before change
before_remove

Results after change
after_remove

Blank theme
Results before change
blank_category

Results after change
blank_category_fix

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] Clean code and remove whitespace in markup layered navigation filters #30448: Clean code and remove whitespace in markup layered navigation filters

@m2-assistant
Copy link

m2-assistant bot commented Oct 4, 2020

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

@ihor-sviziev
Copy link
Contributor

@magento run all tests

@ghost ghost removed the Progress: pending review label Oct 5, 2020
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.

In general looks good. Have only one suggestion

@ihor-sviziev ihor-sviziev added Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests Award: bug fix Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Oct 5, 2020
@mrtuvn mrtuvn force-pushed the clean-whitespace-inside-layer-navigation-items branch from d551b8d to 9e88f96 Compare October 5, 2020 11:32
@mrtuvn
Copy link
Contributor Author

mrtuvn commented Oct 5, 2020

@magento run Static Tests

@mrtuvn
Copy link
Contributor Author

mrtuvn commented Oct 5, 2020

@magento run all tests

@sidolov sidolov added the Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. label Oct 5, 2020
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.

✔ Approved.

Failing tests looks not related to changes form this PR.

@magento-engcom-team
Copy link
Contributor

Hi @ihor-sviziev, thank you for the review.
ENGCOM-8309 has been created to process this Pull Request

@ihor-sviziev
Copy link
Contributor

@magento run Functional Tests B2B, Functional Tests CE, Functional Tests EE

@mrtuvn mrtuvn force-pushed the clean-whitespace-inside-layer-navigation-items branch from 9e88f96 to 374593d Compare October 9, 2020 00:59
@mrtuvn
Copy link
Contributor Author

mrtuvn commented Oct 9, 2020

@magento run Functional Tests B2B, Functional Tests CE, Functional Tests EE

@mrtuvn
Copy link
Contributor Author

mrtuvn commented Oct 9, 2020

@magento run Database Compare, Integration Tests, Magento Health Index, Sample Data Tests CE, Sample Data Tests EE, Sample Data Tests B2B, Static Tests, Unit Tests, WebAPI Tests

@mrtuvn
Copy link
Contributor Author

mrtuvn commented Oct 9, 2020

@magento run Semantic Version Checker

@ihor-sviziev
Copy link
Contributor

@magento run Functional Tests CE, Functional Tests EE

@magento-engcom-team
Copy link
Contributor

Hi @ihor-sviziev, thank you for the review.
ENGCOM-8309 has been created to process this Pull Request

@engcom-Alfa
Copy link
Contributor

@magento create issue

@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

Luma:

Before: ✖️

2020-10-12_11-07

After: ✔️

2020-10-12_11-17

The same results and on the Blank theme

@engcom-Alfa engcom-Alfa added the QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope label Oct 12, 2020
@engcom-Foxtrot engcom-Foxtrot self-assigned this Oct 12, 2020
@magento-engcom-team magento-engcom-team merged commit e8bfc12 into magento:2.4-develop Oct 13, 2020
@m2-assistant
Copy link

m2-assistant bot commented Oct 13, 2020

Hi @mrtuvn, 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.

@mrtuvn mrtuvn deleted the clean-whitespace-inside-layer-navigation-items branch October 13, 2020 14:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests Award: bug fix Component: LayeredNavigation Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

[Issue] Clean code and remove whitespace in markup layered navigation filters
6 participants