Support using="-android viewmatcher", value="<JSON>"

appium/appium-espresso-driver#516

like appium/appium#12372

Acceptance Criteria:

• Ruby
• Python
• Java
• C#
• WebdriverIO ?
• wd ?

Most of the documentation has been rewritten recently. The content minimum content we need is there but there is a lot that can be done to improve it.

If you'd like to contribute to the semantic-release project, helping with the following would be much appreciated:

• Fix typo, misspelling and gramatical mistakes
• Improve language: make short and simpler sentences, improve clarity
• Harmoniz

ISSUE TYPE

• Feature Idea

SUMMAR

Yeah, to be totally honest, I already thought we did this! 😅 This is the intended behavior, so we'll need to fix that. Thanks for reporting!

Originally posted by @simskij in containrrr/watchtower#647 (reply in thread)

Documentation Is:

• Missing
• Needed
• Confusing
• Not Sure?

E

Current behavior

Some tasks in the Task Library require a user to provide certain pieces of configuration as part of the initialization method. Whenever we can, we should try to avoid this because it means that those variables are locked it at the time the Flow is built, instead of at runtime, which prevents the use of Parameters or Secrets

With the support of type-hints Python signatures can give information on the type of returned values of a method. This could be used to improve the documentation generated by libdoc.

def my_func(foo: str, count: int) -> str: will give the following in the Argument column:
foo: str, count: int
This could be expanded to include the type of the returned value:
foo: str, count: int -> str

It would be nice to pass multiple actions to a checkIf method , the same way as a check allows through the comma.

So, for example, instead of writing this:

.check(
   checkIf("${first.exists()}")(do_first),
   checkIf("$first.exists()}")(do_second), 
   checkIf("${first.exists()}")do_third)

it would be nice to have API as follows:

check(checkIf("${first.exists()}")(do