-
-
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
Fix return type #173
Fix return type #173
Conversation
@ramsey Could you approve the workflow so that we can see if the tests pass? Thank you 🙏 |
Codecov Report
@@ Coverage Diff @@
## main #173 +/- ##
===========================================
Coverage 100.00% 100.00%
Complexity 57 57
===========================================
Files 5 5
Lines 112 112
===========================================
Hits 112 112
|
This comment has been minimized.
This comment has been minimized.
It’s not useless. It tells me that the line coverage hasn’t changed as a result of your changes in this PR. 😀 |
This comment has been minimized.
This comment has been minimized.
@ramsey Sorry for the rant. Is there anything you would like me to change? |
Method "Doctrine\DBAL\Types\Type::getSQLDeclaration()" might add "string" as a native return type declaration in the future. Do the same in child class "Ramsey\Uuid\Doctrine\UuidBinaryType" now to avoid errors or add an explicit @return annotation to suppress this message.
I didn't know you can mark a comment as being "off-topic." Interesting. I'll try to get this merged soon. Thanks! |
@ramsey Thanks for the merge ❤️ |
Method "Doctrine\DBAL\Types\Type::getSQLDeclaration()" might add "string" as a native return type declaration in the future. Do the same in child class "Ramsey\Uuid\Doctrine\UuidBinaryType" now to avoid errors or add an explicit @return annotation to suppress this message.