Catch more "There should be a node type provider" exceptions #55
Conversation
This file contains 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
In psalm#47 a try-catch was added to handle one case where `->getStatementsSource()->getNodeTypeProvider()` is being called and is throwing an exception because Psalm's FileAnalyzer doesn't populate the node type provider until after its NamespaceAnalyzer has already tried to analyze the whole file (see also psalm#34). There are three other code paths making a similar call, at least one of which runs into the same problem. Let's add try-catches to all of them.
|
Thanks! |
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.
In #47 a try-catch was added to handle one case where
->getStatementsSource()->getNodeTypeProvider()is being called and is throwing an exception because Psalm's FileAnalyzer doesn't populate the node type provider until after its NamespaceAnalyzer has already tried to analyze the whole file (see also #34).There are three other code paths making a similar call, at least one of which runs into the same problem. Let's add try-catches to all of them.