-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Component Action #62
Comments
Thanks a lot for the kind words, really glad to hear. 😀 For the moment, LeeGo support such kind of // Retrieve target view from hierarchy based on a configured key in `Brick`,
// then either manipulate object directly or keep it into a class property with
// weak reference, just as `IBOutlet`
let likeButton = tweetView.lg_viewForOutletKey("likeButton")
likeButton.addTarget(...) Since this approach let people manipulate directly instance which could introduce easily more mutable states and complexity, which isn't encouraged by LeeGo's philosophy, so we may use declarative blockable actions to replace it in the future release. What you think? |
Exactly. I would think declarative blocks should be the way to go. I and my colleague would be happy to contribute some as we love the work and the concept you've done so far. I believe we could make this one of the best componentKit out there. Sent from my iPhone
|
Yeah, totally cool. It would be great if you'd like to contribute, PR is always welcomed. 👍 |
Hi Wang,
Congrats on the great tool, nicely done !! I was wondering what's your plan for providing actions for components, like Button, swipe, tap, or anything? Blockable actions?
The text was updated successfully, but these errors were encountered: