You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It was discovered that the following code does not produce a lint error.
describe('something',()=>{beforeEach(()=>{// TODO});test('should test something',()=>{expect(true).toBe(false);});});
It is desired to have a blank line between the beforeEach and test blocks.
I first went down the route of debugging padding-line-between-statements thinking that I configured multiline-block-like incorrectly, but that wasn't it. Turns out, multiline-expression causes it to fire an error correctly, but forces us to put blank links after a slew of other things we don't want to care about too.
It was discovered that the following code does not produce a lint error.
It is desired to have a blank line between the
beforeEach
andtest
blocks.I first went down the route of debugging padding-line-between-statements thinking that I configured
multiline-block-like
incorrectly, but that wasn't it. Turns out,multiline-expression
causes it to fire an error correctly, but forces us to put blank links after a slew of other things we don't want to care about too.That lead to some googling and discovery of jest-community/eslint-plugin-jest#17, which ultimately led to the promise land of https://github.com/dangreenisrael/eslint-plugin-jest-formatting.
We should look to incorporate that here.
The text was updated successfully, but these errors were encountered: