Remove optional field from selectors
#2014
Merged
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
bartekpacia
force-pushed
the
optional_arg_testing
branch
from
9470c11
to
60738c2
Compare
bartekpacia
force-pushed
the
optional_arg_testing
branch
from
60738c2
to
a2bf764
Compare
axelniklasson
approved these changes
Sep 5, 2024
|
(for @mobile-dev-inc employees only) I did a quick search of "optional" in our monorepo (LINK). Didn't find many usages. The list of Maestro commands visible in this view: 
is returned by Rollout action items
|
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.
The selector-level
optionalargument has been superseded by the command-leveloptionalargument in #1946.This PR is a follow up of #1946 (specifically, this comment)