no-standalone-expect rule triggered when calling assertions in expect.extend blocks for custom matchers

[nickhall]

When writing custom matchers using the code provided by the docs, the calls to baseExtend are flagged by the no-standalone-expect rule.

import { expect as baseExpect } from '@playwright/test';

const expect = baseExpect.extend({
  async someMatcher() {
    // triggers the error
    await baseExpect(true).toBeTruthy();
  }
}

I would expect that this scenario wouldn't trigger the rule.

[carlbray]

You might need to declare aliases https://github.com/playwright-community/eslint-plugin-playwright/blob/main/README.md#aliased-playwright-globals

{
  "settings": {
    "playwright": {
      "globalAliases": {
        "test": ["myTest"],
        "expect": ["myExpect"]
      }
    }
  }
}

[nickhall]

Thank you, I think that should handle this use case.