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

Fix minisearch not appear when disable suggestions search #30634

Conversation

mrtuvn
Copy link
Contributor

@mrtuvn mrtuvn commented Oct 24, 2020

Description (*)

Previously when owner shop disable suggestions search in backend config when user try search in mobile screen. Mini search will not active. User will not able to search thing

Use declarative syntax data-mage-init for improve performance instead script tag x-magento-init

Preconditions (*)

Magento 2.4-develop
Php 7.4

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes mini search field head does not appear if suggestions and recommendations are disabled. Luma Theme and mobile navigation. #30584

Manual testing scenarios (*)

  1. Go to admin
  2. Catalog > Catalog Search
  3. Enable Search Suggestions Change to No
  4. View storefront in real device mobile screen or resize browser screen
  5. Click on search icon to see problem

Expected result (*)

Appear input form search (form minisearch)

Actual result (*)

✖️ Nothing happens

Peek 2020-10-22 12-37

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 24, 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

@rogyar
Copy link
Contributor

rogyar commented Oct 24, 2020

@magento give me 2.4-develop instance

@magento-deployment-service
Copy link

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

@magento-deployment-service
Copy link

@rogyar
Copy link
Contributor

rogyar commented Oct 24, 2020

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

@rogyar
Copy link
Contributor

rogyar commented Oct 24, 2020

Hi @mrtuvn, great job! Do you think we can cover this fix with auto-tests somehow?

@rogyar rogyar added Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. Priority: P3 May be fixed according to the position in the backlog. labels Oct 24, 2020
@rogyar rogyar self-assigned this Oct 24, 2020
@mrtuvn
Copy link
Contributor Author

mrtuvn commented Oct 24, 2020

Sure let's cover it with some tests

@mrtuvn
Copy link
Contributor Author

mrtuvn commented Oct 24, 2020

@rostyslav-hymon Can you let me know issue related with your change previously ? Why need to wrap quickSearch component initializing with php tag for check suggestions search enable ?
de9318d
CC: @rogyar

@mrtuvn mrtuvn force-pushed the fix-minisearch-not-appear-when-disable-suggestions branch from 73734d6 to 1f9766c Compare October 26, 2020 00:15
@rostyslav-hymon
Copy link
Contributor

@rostyslav-hymon Can you let me know issue related with your change previously ? Why need to wrap quickSearch component initializing with php tag for check suggestions search enable ?
de9318d
CC: @rogyar

Hi @mrtuvn . My change resolved the issue where disabling "Search Suggestions" did not have an effect on "Quick Search" behavior. It looks like your code solves this problem more correctly.

@ghost ghost added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Oct 28, 2020
@mrtuvn
Copy link
Contributor Author

mrtuvn commented Oct 30, 2020

@engcom-Charlie @engcom-Bravo @engcom-Alfa What test type should i start for such case ? MFTF

@engcom-Charlie
Copy link
Contributor

engcom-Charlie commented Nov 2, 2020

@mrtuvn yes, via MFTF.
Thank you.

@engcom-Charlie engcom-Charlie self-assigned this Nov 2, 2020
@ghost ghost added this to Review in Progress in High Priority Pull Requests Dashboard Nov 2, 2020
@ghost ghost removed this from Pending Review in Pull Requests Dashboard Nov 2, 2020
@engcom-Charlie engcom-Charlie moved this from Review in Progress to Changes Requested in High Priority Pull Requests Dashboard Nov 2, 2020
@ghost ghost removed the Progress: review label Nov 2, 2020
@magento-engcom-team
Copy link
Contributor

Hi @rogyar, thank you for the review.
ENGCOM-8464 has been created to process this Pull Request

@engcom-Alfa
Copy link
Contributor

✔️ QA Passed
The result is the same as in #30634 (comment)

@engcom-Alfa engcom-Alfa moved this from Testing in Progress to Extended Testing (optional) in High Priority Pull Requests Dashboard Dec 7, 2020
@engcom-Charlie engcom-Charlie moved this from Extended Testing (optional) to Merge in Progress in High Priority Pull Requests Dashboard Dec 10, 2020
@m2-community-project m2-community-project bot moved this from Merge in Progress to Ready for Testing in High Priority Pull Requests Dashboard Dec 17, 2020
@engcom-Alfa engcom-Alfa moved this from Ready for Testing to Testing in Progress in High Priority Pull Requests Dashboard Dec 18, 2020
@engcom-Alfa engcom-Alfa moved this from Testing in Progress to Extended Testing (optional) in High Priority Pull Requests Dashboard Dec 18, 2020
@engcom-Charlie engcom-Charlie moved this from Extended Testing (optional) to Merge in Progress in High Priority Pull Requests Dashboard Dec 18, 2020
@magento-engcom-team magento-engcom-team merged commit b0d30c2 into magento:2.4-develop Dec 22, 2020
@m2-assistant
Copy link

m2-assistant bot commented Dec 22, 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.

@sidolov sidolov moved this from Merge in Progress to Recently Merged in High Priority Pull Requests Dashboard Dec 23, 2020
@mrtuvn mrtuvn deleted the fix-minisearch-not-appear-when-disable-suggestions branch January 6, 2021 22:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Award: bug fix Award: MFTF test coverage Component: Search Event: MageCONF CD 2020 Priority: P2 A defect with this priority could have functionality issues which are not to expectations. 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
None yet
7 participants