Description:
I encountered a rendering error while working with ClojureScript (cljs). The error was caused by a mistake in the attribute map, where I mistakenly passed children. Unfortunately, without the ErrorBoundary class component, it was challenging to debug the issue effectively.
When I attempted to run the code without the ErrorBoundary, all I received was an empty slot without the DOM mounted, accompanied by a cryptic React error message. Clicking on the message only led me to compiler-generated code, which wasn't very helpful in diagnosing the problem.
I believe implementing an ErrorBoundary on defscene would greatly improve the situation. This would localize the error, allowing it to be captured within the ErrorBoundary.
Description: I encountered a rendering error while working with ClojureScript (cljs). The error was caused by a mistake in the attribute map, where I mistakenly passed children. Unfortunately, without the ErrorBoundary class component, it was challenging to debug the issue effectively.
When I attempted to run the code without the ErrorBoundary, all I received was an empty slot without the DOM mounted, accompanied by a cryptic React error message. Clicking on the message only led me to compiler-generated code, which wasn't very helpful in diagnosing the problem.
I believe implementing an ErrorBoundary on defscene would greatly improve the situation. This would localize the error, allowing it to be captured within the ErrorBoundary.