-
-
Notifications
You must be signed in to change notification settings - Fork 83
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
feat: allow doctrine/dbal v4 #247
Conversation
@ramsey could you please take a look? |
Thanks @greg0ire - on it... |
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.
Looks great. I think some parts of your PR have nothing to do directly with doctrine/dbal
4 compat and you could split them out in a separate commit or even pull request for clarity.
Hi @greg0ire, Do you have one specific suspect you could point out? |
I don't know, I'm not a maintainer of this repository |
Oh, I didn't realize you were just helping with this commit. Let's wait for the maintainer. |
I'm a Doctrine maintainer, and I want DBAL 4 to get more adoption, hence my review :) |
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.
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 outdated.
This comment was marked as outdated.
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 looks good, but it's failing the static analysis checks, and I don't have time to investigate. Can you look into it? |
@ramsey all the issues are related to the unsupported |
@ramsey could you approve the workflow again? |
@ramsey Could you spare some time to take a look at this? Thanks in advance. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #247 +/- ##
============================================
- Coverage 99.27% 90.25% -9.02%
- Complexity 68 75 +7
============================================
Files 6 7 +1
Lines 138 154 +16
============================================
+ Hits 137 139 +2
- Misses 1 15 +14
|
@@ -46,7 +47,7 @@ private function getType(): Type | |||
|
|||
public function testGetName(): void | |||
{ | |||
$this->assertSame('uuid_binary_ordered_time', $this->getType()->getName()); | |||
$this->assertSame('uuid_binary_ordered_time', $this->getType()::lookupName($this->getType())); |
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.
lookupName()
was added in dbal 3.7.0: doctrine/dbal#6130
It's not available at all with DBAL 2. Maybe we should drop support for DBAL 2 in a separate PR first, or use lookupName()
only when that method exists.
Description
Support doctrine/dbal:^4.0
Closes: #246
Types of changes
PR checklist