Removed default configuration of deprecated rules.

[caghand]

Fixes #410.
I could have set all deprecated rules to "false". But instead, I have dropped them completely. I did not want to interfere with any rule configurations that the user might have customized elsewhere.

[msftclas]

All committers have signed the CLA.

[caghand]

I had to go back to my original idea of setting all deprecated rules to "false". Otherwise, validate-config is failing because rules are missing from config. In the next major revision, ideally, all of these deprecated rules should be scrubbed from the rule repository completely.

[JoshuaKGoldberg]

LGTM :)

[HamletDRC]

@JoshuaKGoldberg @caghand
Do you need a release?

Also, check out the final commit. The recommended ruleset is generated by the source file, so you turn rules off in the source code of that rule.

[HamletDRC]

final commit is here: ed832e7

[caghand]

Thank you for the fix! :)
Well, it would be nice to have a release, because we would be able to get rid of the warnings in our build. It would fix #410 basically.
Are you planning to release 5.0.3 soon?

[vreality64]

Is there any news about 5.0.3 release ? I'm waiting for version 5.0.3 ~ 😃

[iangregsondev]

me too :-) I notice I have the following being displayed. I presume that this commit fixes that - right ?

Warning: no-duplicate-case rule is deprecated. Replace your usage with the TSLint no-duplicate-switch-case rule.
Warning: no-stateless-class rule is deprecated. Replace your usage with the TSLint no-unnecessary-class rule.
Warning: no-var-self rule is deprecated. Replace your usage with the TSLint no-this-assignment rule.
Warning: valid-typeof rule is deprecated. Replace your usage with the TSLint typeof-compare rule.

[caghand]

@vreality64 and @appsolutegeek: Version 5.0.3 has been released. And you are right, this commit (and the associated release) fixes the warnings you are seeing.