Skip to content
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

remove array-type eslint rule #1028

Merged
merged 3 commits into from
Oct 14, 2024
Merged

remove array-type eslint rule #1028

merged 3 commits into from
Oct 14, 2024

Conversation

iisaduan
Copy link
Member

@iisaduan iisaduan commented Jul 3, 2024

The "array-type":"error" behavior, seems to have changed in the most recent typescript-eslint release, and as a result, it is generating new errors.

With the addition of the default setting, the error message also becomes wrong:
image

@jakebailey
Copy link
Member

jakebailey commented Jul 3, 2024

Isn't this error right? Readonly of array is not ReadonlyArray and that's usually always a mistake...

This will also disable the style rule we prefer on DT (not that I like it myself)

@iisaduan
Copy link
Member Author

iisaduan commented Jul 3, 2024

Isn't this error right? Readonly of array is not ReadonlyArray and that's usually always a mistake...

The error message changes when you remove the default, so at least one of the messages are wrong

image

@iisaduan
Copy link
Member Author

iisaduan commented Jul 5, 2024

typescript-eslint/typescript-eslint#9498 I filed a bug

Copy link
Member

@jakebailey jakebailey left a comment

Choose a reason for hiding this comment

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

Removing it seems fine, but this PR needs a changeset and test fixes.

@jakebailey
Copy link
Member

Updated the PR so we can get it in.

@jakebailey jakebailey merged commit 9f35009 into microsoft:main Oct 14, 2024
7 checks passed
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.

3 participants