Context
Several Vue components (e.g. step-row-editor.vue, added in #1204) include an empty <style scoped></style> block at the end of the file. This is dead weight — harmless but adds no value and is copy-pasted boilerplate rather than an intentional choice.
Goal
Investigate whether an ESLint rule (via eslint-plugin-vue or a custom rule) can flag/auto-fix empty <style> blocks in .vue files under ui/menu-website/src/, so future components don't carry this pattern forward.
Notes
- Check
eslint-plugin-vue's rule set first for anything close (e.g. rules around empty blocks) before writing a custom rule.
- If a suitable rule doesn't exist, a small custom ESLint rule or a Vue-SFC-aware lint check would work.
- Low priority / nice-to-have — not blocking any current work.
Context
Several Vue components (e.g.
step-row-editor.vue, added in #1204) include an empty<style scoped></style>block at the end of the file. This is dead weight — harmless but adds no value and is copy-pasted boilerplate rather than an intentional choice.Goal
Investigate whether an ESLint rule (via
eslint-plugin-vueor a custom rule) can flag/auto-fix empty<style>blocks in.vuefiles underui/menu-website/src/, so future components don't carry this pattern forward.Notes
eslint-plugin-vue's rule set first for anything close (e.g. rules around empty blocks) before writing a custom rule.