Replies: 2 comments
-
You can use a UI store or manage a map where the key is the entity id, and the value is the error. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Sure. I think it would be a nice addition, fwiw. Not something I have time to issue a PR, for, though. Thanks for the response. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm submitting a...
Current behavior
Is there a way to flag a specific entity as being in error vs the entire store being in error?
If you have a container component that, say, iterates a bunch of entities and creates a new component for each and each component allows inline editing of that entity, is there any way to distinguish errors for entity 1 from errors for entity 2, etc.?
Without that, I think that each component will need to subscribe to the update call AND add the appropriate pipes to the observable in order to catch errors specific to their item, instead of just using an async pipe for errors associated with their own item.
Expected behavior
Something like:
And then in the component for the individual entity:
What is the motivation / use case for changing the behavior?
To allow for simpler error handling with EntityStores and queries.
Beta Was this translation helpful? Give feedback.
All reactions