We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I saw a warning similar to this in my IDE the other day:
The use of function filectime() / filemtime() is discouraged.
It was not coming from Magento CS but from PHPCS which I am currently using WITH Magento 2 CS.
If this check / warning is already there, would not be helpful to provide developers with some guidance or alternatives on what they can use instead?
TBC: I am still doing some research to understand WHY the use of this is discouraged. I will complete this section with my findings.
This guy proposes to use \Magento\Framework\Filesystem\Driver\File, same we are already advising to use to replace these kind of PHP functions.
\Magento\Framework\Filesystem\Driver\File
The text was updated successfully, but these errors were encountered:
Merge pull request #172 from magento-commerce/imported-eliseacornejo-…
8085e03
…magento-coding-standard-384 [Imported] AC-2724: Update rector dependency to the latest version
diazwatson
No branches or pull requests
Rule
I saw a warning similar to this in my IDE the other day:
It was not coming from Magento CS but from PHPCS which I am currently using WITH Magento 2 CS.
If this check / warning is already there, would not be helpful to provide developers with some guidance or alternatives on what they can use instead?
Reason
TBC: I am still doing some research to understand WHY the use of this is discouraged. I will complete this section with my findings.
Implementation
This guy proposes to use
\Magento\Framework\Filesystem\Driver\File
, same we are already advising to use to replace these kind of PHP functions.The text was updated successfully, but these errors were encountered: