[8.x] Remove an useless check in Console Application class #40145
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.
What I do?
I create this PR as a re-open PR of #40133
Why I do this?
@GrahamCampbell said I was incorrect but I was NOT incorrect.
! isset($callingClass) && empty($parameters)
is true, this line below will be executed and the$input
will be an instance of StringInput.$input
will be an instance of ArrayInput.Conclusion
To conclude, there are no cases of this context in which the
$input
isn't set, it's always set. Therefore, the check$input ?? null
is absolutely useless.If the Laravel team rejects this PR, it will be your final decision and I understand. But rejecting this PR doesn't mean my PR is incorrect. It's reasonable.
Let's see the method more details: