-
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
Add filename paramenter log #4147
Add filename paramenter log #4147
Conversation
eb77080
to
cceab50
Compare
cceab50
to
67950c5
Compare
* @return string | ||
* @throws \InvalidArgumentException | ||
*/ | ||
public function sanitizeFileName($fileName) |
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.
This should be private
. Don't think child classes need to access that, let alone other objects.
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.
I agree with you... actually I prefer making methods protected, in case someone needs to overwrite the class but doesn't want to change the behaviour of this method.
I'm not sure how to make the proper test then, should those be integration test instead of unit tests? What do you think would be the proper approach?
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.
Why not just use reflection?
2d830ec
to
c364c4e
Compare
c364c4e
to
e1c7bd3
Compare
@fcapua-summa please sync with the develop branch and rerun travis builds. |
[pangolin] MQE-1536: Magento\Install\Test\TestCase\InstallTest is failing on php 7.0
Reopening PR #2679