Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
aslilac merged 1 commit intomainfromlilac/remove-unused
Mar 5, 2025
Merged

chore: remove unused code#16815

aslilac merged 1 commit intomainfromlilac/remove-unused
Mar 5, 2025

Conversation

aslilac
Copy link
Member

Remove unused variables and imports from several files

Copy link
Contributor

@brettkolodnybrettkolodny left a comment

Choose a reason for hiding this comment

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

🚢

@aslilacaslilac merged commitdeb95f9 intomainMar 5, 2025
38 checks passed
@aslilacaslilac deleted the lilac/remove-unused branchMarch 5, 2025 20:53
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsMar 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

@ParkreinerParkreinerMar 6, 2025
edited
Loading

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 freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@brettkolodnybrettkolodnybrettkolodny approved these changes

@ParkreinerParkreinerParkreiner left review comments

Assignees

@aslilacaslilac

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@aslilac@brettkolodny@Parkreiner

[8]ページ先頭

©2009-2025 Movatter.jp