Skip to content

[View] Removed extra space in link and script tag #32919

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

Merged
merged 5 commits into from
May 28, 2024
Merged

[View] Removed extra space in link and script tag #32919

merged 5 commits into from
May 28, 2024

Conversation

srsathish92
Copy link
Contributor

@srsathish92 srsathish92 commented Apr 30, 2021

Description (*)

This PR helps to change extra spaces into single space in <link> and <script> tag.

Fixed Issues (if relevant)

N/A

Manual testing scenarios (*)

  1. ./vendor/bin/phpunit -c dev/tests/unit/phpunit.xml.dist lib/internal/Magento/Framework/View/Test/Unit/Page/Config/RendererTest.php
  2. Open the store and see <link> and <script> tag using view source code.
  3. <link> and <script> should be without double spaces between attributes.

Actual Result:
w_extraspace

Excepted Result:
wo_extraspace

Questions or comments

Please let me your suggestions if any

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)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)

Resolved issues:

  1. resolves [Issue] [View] Removed extra space in link and script tag #32920: [View] Removed extra space in link and script tag

@m2-assistant
Copy link

m2-assistant bot commented Apr 30, 2021

Hi @srsathish92. Thank you for your contribution
Here are 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
  13. Semantic Version Checker

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

@srsathish92 srsathish92 changed the title [Framework] Removed extra space in link and script tag [View] Removed extra space in link and script tag Apr 30, 2021
@srsathish92
Copy link
Contributor Author

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@srsathish92
Copy link
Contributor Author

@magento create issue

@Den4ik
Copy link
Contributor

Den4ik commented Apr 30, 2021

@magento run Functional Tests EE, Functional Tests B2B

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@srsathish92
Copy link
Contributor Author

@magento run Functional Tests B2B

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@srsathish92
Copy link
Contributor Author

@magento run Functional Tests B2B

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@m2-community-project m2-community-project bot 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 May 3, 2021
Copy link
Contributor

@Den4ik Den4ik left a comment

Choose a reason for hiding this comment

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

Hi @srsathish92 Thanks for your contribution

@magento-engcom-team
Copy link
Contributor

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

@Den4ik Den4ik added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label May 3, 2021
@Den4ik
Copy link
Contributor

Den4ik commented May 7, 2021

I'm not sure that usage of multiple spaces in attributes is a good practice and useful use case

@engcom-Delta
Copy link
Contributor

Hi @srsathish92 , Thanks for your contribution.Please resolve the conflicts to move ahead on this PR

Copy link
Contributor

@engcom-Delta engcom-Delta left a comment

Choose a reason for hiding this comment

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

Please resolve the conflicts on this PR

@srsathish92 srsathish92 requested a review from engcom-Delta March 7, 2024 06:12
@srsathish92
Copy link
Contributor Author

@magento run all tests

@engcom-November engcom-November self-assigned this May 21, 2024
@engcom-November
Copy link
Contributor

@magento run all tests

@engcom-November
Copy link
Contributor

This is a code-quality pr, no manual testing is required.

As the builds are failing moving this to Extended testing.

@engcom-November
Copy link
Contributor

@magento run all tests

@engcom-November
Copy link
Contributor

@magento run Static Tests, Integration Tests, Functional Tests B2B, Functional Tests CE, Functional Tests EE, WebAPI Tests

@engcom-November
Copy link
Contributor

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

@engcom-November
Copy link
Contributor

For functional tests, repeating failures are known issues and are flaky.

Functional Tests B2B:
1st Run:
image

2nd Run:
image

Known issues:
ACQE-6523 - AdminReorderWithCatalogPriceRuleDiscountTest

Functional Tests CE:
1st Run:
image

2nd Run:
image

Known issues:
ACQE-6590 - AdminCheckConfigurationForPayPalExpressCheckoutInUnitesStatesTest

Functional Tests EE:
1st Run:
image

2nd Run:
image

Known issues:
ACQE-6523 - AdminReorderWithCatalogPriceRuleDiscountTest
ACQE-6331 - StorefrontCreateOrderAllQuantityGroupedProductOptionDefaultStockTest

@engcom-November
Copy link
Contributor

WebAPI repeating failure is known issue and is flaky.

1st Run:
image

2nd Run:
image

Known issue:
ACP2E-3082 - testSendNegotiableQuoteCannotResend

Hence moving this to Merge in Progress

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Cleanup Component: View Partner: ITG Commerce partners-contribution Pull Request is created by Magento Partner Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Progress: accept Release Line: 2.4 Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”.
Projects
Status: Recently Merged
Development

Successfully merging this pull request may close these issues.

[Issue] [View] Removed extra space in link and script tag
9 participants