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

fix(experimental-utils): treat RuleTester arrays as readonly #2601

Merged
merged 1 commit into from Sep 28, 2020

Conversation

danielnixon
Copy link
Contributor

Similar story to #2232 and #2235

@typescript-eslint
Copy link
Contributor

Thanks for the PR, @danielnixon!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!


🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day.

@danielnixon danielnixon changed the title fix(experimental-utils): Treat RuleTester arrays as readonly fix(experimental-utils): treat RuleTester arrays as readonly Sep 25, 2020
@bradzacher bradzacher added the bug Something isn't working label Sep 25, 2020
Copy link
Member

@bradzacher bradzacher left a comment

Choose a reason for hiding this comment

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

thanks for doing this!

@bradzacher bradzacher merged commit 8025777 into typescript-eslint:master Sep 28, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants