Searched refs:cases (Results 1 – 6 of 6) sorted by relevance
552 fun cases() { in <lambda>() method583 cases() in <lambda>()587 cases() in <lambda>()616 fun MockViewValidator.cases() { in <lambda>() method646 this.cases() in <lambda>()650 this.cases() in <lambda>()
341 … functions named differently to signify the difference in styling and use cases for those componen…448 … is usually worth the aforementioned downsides of the implicit inputs. In cases like this, compone…875 …esent, leaving the button to arrange the show. While it handles basic use cases or sample usages w…879 …resulting in the big number of overloads we have to provide in order to cater the users’ use cases.1070 …onent or its children should be perceived as an exception. There are some cases that benefit from …1092 Even in such cases like with `LazyColumn` it is possible to define the API structure without DSL, s…1253 … them for especially common cases where it would be inconvenient to write out the `semantics` bloc…1322 * New parameters MAY be added as a last parameter, or second to last in cases of trailing lambdas.
511 This section outlines patterns for addressing common use cases when designing a Jetpack Compose API.643 When designing an open or abstract class to be properly extensible for these use cases it is easy t…676 In extreme cases this can defeat the benefits of reactive UI API designs by creating multiple sourc…
50 subtle cases where state is lost. Consider the following example which splits a collection in two310 the effects of the singleton would appear in two places simultaneously. In some cases, such
203 …rameter `$changed` that is used to avoid calling `$composer.changed()` in cases where either the v…
9 performance, or adding additional use cases for `semantics`.268 Compose `semantics` API was designed to support testing and accessibility use cases at the same