This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
[New feature] Add more info links to the output #17
Comments
webschik
added a commit
that referenced
this issue
Apr 13, 2019
From v1.16.0 each rule contains a property |
Hi @MVrachev , My mistake, To the JSON output https://palantir.github.io/tslint/formatters/json/ I can pass only a |
So, that means that still, we can't access the "descriptionDetails" property from the command line? One solution I think will be to pass "descriptionDetails" string into the failure string. |
Yes |
This was referenced Apr 15, 2019
mergify bot
pushed a commit
to securesauce/precaution-beta
that referenced
this issue
Apr 26, 2019
Because TSLint doesn't provide us with reference links and doesn't have an API for such metadata as explained by the developer of tslint-config-security: webschik/tslint-config-security#17 All rules are documented as part of the README for tslint-config-security on GitHub, therefore we can use this documentation to provide reference links. When we have documentation of JavaScript/TypeScript issues will educate our users on how to prevent future mistakes again. Signed-off-by: Martin Vrachev <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It will be really useful to have "more info about the issue" field in the output.
Maybe you don't want to overwhelm the default human-readable output of TSLint but maybe you can add this into the JSON output?
I see that the JSON output provides a lot of information then more info information will be really cool.
You already have good documentation about every rule so it won't be hard to do.
PS: I have seen a few linters that do that - Bandit for Python is one example and I am helping with the Gosec for golang to do just that.
The text was updated successfully, but these errors were encountered: