fix: use @psalm-template annotation to avoid clashes#345
Closed
redjam13 wants to merge 1 commit intodoctrine:1.8.xfrom
Closed
fix: use @psalm-template annotation to avoid clashes#345redjam13 wants to merge 1 commit intodoctrine:1.8.xfrom
redjam13 wants to merge 1 commit intodoctrine:1.8.xfrom
Conversation
Member
|
Shouldn't this be fixed by doctrine/annotations#298? What version of Doctrine Annotations are you using? |
Author
|
Thanks @derrabus. Yes, so it seems The project I am working on was maybe pegged at Either way - we have inconsistent use of |
Member
|
Right, but I'd rather move forward and use the non-prefixed |
Member
|
Agree, this is a bug in |
This file contains hidden or 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
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.
[Semantical Error] The annotation "@template" in method Doctrine\Common\Collections\ArrayCollection::contains() was never imported. Did you maybe forget to add a "use" statement for this annotation?This is an issue since 1.7.3...1.8.0.
See #186. History repeating itself I think 🙂