docs(en): merge docs-cn/sync-docs into docs-cn/dev @ 30df9417#963
docs(en): merge docs-cn/sync-docs into docs-cn/dev @ 30df9417#963docschina-bot wants to merge 5 commits intodevfrom
Conversation
Co-authored-by: Ari Perkkiö <ari.perkkio@gmail.com>
❌ Deploy Preview for cn-vitest failed.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: eb3262d76f
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| <<<<<<< HEAD | ||
| - **类型:** `<T>(value: T, message?: string) => asserts value` | ||
| - **Alias** `ok` | ||
| ======= |
There was a problem hiding this comment.
This commit leaves raw conflict markers (<<<<<<<, =======, >>>>>>>) in published docs content (for example here, and repeated across many files in the same commit such as api/expect.md, config/sequence.md, and guide/cli.md). That indicates the merge was not actually resolved, so readers will see broken mixed content and any CI checks that enforce clean merges/content can fail. Please pick one side (or a true manual merge) and remove the markers everywhere.
Useful? React with 👍 / 👎.
| ::: tip Agent Reporter | ||
| This reporter is well optimized for AI coding assistants and LLM-based workflows to reduce token usage. It is automatically enabled when no `reporters` option is configured and Vitest detects it is running inside an AI coding agent. If you configure custom reporters, you can explicitly add `minimal` or `agent`: | ||
|
|
||
| :::code-group |
There was a problem hiding this comment.
A ::: tip Agent Reporter container is opened here, then a nested :::code-group is closed, but the outer tip is never closed before ### Blob 报告器. In VitePress-style markdown containers this can swallow subsequent sections into the tip block and break page structure/rendering. Add a closing ::: for the tip after the code-group block.
Useful? React with 👍 / 👎.
| toMatchTrimmedSnapshot(received: string) { | ||
| return toMatchSnapshot.call(this, received.slice(0, 10)) |
There was a problem hiding this comment.
The matcher is changed to toMatchTrimmedSnapshot(received: string) (no length argument), but the same snippet still calls toMatchTrimmedSnapshot(10) later. That makes the example internally inconsistent and can produce TypeScript errors for readers who copy it (extra argument no longer matches the declared matcher API). Either keep the length parameter or update the callsite to match the new signature.
Useful? React with 👍 / 👎.
5 participants
此 PR 自动生成。
合并 vitest-dev/docs-cn 的修改至本仓库（@ 30df941）
以下文件存在冲突，可能需要重新翻译：
请解决所有冲突后提交到此 pull request，可直接在 Github 修改、切换到 sync-30df9417-1 分支进行修改或者使用 Github Desktop 拉取此 pr 修改并提交。
禁止使用 Squash Merge 来合并此 Pull Request！
使用该操作会导致上游仓库的内容丢失，并致使下一次合并产生冲突。