-
Notifications
You must be signed in to change notification settings - Fork 431
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
ORM3 compatibility #421
ORM3 compatibility #421
Conversation
5a7205e
to
bc0f53c
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.
Thank you for starting the work on this topic. I get the impression that you're trying to cover multiple topic at once. Try to keep your PR focused. For instance, dropping PHP 7 support or upgrading PHP CS Fixer should be separate PRs.
b06e4f7
to
daaa858
Compare
@connorhu ah, i merged a PR that does some improvements to Lexer compatibility already causing a few conflicts here. Can you integrate it or is that problematic? |
@beberlei Sure, I can integrate it, because I've done those conversions too. There are still some open questions around code simplification, whether it makes sense or not, whether I should do it or not. I can make a table showing how much repetitive logic is in the code. |
daaa858
to
5ced9da
Compare
667230f
to
c7e89ff
Compare
63f31a9
to
55ef25e
Compare
Please revert the changes you've made to the CI. We don't need them. |
437e9b6
to
1f307bb
Compare
a5fba21
to
4d47e8d
Compare
Whenever you have time:
|
a4b605e
to
a08bb04
Compare
To answer your question I have to figure out whats going on here with the carbon. The types for Carbon were extend from |
Current implementation is not compatible with DBAL4. The problem here is that
If we want these 4 tests to run, we need our own |
f3da722
to
082fbe8
Compare
082fbe8
to
1927ba7
Compare
PR rebased, squasd into one commit. Now we have to wait for release ORM 2.19.0. |
Co-authored-by: Alexander M. Turek <[email protected]>
Yes. Thank you very much! |
Thank you for helping the process. |
Co-authored-by: Théo Attali <[email protected]>
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
When to expect the new release? |
When it's ready. |
@derrabus I was thinking. It is a legitimate wish to use the code with orm3. Which is ready anyway. What if you make an orm3 branch, apply the contents of this PR as a patch, rewrite the requirement for orm3 only and put a note in the install description that until 2.19 is released, the ORM3 compatible code is there? If 2.19 is released, we will merge this PR, drop the orm3 branch and leave the master only. |
I mean, we can merge the branch as is. It's ready anyway and Composer will take care that this package is not installed with ORM 2.18. |
Ah well, we should've done a rebase before, to have PHPStan analyze your changes. I've pushed b6349f3 in order to make the CI green. |
Thanks. But we should not forget to remove the |
Sure. Not that it has any impact downstream, but we will remove it. |
No description provided.