Skip to content
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

Use setTimeout for "forced" async. #239

Closed

Commits on Nov 8, 2017

  1. Use setTimeout for "forced" async.

    Using `Ember.run.next` has a negative impact on developer ergonomics
    because we loose access to the automatic stack stitching that is done
    by Chrome (which ends up being very nice when working with `async` /
    `await`.
    rwjblue committed Nov 8, 2017
    Configuration menu
    Copy the full SHA
    30cd8ae View commit details
    Browse the repository at this point in the history