Bounty: Dead Code Cleanup and Code Formatting (React) - #91
Open
taherdhanera wants to merge 1 commit into
Open
Conversation
Author
|
Polite maintainer follow-up for This PR remains open, non-draft, and clean/mergeable for the dead-code cleanup and React formatting bounty. The PR body includes I know the issue is now closed, so I wanted to ask respectfully: is PR #91 still eligible for review/reward, or is there an exact blocker or reason it should be withdrawn? I can respond quickly if a maintainer wants any revision. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
/claim #55
Fixes #55.
Summary
dist/output so lint does not scan build artifacts after a production build.Validation
npm run buildnpm run lintNote: lint exits successfully. The remaining output is the repository's existing
@typescript-eslint/no-explicit-anywarnings, not new unused/dead-code errors.