Skip to content
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

Merged

Conversation

konarshankar07
Copy link
Contributor

@konarshankar07 konarshankar07 commented Jan 20, 2021

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)

  1. Fixes Update pelago/emogrifier dependency version to "^5.0.0" #31342
  2. Fixes Update friendsofphp/php-cs-fixer dependency to PHP 8 Compatible version #31343

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)
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Jan 20, 2021

Hi @konarshankar07. Thank you for your contribution
Here is 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

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

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests
  13. Semantic Version Checker

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.

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

🕙 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

@konarshankar07
Copy link
Contributor Author

@magento run all tests

@hostep
Copy link
Contributor

hostep commented Jan 20, 2021

@konarshankar07: could you update your composer version to at least 1.10.19 and regenerate the composer.lock file by running composer update --lock? There are a lot of changes in the composer.lock file you submitted which makes it much harder to see what changed in there. I suspect you are running a pretty old composer version.

Thanks!

@konarshankar07
Copy link
Contributor Author

@magento run all tests

1 similar comment
@konarshankar07
Copy link
Contributor Author

@magento run all tests

@konarshankar07
Copy link
Contributor Author

@magento run all tests

Copy link
Member

@sivaschenko sivaschenko left a 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

@konarshankar07
Copy link
Contributor Author

@magento run all tests

@konarshankar07
Copy link
Contributor Author

@magento run all tests

@konarshankar07
Copy link
Contributor Author

@magento run all tests

@konarshankar07
Copy link
Contributor Author

@magento run Static Tests, Unit Tests, Integration Tests

@konarshankar07
Copy link
Contributor Author

@magento run Functional Tests CE

@konarshankar07
Copy link
Contributor Author

@magento run Static Tests, Unit Tests, Integration Tests, Functional Tests CE

Copy link
Member

@sivaschenko sivaschenko left a 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

@sivaschenko sivaschenko changed the base branch from 2.4-develop to php8-develop January 26, 2021 21:42
@sivaschenko
Copy link
Member

@konarshankar07 I have applied the review suggestions, updated the branch and switched the PR to php8-develop branch

@magento run all tests

@konarshankar07
Copy link
Contributor Author

Thanks @sivaschenko for the update and I have fixed unit test
@magento run Unit Tests

Comment on lines 1049 to 1050
!== false ||
strpos($cssToInline, 'undefined')
Copy link
Contributor Author

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

'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

Copy link
Member

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!

@konarshankar07
Copy link
Contributor Author

@magento run all tests

@konarshankar07
Copy link
Contributor Author

@magento run all tests

@sivaschenko
Copy link
Member

@magento run all tests

@sivaschenko sivaschenko merged commit 4523b3a into magento:php8-develop Jan 29, 2021
@m2-assistant
Copy link

m2-assistant bot commented Jan 29, 2021

Hi @konarshankar07, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants