-
Notifications
You must be signed in to change notification settings - Fork 889
Missing no-duplicate-key implementation #1599
Comments
Yes, it was removed (#885) because this functionality is covered by the compiler now. Sorry I didn't get around to writing the changelog for v4.0.0-dev.0, but you can check out the milestone: https://github.com/palantir/tslint/milestone/26?closed=1 |
Thanks! Will close this then. 😃 |
@adidahiya How would one get around this issue if they were using the development branch + using |
@dsifford do you mean 4.0.0-dev.0? It was removed from the built-in configurations in that release too... https://github.com/palantir/tslint/blob/4.0.0-dev.0/src/configs/recommended.ts |
@adidahiya Hm.. Let me try again in a bit and report back. Here's my build from earlier this afternoon that failed after bumping up to And here's the commit (you'll see 4.0.0-dev.0 listed in the Let me know if I'm missing something obvious (which is generally the case!) Also, please extend my thanks to the rest of the Palantir team for all their work on this. Such a critical part of my workflow! 💯 👍 |
@adidahiya Sorry for the delay. This is an issue with All good now 👍 |
Tests: - Remove two deprecated rules in tslint.json (palantir/tslint#1599 and palantir/tslint#661)
Bug Report
4.0.0-dev0
2.0.3
Actual behavior
Expected behavior
To have a
no-duplicate-key
implementationIt's the rule
no-duplicate-key
have been remove or rename or something?The text was updated successfully, but these errors were encountered: