Skip to content

issues Search Results · repo:playwright-community/eslint-plugin-playwright language:TypeScript

Filter by

200 results
 (57 ms)

200 results

inplaywright-community/eslint-plugin-playwright (press backspace or delete to remove)

TypeScript reports the following error after upgrading eslint from 9.28.0 to 9.29.0: Error: scripts-eslint/eslint_plugin_playwright.js:6:16 - error TS2375: Type { rules: { guard-for-in : off ; new-cap ...
  • doberkofler
  • Opened 
    3 hours ago
  • #367

This rule underlines the whole test yellow, even when the developer is still authoring the test. It makes for so much visual noise and increases the cognitive overhead of just reading my test flow especially ...
  • toduyemi
  • Opened 
    12 days ago
  • #366

no-unsafe-references rule now only targets page.evaluate method. How about to target addInitScript too? This is the same kind of method and we ran in mistakes with using variables from closure sometimes. ...
  • Raykeen
  • Opened 
    24 days ago
  • #365

If you import the test function from playwright and rename it, all expect inside the renamed test function are considered as standalone `import { test as base, expect } from @playwright/test ; base( ...
  • 2Fake
  • 2
  • Opened 
    25 days ago
  • #364

When using a conditional in the test function s metadata parameters, the no-conditional-in-test rule is triggered, even though the conditional is outside the actual test body. test( My Test , { tag: productType ...
  • touchedthecode
  • Opened 
    on May 9
  • #363

I would like to have more rules to disallow flaky locators like .allTextContents(). As far as I can see there is only a rule for .count(), but the docs have warnings for more flaky text assertions. See ...
  • eins78
  • Opened 
    on Apr 28
  • #362

After installing eslint-plugin-playwright in our workspace we see a warning every time we do a yarn install. warning Workspaces can only be enabled in private projects. This warning is caused because ...
  • Roozenboom
  • Opened 
    on Apr 14
  • #360

I m creating a custom expectation for the first time, and I m getting lint errors from the no-standalone-expect rule. My expectation is this: const expect = baseExpect.extend({ async toBeAuthenticated(page: ...
  • sazzer
  • 1
  • Opened 
    on Mar 30
  • #357

Consider these scenarios: await page.getByRole( button ).isDisabled(); expect(page.getByRole( button ).isVisible()).toBeTruthy(); If you hover over the isX methods there is some documentation ...
  • MattyBalaam
  • Opened 
    on Mar 28
  • #356

If you import the test method and rename it to something else then this lint rule will throw an error. Reproduction: import { expect, test as setup } from @playwright/test ; setup( set local state ...
  • MathiasWP
  • 4
  • Opened 
    on Mar 13
  • #355
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Press the
/
key to activate the search input again and adjust your query.
Issue search results · GitHub