mirror of
https://github.com/deepseek-ai/deepseek-harness
synced 2026-08-15 21:04:50 +00:00
ec601ca13d
Machine-produced by `pnpm run rescope-vendor --apply` plus the regeneration it prints: `pnpm install` for the lockfile, `pnpm run gen-third-party-notices`, `verify-translation-pairing --write` for the touched bilingual pairs, `gen-doc-graphs`, and one typert snapshot whose ids embed character offsets. `pnpm run rescope-vendor --check` verifies the result. Renames nine vendored packages (cordis, cosmokit, schemastery and the six @cordisjs plugins) and every reference that resolves them: manifest names and dependency keys, module specifiers including declare-module merges, cordis.yml plugin names, tsconfig paths, every Markdown fence, and `docs/` prose. Directory names, upstream versions, and dependency ranges are unchanged, so vendor/README.md still reads as an upstream snapshot; its manifest table gains an upstream-name column so THIRD_PARTY_NOTICES keeps MIT attribution pointed at each fork's origin. The tutorial tier follows the rename end to end: its yaml fences named plugins the Loader can no longer resolve, its `ts ignore-check` fences disagreed with the compiled fences beside them, and its prose quoted both. The contracts that told readers to keep upstream names — the root convention and the vendoring cookbook's tree comment and manifest invariant — now say to rescope instead. Two rules read `@deepseek-ai/` as "another workspace plugin": the client bundle purity gate now names the vendored libraries a browser bundle inlines, and the files where a bare `cordis` is an agent-preset id keep that product data.
85 lines
2.8 KiB
Markdown
85 lines
2.8 KiB
Markdown
# 5. 配置
|
||
|
||
[English](05-config.md) | 中文
|
||
|
||
`cordis.yml` 中的每个 Cordis 配置项都可以携带 `config` 块，插件则声明一个 schema，在运行 `apply` 前验证该块。错误配置会导致加载失败，并给出准确的错误：插件绝不会在配置不完整时启动。
|
||
|
||
## 可配置插件
|
||
|
||
创建 `config-demo.ts`，并将其放在 `tmp/cordis-tutorial` 中：
|
||
|
||
```ts
|
||
import type { Context } from '@deepseek-ai/cordis'
|
||
import Schema from '@deepseek-ai/schemastery'
|
||
|
||
export const name = 'config-demo'
|
||
|
||
export interface Config {
|
||
greeting: string
|
||
targets: string[]
|
||
}
|
||
|
||
export const Config: Schema<Config> = Schema.object({
|
||
greeting: Schema.string().default('Hello'),
|
||
targets: Schema.array(String).default(['world']),
|
||
})
|
||
|
||
export function apply(ctx: Context, config: Config) {
|
||
for (const target of config.targets) {
|
||
console.log(`${config.greeting}, ${target}!`)
|
||
}
|
||
}
|
||
```
|
||
|
||
导出的 `Config` 既是 TypeScript 接口，也是同名的运行时 schema：消费方获得类型，Cordis 获得验证器。本仓库使用 [Schemastery](https://github.com/shigma/schemastery) 定义 schema；Cordis 本身接受任意 [Standard Schema](https://standardschema.dev/) 验证器，因此将普通对象导出为 `Config` 无法工作。
|
||
|
||
对其进行配置：
|
||
|
||
```yaml
|
||
- name: './config-demo.ts'
|
||
config:
|
||
targets: ['alpha', 'beta']
|
||
```
|
||
|
||
运行：
|
||
|
||
```
|
||
Hello, alpha!
|
||
Hello, beta!
|
||
```
|
||
|
||
未提供 `greeting`，因此 schema 默认值会将其补齐：`apply` 始终会收到完整且经过验证的配置。
|
||
|
||
## 明确报错
|
||
|
||
现在向它传入无效内容：
|
||
|
||
```yaml
|
||
- name: './config-demo.ts'
|
||
config:
|
||
targets: 'not-an-array'
|
||
```
|
||
|
||
```
|
||
ValidationError: invalid config:
|
||
- $.targets expected array but got not-an-array (at targets)
|
||
```
|
||
|
||
插件的 fiber 进入 FAILED 状态，本教程的启动器打印错误后以状态码 1 退出。如果某个插件的配置通过了 schema 验证，但其中指定的资源或提供方不可用，该插件也应当在能解析该引用时立即拒绝。
|
||
|
||
## 计算得到的配置值
|
||
|
||
本仓库使用的 loader 支持 `!!js` 标签，用于必须在加载时计算的配置值：
|
||
|
||
```yaml
|
||
- name: './config-demo.ts'
|
||
config:
|
||
greeting: !!js process.env.DEMO_GREETING ?? 'Hello'
|
||
```
|
||
|
||
`!!js` **仅在 `config` 内有效**。Cordis 配置项的元数据（`name`、`id`、`disabled`、`inject` 等）是静态的；`disabled: !!js ...` 会生成一个真值表达式对象，始终禁用该 Cordis 配置项。详见 [loader 配置](../cordis-primer.md#loader-configuration)。
|
||
|
||
下一章：[组合与 HMR（热模块替换）](06-composition-and-hmr.md)：将 `cordis.yml` 视为应用。
|
||
|
||
[](https://github.com/deepseek-ai/deepseek-harness-sdk)
|