Skip to content
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

Add a lint rule for classes to have no "Uncategorized" classes in the package #8032

Closed
astares opened this issue Dec 10, 2020 · 1 comment · Fixed by #8033
Closed

Add a lint rule for classes to have no "Uncategorized" classes in the package #8032

astares opened this issue Dec 10, 2020 · 1 comment · Fixed by #8033

Comments

@astares
Copy link
Member

astares commented Dec 10, 2020

If one or more class tags exist in the package but a class is not using it or not tagged with an own class tag then the system browser shows this class as "Uncategorized".

image

This can for instance easily happen when you have an uncategorized/untagged class is in the package and a manifest class gets added (which is usually categorized in "Manifest").

We should provide a lint rule that checks this.

To heal the situation the user should put the class into one of the existing tag categories or create a custom one (like "Base", if there is no other name)

@astares
Copy link
Member Author

astares commented Dec 10, 2020

System should lament on the situation like this:

image

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

Successfully merging a pull request may close this issue.

1 participant