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

Readout all available rules & options #674

Closed
manuelhuber opened this issue Sep 21, 2015 · 6 comments
Closed

Readout all available rules & options #674

manuelhuber opened this issue Sep 21, 2015 · 6 comments

Comments

@manuelhuber
Copy link

Hello,
is there a good way to readout all current rules & their options? I'm working on a TSLint Plugin for Sonar and currently the Rules are all entered manually wich is obviously far from perfect. A simple json or xml file would be good.
Greetings
Manuel

@adidahiya
Copy link
Contributor

ok, I'd be happy to support some kind of "schema" JSON or XML file (it could live in docs/) that describes all the rule names & options, but it would need a more detailed proposal that describes its format / structure.

@alexkrauss
Copy link

The main obstacle here seems to be #629: Currently, rule configuration is basically untyped, and there is no sensible way of specifying the allowed rule arguments formally.

@jkillian
Copy link
Contributor

Instead of a schema JSON or XML file, I'm thinking that rule options should be specified in code somehow. Maybe something sort of like how TypeScript does it, except that each rule would contain it's own metadata instead of having one file like this.

@jkillian
Copy link
Contributor

Experimental rule option schemas implemented on the next-rule-metadata branch

@jkillian
Copy link
Contributor

#1311 should help with this, each rule will now contain a schema for its options

@adidahiya
Copy link
Contributor

All the rules now have metadata. There is also a tslint:all configuration that enables (almost) all of them.

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

4 participants