-
-
Notifications
You must be signed in to change notification settings - Fork 51
Return value parseTypes() is bad #141
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
Hi, Thanks for reporting this. Could you please provide some more information about the type that should be resolved that results into a null value? It looks like you found a bug which I would like to cover with a test before we start fixing this problem. |
oh well. Here is the full stacktrace - https://forge.typo3.org/issues/96148 |
@jaapio Hi. Could you please try to reproduce the behaviour with the following:
Changing it to
solved the problem for me. |
Thanks, that reproduces this issue |
I created a patch, It would be nice if somebody was able to help me test this to see if it works like you are expecting it to work. The type resolver will now throw an exception, because |
I released v1.6.0 containing this patch. Let me know if you have any problems with this patch :-) |
I tested where I originally got the problem (TYPO3v10/Extbase) and it's solved. thx. @jaapio |
phpDocumentor v1.5.1 on TYPO3v10.4.21 with PHPv7.4.19
The text was updated successfully, but these errors were encountered: