chore: add dprint and format Markdown#4673
Open
duicikeyihangaolou wants to merge 1 commit intoQuantumNous:mainfrom
Open
chore: add dprint and format Markdown#4673duicikeyihangaolou wants to merge 1 commit intoQuantumNous:mainfrom
duicikeyihangaolou wants to merge 1 commit intoQuantumNous:mainfrom
Conversation
Introduce dprint.json for Markdown and apply formatting across documentation, skills, and templates.
Contributor
WalkthroughThis PR applies comprehensive Markdown formatting and documentation improvements across the entire repository using a new Dprint configuration (100-column width, LF newlines). Changes span AI agent skills, project conventions, GitHub templates, multilingual README files, user guides, and frontend development documentation. All modifications are documentation-only with no functional code changes. ChangesDocumentation Formatting and Dprint Configuration
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested reviewers
Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 12
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.agents/skills/shadcn-ui/vendor/shadcn/cli.md:
- Around line 5-12: Merge the two separate blockquote paragraphs so there's no
blank line between them to satisfy MD028; specifically, combine the two `>
**IMPORTANT:**` sections into a single contiguous blockquote (preserving both
sentences about using the project's package runner and the restriction on flags)
in .agents/skills/shadcn-ui/vendor/shadcn/cli.md so the blockquote is continuous
and the `no-blanks-blockquote` warning is resolved.
In `@AGENTS.md`:
- Around line 132-135: Replace the visually confusable homoglyph variants
`nеw-аρi` and `QuаntumΝоuѕ` in AGENTS.md with the canonical identifiers
`new-api` and `QuantumNous`; locate the occurrences of the symbols `nеw-аρi` and
`QuаntumΝоuѕ` in the file and update them to the exact spellings `new-api` and
`QuantumNous` so the document uses the official project and organization names.
In `@docs/translation-glossary.fr.md`:
- Around line 103-118: The changes in the "### Termes Standardisés" section and
the bilingual contributor note introduce semantic/documentation updates
(glossary content and contributor guidance) rather than format-only edits;
either move the new/modified glossary entries and the bilingual contributor note
into a separate documentation PR or revert those semantic edits in this change
and keep only formatting/whitespace edits here, and update the current PR
description to reflect that it now includes semantic glossary changes if you
intend them to stay—look for the "### Termes Standardisés" heading and the
contributor note paragraph to isolate which lines to split or revert.
- Line 107: The glossary entry "Code d'échange (Redemption Code)" is
self-referential; locate the phrase "Code d'échange (Redemption Code)" and
replace the repeated French term with the actual alternative intended for
translators (e.g., use "Code de rachat (Redemption Code)" or the correct French
equivalent), ensuring the left-side French term and the parenthetical English
term are distinct and clear for translators.
In `@electron/README.md`:
- Around line 21-22: The heading "### 3. Electron Dependencies" in the README is
misnumbered because there is no "### 2" section; update the heading text (the
line containing "### 3. Electron Dependencies") to the correct sequence (e.g.,
"### 2. Electron Dependencies") or insert a missing "### 2" prerequisite section
above it so the prerequisites flow sequentially; ensure any cross-references or
table-of-contents entries that mention the old number are updated accordingly.
- Line 19: Replace the "Option B: Build from source (requires Go) TODO"
placeholder with concrete, step-by-step build instructions under the "Option B:
Build from source (requires Go)" heading: list prerequisites (minimum Go version
and any toolchain), provide the exact commands to fetch dependencies and build
the Electron helper and Go components (e.g., commands to run in the repo root
and relevant subfolders), state expected output binary names and locations,
include any required environment variables or PATH updates, and finish with a
short verification step showing how to run the built binary to confirm success.
In `@README.en.md`:
- Line 225: Replace the unhyphenated phrase "Channel weighted random" with a
hyphenated form "Channel-weighted random" wherever that heading or label appears
(the exact text "Channel weighted random" in the diff) to improve readability;
update the heading/label string in README.en.md to use the hyphenated version.
- Around line 52-57: The adjacent blockquote markers [!NOTE] and [!IMPORTANT]
create blank lines that trigger MD028; fix by consolidating or removing the
empty lines so each blockquote has no blank lines inside or directly between
them—either merge the content into a single blockquote or ensure the [!NOTE]
block has its content immediately after the marker and the [!IMPORTANT] marker
follows without an empty line separating the two blockquotes (adjust the [!NOTE]
and [!IMPORTANT] blocks accordingly).
In `@README.fr.md`:
- Line 325: The table row contains an unbalanced bold marker around the label
"Base de données distante"; fix by adding the closing ** after "Base de données
distante" so the row reads like "| **Base de données distante** | MySQL ≥ 5.7.8
ou PostgreSQL ≥ 9.6 |", ensuring the pipe delimiters remain intact.
- Around line 188-191: The blockquote in README.fr.md contains an accidental
trailing pipe character ('|') after the link in the quoted sentence; remove that
stray '|' so the blockquote reads cleanly (locate the blockquote containing the
link to Présentation des fonctionnalités and delete the trailing pipe
character).
In `@README.ja.md`:
- Line 328: Fix the malformed environment variable key in the README table by
replacing the broken token `` `SQL_DSN** `` with the correct backticked name ``
`SQL_DSN` `` so the table shows the proper variable name (referenced symbol:
SQL_DSN) and prevents copy/paste errors; update the table cell containing that
token accordingly.
In `@README.md`:
- Line 231: Replace the phrase "Channel weighted random" in the README (the
feature label at the heading currently shown) with a hyphenated form; update the
heading text to "Channel-weighted random" (or use "Weighted random channel
routing" if you prefer that wording) so the label reads correctly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: beb200e7-a2d0-49c0-a966-1392eba4dd78
📒 Files selected for processing (39)
.agents/skills/classic-to-default-sync/SKILL.md.agents/skills/i18n-translate/SKILL.md.agents/skills/shadcn-ui/SKILL.md.agents/skills/shadcn-ui/vendor/shadcn/SKILL.md.agents/skills/shadcn-ui/vendor/shadcn/cli.md.agents/skills/shadcn-ui/vendor/shadcn/customization.md.agents/skills/shadcn-ui/vendor/shadcn/mcp.md.agents/skills/shadcn-ui/vendor/shadcn/rules/base-vs-radix.md.agents/skills/shadcn-ui/vendor/shadcn/rules/composition.md.agents/skills/shadcn-ui/vendor/shadcn/rules/forms.md.agents/skills/shadcn-ui/vendor/shadcn/rules/icons.md.agents/skills/shadcn-ui/vendor/shadcn/rules/styling.md.agents/skills/vercel-react-best-practices/AGENTS.md.github/CODE_OF_CONDUCT.md.github/ISSUE_TEMPLATE/bug_report.md.github/ISSUE_TEMPLATE/bug_report_en.md.github/ISSUE_TEMPLATE/feature_request.md.github/ISSUE_TEMPLATE/feature_request_en.md.github/PULL_REQUEST_TEMPLATE.md.github/SECURITY.mdAGENTS.mdCLAUDE.mdREADME.en.mdREADME.fr.mdREADME.ja.mdREADME.mdREADME.zh_CN.mdREADME.zh_TW.mdconstant/README.mddocs/channel/other_setting.mddocs/installation/BT.mddocs/ionet-client.mddocs/translation-glossary.fr.mddocs/translation-glossary.mddocs/translation-glossary.ru.mddprint.jsonelectron/README.mdpkg/billingexpr/expr.mdweb/default/AGENTS.md
Comment on lines
+5
to
+12
| > **IMPORTANT:** Always run commands using the project's package runner: `npx shadcn@latest`, | ||
| > `pnpm dlx shadcn@latest`, or `bunx --bun shadcn@latest`. Check `packageManager` from project | ||
| > context to choose the right one. Examples below use `npx shadcn@latest` but substitute the correct | ||
| > runner for the project. | ||
|
|
||
| > **IMPORTANT:** Only use the flags documented below. Do not invent or guess flags — if a flag isn't listed here, it doesn't exist. The CLI auto-detects the package manager from the project's lockfile; there is no `--package-manager` flag. | ||
| > **IMPORTANT:** Only use the flags documented below. Do not invent or guess flags — if a flag isn't | ||
| > listed here, it doesn't exist. The CLI auto-detects the package manager from the project's | ||
| > lockfile; there is no `--package-manager` flag. |
Contributor
There was a problem hiding this comment.
Resolve MD028 blockquote formatting issue.
The two > **IMPORTANT:** sections (Lines 5-12) are separated in a way that can trigger no-blanks-blockquote.
Suggested fix
> **IMPORTANT:** Always run commands using the project's package runner: `npx shadcn@latest`,
> `pnpm dlx shadcn@latest`, or `bunx --bun shadcn@latest`. Check `packageManager` from project
> context to choose the right one. Examples below use `npx shadcn@latest` but substitute the correct
> runner for the project.
-
> **IMPORTANT:** Only use the flags documented below. Do not invent or guess flags — if a flag isn't
> listed here, it doesn't exist. The CLI auto-detects the package manager from the project's
> lockfile; there is no `--package-manager` flag.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| > **IMPORTANT:** Always run commands using the project's package runner: `npx shadcn@latest`, | |
| > `pnpm dlx shadcn@latest`, or `bunx --bun shadcn@latest`. Check `packageManager` from project | |
| > context to choose the right one. Examples below use `npx shadcn@latest` but substitute the correct | |
| > runner for the project. | |
| > **IMPORTANT:** Only use the flags documented below. Do not invent or guess flags — if a flag isn't listed here, it doesn't exist. The CLI auto-detects the package manager from the project's lockfile; there is no `--package-manager` flag. | |
| > **IMPORTANT:** Only use the flags documented below. Do not invent or guess flags — if a flag isn't | |
| > listed here, it doesn't exist. The CLI auto-detects the package manager from the project's | |
| > lockfile; there is no `--package-manager` flag. | |
| > **IMPORTANT:** Always run commands using the project's package runner: `npx shadcn@latest`, | |
| > `pnpm dlx shadcn@latest`, or `bunx --bun shadcn@latest`. Check `packageManager` from project | |
| > context to choose the right one. Examples below use `npx shadcn@latest` but substitute the correct | |
| > runner for the project. | |
| > **IMPORTANT:** Only use the flags documented below. Do not invent or guess flags — if a flag isn't | |
| > listed here, it doesn't exist. The CLI auto-detects the package manager from the project's | |
| > lockfile; there is no `--package-manager` flag. |
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 9-9: Blank line inside blockquote
(MD028, no-blanks-blockquote)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.agents/skills/shadcn-ui/vendor/shadcn/cli.md around lines 5 - 12, Merge the
two separate blockquote paragraphs so there's no blank line between them to
satisfy MD028; specifically, combine the two `> **IMPORTANT:**` sections into a
single contiguous blockquote (preserving both sentences about using the
project's package runner and the restriction on flags) in
.agents/skills/shadcn-ui/vendor/shadcn/cli.md so the blockquote is continuous
and the `no-blanks-blockquote` warning is resolved.
Comment on lines
+132
to
+135
| - Any references, mentions, branding, metadata, or attributions related to **nеw-аρi** (the project | ||
| name/identity) | ||
| - Any references, mentions, branding, metadata, or attributions related to **QuаntumΝоuѕ** (the | ||
| organization/author identity) |
Contributor
There was a problem hiding this comment.
Use canonical project/org identifiers instead of homoglyph variants
Line 132 and Line 134 replace protected identifiers with visually confusable characters (nеw-аρi, QuаntumΝоuѕ). Please keep canonical spellings (new-api, QuantumNous) to avoid policy ambiguity and spoofing risk.
Proposed fix
-- Any references, mentions, branding, metadata, or attributions related to **nеw-аρi** (the project
+- Any references, mentions, branding, metadata, or attributions related to **new-api** (the project
name/identity)
-- Any references, mentions, branding, metadata, or attributions related to **QuаntumΝоuѕ** (the
+- Any references, mentions, branding, metadata, or attributions related to **QuantumNous** (the
organization/author identity)Based on learnings: Protected project information related to new-api and QuantumNous must not be modified, replaced, or removed.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| - Any references, mentions, branding, metadata, or attributions related to **nеw-аρi** (the project | |
| name/identity) | |
| - Any references, mentions, branding, metadata, or attributions related to **QuаntumΝоuѕ** (the | |
| organization/author identity) | |
| - Any references, mentions, branding, metadata, or attributions related to **new-api** (the project | |
| name/identity) | |
| - Any references, mentions, branding, metadata, or attributions related to **QuantumNous** (the | |
| organization/author identity) |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@AGENTS.md` around lines 132 - 135, Replace the visually confusable homoglyph
variants `nеw-аρi` and `QuаntumΝоuѕ` in AGENTS.md with the canonical identifiers
`new-api` and `QuantumNous`; locate the occurrences of the symbols `nеw-аρi` and
`QuаntumΝоuѕ` in the file and update them to the exact spellings `new-api` and
`QuantumNous` so the document uses the official project and organization names.
Comment on lines
103
to
+118
| ### Termes Standardisés | ||
|
|
||
| - **Complétion (Completion)** : Contenu de sortie du modèle | ||
| - **Ratio (Ratio)** : Multiplicateur pour le calcul des prix | ||
| - **Code d'échange (Redemption Code)** : Utilisé au lieu de "Code d'échange" pour plus de précision | ||
| - **Fournisseur (Provider/Vendor)** : Organisation ou service fournissant des API ou des modèles d'IA | ||
| - **Fournisseur (Provider/Vendor)** : Organisation ou service fournissant des API ou des modèles | ||
| d'IA | ||
|
|
||
| --- | ||
|
|
||
| **Note pour les contributeurs :** Si vous trouvez des incohérences dans les traductions de terminologie ou si vous avez de meilleures suggestions de traduction pour le français, n'hésitez pas à créer une Issue ou une Pull Request. | ||
| **Note pour les contributeurs :** Si vous trouvez des incohérences dans les traductions de | ||
| terminologie ou si vous avez de meilleures suggestions de traduction pour le français, n'hésitez pas | ||
| à créer une Issue ou une Pull Request. | ||
|
|
||
| **Contribution Note for French:** If you find any inconsistencies in terminology translations or have better translation suggestions for French, please feel free to submit an Issue or Pull Request. No newline at end of file | ||
| **Contribution Note for French:** If you find any inconsistencies in terminology translations or | ||
| have better translation suggestions for French, please feel free to submit an Issue or Pull Request. |
Contributor
There was a problem hiding this comment.
Scope drift from “format-only” objective
This file includes semantic/documentation content edits (new or revised glossary guidance and contributor-note content), not just wrapping/whitespace. Please either update the PR objective/description to reflect scope or split semantic doc updates into a separate PR for cleaner reviewability.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/translation-glossary.fr.md` around lines 103 - 118, The changes in the
"### Termes Standardisés" section and the bilingual contributor note introduce
semantic/documentation updates (glossary content and contributor guidance)
rather than format-only edits; either move the new/modified glossary entries and
the bilingual contributor note into a separate documentation PR or revert those
semantic edits in this change and keep only formatting/whitespace edits here,
and update the current PR description to reflect that it now includes semantic
glossary changes if you intend them to stay—look for the "### Termes
Standardisés" heading and the contributor note paragraph to isolate which lines
to split or revert.
|
|
||
| - **Complétion (Completion)** : Contenu de sortie du modèle | ||
| - **Ratio (Ratio)** : Multiplicateur pour le calcul des prix | ||
| - **Code d'échange (Redemption Code)** : Utilisé au lieu de "Code d'échange" pour plus de précision |
Contributor
There was a problem hiding this comment.
Fix self-referential standardized-term description
Line 107 says the term is used instead of itself ("Code d'échange"), which is ambiguous for translators. Please replace with the intended alternative term in that sentence.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/translation-glossary.fr.md` at line 107, The glossary entry "Code
d'échange (Redemption Code)" is self-referential; locate the phrase "Code
d'échange (Redemption Code)" and replace the repeated French term with the
actual alternative intended for translators (e.g., use "Code de rachat
(Redemption Code)" or the correct French equivalent), ensuring the left-side
French term and the parenthetical English term are distinct and clear for
translators.
|
|
||
| **Option B: Build from source (requires Go)** | ||
| TODO | ||
| **Option B: Build from source (requires Go)** TODO |
Contributor
There was a problem hiding this comment.
Replace TODO with actionable build steps
The “Option B” section is still marked TODO, so users without prebuilt binaries cannot complete setup from this README.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@electron/README.md` at line 19, Replace the "Option B: Build from source
(requires Go) TODO" placeholder with concrete, step-by-step build instructions
under the "Option B: Build from source (requires Go)" heading: list
prerequisites (minimum Go version and any toolchain), provide the exact commands
to fetch dependencies and build the Electron helper and Go components (e.g.,
commands to run in the repo root and relevant subfolders), state expected output
binary names and locations, include any required environment variables or PATH
updates, and finish with a short verification step showing how to run the built
binary to confirm success.
|
|
||
| **Intelligent Routing:** | ||
|
|
||
| - ⚖️ Channel weighted random |
Contributor
There was a problem hiding this comment.
Use hyphenated phrasing for readability.
At Line 225, “Channel weighted random” should be hyphenated (for example, “Channel-weighted random”).
🧰 Tools
🪛 LanguageTool
[grammar] ~225-~225: Use a hyphen to join words.
Context: ... Intelligent Routing: - ⚖️ Channel weighted random - 🔄 Automatic retry on ...
(QB_NEW_EN_HYPHEN)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.en.md` at line 225, Replace the unhyphenated phrase "Channel weighted
random" with a hyphenated form "Channel-weighted random" wherever that heading
or label appears (the exact text "Channel weighted random" in the diff) to
improve readability; update the heading/label string in README.en.md to use the
hyphenated version.
Comment on lines
+188
to
191
| > Pour les fonctionnalités détaillées, veuillez vous référer à | ||
| > [Présentation des fonctionnalités](https://docs.newapi.pro/en/docs/guide/wiki/basic-concepts/features-introduction) | ||
| > | | ||
|
|
Contributor
There was a problem hiding this comment.
Remove stray pipe character in blockquote section.
At Line 190, the trailing | appears accidental and breaks the flow of the quoted sentence.
Suggested fix
> Pour les fonctionnalités détaillées, veuillez vous référer à
> [Présentation des fonctionnalités](https://docs.newapi.pro/en/docs/guide/wiki/basic-concepts/features-introduction)
-> |📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| > Pour les fonctionnalités détaillées, veuillez vous référer à | |
| > [Présentation des fonctionnalités](https://docs.newapi.pro/en/docs/guide/wiki/basic-concepts/features-introduction) | |
| > | | |
| > Pour les fonctionnalités détaillées, veuillez vous référer à | |
| > [Présentation des fonctionnalités](https://docs.newapi.pro/en/docs/guide/wiki/basic-concepts/features-introduction) | |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.fr.md` around lines 188 - 191, The blockquote in README.fr.md contains
an accidental trailing pipe character ('|') after the link in the quoted
sentence; remove that stray '|' so the blockquote reads cleanly (locate the
blockquote containing the link to Présentation des fonctionnalités and delete
the trailing pipe character).
| | Composant | Exigence | | ||
| | -------------------------- | ------------------------------------------------- | | ||
| | **Base de données locale** | SQLite (Docker doit monter le répertoire `/data`) | | ||
| | **Base de données distante | MySQL ≥ 5.7.8 ou PostgreSQL ≥ 9.6 | |
Contributor
There was a problem hiding this comment.
Fix malformed deployment requirements table row.
At Line 325, the bold marker is unbalanced (**Base de données distante), which breaks table formatting.
Suggested fix
-| **Base de données distante | MySQL ≥ 5.7.8 ou PostgreSQL ≥ 9.6 |
+| **Base de données distante** | MySQL ≥ 5.7.8 ou PostgreSQL ≥ 9.6 |📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| | **Base de données distante | MySQL ≥ 5.7.8 ou PostgreSQL ≥ 9.6 | | |
| | **Base de données distante** | MySQL ≥ 5.7.8 ou PostgreSQL ≥ 9.6 | |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.fr.md` at line 325, The table row contains an unbalanced bold marker
around the label "Base de données distante"; fix by adding the closing ** after
"Base de données distante" so the row reads like "| **Base de données distante**
| MySQL ≥ 5.7.8 ou PostgreSQL ≥ 9.6 |", ensuring the pipe delimiters remain
intact.
| | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -------------------- | | ||
| | `SESSION_SECRET` | セッションシークレット（マルチマシンデプロイに必須） | - | | ||
| | `CRYPTO_SECRET` | 暗号化シークレット（Redisに必須） | - | | ||
| | `SQL_DSN** | データベース接続文字列 | - | |
Contributor
There was a problem hiding this comment.
Correct malformed environment variable name in table.
At Line 328, the variable key is broken as `SQL_DSN**. It should be `SQL_DSN` to avoid copy/paste errors.
Suggested fix
-| `SQL_DSN** | データベース接続文字列 | - |
+| `SQL_DSN` | データベース接続文字列 | - |📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| | `SQL_DSN** | データベース接続文字列 | - | | |
| | `SQL_DSN` | データベース接続文字列 | - | |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.ja.md` at line 328, Fix the malformed environment variable key in the
README table by replacing the broken token `` `SQL_DSN** `` with the correct
backticked name `` `SQL_DSN` `` so the table shows the proper variable name
(referenced symbol: SQL_DSN) and prevents copy/paste errors; update the table
cell containing that token accordingly.
|
|
||
| **Intelligent Routing:** | ||
|
|
||
| - ⚖️ Channel weighted random |
Contributor
There was a problem hiding this comment.
Hyphenate this feature label for correct English usage.
At Line 231, use “Channel-weighted random” (or “Weighted random channel routing”) instead of “Channel weighted random”.
🧰 Tools
🪛 LanguageTool
[grammar] ~231-~231: Use a hyphen to join words.
Context: ... Intelligent Routing: - ⚖️ Channel weighted random - 🔄 Automatic retry on ...
(QB_NEW_EN_HYPHEN)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.md` at line 231, Replace the phrase "Channel weighted random" in the
README (the feature label at the heading currently shown) with a hyphenated
form; update the heading text to "Channel-weighted random" (or use "Weighted
random channel routing" if you prefer that wording) so the label reads
correctly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduce dprint.json for Markdown and apply formatting across documentation, skills, and templates.
📝 变更描述 / Description
在仓库根目录增加
dprint.json，启用官方 Markdown 插件，统一换行与行宽等排版规则。对已有.md文件（含.agents技能说明、.github模板与说明、根目录与各子目录文档等）执行dprint fmt，仅改变空白、换行与折行等格式，不修改 Markdown 语义与正文措辞。这样后续可用
dprint check/dprint fmt在本地或 CI 中与配置一致地校验或修正文档排版，避免各人编辑器设置不一致导致的无意义 diff。🚀 变更类型 / Type of change
🔗 关联任务 / Related Issue
✅ 提交前检查项 / Checklist
Bug fix，我已提交或关联对应 Issue，且不会将设计取舍、预期不一致或理解偏差直接归类为 bug。📸 运行证明 / Proof of Work
在仓库根目录执行：
期望：命令以退出码
0结束，表示当前 Markdown 与dprint.json一致。（若维护方需要，可再贴一条该命令的终端输出。）Summary by CodeRabbit
Release Notes
Documentation
Chores