This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 885
Support yaml configuration #1598
Comments
yeah, that'd be nice. stylelint uses cosmiconfig, which I'm tracking as an enhancement here #1071. accepting PRs :) |
@remcohaszing We actually support comments in our configuration JSON files. Yes, technically outside of the standard, but it's useful! 😄 |
JSON comments help a lot! 😄 However, I'd still prefer yaml support. 😉 |
4 tasks
+1 |
jhanschoo
added a commit
to jhanschoo/tslint
that referenced
this issue
Nov 1, 2017
jhanschoo
added a commit
to jhanschoo/tslint
that referenced
this issue
Nov 1, 2017
jhanschoo
added a commit
to jhanschoo/tslint
that referenced
this issue
Nov 1, 2017
jhanschoo
added a commit
to jhanschoo/tslint
that referenced
this issue
Nov 5, 2017
jhanschoo
added a commit
to jhanschoo/tslint
that referenced
this issue
Nov 6, 2017
jhanschoo
added a commit
to jhanschoo/tslint
that referenced
this issue
Nov 6, 2017
jhanschoo
added a commit
to jhanschoo/tslint
that referenced
this issue
Nov 7, 2017
ajafff
pushed a commit
that referenced
this issue
Nov 8, 2017
Fixed by #3433 |
HyphnKnight
pushed a commit
to HyphnKnight/tslint
that referenced
this issue
Apr 9, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be nice if the configuration file could be written in yaml format instead of json.
why? Unlike json, yaml supports comments.
why? Both eslint and stylelint support this. It's nice if linters support similar configuration files.
The text was updated successfully, but these errors were encountered: