-
Notifications
You must be signed in to change notification settings - Fork 9.4k
replace deprecated escaper #38135
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
base: 2.4-develop
Are you sure you want to change the base?
replace deprecated escaper #38135
Conversation
Hi @Morgy93. Thank you for your contribution! Add the comment under your pull request to deploy test or vanilla Magento instance:
❗ Automated tests can be triggered manually with an appropriate comment:
Allowed build names are:
You can find more information about the builds here For more details, review the Code Contributions documentation. |
f46a30b
to
fd3664e
Compare
@magento run all tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues. |
fd3664e
to
59600cd
Compare
I fixed the additional phpcs errors that came up. |
@magento run Functional Tests B2B,Functional Tests CE,Functional Tests EE,Static Tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues. |
@magento run Database Compare,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 |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues. |
@magento run Sample Data Tests CE,Sample Data Tests B2B,Sample Data Tests EE |
Failed to run the builds. Please try to re-run them later. |
@magento run Sample Data Tests CE,Sample Data Tests B2B,Sample Data Tests EE |
Failed to run the builds. Please try to re-run them later. |
What a great developer experience. 🙄 Will leave it as it is until someone gets in touch. |
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.
Hi @Morgy93
Thanks for your contribution.
Please follow backward compatibility documentation for adding new constructor params.
eff1da9
to
779eabe
Compare
Interesting, that's why I see this approach used everywhere. @Den4ik Changed the files accordingly. Please review. |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues. |
@@ -32,24 +32,27 @@ class BlockActions extends Column | |||
/** | |||
* @var Escaper | |||
*/ | |||
private $escaper; | |||
protected $escaper; |
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.
What's the reason for changing this? I don't immediately see why this would be needed? I think this can be put back to private
, no?
Same remark goes for the other class.
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.
@hostep I'm agree with you, but at the same time I don't see any restrictions to use protected access type
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.
Purely because the UrlBuilder was protected as well. I thought that is some kind of coding standard.
I'd be happy to change it to private if you agree to this change.
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.
@Den4ik: Magento encourages composition over inheritance, if we make members protected again, we are pushing people in the direction of using inheritance again.
I would suggest we change it back to private
.
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.
@hostep It make sense 👍
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.
@hostep Great. I updated the files accordingly. Please review.
c41a2a3
to
3a1cefa
Compare
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.
@magento run all tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues. |
0b62db7
to
0a0341c
Compare
@magento run all tests Run tests again |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues. |
@magento run all tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues. |
0a0341c
to
341601a
Compare
341601a
to
e767817
Compare
@magento run all tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues. |
@Den4ik Any idea? |
@magento run all tests |
@magento run WebAPI Tests |
@magento run Functional Tests B2B |
I see that failed tests is not related to PR changes. |
Description (*)
The
getEscaper
is deprecated so it has been replaced by dependency injection.Manual testing scenarios (*)
./vendor/bin/phpunit -c dev/tests/unit/phpunit.xml.dist app/code/Magento/Cms/Test/Unit
Contribution checklist (*)