Skip to content

Rule proposal: no-nested-components #249

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
michalsnik opened this issue Nov 26, 2017 · 2 comments
Closed

Rule proposal: no-nested-components #249

michalsnik opened this issue Nov 26, 2017 · 2 comments

Comments

@michalsnik
Copy link
Member

Style guide:
https://vuejs.org/v2/style-guide/#Tightly-coupled-component-names-strongly-recommended

Description:
This rule would warn about nested components, as it is recommended to keep components directory flat, for reasons explained in the style guide.

@chrisvfritz
Copy link
Contributor

Hm, I'm not sure this rule would actually have value. We do mention in the detailed explanation that for larger applications, some limited nesting is probably OK, so it's not a "hard" rule. Also, it would be difficult to accidentally nest components and also difficult to miss nesting in a code review, so I'm guessing it would possibly take up more time to configure than it would save.

@michalsnik
Copy link
Member Author

You're right @chrisvfritz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants