- Make glint template an optional peer dependency (#572)
- Update assert in task-public-api.js to include note about required Babel transform for arrow functions (#569)
- Ember Concurrency is now a V2 Embroider Addon (#551)
- BREAKING CHANGE: you must now register the Babel transform used by Ember Concurrency within consuming apps and addons
- See upgrade docs: https://ember-concurrency.com/docs/v4-upgrade
- BREAKING CHANGE: you must now register the Babel transform used by Ember Concurrency within consuming apps and addons
- The guides have been updated to reflect modern/best practices:
- Instead of using the
(perform)
helper, it is now recommended that the bound.perform()
method on each Task be directly invoked in the template, e.g.{{on "click" this.myTask.perform}}
, or, when arguments are present,{{on "click" (fn this.myTask.perform 123 'foo')}}
- Instead of using the
- Glint template registry has been provided for EC's 3 helpers.
- Add ember 5 as peerDependencies (#542)
- Support waitFor()-type modifiers in async arrow transform (#536)
- Drop now-unneeded dependency on polyfill for unsupported Ember versions
- [docs] Fix broken code block rendering for examples (#522, #524)
- Drop support for Node versions below version 16 (#520)
- Add support and tests for Ember 4 (#515)
- Minimum supported Ember version is now 3.28+ (but still likely to work for lower versions)
- TypeScript: use the types published directly from Ember.js (#512)
- Mention native class requirement in un-transpiled task() error (#494)
- Additional fix for Babel transpiler conflict with ember-cli-code-coverage / istanbul (#492)
- Fix Babel transpiler conflict with ember-cli-code-coverage (#490)
- Bugfix: observers stopped working in 2.3.0+ (#487)
- Fix types for the async arrow API for
dropTask
,restartableTask
, and others (#486)
- Simplify the async arrow fn task() API to allow omitting the
this
param, e.g.myTask = task(async () => {})
(#477)
- Add runtime assertion to detect transpilation failures with the new async arrow fn API
- Introduce async-arrow task() API as the new universal JS/TS API, e.g.
myTask = task(this, { drop: true }, async (arg: string) => {})
. This new API sidesteps the vast majority of TypeScript issues that plagued past decorators- and generators- based APIs. All prior APIs are still supported, but users are strongly recommended to migrate to the new API. Recommended steps:- Finish migrating any classes with EC tasks to ES6 class syntax
- Once you've done that, use the following codemods on any
app/
oraddon/
folders that are using Ember Concurrency tasks- Convert
@task
decorator based APIs to the new async-arrow fnnpx machty-ember-concurrency-codemods async-arrow-task app/**/*.ts app/**/*.js
- If you've used
ember-concurrency-ts
, run the following codemod to removetaskFor()
npx machty-ember-concurrency-codemods rm-ember-concurrency-ts app/**/*.ts app/**/*.js
- Convert
- The
ember-concurrency-ts
andember-concurrency-async
packages are no longer needed and can be removed - Soft-deprecated (removed from documentation, likely to formally deprecate later)
a number of less commonly used features
- Encapsulated Tasks
- Task Groups
- Added missing TypeScript types for
onState
task modifier andTaskFactory#setOnState
(#449, fixed #447. Thanks @johanrd for the heads up!)
- Implemented a public API for Task Modifiers,
providing a way for users to define additional modifiers and behavior in
application code. (#441) Please consider the
TaskProperty
prototype extension method of implementing task modifiers to be deprecated in favor of theregisterModifier
API. - Add
onError
parameter toperform
helper to allow UI-triggered tasks to specify alternative or null error handlers (#443, fixes #435. Thanks @lolmaus for the discussion) - Fix inefficent use of
run.once
(#442, fixes #437. Thanks @stefanpenner for the heads up!)
- Same as 2.1.1, but with the changes actually published.
- Expose
TaskInstance
state inside encapsulated tasks (#434) - [dev] use prettier to format code (#415, thanks @alexlafroscia!)
- [dev] test against embroider scenarios (#430, thanks @alexlafroscia!)
- Implemented a public API for Yieldables, a new way to instrument TaskInstances by providing a safe mechanism to implement custom waiters, hooks, introspection, and other operations from application code. (#413)
- Avoid applying task state updates out of order (#423, #426, fixes #422)
- [docs] Document that
@lastValue
does not support chained property access (#429)
- Remove runloop binding for
perform
andcancel-all
helpers, preventing proper instrumentation. (#414, fixes #409) - Fix incorrect import for deprecated private
task-instance
module alias (#411, thanks @mydea!) - [dev] Upgrade qunit to v5 (#410, thanks @alexlafroscia)
- [docs] Fix missing jsdoc documentation (#407)
- Ensure
lastRunning
resets one-by-one as tasks are completed, successfully or not. (Fixes #403) - Expose
lastValue
decorator in TS definitions (Fixes #406)
- Prevent synchronous errors in cancelable promise helpers from being rethrown asynchronously later (#402, fixes #400. thanks @Turbo87 for flagging!)
- Restore access to host context from encapsulated tasks (#401)
- No substantive changes from 2.0.0-rc.2
- Make
Task#cancelAll
andTaskInstance#cancel
awaitable (#396). See topic in UPGRADING-2.x.md for more info. - Fix
TaskProperty
extension methods not working with built-in decorators (e.g.ember-concurrency-retryable
,ember-concurrency-test-waiters
, etc.) - [dev] Add test for interop w/ ember-concurrency-decorators
- [dev] Migrate CI to GitHub Actions (#393)
-
Implement decorators from
ember-concurrency-decorators
. The "nice" decorators fromember-concurrency-decorators
are now built-in to ember-concurrency, without requiring an additional addon or separate import. All decorators are available for import directly from the top-levelember-concurrency
package.Addon maintainers: Please see notes in
UPGRADING-2.x.md
if you're using decorators currently, and wish to support both ember-concurrency 1.x and 2.x at runtime. -
[docs] Rewrite documentation to use native classes and decorators, and update tutorial to show rewriting of async function code, rather than Promise code, as is more common today.
-
Migrate task lifetimes to
@ember/destroyable
underneath, rather than patchingwillDestroy
(#377).Potentially breaking: this drops support for Node 8 and Ember < 3.8 LTS
-
Ensure encapsulated task state can be accessed on the TaskInstance (#381, #383)
Note: this uses
Proxy
andWeakMap
, which may need to be polyfilled on IE 11. -
Make sure task/group-level
state
field is tracked (#382) -
Drop unused
broccoli-file-creator
andember-maybe-import-regenerator
dependencies.Note on
ember-maybe-import-regenerator
: This was originally added back when generator support in browsers was far lower and Babel 5 and 6 were used. The addon does nothing for Babel 7, which is used forember-concurrency
these days. Tweakingconfig/targets.js
or adding the regenerator Babel plugin to your babel config can be done instead if the regenerator runtime is needed to transpile generators for older browsers. -
[dev] Upgrade Ember-CLI to 3.22 (#380)
-
Port over changes from 1.1.6 through 1.3.0 (#367)
-
Use
@tracked
underneath on Ember 3.16+ (#354)Note: Within applications with both tracked & computed properties, if using a native getter to access task state, and wishing to use it alongside a computed property, @dependantKeyCompat will need to be used on the getter as expected with any other tracked-prop using getter.
-
Remove ability to directly use tasks with
{{action}}
helper stuff (deprecated in 1.3.0) (#374) -
Fixes the deprecated
-task-property
module (for compatibility w/ some external addons).TaskProperty
is available at the top-level. -
Remove
get
andset
compatibility methods fromTask
,TaskGroup
, andTaskInstance
.
Documentation about upgrading to 2.0.0-beta.1 and other future 2.x releases in general can be found in UPGRADING-2.x.md
-
Add
animationFrame
yieldable helper. YieldinganimationFrame()
will pause a task until after the next animation frame using the nativerequestAnimationFrame()
browser API.Note: ember-concurrency tasks are scheduled on the runloop, so this will not cause the remainder of the task to instead run during the next animation frame, but the runloop after the next animation frame.
-
Add
hashSettled
helper for cancellation-aware implementation of RSVP'shashSettled
(#353, thanks @kwliou!) -
Add missing types for
linked()
andunlinked()
(#373) -
Deprecate direct usage of task with action helper and disable tests for it on 3.20+.
This feature unfortunately depends on private APIs that will be removed in Ember 3.25. Unfortunately, the mechanism was already removed in Ember 3.20, making it impossible to support this for releases at least until recent canaries where it was re-introduced with a deprecation. However, the feature is rarely used, only documented in this changelog, and frequently breaks whenever the private constant it depends on moves modules internally throughout new versions of Ember.
It will continue to remain available for Ember < 3.20, but will not be available in Ember-Concurrency 2.0, and will show a deprecation warning from 1.3.0 forward.
Any existing uses can be converted to using
{{perform}}
directly or wrapping the task in(perform)
before passing to{{action}}
or{{fn}}
Before:
After:
- Correct types for encapsulated tasks to allow accessing encapsulated task state (#362, thanks @chancancode!)
- Correct types to reflect that Task, TaskInstance, and TaskGroup extend EmberObject (#363, thanks @jamescdavis!)
-
Introduce official TypeScript definitions targetting the last 3 versions of TypeScript. A big, big thank you to @chancancode for this heroic effort! Also, a thank you to all others before who worked on previous iterations of typing experiments for ember-concurrency and provided feedback. **If you were using one of the community-provided solutions or other custom type definitions, you will likely need to remove those and refactor to adhere to the new official types. (#357)
For more information about using TypeScript with ember-concurrency, please see the new docs page
- Fix waitForProperty on non-EmberObject hosts (#352. Fixes #292. Thanks @andrewfan for the find!)
- Add support for
waitForEvent
helper on host objects supporting 'on' API. Previously,waitForEvent
only supported DOM-like objects withaddEventListener
/removeEventListener
or jQuery-like objects withone
/off
, but did not support those with juston
/off
. (#348. Fixes #164)
- Avoid auto-tracking rerender assertion / infinite rerender during cancelation in certain contexts in Ember 3.15+ (#341, Fixes #340)
- Avoid auto-tracking rerender assertion thrown in certain contexts in Ember 3.15+
- Fix passing tasks into
action
helper directly on Ember 2.8 (yes, 2.8)
- Fix issue where
rawTimeout
,waitForEvent
, andwaitForQueue
helper timers were not properly canceled or cleaned up in some cases, such as when used with Task-aware Promise helpers such asrace
. (#331. Fixes #309, #329) - Fix use of Tasks with
action
andfn
helpers in Ember 3.x (#312, #333. Thanks @thiagofelix for the find!) - [docs] Remove 404'd link on outdated regenerator runtime removal
- [docs] Document task syntax for use with ES native classes and Ember Octane
- Totally fix use of task groups with ES native class/Glimmer components (#324, thanks @jrjohnson)
- [dev] Add test coverage for tasks on ES native class/Glimmer components
- Fix use of task groups with ES native class components (#321, thanks @jrjohnson)
- Document and export
rawTimeout
helper in top-levelember-concurrency
module. (#310, thanks @Turbo87)
- Babel 7 (#317)
- Assert argument is an
Array
for Promise helpers (race
,all
,allSettled
) (#313, thanks @buschtoens!) - Throw an error in
waitForQueue
when queue does not exist (#314, @mydea!) - Resolve warning about colliding
ember-maybe-import-regenerator
versions (#316, thanks @jherdman!) - Fix service injection on nested encapsulated tasks on Ember 3.13+ (#318)
- Use
clearTimeout()
instead ofclearInterval()
on timer set withsetTimeout
(#309, thanks @Turbo87!) - Document options for
cancelAll()
(#305, thanks @ggayowsky!) - [dev] Upgrade Ember-CLI to 3.12 (#317)
- [dev] Upgrade ember-cli-sass to enable use on Node 12 (#299, thanks @buschtoens!)
- No changes, just a long overdue 1.0 release :)
- Fix Ember.Logger deprecations (#266)
- Add the ability to
yield forever
to pause a task indefinitely (#274) - Better error messaging for later versions of Ember (#270)
- cancelAll({ resetState: true }) can remove existing derived state (#253)
- fix issue with Ember 3.6.0+ when IE11 is not being targeted (#261)
- Fixes ember-metal related issues on Ember Canary.
- Fixes ES5 getter syntax on Ember Canary (#248)
- Adds
.evented()
task modifier and task lifecycle events.
- waitForEvent/Queue/Property helpers now work with the various
promise helpers (e.g.
all
andrace
)
- Allow passing a non-Function value to waitForProperty() as
a shortcut for waiting for the observed property to
===
that value.
- Added waitForProperty() to pause execution until a property on an Ember Object becomes a certain value.
- Revert to "old style" Ember imports in
app/
tree
- waitForEvent() support for native DOM EventTargets (instead of just Ember / jQuery objects) (#187)
- Officially release and document "Encapsulated Tasks", which are tasks that can maintain/mutate their own state without having direct access to the host object's state. In conjunction with Derived State, this allows for some nice patterns for containing state/logic/mutations within the tasks, rather than requiring that state/events generated by tasks live on / bleed into the host objects.
- Added Task.linked()/unlinked() as a means to avoid circular cancelation errors. There is no change to behavior here, but in the case that ember-concurrency detects a circular self-cancel-on-destroy scenario, it'll warn you about the issue and require you to annotate the desired behavior with linked()/unlinked(). A "circular self-cancel-on-destroy" usually occurs when a component task performs a task on a service, which causes a state change that causes the component to be destroyed, canceling the original task, thus canceling the service task.
- Added helpful error when improperly trying to perform a
task via
this.taskName.perform()
- Add
.debug()
Task Modifier and EmberENV.DEBUG_TASKS to log the reason a task is canceled, e.g. "TaskInstance 'doStuff' was canceled because the object it lives on was destroyed or unrendered"
- Support null/undefined values in cancelable promise helpers (#153)
- Added helpful link to TaskCancelation errors
- Added informative messages as to the root cause of a TaskCancelation, e.g. "TaskCancelation: TaskInstance 'doStuff' was canceled because .cancel() was explicitly called" "TaskInstance 'doStuff' was canceled because .cancelAll() was explicitly called on the Task" "TaskInstance 'doStuff' was canceled because it belongs to a 'restartable' Task that was .perform()ed again"
- Reverted some of the changes introduced in 0.8.0; in particular, while the first "slice" of a task function executes synchronously when performed, advancing the task is deferred to a run loop queue. This fixes some regressions caused by the overzealous as-sync-as-possible scheduling introduced in 0.8.0 (#148, #138)
- Removed a left-over
debugger
statement. :(
- POSSIBLE BREAKING CHANGE: the internal task scheduler
has been rewritten to be more performant, but to also
more immediately start executing task functions. Prior
to this version,
perform()
ing a task wouldn't actually start executing the task function until theactions
queue on the run loop; this behavior was inconsistent with the timing of async functions, and meant that certain lifecycle hooks that depended on logic being run synchronously couldn't be used with ember-concurrency Tasks (because they already missed their window of execution). This is unlikely to break anyone's apps, but it's possible some apps out there have subtle timing dependencies on tasks running within run loop queues, so it's better to announce this as a possible breaking change. (#107) - Derived state: Task Instances now have an additional
isSuccessful
andisError
property (#119) - Derived state: Tasks expose
performCount
that tracks how many times a task has been performed. - waitForEvent and waitForQueue for pausing the task until a jQuery / Ember event occurs, or until a particular run loop queue has been reached.
- Added the ability to extend/wrap/decorate
TaskProperty
s (the value returned fromtask()
, so that things like task test waiter APIs can be built without having to merge such functionality into the main EC repo. TL;DR, the.taskFn
property is exposed, so it can be swapped out with another generator fn with wrapping code aroundyield * originalTaskFn.call(this, arg)
(#116 + #117)
- TaskGroup.isRunning always returns a Boolean (#112)
- Fix Ember.K deprecation warnings (#110)
- The (perform) helper won't throw an error when passed a non-Task until the helper is actually invoked (e.g. a button is clicked). Previously it would error more eagerly, right at first render, which was often a poor dev experience and at odds with the (action) helper's behavior.
- Fixed Ember 2.10 error when passing (hash) helper values as an arg to a task (#99)
- Using ember-owner-polyfill to cut down on bloat
- BREAKING: revert the feature introduced in 0.7.11 for being
able to do
this.myTask.perform()
instead ofthis.get('myTask').perform()
. The internal semantics of ember-metal are too different between versions of Ember to be able to support this with any confidence; we'll just have to wait for ES5 getter syntax to come to Computed Properties in general in order to support this. Apologies for too eagerly introducing this broken feature.
- no functional changes; just removed unneeded files from NPM package to decrease package size
- fix not being able to mock tasks in tests (#84) and other related bugs
- fix tasks not being overridable in subclass (#81)
- support for
this.myTask.perform()
, i.e. you can get a reference to a Task using simple JavaScript accessors rather than having to writethis.get('myTask').perform()
- tasks can be tested in component integration tests (#66)
- deprecation: using
.maxConcurrency()
without any other task modifier will produce a deprecation warning because it is unclear/ambiguous as to how to constrain concurrency in such a case (#79)
- Add task-aware
allSettled
promise equivalent (#75)
- Adds Object.assign polyfill so that tests pass on on non-supporting browsers for apps that don't set includePolyfill:true
- Upgraded ember-maybe-import-regenerator so that other addons can consume/depend on ember-concurrency without making the end user have to make any additional configuration to support transpiled generator function syntax.
- Upgraded to more Node-backwards-compatible version of ember-maybe-import-regenerator.
- You no longer have to set
includePolyfill:true
in ember-cli-build.js as a requirement for using ember-concurrency.regenerator-runtime
is now provided by https://github.com/machty/ember-maybe-import-regenerator, which gracefully no-ops if you still want to keepincludePolyfill:true
. Babel's polyfill is 98kb minified, whereas the regenerator runtime is only 4kb minified.
- When using Ember 2.5.0 or higher, you can now pass task objects
directly to the closure
action
helper, e.g.onclick={{action myTask 1 2 3}}
. This works exactly the same asonclick={{perform myTask 1 2 3}}
but it's nice because any component that fires actions using the(action)
helper can now directly be passed a task and have it run properly, rather than having to cast to an action using the(perform)
helper.
- removed any attempt to auto-polyfill using babel.includePolyfill, fixing #57. The auto-polyfill was never working reliably so it shouldn't break anyone's code.
- (perform) and (cancel-all) helpers no longer cause run loop autoruns
- The .keepLatest() task modifier has been redocumented due to popular demand; it's useful for when you want to enqueue only the most recent intermediate .perform() and drop everything in between.
- Support for Ember 1.13.0
- within a task generator function, TaskCancelation "errors" are longer "catchable" in the catch block of a try/catch. This means you no longer have to check if the error thrown is a cancelation in order to handle it differently than an exception.
- That said, since promises have no concept of cancelation, if
you perform a task within a promise (or you call
someTask.perform().then(...).catch(...)
), then any promisecatch
handlers will be called with TaskCancelation "errors", and if you need to distinguish between cancelation and exceptions thrown, you can import and use the newdidCancel
utility function, which returns true if the error passed to it is a TaskCancelation. Previously, the only safe way to test this was to checkerr && err.name === 'TaskCancelation'
; now you can justimport { didCancel } from 'ember-concurrency'
and checkdidCancel(err)
.
- bugfix: errors that bubble throw arbitrary depths of child tasks will only call window/Ember.onerror once
- bugfix: errors thrown from child tasks don't "rethrow" when caught by parent task
- Fixed bug when using ember-concurrency in an addon that is consumed by another app. #46
- feature: Task Groups: http://ember-concurrency.com/#/docs/task-groups. Task Groups let you enforce concurrency constraints across multiple tasks, which previously wasn't possible.
- feature: Moar Derived State: http://ember-concurrency.com/#/docs/derived-state
Task Instances now expose .value and .error properties for the
value returned from the task function, or the error thrown from it.
Furthermore: Task objects expose
last
andlastSuccessful
, which point to recently performed TaskInstances, which then make it possible to idiomatically access .value and .error, e.g.{{myTask.last.value}}
or{{myTask.last.error}}
. This is a continuation of ember-concurrency's goal of exposing as much Derived State as possible, and minimizing boilerplate. - feature: .observes() Task Modifier: appending .observes('foo', 'bar') to a task will automatically perform the task when 'foo' or 'bar' changes. Thanks to @ofbriggs for co-authoring this feature.
- bugfix: once an object is destroyed, any attempts to perform a task on that object will be immediately canceled.
- experimental: support for linking tasks
- bugfix: timeout() internally uses Ember.run.later() now so that Ember testing helpers know to wait for it. Note: this means that infinite loops in tasks that pause with a timer can pause your acceptance tests until they timeout unless you break the loop somehow; one way to do this is to call Ember.run.cancelTimers()
- bugfix: fixed a few more corner cases where a TaskCancelation error unnecessarily bubbled to the top even though the user hadn't opted into handling cancelations (by calling .then() on the TaskInstance returned from task.perform()).
- bugfix: don't set taskInstance.isCanceled to true if cancel() is called after a successful finish.
- bugfix: No longer treat the most recent yield as the implicit return of a function.
- bugfix: perform helper returns the performed TaskInstance
- bugfix: perform helper properly curries arguments
- Added perform and cancel-all helper for a more familiar
approach to calling tasks from templates:
onclick={{perform taskName 1 2 3}}
andonclick={{cancel-all taskName}}
- EXPERIMENTAL: integration with observables via
subscribe
function
- Prevent promises from being swallowed in some cases
- EXPERIMENTAL: Task#performWillSucceed boolean property
- EXPERIMENTAL: TaskProperty#.performs() for linking to tasks you intend to call.
- added Task-aware/cancelable variant of Promise.race
- added Task-aware/cancelable variant of Promise.all for joining multiple child tasks.
- added task(...).cancelOn('eventName'), which calls cancelAll() on the task whenever the event is fired
- .state properties for Tasks and TaskInstances
- task.cancelAll() cancels all running/pending task instances
- taskInstance.cancel() cancels an individual instance
- Added .maxConcurrency(n) task modifier which works in conjunction with the other task modifiers.
nameOfTask.perform()
returns a Task Instance, which represents a single execution of that task which might be cancelled, dropped, or run to completion. It exposes a .cancel() method and other properties like .isRunning or .isFinished
- First stable version since re-working the docs site
- No more reliance on js-csp, or CSP concepts whatsoever