no-standalone-expect: False positive when there are multiple describe blocks

[michaelfaith]

If using nested describe blocks to organize multiple sets of tests, the expect calls within the it tests in the describe blocks after the first, are causing no-standalone-expect to flag them incorrectly.

describe('base', () => {
  it('top level test', async () => {
    expect... // << this one doesn't flag
  });

  describe('nested', () => {
    it('nested test', async () => {
      expect... // << this one flags no-standalone-expect (false positive)
    });
  });
});

Note: if the test function is test instead of it, then it also doesn't flag. It only seems to impact tests that use it

[mskelton]

Interesting, sounds like an issue with the aliases not applying in all instances for some reason.

[mskelton]

@michaelfaith I was unable to reproduce this. Could you create a reproduction code sandbox?