Skip to content

chore: remove unused code #16815

New issue

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

Merged
merged 1 commit into from
Mar 5, 2025
Merged

chore: remove unused code #16815

merged 1 commit into from
Mar 5, 2025

Conversation

aslilac
Copy link
Member

@aslilac aslilac commented Mar 5, 2025

Remove unused variables and imports from several files

@aslilac aslilac added the hotfix PRs only. Harmless small change. Only humans may set this. label Mar 5, 2025
@aslilac aslilac added hotfix PRs only. Harmless small change. Only humans may set this. and removed hotfix PRs only. Harmless small change. Only humans may set this. labels Mar 5, 2025
@brettkolodny brettkolodny self-requested a review March 5, 2025 20:50
Copy link
Contributor

@brettkolodny brettkolodny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚢

@aslilac aslilac merged commit deb95f9 into main Mar 5, 2025
38 checks passed
@aslilac aslilac deleted the lilac/remove-unused branch March 5, 2025 20:53
@github-actions github-actions bot locked and limited conversation to collaborators Mar 5, 2025
Comment on lines -1 to -9
/**
* @file A global error boundary designed to work with React Router.
*
* This is not documented well, but because of React Router works, it will
* automatically intercept any render errors produced in routes, and will
* "swallow" them, preventing the errors from bubbling up to any error
* boundaries above the router. The global error boundary must be explicitly
* bound to a route to work as expected.
*/
Copy link
Member

@Parkreiner Parkreiner Mar 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aslilac @brettkolodny Why was this comment deleted?
Up until 2 months ago, we had a broken error boundary for over a year, because the setup doesn't follow standard React and isn't as obvious as it could be

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aslilac will have to give a definitive answer on this. I mistakenly assumed that the comment was related to the import below it that was deleted which is my bad for not reading it fully.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
hotfix PRs only. Harmless small change. Only humans may set this.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants