magento2 magento/magento2#35881: Final Price for grouped products does not include tax in the Recently Viewed Widget

Description (*)

In Magento\Catalog\Ui\DataProvider\Product\Listing\Collector\Price::collect Added a product type check. If it's a grouped, I choose child product with the final minimum price
For Grouped product in file GroupedProduct/view/frontend/ui_component/widget_recently_viewed.xml need add empty special_price template. If you don't edit it, the price block is duplicated in the widget.
In Catalog/view/frontend/templates/product/view/opengraph/general.phtml meta tag <meta property="product:price:amount" add product type check. If it's a grouped, I choose child product with the final minimum price

Related Pull Requests

Fixed Issues (if relevant)

Fixes magento/magento2#35881

Manual testing scenarios (*)

made sure that tax classes are set for taxable goods
I made sure that I see the prices both with and without tax
Visit sample grouped product
Go back to the home page to view the Recently Viewed Block
Go to the Grouped product page. Find the tag (<meta property="product:price:amount" ) in the browser code inspector - and check the price

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)
[ ] 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)

Aug 26 '22 12:08 shmVan

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

:exclamation: 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:

Database Compare
Functional Tests CE
Functional Tests EE,
Functional Tests B2B
Integration Tests
Magento Health Index
Sample Data Tests CE
Sample Data Tests EE
Sample Data Tests B2B
Static Tests
Unit Tests
WebAPI Tests
Semantic Version Checker

You can find more information about the builds here

:information_source: Run only required test builds during development. Run all test builds before sending your pull request for review.

For more details, review the Magento Contributor Guide documentation.

:warning: According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel