Skip to content

Issues: jonaskello/tslint-immutable

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.

Sign up for GitHub

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

12 Open 85 Closed
12 Open 85 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

"no-expression-statement" should allow super() call in constructors
#147 opened Aug 7, 2019 by karol-majewski
1
Split readme up into smaller files. fixed in eslint port This issue has been fixed in github.com/jonaskello/eslint-plugin-ts-immutable
#142 opened Jun 21, 2019 by RebeccaStevens
@jonaskello
5
Some tests fail with node v12. bug
#141 opened Jun 19, 2019 by RebeccaStevens
Class member mutation in constructors is seen as initialization when it may not be. [no-object-mutation] bug
#126 opened Mar 12, 2019 by RebeccaStevens
New option ignore-interface-prefix on readonly-keyword rule new rule option
#123 opened Mar 8, 2019 by jonaskello
3
Enforce ReadonlySet over Set, and ReadonlyMap over Map fixed in eslint port This issue has been fixed in github.com/jonaskello/eslint-plugin-ts-immutable
#109 opened Dec 22, 2018 by astorije
2
[Discussion] Are there any compile-time performance costs to have readonly everywhere? discussion
#93 opened Aug 26, 2018 by kirillgroshkov
1
"readonly-array": [true, "ignore-local"] should not affect interface definitions
#87 opened Aug 1, 2018 by geon
Mutable prefix for indexer interfaces
#75 opened Feb 20, 2018 by jonaskello
1
Prefer ReadOnly<T> over readonly keyword transferred to eslint port This issue has been transferred to github.com/jonaskello/eslint-plugin-ts-immutable
#58 opened Dec 10, 2017 by elldritch
5
Rule Idea: no-break, no-if, no-loops fixed in eslint port This issue has been fixed in github.com/jonaskello/eslint-plugin-ts-immutable help wanted
#54 opened Sep 28, 2017 by kevinSuttle
7
Prefer type literal over interface transferred to eslint port This issue has been transferred to github.com/jonaskello/eslint-plugin-ts-immutable
#4 opened Mar 16, 2017 by goodmind
5
ProTip! Find all open issues with in progress development work with linked:pr.