Do not infer getArrayResult for now#592
Merged
ondrejmirtes merged 1 commit into1.4.xfrom Jun 30, 2024
Merged
Conversation
ondrejmirtes
force-pushed
the
revert-array-result
branch
from
fa08709 to
ff616fe
Compare
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
1 participant
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.
/cc @VincentLanglet With @janedbal we decided not to release this alongside the huge changes from #506.
I'm worried about the impact of #506 and I want to minize it. There's nothing wrong with your PR but it surfaces some issues we should solve first (and that are already present in object hydration to be fair).
I'd love if we could make phpstan-doctrine understand that
where/andWherecan make a selected field non-nullable for example.