docs: add inline comment guidance · openclaw/openclaw@64ba5e2
steipete
·
2026-05-13
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -36,6 +36,7 @@ Skills own workflows; root owns hard policy and routing.
|
36 | 36 | - Channels are implementation under `src/channels/**`; plugin authors get SDK seams. Providers own auth/catalog/runtime hooks; core owns generic loop. |
37 | 37 | - Hot paths should carry prepared facts forward: provider id, model ref, channel id, target, capability family, attachment class. Do not rediscover with broad plugin/provider/channel/capability loaders. |
38 | 38 | - Do not fix repeated request-time discovery with scattered caches. Move the canonical fact earlier; reuse prepared runtime objects; delete duplicate lookup branches. |
| 39 | +- Inline code comments: brief notes for tricky, bug-prone, or previously buggy logic. |
39 | 40 | - Gateway protocol changes: additive first; incompatible needs versioning/docs/client follow-through. |
40 | 41 | - Config contract: exported types, schema/help, metadata, baselines, docs aligned. Retired public keys stay retired; compat in raw migration/doctor only. |
41 | 42 | - Prompt cache: deterministic ordering for maps/sets/registries/plugin lists/files/network results before model/tool payloads. Preserve old transcript bytes when possible. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
