877f982924
* Use recommended pattern in testing example Since the official linter for testing library, `eslint-plugin-testing-library` recommends using `screen` to write queries, this MR updates the testing library example to follow the pattern recommended by the linter. > DOM Testing Library (and other Testing Library frameworks built on top of it) exports a screen object which has every query (and a debug method). This works better with autocomplete and makes each test a little simpler to write and maintain. > This rule aims to force writing tests using built-in queries directly from screen object rather than destructuring them from render result. Given the screen component does not expose utility methods such as rerender() or the container property, it is correct to use the render returned value in those scenarios. See the `prefer-screen-queries` rules docs for more info: https://github.com/testing-library/eslint-plugin-testing-library/blob/main/docs/rules/prefer-screen-queries.md * Update devDependencies * Install and configure test linting * Use recommended pattern in test * Update test names for consistency * Update docs * Set jest environment in each file * Use root true in `with-jest` eslint config * Ensure nested .eslintrcs are not loaded for repo lint Co-authored-by: jj@jjsweb.site <jj@jjsweb.site> |
||
|---|---|---|
| .. | ||
| advanced-features | ||
| api-reference | ||
| api-routes | ||
| basic-features | ||
| migrating | ||
| routing | ||
| authentication.md | ||
| deployment.md | ||
| faq.md | ||
| getting-started.md | ||
| going-to-production.md | ||
| manifest.json | ||
| testing.md | ||
| upgrading.md | ||