From b0ebb34d0bda71372ad0e8c7e62b564ca825af0b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andi=20P=C3=A4tzold?= Date: Wed, 11 Oct 2023 12:10:22 +0200 Subject: [PATCH] docs: typo in v6 migration guide MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The rules are called `no-await-sync-query` and `no-await-sync-queries` Signed-off-by: Andi Pätzold --- docs/migration-guides/v6.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/migration-guides/v6.md b/docs/migration-guides/v6.md index 05557e2b..bc885a59 100644 --- a/docs/migration-guides/v6.md +++ b/docs/migration-guides/v6.md @@ -10,7 +10,7 @@ If you are not on v5 yet, we recommend first following the [v5 migration guide]( - `await-async-events` is now enabled by default for `fireEvent` in Vue and Marko shared configs - `await-async-events` is now enabled by default for `userEvent` in all shared configs - `await-async-query` is now called `await-async-queries` -- `no-await-async-query` is now called `no-await-async-queries` +- `no-await-sync-query` is now called `no-await-sync-queries` - `no-render-in-setup` is now called `no-render-in-lifecycle` - `no-await-sync-events` is now enabled by default in React, Angular, and DOM shared configs - `no-manual-cleanup` is now enabled by default in React and Vue shared configs @@ -25,6 +25,6 @@ If you are not on v5 yet, we recommend first following the [v5 migration guide]( - Removing `testing-library/no-wait-for-empty-callback` if you were referencing it manually somewhere - Renaming `testing-library/await-fire-event` to `testing-library/await-async-events` if you were referencing it manually somewhere - Renaming `testing-library/await-async-query` to `testing-library/await-async-queries` if you were referencing it manually somewhere -- Renaming `testing-library/no-await-async-query` to `testing-library/no-await-async-queries` if you were referencing it manually somewhere +- Renaming `testing-library/no-await-sync-query` to `testing-library/no-await-sync-queries` if you were referencing it manually somewhere - Renaming `testing-library/no-render-in-setup` to `testing-library/no-render-in-lifecycle` if you were referencing it manually somewhere - Being aware of new rules enabled or changed above in shared configs which can lead to newly reported errors