Removing Elements/Nodes Asynchronously(?)

Here’s a fiddle to illustrate my use case: https://jsfiddle.net/dylanrw/mcg324a4/

Typically there isn’t a problem, if state changes, I want the irrelevant elements removed. But when it comes to animating elements before removal, it would be nice if I could begin a transition and have the removal/sorting process occur once that transition is completed, or do something to have the soon-to-be-removed element stay in place until the transition is complete (even if the other elements update). (As you see in the fiddle, if you click an element, the elements are sorted, and then the element clicked is removed at the bottom.)

I tried one experiment at @jbucaran’s encouragement where I added a lifecycle event onreorder, and I noticed that I got the results I was after by skipping the element.insertBefore in app.js#265. I wonder if something like a noreorder node attribute that does similar would work?

Thanks in advance to @jbucaran and @zaceno for their collective patience!

[jorgebucaran]

componentWillReceiveProps looks very similar to what @zaceno and I were talking about to do about #313, that is, to introduce a new lifecycle event: onpatch. 🤔

[dylan]

You can’t expect issues to be resolved in a couple of days. FYI, issues are sometimes open for longer than 3 days before anything actionable can happen.

Hopefully you didn’t consider my “waste of time” comment sarcasm or a snide remark about responsiveness, my initial writeup/problem/goals are just fuzzy enough that I was self conscious about my taking up you guys’ time.

In the future I won’t close any issues.

P.S: Also, it’s not up to you to decide if you are wasting my time or not. AFIC you are/were not wasting my time. 😉

Cool, reopen the issue if you want.

Slightly back on topic however, something like react’s componentWillReceiveProps may allow me to pull off what I was originally after, but I need to rethink how I’m approaching the problem with Hyper to better articulate things.

Thanks again!