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

[New]no-unused-state: Support ignore option#3881

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

Open
fwgood wants to merge1 commit intojsx-eslint:master
base:master
Choose a base branch
Loading
fromfwgood:no-unused-state-ignore

Conversation

fwgood
Copy link

This is adding a new propertyignore to ignore specific state.

@fwgoodfwgood closed thisJun 27, 2025
@ljharb
Copy link
Member

Sorry this fell through the cracks. Can you elaborate a bit more on the problem this will solve?

@ljharbljharb reopened thisJun 27, 2025
@fwgood
Copy link
Author

fwgood commentedJun 28, 2025
edited by ljharb
Loading

Sorry this fell through the cracks. Can you elaborate a bit more on the problem this will solve?

@ljharb I'm very glad that you can reopen this PR.

In some React frameworks that use JSX, certain specific states are defined for internal rendering purposes (such as marking rendering stages, measuring performance, etc.). There is a similar usage pattern where the state is not consumed by the developers but is consumed by the framework internally. In this case, an ignore rule is needed (the usage of links uses hooks, which is different from class-based states, but the principle is similar).https://lynxjs.org/guide/performance/evaluating-performance.html

@ljharb
Copy link
Member

I'm not familiar with Lynx but this is eslint-plugin-react - it's intended for use with a react codebase, not any jsx codebase.

Unfortunately that link doesn't explain the use case to me - but it doesn't make sense to me that you'd declare state that you don't personally set - if the framework is assigning state, it should be declaring it.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@fwgood@ljharb

[8]ページ先頭

©2009-2025 Movatter.jp