Currently, none of the ObServe structures are very tolerant of exceptions. They don't catch them, so when they occur, they propagate upward, interrupting the data flow.
This can render an ObServe-backed application completely unusable because its state is inconsistent across data views.
I need to go through ObServe line-by-line and add exception handling so that exceptions occurring in listeners, filters, transformations, etc. can be handled and reported, but not propagated. This may require some architecture enhancements to handle internal exceptions.
As an example, if there is a filter on a collection which throws an exception for a particular element, the filtered collection should act as if that element is filtered out.
Currently, none of the ObServe structures are very tolerant of exceptions. They don't catch them, so when they occur, they propagate upward, interrupting the data flow.
This can render an ObServe-backed application completely unusable because its state is inconsistent across data views.
I need to go through ObServe line-by-line and add exception handling so that exceptions occurring in listeners, filters, transformations, etc. can be handled and reported, but not propagated. This may require some architecture enhancements to handle internal exceptions.
As an example, if there is a filter on a collection which throws an exception for a particular element, the filtered collection should act as if that element is filtered out.