fix 错误

Author: zuohuadong

.github/workflows/fix-code-blocks.yml

@@ -0,0 +1,77 @@
+name: Fix Code Blocks Daily
+
+on:
+  schedule:
+    # 每天北京时间上午 9:00 执行 (UTC+8 = UTC 01:00)
+    - cron: '0 1 * * *'
+  workflow_dispatch:
+    # 允许手动触发
+  push:
+    branches:
+      - main
+    paths:
+      - 'docs/**/*.md'
+      - 'content/**/*.md'
+
+jobs:
+  fix-code-blocks:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+    
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          
+      - name: Setup Bun
+        uses: oven-sh/setup-bun@v1
+        with:
+          bun-version: latest
+          
+      - name: Install dependencies
+        run: bun install
+        
+      - name: Fix code blocks
+        run: |
+          echo "开始修复代码块..." >> $GITHUB_STEP_SUMMARY
+          bun run fix-code-blocks 2>&1 | tee fix_output.log
+          echo "修复完成，查看详细日志..." >> $GITHUB_STEP_SUMMARY
+          echo '```' >> $GITHUB_STEP_SUMMARY
+          tail -20 fix_output.log >> $GITHUB_STEP_SUMMARY
+          echo '```' >> $GITHUB_STEP_SUMMARY
+        
+      - name: Check for changes
+        id: changes
+        run: |
+          if git diff --quiet docs/; then
+            echo "has_changes=false" >> $GITHUB_OUTPUT
+          else
+            echo "has_changes=true" >> $GITHUB_OUTPUT
+            echo "修改的文件:" >> $GITHUB_STEP_SUMMARY
+            git diff --name-only docs/ >> $GITHUB_STEP_SUMMARY
+          fi
+          
+      - name: Commit and push changes
+        if: steps.changes.outputs.has_changes == 'true'
+        run: |
+          git config --local user.email "[email protected]"
+          git config --local user.name "GitHub Action"
+          git add docs/
+          git commit -m "🔧 自动修复代码块格式 (@@filename 和 @@switch)"
+          git push
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          
+      - name: Create summary
+        run: |
+          echo "## 代码块修复结果 🔧" >> $GITHUB_STEP_SUMMARY
+          if [[ "${{ steps.changes.outputs.has_changes }}" == "true" ]]; then
+            echo "✅ 发现并修复了代码块格式问题" >> $GITHUB_STEP_SUMMARY
+            echo "- 将 \`@@filename()\` 转换为 rspress 语法" >> $GITHUB_STEP_SUMMARY
+            echo "- 删除了 \`@@switch\` 后的 JavaScript 代码块" >> $GITHUB_STEP_SUMMARY
+          else
+            echo "✅ 所有代码块格式都是正确的，无需修复" >> $GITHUB_STEP_SUMMARY
+          fi

docs/cli/usages.md

@@ -183,6 +183,7 @@ $ nest info
 | . ` | / _ \/ __|| __|    | | `--. \| |    | |     | |
 | |\  ||  __/\__ \| |_ /\__/ //\__/ /| \__/\| |_____| |_
 \_| \_/ \___||___/ \__|\____/ \____/  \____/\_____/\___/
+```
 
 [System Information]
 OS Version : macOS High Sierra

docs/cli/workspaces.md

@@ -263,6 +263,7 @@ Nest 将组织和构建标准项目及 monorepo 结构项目所需的元数据
 >   ...
 > }
 > ```
+```
 
 #### 项目专属生成选项
 

docs/contributors.md

@@ -29,13 +29,15 @@
    git clone https://github.com/YOUR_USERNAME/docs.nestjs.cn.git
    cd docs.nestjs.cn
    ```
+```
 
 2. **创建特性分支**
    ```bash
    git checkout -b feature/amazing-feature
    # 或者
    git checkout -b fix/some-bug
    ```
+```
 
 3. **进行你的修改**
    - 📝 翻译新内容或改进现有翻译
