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
valid-describe should support describe.each #336
Comments
I'm wondering if this should be a separate rule? ( Just b/c the domains are nicely encapsulated - otherwise |
I think conceptually it doesn't make sense to separate them, even though the implementation might be a bit big. But branching inside of it into what's essentially to separate rules can work? Without increasing implementation complexity |
It doesn't bail out anymore, it has false positives |
Yeah huh I thought I closed this already 🤷♀ |
False positives is worse than bailing 😛 |
Well then make an issue 😜 I thought I fixed all the false positives? |
As per #334,
valid-describe
currently doesn't supportdescribe.each
, instead just bailing out.The text was updated successfully, but these errors were encountered: