Show effect of vue/html-self-closing rule re #172 #173
Conversation
| @@ -38,6 +38,9 @@ export default [ | |||
| }, | |||
| "rules": { | |||
| "semi": ["error", "always"], | |||
| "vue/html-self-closing": [ | |||
| "error", { "html": { "void": "any" } } | |||
There was a problem hiding this comment.
If we don't like the <div> elements being touched, there should be a way to turn this off with normal: any
|
Yeah I'd say this deserves a larger discussion, as it deviates from the standard ruleset. If the change is agreed upon then it should also happen in core and whatnot. On this I guess I tend to lean in the direction that it doesn't need programmatic enforcement -- nothing's breaking right? |
|
For sure we'd do it in core, this is just opened against lingo where we have Vue code to look at. I guess I wouldn't say it deviates from the standard ruleset -- we have And then the other rules are not shown in the diff because they're not auto-fixable, but since they're emitting warnings they are part of the standard ruleset and I think we should decide whether to turn 'em up to errors. Otherwise they just become things everybody ignores. Thoughts? |
That's totally fair. For another view: |
Refs #172, just to spur discussion
see this particular "strongly recommended" rule here, but the point is that there are other rules at the warning level flying under radar