One thing that annoys/worries me is that Crank seems to unrender everything when a runtime error is thrown during component execution. The sucky thing is that once we throw an error from a generator function, the function exits, so unlike other frameworks where components are just functions that get executed all the time, there isn’t really a nice way to recover.
At the very least, I want components to error gracefully, so the last valid render is shown. We could also consider logic to restart generator functions somehow, though this could be problematic, leading to weird infinite loops or swallowed errors which developers don’t notice.
One thing that annoys/worries me is that Crank seems to unrender everything when a runtime error is thrown during component execution. The sucky thing is that once we throw an error from a generator function, the function exits, so unlike other frameworks where components are just functions that get executed all the time, there isn’t really a nice way to recover.
At the very least, I want components to error gracefully, so the last valid render is shown. We could also consider logic to restart generator functions somehow, though this could be problematic, leading to weird infinite loops or swallowed errors which developers don’t notice.