vue/html-closing-bracket-spacing (and more) does not work for top-level tags

[CyanSalt]

Currently vue/html-closing-bracket-spacing only reports issues in the template, not issues with SFC top-level tags. This behavior is consistent with the implementation, but I'm not sure if this is intentional by design. I would like this rule to support a new option to check and report issues in top-level tags.

What rule do you want to change?

vue/html-closing-bracket-spacing and vue/html-closing-bracket-newline. Maybe there are others, I'm not sure.

Does this change cause the rule to produce more or fewer warnings?

Yes, it may add warnings. But we can also prevent breaking changes with a new option.

How will the change be implemented? (New option, new default behavior, etc.)?

This rule currently contains an object option, so it looks like we just need to add a checkTopLevelTags: true option. Further, this option should probably become the default behavior in the next major release.

Please provide some example code that this change will affect:

What does the rule currently do for this code?

What will the rule do after it's changed?

You can compare line 4 and line 16 of this demo to confirm this issue.

<script setup >
//           ↑ should be reported
</script>

[FloEdelmann]

Interestingly, both rules actually already work for the top-level <template> tag (and even include test cases for that), but not for other top-level tags.

I'd say that this is a bug and it shouldn't be an option but a new default behavior. A new major release is due soon anyway (see #1850), so even if this is considered a breaking change, it would be a good time.

@ota-meshi, what do you thing?

[ota-meshi]

I think it's good to change those rules and apply the rules to the top level tags 👍