We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Perhaps with Error Boundaries.
I haven't used them before, but they can allow us to gracefully catch problems rendering components.
Maybe @appigram can give some guidance :)
The text was updated successfully, but these errors were encountered:
Hi @ekelen . You can copy ErrorBoundry implementation from Depviz repo https://github.com/moul/depviz/tree/master/web/src/ui/components/ErrorBoundary and wrap any component, like I did for Visualizer, or wrap a whole App component to catch any app bugs, like
<ErrorBoundary> {rendererBlock} </ErrorBoundary>
You can modify ErrorBoundary component to send custom error message as prop, and/or leave error stack for main components. Hope it helps :-)
GitHubmoul/depviz👓 dependency visualizer for GitHub & GitLab (a.k.a., "auto-roadmap") - moul/depviz
Sorry, something went wrong.
moved to #2
ekelen
No branches or pull requests
Perhaps with Error Boundaries.
I haven't used them before, but they can allow us to gracefully catch problems rendering components.
Maybe @appigram can give some guidance :)
The text was updated successfully, but these errors were encountered: