-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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 #29971 - Layered navigation swatches ignore show tooltip setting #30115
base: 2.5-develop
Are you sure you want to change the base?
Fix #29971 - Layered navigation swatches ignore show tooltip setting #30115
Conversation
Hi @Bartlomiejsz. Thank you for your contribution
❗ Automated tests can be triggered manually with an appropriate comment:
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. 🕙 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 |
20664cb
to
81cda6f
Compare
@magento run all tests |
@magento run Functional Tests CE, Functional Tests EE, WebAPI Tests |
@magento run Functional Tests EE |
Hi @Bartlomiejsz. Thank you for your contribution. Could I ask you to create an integration/functional test for this case, please? The test will set all the preconditions and assert that the page source does not have the tooltip selector. Thank you! |
Hi @rogyar, I believe I can work on it in the upcoming days |
81cda6f
to
5599cdd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Bartlomiejsz could you please cover changes with automated test?
*/ | ||
protected $block = \Magento\Swatches\Block\LayeredNavigation\RenderLayered::class; | ||
protected $swatchHelper; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make property private
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
) { | ||
$this->layout = $layout; | ||
$this->swatchHelper = $swatchHelper; | ||
$this->configurableViewModel = $configurableViewModel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You may not follow BC development rules in plugins.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Hi @sidolov, yes, I will work on that, just didn't yet have time for it unfortunately |
b5397d2
to
5fe0d4a
Compare
5fe0d4a
to
354ec22
Compare
@magento run all tests |
@magento run Functional Tests CE |
@magento run WebAPI Tests |
<checkOption selector="{{AdminProductFormSection.selectCategory(categoryName)}}" stepKey="selectCategory"/> | ||
<click selector="{{AdminProductFormSection.done}}" stepKey="clickDone"/> | ||
<waitForPageLoad stepKey="waitForApplyCategory"/> | ||
<actionGroup name="AdminAssignCategoryToProductAndSaveActionGroup" extends="AdminAssignCategoryToProductActionGroup"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a very good cleanup. But unfortunately, it makes the PR backward-incompatible for 2.4-develop branch. There might be 3rd-party modules that extend the current action group and rely on the step keys. By removing the existing step keys we may brake such systems
<actionGroup ref="AdminLoginActionGroup" stepKey="loginAsAdmin"/> | ||
</before> | ||
<after> | ||
<!-- Clean up our modifications to the existing color attribute --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here as well, if we remove the existing step keys, we introduce backward-incompatible changes.
Hi @Bartlomiejsz. Awesome job! Thank you. How does it sound? |
@rogyar that sounds good to me, just wondering - is it known already when 2.5 branch will be available? |
Hi @Bartlomiejsz. We have not publicly available info about that point so far |
Description (*)
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
Please check fixed issue for testing scenario
Questions or comments
Contribution checklist (*)