-
Notifications
You must be signed in to change notification settings - Fork 20
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
Fix path on windows #63
Conversation
Well in fact it's normal as the method is called from |
I'm curious if we need to write a test for this issue. Would it be enough to run the current test suite on a Windows runner in order to detect this kind of problem? |
@derrabus I checked running the On windows without the fix:
On windows with the fix:
I'm going to update the |
With the new assert on Windows, without the fix of this PR, we have the following result:
|
Hello, I just noticed the same kind of issue with another project I currently upgrade. I have the following deprecation raised on Linux (in CI server) that is not raised when running my tests locally on Windows.
If I apply this patch, I get the same deprecation on Linux and Windows. Any chance to merge the fix? |
Sure, thanks @raziel057! |
While running my project test suite on Windows (local env) and linux (CI env) I could notice that I have a deprecation raised on Linux that is not on Windows.
When the path is created on Windows using the package name (ex.:
doctrine/dbal
) it results as\vendor\doctrine/dbal\
but the real path to the library coming from$backtrace[1]['function']
is...\vendor\doctrine\dbal\src\Platforms\AbstractPlatform.php
so currently it match the following condition on windows while it's not the case on Linux.After, that been say, I'm not sure if it's normal that I got the deprecation as it's raised from a call to the deprecated method
supportsForeignKeyConstraints()
of AbstractPlatform of thedoctrine/dbal
package done from thedelete
method ofvendor/doctrine/orm/lib/Doctrine/ORM/Persisters/Entity/JoinedSubclassPersister.php
.