Add more details to TypeInfo documentation #20407
Open
+97
−3
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
Korbeil
force-pushed
the
feature/type-info-updates
branch
from
a8425ee
to
e8ed9bc
Compare
Korbeil
force-pushed
the
feature/type-info-updates
branch
from
e8ed9bc
to
dc999f3
Compare
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.
This pull request is to revamp current TypeInfo documentation.
I tried to make the most of the recent changes while answering @javiereguiluz's issue (thanks to "PHPDoc parsing" part).
It should fixes #20389, #20064 and #20014.