This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of zone.js.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
6d31734feat(electron/nw): fix #533, in electron/nw.js, we may need to patch both browser API and nodejs API, so we need a zone-mix.js to contains both patched API.
ac7b046feat(promise a+) fix #591, make ZoneAwarePromise pass promise a+ test (#592)
9e81037fix(node): patch crypto as macroTask and add test cases for crypto, remove http patch (#612)
7665e5atest(fix): fix flaky test setInterval in android 4.4 (#611)
437ab4edocs: Document non standard web apis (#610)
33d0d8dfix(minification): fix #607 to change catch variable name to error/err (#609)
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
zone.js just published its new version 0.7.7.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of zone.js. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 14 commits .
8af21b5
chore: release v0.7.7
808f6fd
feat: allow tasks to be canceled and rescheduled on different zone in a zone delegate
47962df
fix(patch): check timer patch return undefined (#628)
f300658
docs(core): add standard api document (#625)
35aeb68
docs(core): remove old example, update counting example with new API (#624)
6731ad0
feat: make fetch() zone-aware without triggering extra requests or uncatchable errors. (#622)
d6772e2
refactor(node): patch nextTick with more general patchMicroTask method (#617)
9818139
feat: add Zone.root api (#601)
6d31734
feat(electron/nw): fix #533, in electron/nw.js, we may need to patch both browser API and nodejs API, so we need a zone-mix.js to contains both patched API.
ac7b046
feat(promise a+) fix #591, make ZoneAwarePromise pass promise a+ test (#592)
9e81037
fix(node): patch crypto as macroTask and add test cases for crypto, remove http patch (#612)
7665e5a
test(fix): fix flaky test setInterval in android 4.4 (#611)
437ab4e
docs: Document non standard web apis (#610)
33d0d8d
fix(minification): fix #607 to change catch variable name to error/err (#609)
See the full diff.
Screencast
Try it today. Free for private repositories during beta.