We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
lowercase-name
ignoreTopLevelDescribe
describe
The ignoreTopLevelDescribe option for lowercase-name rule, added in #611, seems to only apply to the first describe block in a file.
e.g. 'Booleans' gets flagged as a rule violation here:
'Booleans'
describe('Strings', () => { it('are strings', () => { expect('abc').toBe('abc'); }); }); describe('Booleans', () => { it('are booleans', () => { expect(true).toBe(true); }); });
The text was updated successfully, but these errors were encountered:
fix(lowercase-name): ignore all top level describes when option is true
4b8089d
closes #613
Whoops that's my bad - I forgot to decrease the describe counter when going back up the nest 😬
Sorry, something went wrong.
fix(lowercase-name): ignore all top level describes when option is tr…
624018a
…ue (#614) closes #613
chore(release): 23.17.1 [skip ci]
e4e828d
## [23.17.1](v23.17.0...v23.17.1) (2020-06-23) ### Bug Fixes * **lowercase-name:** ignore all top level describes when option is true ([#614](#614)) ([624018a](624018a)), closes [#613](#613)
🎉 This issue has been resolved in version 23.17.1 🎉
The release is available on:
Your semantic-release bot 📦🚀
Successfully merging a pull request may close this issue.
The
ignoreTopLevelDescribe
option forlowercase-name
rule, added in #611, seems to only apply to the firstdescribe
block in a file.e.g.
'Booleans'
gets flagged as a rule violation here:The text was updated successfully, but these errors were encountered: