Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Support rules that require type information #335

Closed
ccjmne opened this issue Oct 30, 2019 · 3 comments
Closed

Support rules that require type information #335

ccjmne opened this issue Oct 30, 2019 · 3 comments

Comments

@ccjmne
Copy link

ccjmne commented Oct 30, 2019

Hey guys,

I am trying to use custom rules, some of which require type information.
These rules are disregarded in Atom, and the console outputs warnings such as:

Warning: The 'rx-ninja-subscribe-takeuntil' rule requires type information.

I have read through most of the related documentation and I think enabling "semantic rules" should solve my issue... but it doesn't.
I have tried disabling/reenabling the package, restarting Atom itself, but nothing seemed to help.

Using tslint --project . in the CLI instead works just fine...

What am I not understanding, or doing wrong?

@ccjmne
Copy link
Author

ccjmne commented Oct 30, 2019

I also just realised my usage of deprecated methods isn't pointed out to me...
I tried cranking up its severity to error in my tslint.json to see if it would be displayed, but it still doesn't. Maybe something is very broken with my setup!

For the record, once again, using tslint from the command line does give me the deprecation warnings (or errors, when the severity is set as such).

I am very lost and could really use some help.
I would be very grateful to be pointed in the right direction!

@ccjmne
Copy link
Author

ccjmne commented Oct 30, 2019

Following up on this:

It's only a problem on my end. It has to do with all the configuration Angular's CLI sets up — starting a new, fresh, empty, plain TS project works just fine, as one would expect.

I'm gonna leave this Issue open for a day or two, just in case somebody has any idea what could be the cause of the symptoms I experience...

If I figure it out, I'll answer myself :)

@ccjmne
Copy link
Author

ccjmne commented Oct 30, 2019

Okay, after further fiddling with everything, it appears the extends property isn't picked up/acted upon.

That would be a duplicate of #231.

@ccjmne ccjmne closed this as completed Oct 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant