docs: clarify use of hasOption()#54415
Merged
Merged
Conversation
`hasOption()` does not check whether the command has been _called_ with the given option, but rather whether the command even _accepts_ the option.
shaedrich
reviewed
Jan 30, 2025
Co-authored-by: Sebastian Hädrich <11225821+shaedrich@users.noreply.github.com>
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
3 participants
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.
hasOption()does not check whether the command has been called with the given option, but rather whether the command even accepts the option.i.e. it is not like
request()->has('option')https://laravel.com/docs/11.x/requests#input-presence