Skip to content

ref: Error on no-unused-expressions, no-empty-object-type, no-restricted-syntax and no-unsafe-function-type lint rules#1472

Open
lforst wants to merge 2 commits intomainfrom
lforst/more-lint-rules
Open

ref: Error on no-unused-expressions, no-empty-object-type, no-restricted-syntax and no-unsafe-function-type lint rules#1472
lforst wants to merge 2 commits intomainfrom
lforst/more-lint-rules

Conversation

@lforst
Copy link
Contributor

@lforst lforst commented Mar 2, 2026

Ref: #1405

The no-restricted-syntax is a weird one because we are like full on violating it seemingly intentionally - opted to just ignore the instances we have.

Fixes #1473

…stricted-syntax` and `no-unsafe-function-type` lint rules
@lforst
Copy link
Contributor Author

lforst commented Mar 2, 2026

api compat check is failing but I think it should be fine... (?) - we're merely changing interface -> type which I have never seen go wrong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix no-unused-expressions, @typescript-eslint/no-empty-object-type, @typescript-eslint/no-unsafe-function-type, no-restricted-syntax

1 participant