Work around vue/one-component-per-file violations
What does this MR do?
Work around vue/one-component-per-file violations
We don't currently violate this rule at all, but the rule does find some false positives due to a loose heuristic. This is tracked upstream as https://github.com/vuejs/eslint-plugin-vue/issues/1411.
Addresses #297217 (closed).
Screenshots (strongly suggested)
n/a
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
- [-] Documentation (if required)
-
Code review guidelines - [-] Merge request performance guidelines
-
Style guides - [-] Database guides
-
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. - [-] Tested in all supported browsers
- [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Edited by Mark Florian