Interesting benefit of the `tapAction` modifier in...

# compose

[Fudge]

Interesting benefit of the tapAction modifier in SwiftUI.

Text("hello")
.tapAction { println("tapped") }

Over

Clickable(onClick = { println("tapped") }){
     Text("hello")
}

You get { println("tapped") } over
(onClick = { println("tapped") })

[Andrey Kulikov]

it will not be required to write "onClick =" though

[Fudge]

Why not?

[Fudge]

Oh right, because you don't need to name it

[Andrey Kulikov]

yes, it is optional here

[Fudge]

Not naming the argument is arguably worse though

Clickable ( { println("tapped") }){
     Text ("hello")
}

And you will need to name it if there is some other arguments.
Anyway the point is you get to take advantage of the trailing lamda syntax

[Andrey Kulikov]

They also had such example in the video

Button(action: {}) {
   Text("Add room")
}

In Compose it is almost the same

Button(onClick = {}) {
   Text("Add room")
}

[Andrey Kulikov]

not sure then why do they provide both ways of adding click callbacks, with wrapping and with a modifier

[voddan]

For me this example with clicking is a clear argument in favor of the Compose approach. In SwiftUI an element is tappable (can have on-click), while in Compose a whole region is clickable (can contain multiple elements). IMO the Compose approach is more general and also is close to the intuitive understanding of how a GUI works.