fix(store): enable throwing errors from selectors by default #2111
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit updates the
suppressErrors
configuration property to default to falsy.Consequently, if the selector function throws a type error (such as when accessing a
property unsafely), the error will now be thrown.
selectSnapshot
will throw synchronously, while errors fromselect
will be thrownasynchronously because the RxJS error reporter operates within a
setTimeout
.We log errors in development mode to assist developers in identifying selectors that have thrown.
This change is breaking and is part of the v4 release preparation.