Introduce `resumeTest` to complement `pauseTest`? about rfcs HOT 11 CLOSED

Note: To make the Final Comment Period official, we need to announce it here and on Twitter, so we're restarting the period now.

This RFC is now entering a "final comment period". This period is intended to focus the community's attention for a final round of consideration and feedback before an RFC is merged.

Please carefully consider the implications of this RFC and how it will affect your Ember projects. Now would be a good time to re-raise any concerns that you feel haven't been fully addressed.

If no significant blockers are raised by October 7, we plan to merge this RFC and make plans for its implementation.

from rfcs.

Closing this issue in favor of emberjs/ember.js#13663

from rfcs.

The implementation that I have seen was a gist from @stefanpenner, maybe he still has it handy?

from rfcs.

There was also this in the original PR (seems to have gone largely unnoticed): emberjs/ember.js#9383 (comment)

from rfcs.

https://gist.github.com/stefanpenner/0baadd08d0733f9e8ae0#file-pause-test-js although that example uses a getter, which may or may not be of value.

from rfcs.

Would a PR adding this into core be welcome? If so, I'll pull it together with some tests

from rfcs.

I'm not certain how well making a change and resuming will work in practice, but this would be pretty low hanging fruit to add behind a feature flag and experiment with. I'd be +1 to see a PR. :-D

from rfcs.

Agree

from rfcs.

I'm not certain how well making a change and resuming will work in practice

True, but at the very least this will enable the ability to use more than one pauseTest to walk through an Acceptance test (which means I can stop using andThen(() => { debugger; })).

from rfcs.

I'm not certain how well making a change and resuming will work in practice,

its less about resuming after a change, and more about being able to emulate debugger, without blocking the entire thread of execution. I can say with confidence this pause/resume works really well with acceptance tests. So +1 from me.

from rfcs.

FCP didn't drum up any additional feedback, and we are still 👍 on the feature. Lets do it!

from rfcs.