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

Enforce ReadonlySet over Set, and ReadonlyMap over Map #109

Open
astorije opened this issue Dec 22, 2018 · 2 comments
Open

Enforce ReadonlySet over Set, and ReadonlyMap over Map #109

astorije opened this issue Dec 22, 2018 · 2 comments
Labels
fixed in eslint port This issue has been fixed in github.com/jonaskello/eslint-plugin-ts-immutable

Comments

@astorije
Copy link

I am making extensive use of the readonly-array rule, and was wondering: do you happen to have any plans for equivalent readonly-set and readonly-map rules that would enforce the same constraint on Maps and Sets?

@jonaskello
Copy link
Owner

I currently have no plans to implement those rules but it sound like a really nice idea! I will see if I can get some time to implement that, and I would certainly accept a PR for those rules if someone else wants to work on it. (I currently don't use Map and Set much in my own projects as I mostly deal with state that needs to be serializable to JSON).

@astorije
Copy link
Author

That's great, thanks for the update @jonaskello!

@RebeccaStevens RebeccaStevens added transferred to eslint port This issue has been transferred to github.com/jonaskello/eslint-plugin-ts-immutable fixed in eslint port This issue has been fixed in github.com/jonaskello/eslint-plugin-ts-immutable and removed help wanted new rule transferred to eslint port This issue has been transferred to github.com/jonaskello/eslint-plugin-ts-immutable labels Jul 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed in eslint port This issue has been fixed in github.com/jonaskello/eslint-plugin-ts-immutable
Projects
None yet
Development

No branches or pull requests

3 participants