Open tronguye opened 9 months ago
Yes
6.2.0
8.45.0
18.16.0
yarn 1.22.19
Windows 10 Enterprise version 22H2
await renderResult?.findBy* is reporting testing-library/await-async-queries, even though the query is in fact getting awaited
await renderResult?.findBy*
Add code like
it('...', async () => { let renderResult: RenderResult | undefined; renderResult = render(<div>text</div>); expect(await renderResult?.findByText('text')).toBeDefined(); ));
expect
No response
{ ..., plugins: [ ..., 'eslint-plugin-testing-library' ], rules: { ..., 'testing-library/await-async-queries': 'error' } }
testing-library/await-async-queries
No
Thanks for reporting. Indeed, the rule doesn't take optional chaining into account properly. Bear in mind that's a really strange way of asserting if the element is present tho.
Have you read the Troubleshooting section?
Yes
Plugin version
6.2.0
ESLint version
8.45.0
Node.js version
18.16.0
package manager and version
yarn 1.22.19
Operating system
Windows 10 Enterprise version 22H2
Bug description
await renderResult?.findBy*
is reporting testing-library/await-async-queries, even though the query is in fact getting awaitedSteps to reproduce
Add code like
expect
, when we are in fact awaiting the returned promise of findByTextError output/screenshots
No response
ESLint configuration
Rule(s) affected
testing-library/await-async-queries
Anything else?
No response
Do you want to submit a pull request to fix this bug?
No