NoSuperfluousPhpdocTagsFixer - handle null in every position #3884
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
dmvdbrugge
force-pushed
the
no_superfluous_phpdoc_tags_nullable_fix
branch
from
b14eaad
to
b74dbd3
Compare
julienfalque
approved these changes
Jul 8, 2018
|
Note: my commit can be squashed when merging :) |
SpacePossum
changed the title
SpacePossum
force-pushed
the
no_superfluous_phpdoc_tags_nullable_fix
branch
from
403f61a
to
9956636
Compare
SpacePossum
added a commit
that referenced
this pull request
Jul 9, 2018
…n (dmvdbrugge, julienfalque) This PR was squashed before being merged into the 2.12 branch (closes #3884). Discussion ---------- NoSuperfluousPhpdocTagsFixer - handle null in every position … instead of last only. This fixes #3849 Commits ------- 9956636 NoSuperfluousPhpdocTagsFixer - handle null in every position
|
thanks @dmvdbrugge and @julienfalque 👍 |
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.
… instead of last only.
This fixes #3849