v0.9 Cleanup ​

This release is technical. It includes only deletions of deprecated features and general refactoring of the API. This release intentionally does not include any new features, so you can upgrade your codebase without any pressure.

Migration guide ​

There are a bunch of breaking changes, but they are all minor and should not affect your code much. Furthermore, they are the soundness as promised. Please read the migration guide carefully before upgrading.

Do not use externalCache adapter ​

externalCache adapter was deprecated in 0.8, write your own adapter instead by recipe.

Read-only Stores and Events ​

Events finished.* have never been supposed to be called in application code. Now they are read-only. In case you call them, you will get a warning in console in Effector 22 and exception in Effector 23.

Stores $data, $error, $status, $idle, $pending, $succeeded, $failed, $enabled have never been supposed to be changed in application code directly. Now they are read-only. In case you change them, you will get a warning in console in Effector 22 and exception in Effector 23.

Separate Event for Query cancelation ​

Cancelled Queries were treated as failed before this release. We have added a separate Event .aborted to Query to distinguish between cancelation and failure. It is recommended to use .aborted instead of .finished.failure to handle cancelation.

supressIntermediateErrors in retry operator ​

Before this release, retry operator was marking Query as failed on every failed attempt. Since v0.9 it accepts options supressIntermediateErrors to overwrite this behavior. If true, then the Query will not be marked as failed until the last attempt is failed.

Re-worked Sourced internal implementation ​

Before Sourced fields internally were represented as Stores with a final value of a field, which value changes fast right before read. This scheme was based on Effector's computation priority and served well for a long time. But it had a few drawbacks:

• It could be easily broken by minor changes in Effector itself. And we plan such changes in the future major releases of Effector (e.g. experimental phasing, batching improvements, combine improvements, etc.);
• It led to race-conditions in some cases (e.g. simultaneously started Query created by attachOperation).

After v0.9 Sourced fields internally is represented as Stores with a function return final value of a field. It is more stable and less error-prone.

If you use normalizeSourced or combineSourced in your code, you may need to update it to the new API. Examples can be found in the PR. Since normalizeSourced and combineSourced are low-level undocumented functions, we do not provide a migration guide for them.

Full changelog ​

0.9.0 ​