Fix a few MongoDB definitions in functionMap.php#2140
Merged
ondrejmirtes merged 1 commit intophpstan:1.9.xfrom Jan 4, 2023
Merged
Fix a few MongoDB definitions in functionMap.php#2140ondrejmirtes merged 1 commit intophpstan:1.9.xfrom
ondrejmirtes merged 1 commit intophpstan:1.9.xfrom
Conversation
Member
|
Thank you! |
Member
Yes. Reflection is often wrong or incomplete. PHPStan uses multiple sources of data, see https://phpstan.org/user-guide/troubleshooting-types#internal-stubs for more details. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I think a few function definitions related to the MongoDB extension are incorrect or outdated. This results in incorrect errors as shown here: https://phpstan.org/r/0bdf022f-164a-4daa-bd51-6f127a5c3e44
I have updated two of the obvious errors, but there might be more outdated definitions. Are these definitions required at all? It appears I can get the same information using runtime reflection.