-
Notifications
You must be signed in to change notification settings - Fork 87
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
New Rule: avoid high number of export_types #539
Comments
Is that even an issue anywhere? I mean… people not defining enough types… I've seen a lot. |
I didn't come up with this; I saw it in production code. 😄 If it's not an issue, sure, it's not an issue. |
And now I want to see that code!!! |
Oh, it's not shared online 😞. But I can tell you this: it's not a god module, but it has more than 20 types 😄. When I suggested the idea, it would be for a number like that: at least 20 types. No worries, though; we'll get there. There's so much more interesting stuff to implement and fix, like that |
e.g. like
god_module
, but for-export_type
.Ideas?
The text was updated successfully, but these errors were encountered: