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
Update call maps for MongoDB extension #8432
Conversation
Thanks! Can you look at the mismatch reported in Unit Tests 4? |
b8f65a6
to
b521488
Compare
Ah, there were some more (lowercased) entries in a completely separate portion of the file. These were now duplicated, but since they were originally lowercased they were treated as different. I removed the obsolete definitions. |
b521488
to
6a6922d
Compare
I noticed that some of the interface declarations aren't correct. Please hold off on merging while I figure out where the script failed (probably has to do with tentative return types). |
That's fixed now. I didn't consider tentative return types for interfaces. |
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.
Can you sort declaration in alphabetical order? It seems to be the previous order and it would help reviewing. Please see a few notes also
'MongoDB\BSON\Decimal128::__construct' => ['void', 'value='=>'string'], | ||
'MongoDB\BSON\Binary::__toString' => ['string'], | ||
'MongoDB\BSON\Binary::serialize' => ['string'], | ||
'MongoDB\BSON\Binary::unserialize' => ['void', 'serialized' => ''], |
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.
serialized should have a type here, either mixed or more narrow
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.
Ah, thanks. Added the correct string
type for all unserialize
methods.
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 don't see a new commit on the branch? Forgot to push?
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.
Whopsie, yes. I pushed the commit now.
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.
Well, I have bad news then, I still don't see anything
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.
nvm, I was mistaken apparently
'MongoDB\BSON\BinaryInterface::__toString' => ['string'], | ||
'MongoDB\BSON\DBPointer::__toString' => ['string'], | ||
'MongoDB\BSON\DBPointer::serialize' => ['string'], | ||
'MongoDB\BSON\DBPointer::unserialize' => ['void', 'serialized' => ''], |
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.
same
Thanks! |
While adding psalm checks to the MongoDB driver, I noticed that a number of method signatures in the call map were either missing or out-of-date. This PR updates them to what we'll ship in 1.15. They have been automatically generated from the definitions in the driver and made to match the format required by Psalm.