Conversation
Refactors the `product_card` Twig hook by introducing hooks. The goal is to make it easier to customize and extend the product card by allowing other templates or plugins to inject additional content without overriding the entire template. This improves flexibility and maintainability when adding features like badges, custom buttons, or additional information.   <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Introduced a modular, hook-based system for rendering product cards, allowing for greater customization and extension. - Added new template fragments for product card details, images, names, and prices, each rendered via dedicated hooks. - **Refactor** - Simplified the product card template to delegate all rendering to the new hook system. - **Style** - Enhanced product card image presentation for consistent aspect ratio and styling. - **Chores** - Removed unnecessary whitespace from configuration files. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
❌ Preview Environment deleted from BunnyshellAvailable commands:
|
This PR has been generated automatically.
For more details see upmerge_pr.yaml.
Remember! The upmerge should always be merged with using
Merge pull requestbutton.In case of conflicts, please resolve them manually with usign the following commands:
If you use other name for the upstream remote, please replace
upstreamwith the name of your remote pointing to theSylius/Syliusrepository.Once the conflicts are resolved, please run
git merge --continueand push the changes to this PR.