@@ -49,6 +51,7 @@
    npm run dev
    ```
    在浏览器中查看你的修改效果
+```
 
 5. **提交你的修改**
    ```bash
@@ -57,11 +60,13 @@
    # 或者
    git commit -m "fix: correct translation error"
    ```
+```
 
 6. **推送到你的分支**
    ```bash
    git push origin feature/amazing-feature
    ```
+```
 
 7. **创建 Pull Request**
    - 访问你的 Fork 仓库页面

docs/deployment.md

@@ -108,6 +108,7 @@ git push heroku main
 
 ```dockerfile
 FROM node:18-alpine
+```
 
 WORKDIR /usr/src/app
 
@@ -420,6 +421,7 @@ Sentry.init({
 ```bash
 # 启用调试模式
 DEBUG=* npm run start:prod
+```
 
 # 分析内存使用
 node --inspect dist/main.js

docs/devtools/ci-cd.md

@@ -77,6 +77,7 @@ Devtools 会为每次构建生成报告**前提是**中央注册表中已存储
 
 ```yaml
 name: Devtools
+```
 
 on:
   push:
@@ -172,6 +173,7 @@ const publishOptions = {
 
 ```yaml
 image: node:16
+```
 
 stages:
   - build

docs/faq/errors.md

@@ -10,6 +10,7 @@
 
 ```bash
 Nest can't resolve dependencies of the <provider> (?). Please make sure that the argument <unknown_token> at index [<index>] is available in the <module> context.
+```
 
 Potential solutions:
 - Is <module> a valid NestJS module?
@@ -71,6 +72,7 @@ Please make sure that the argument ModuleRef at index [<index>] is available in
 ```bash
 Nest cannot create the <module> instance.
 The module at index [<index>] of the <module> "imports" array is undefined.
+```
 
 Potential causes:
 - A circular dependency between modules. Use forwardRef() to avoid it. Read more: https://docs.nestjs.com/fundamentals/circular-dependency

docs/faq/http-adapter.md

@@ -9,7 +9,6 @@
 要从应用上下文外部获取 `HttpAdapter` 的引用，请调用 `getHttpAdapter()` 方法。
 
 ```typescript
-@@filename()
 const app = await NestFactory.create(AppModule);
 const httpAdapter = app.getHttpAdapter();
 ```
@@ -19,7 +18,6 @@ const httpAdapter = app.getHttpAdapter();
 要从应用上下文内部获取 `HttpAdapterHost` 的引用，可使用与其他现有提供者相同的注入技术（例如通过构造函数注入）。
 
 ```typescript
-@@filename()
 export class CatsService {
   constructor(private adapterHost: HttpAdapterHost) {}
 }

docs/faq/hybrid-application.md

@@ -41,7 +41,6 @@ await app.listen(3001);
 要将 `@MessagePattern()` 绑定到混合应用中多个微服务里的单一传输策略（例如 MQTT），我们可以传入类型为 `Transport` 的第二个参数，这是一个包含所有内置传输策略定义的枚举。
 
 ```typescript
-@@filename()
 @MessagePattern('time.us.*', Transport.NATS)
 getDate(@Payload() data: number[], @Ctx() context: NatsContext) {
   console.log(`Subject: ${context.getSubject()}`); // e.g. "time.us.east"

docs/faq/serverless.md

@@ -175,6 +175,7 @@ $ npm i -D @types/aws-lambda serverless-offline
 
 ```yaml
 service: serverless-example
+```
 
 plugins:
   - serverless-offline
@@ -294,8 +295,7 @@ return {
 
 或者，如果您希望保持函数非常轻量级且不需要任何 HTTP 相关功能（路由、守卫、拦截器、管道等），可以仅使用 `NestFactory.createApplicationContext` （如前所述）而不运行整个 HTTP 服务器（以及底层的 `express`），如下所示：
 
-```typescript
-@@filename(main)
+```typescript title="main"
 import { HttpStatus } from '@nestjs/common';
 import { NestFactory } from '@nestjs/core';
 import { Callback, Context, Handler } from 'aws-lambda';