Skip to content

Commit 9ece275

Browse files
committed
docs: flesh out resource error problem description
1 parent f8152f4 commit 9ece275

2 files changed

Lines changed: 4 additions & 2 deletions

File tree

docs/docs/with-entity-resources.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,8 @@ This exposes per-resource members with the resource name as a prefix:
8888

8989
## Error Handling
9090

91-
The behavior of Angular's resources' error handling and the NgRx SignalStore's `getState/patchState` required `withEntityResource` to handle error handling with a particular strategy.
91+
The behavior of Angular's resources' error handling and the NgRx SignalStore's `getState/patchState` required `withEntityResource` to approach error handling
92+
with a particular strategy unique to the intersection of resources and the Signal Store.
9293
To prevent resource failures from blocking the store, the Toolkit provides some strategies to handle errors.
9394

9495
```ts

docs/docs/with-resource.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,8 @@ With named resources, each resource gets prefixed properties:
8585

8686
## Error Handling
8787

88-
The behavior of Angular's resources' error handling and the NgRx SignalStore's `getState/patchState` required `withResource` to handle error handling with a particular strategy.
88+
The behavior of Angular's resources' error handling and the NgRx SignalStore's `getState/patchState` required `withResource` to approach error handling
89+
with a particular strategy unique to the intersection of resources and the Signal Store.
8990
To prevent resource failures from blocking the store, the Toolkit provides some strategies to handle errors.
9091

9192
```ts

0 commit comments

Comments
 (0)