Skip to content
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.

Task: simplify uses of createFailure #1867

Closed
4 tasks done
andy-hanson opened this issue Dec 14, 2016 · 5 comments
Closed
4 tasks done

Task: simplify uses of createFailure #1867

andy-hanson opened this issue Dec 14, 2016 · 5 comments

Comments

@andy-hanson
Copy link
Contributor

andy-hanson commented Dec 14, 2016

As of #1845, noUnusedVariableRule.ts and objectLiteralKeyQuotesRule.ts are the only rules using createFailure directly. We should look into simplifying these.

edit: other rules using createFailure:

  • banTypesRules.ts
  • importSpacingRule.ts
  • noFloatingPromisesRule.ts
  • noStringThrowRule.ts
@nchen63
Copy link
Contributor

nchen63 commented Mar 6, 2017

we can remove the deprecated functions now.

@nchen63 nchen63 self-assigned this Mar 27, 2017
@nchen63
Copy link
Contributor

nchen63 commented Mar 28, 2017

having second thoughts on removing the deprecated functions, which would break almost all 3rd party rules. I think we should leave these in.

@adidahiya
Copy link
Contributor

@nchen63 that's a good point; let's add a deprecation warning in the console in 5.0 though?

@nchen63
Copy link
Contributor

nchen63 commented Mar 29, 2017

taking out of 5.0 release since we can deprecate later in 5.x, and we're still using the addFailure in some files

@nchen63 nchen63 removed this from the TSLint 5.0 milestone Mar 29, 2017
@adidahiya
Copy link
Contributor

fair enough

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants