-
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
pelago/emogrifier and friendsofphp/php-cs-fixer updated #31772
pelago/emogrifier and friendsofphp/php-cs-fixer updated #31772
Conversation
Hi @konarshankar07. 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 |
@magento run all tests |
@konarshankar07: could you update your composer version to at least 1.10.19 and regenerate the Thanks! |
@magento run all tests |
1 similar comment
@magento run all tests |
@magento run all tests |
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.
Thanks for the pull request @konarshankar07 ! Please see my review comments
@magento run all tests |
@magento run all tests |
@magento run all tests |
@magento run Static Tests, Unit Tests, Integration Tests |
@magento run Functional Tests CE |
@magento run Static Tests, Unit Tests, Integration Tests, Functional Tests CE |
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.
Thanks for updates @konarshankar07 ! Please see my comment
lib/internal/Magento/Framework/Css/PreProcessor/Adapter/CssInliner.php
Outdated
Show resolved
Hide resolved
@konarshankar07 I have applied the review suggestions, updated the branch and switched the PR to php8-develop branch @magento run all tests |
Thanks @sivaschenko for the update and I have fixed unit test |
!== false || | ||
strpos($cssToInline, 'undefined') |
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.
@sivaschenko .. I have added this commit to fix the integration test for
magento2/dev/tests/integration/testsuite/Magento/Email/Model/Template/FilterTest.php
Line 423 in 2b21388
'Developer mode - File with compilation error results in error message' => [ |
Can you please review this? I feel we need to handle this in different way
Thanks
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.
@konarshankar07 Looks like emogrifier is no longer actually working with CSS string containing the error message.
I think the best way to handle the CSS parsing error is to throw an exception in \Magento\Email\Model\Template\Filter::getCssFilesContent
and handle it in client code.
Instead of returning an exception message as the result css and then parsing the result for error messages.
Thank you!
@magento run all tests |
@magento run all tests |
@magento run all tests |
Hi @konarshankar07, thank you for your contribution! |
Description (*)
Following packages upgraded
pelago/emogrifier
friendsofphp/php-cs-fixer
Related Pull Requests
https://github.com/magento/partners-magento2ee/pull/464
Fixed Issues (if relevant)
Questions or comments
Contribution checklist (*)