-
Notifications
You must be signed in to change notification settings - Fork 52
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
replace children sugar #232
Labels
Comments
This will help with some of the semantics in discussion over on RedPotion. infinitered/redpotion#63 |
we have a few places that we replace all the views when something happens (like a user enters their weight, and we want to remove an empty state and show a current state, I could see this being a bit cleaner with something like this in place. In my case its messy either way, I think - but this might be less messy :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jamon and I discussed this new feature, you can do this now with rmq, but this is symantically very nice:
replace_children
will simply remove all children, then returnrmq(@my_view)
, which can be used with Jamon's new do syntax. So really replace children is just a nicer way to dormq(@my_view).children.remove.back
(assuming that works with remove).What do you fellow contributors think?
The text was updated successfully, but these errors were encountered: