-
Notifications
You must be signed in to change notification settings - Fork 185
TypeError: Return value of LanguageServer\DefinitionResolver::resolveExpressionNodeToType() must implement interface phpDocumentor\Reflection\Type, null returned #252
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
Comments
Got the same error:
|
Since my issue (in v1.2.0) was closed as a duplicate of this issue (in v1.0.0), which is also closed, when can we expect an actual fix for this issue? :) |
When someone does a PR and fixes it |
It's a bit discouraging when PRs sit pending review from the maintainer for ~2 weeks, but I went ahead and created a PR anyway, #362 :) |
Um, what PR exactly sits pending for review for 2 weeks? You do realise I am responding to your issues right now on the weekend, in my free time, do you? ;) |
#352, which is a feature that I personally care about. I don't mean to sound entitled, it just strikes me as weird that a bug that causes the parser to not work at all for some users would sit unfixed for 2 months (#286) and when a PR is created, it's rejected because it fixes the crash, not the core issue. To me, it makes more sense that the parser runs, but returns incorrect data for a small percentage of outcomes, rather than it not running at all and thus producing no data for 100% of outcomes, until such a time as it would be possible to investigate the root cause. |
It's not weird at all. #352 has merge conflicts and includes a PR already merged, so I can't even review the real diff against master. |
@ the Defintion->type - fair enough. Would you be able to offer any assistance with what I need to do in order to help track down this problem? @ #352 - okay, I just didn't see any comments from you or discussion with the author requesting a re-do from the latest master, or anything like that. To me, it looks like it's been ignored, that's all I was trying to say :) |
I would go to that method and set a conditional breakpoint when |
The text was updated successfully, but these errors were encountered: