fix(browser): explain TypeScript support in docs and add asymmetric matchers to types by sheremet-va · Pull Request #6934 · vitest-dev/vitest (original) (raw)

Description

This PR adds more examples on how to make TS see expect.* types and also adds missing asymmetrict matchers type definitions:

expect(elements).toEqual([ expect.toHaveTextContent('First'), expect.toHaveTextContent('Second'), ])

(Asymmetric definitions only support Elements, they don't support locators yet)

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.