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

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented Nov 8, 2017

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.

Other than improved ergonomics if a failure occurs during setup or teardown, there should be no perceived changes from this PR...

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`.
@Turbo87
Copy link
Member

Turbo87 commented Nov 8, 2017

CI is unhappy... 😞

the automatic stack stitching that is done by Chrome

not sure what this means. do you have a screenshot?

Other than improved ergonomics if a failure occurs during setup or teardown, there should be no perceived changes from this PR...

what do you mean by "improved ergonomics"?

@rwjblue
Copy link
Member Author

rwjblue commented Nov 8, 2017

Ya, I’ll grab a screenshot to show what I mean shortly.

@rwjblue
Copy link
Member Author

rwjblue commented Nov 28, 2017

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.

I believe that I may have been suffering from the poor ergonomics that emberjs/ember.js#15871 is addressing. Closing for now, will revisit if this isn't solved by an Ember bump...

@rwjblue rwjblue closed this Nov 28, 2017
@rwjblue rwjblue deleted the use-settimeout-for-forced-async branch November 28, 2017 22:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants