Closed andreeacalinvtex closed 2 years ago
Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖
Please select which version do you want to release:
[x] Patch (backwards-compatible bug fixes)
[ ] Minor (backwards-compatible functionality)
[ ] Major (incompatible API changes)
And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.
Beep boop :robot:
Thank you so much for keeping our documentation up-to-date :heart:
Your PR has been merged! App is being published. :rocket: Version 0.8.1 → 0.8.2
After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:
vtex deploy vtex.store-link@0.8.2
After that your app will be updated on all accounts.
For more information on the deployment process check the docs. :book:
What problem is this solving?
In plp the two components took the link from the product summary and not their own. By adding a container div with the appropriate onClick event in which the propagation stops, we were able to overcome the problem. A class with css handles has been associated with the container div so that the style can be managed from the theme.
How to test it?
You can try it on the workspace https://testwk--mcxhoreca.myvtex.com, where the app with the change is installed with version vtex.store-link@0.8.2-hkignore.0.