-
-
Notifications
You must be signed in to change notification settings - Fork 192
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 Excalibur promise implementation with browser implementation #994
Comments
Looks like we also need to add |
Hello again! I am sorry, bear with me. :D Could you look into this, please? |
@LoserAntbear Adding Please send a PR, as long as the new implementation of |
You could be even more specific I think and do es2015.promise or something
like that.
…On Wed, Jun 13, 2018, 06:41 Erik Onarheim ***@***.***> wrote:
@LoserAntbear <https://github.com/LoserAntbear> Adding lib: [es2015, dom]
makes sense to me.
Please send a PR, as long as the new implementation of ex.Promise backed
by the _nativePromise behaves in a similar way to the old one (the tests
should be a good indicator) that's what we want.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#994 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAiaazzM7l-QRtCdaSJCHrJtUv6UE-Vbks5t8PpNgaJpZM4UJLMu>
.
|
Closes #994 ## Changes: - Retarget to es2015 from es5 for browser promises (without polyfill) - Replace Excalibur `ex.Promise` with built in browser promise - Refactor loader - Fix tests, subtle changes needed to be made because callbacks are now on the microtask queue
Context
Currently we have a basic functioning custom promise implementation, but this prevents new browser features like
async
/await
from working natively. Additionally we will get a bunch of promise features for free by switching to native promises. It may also come with a bonus of closing these #533 #365 #341Proposal
lib: ES2018.Promise
ex.Promise
implementation to wrap the native one.ex.Promise
and use the native Promise returns (this will be a breaking change, unless use theex.Promise
wrapper, there can be no easy transition unless we rename methods)The text was updated successfully, but these errors were encountered: