Repository navigation
ref(extensions): 用写入与数据访问能力命名原生接口 - #9
Merged
Merged
Conversation
3 of 5 tasks
- 将 CaptureClient/CaptureTransport 迁移为 CaptureWriter/CaptureWriting，注入点使用 writer - 将 LocalFileClient 迁移为 LocalFilesRepository，统一扫描、视图模型与测试调用 - 保留 PostgreSQL 协议客户端及固定历史来源名称，说明候选 API 的直接迁移
xiaoland
force-pushed
the
feat/app-peer-naming
branch
from
November 5, 2026 09:42
ebf74b9 to
d2f19b0
Compare
xiaoland
marked this pull request as ready for review
November 5, 2026 09:43
github-project-automation
Bot
moved this from Review / acceptance
to Done
in InKCre Current Work
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
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.
Capture 与 Local Files 的业务接口过去使用 Client 命名，实际却由本地 Peer 直接构图、读写共享数据库并执行任务。此 PR 按实际职责命名，消除对另一个中心服务的依附暗示。
CaptureClient→CaptureWriter，CaptureTransport→CaptureWriting，调用和注入参数统一为writer。LocalFileClient→LocalFilesRepository，扫描、视图模型及测试中的业务依赖统一为repository。PostgresClient、数据库协议方法与固定提交的品牌来源记录保留原名。本次 Swift 候选尚未发布，源码调用方同步改名，不新增旧名别名。应用 bundle ID、Keychain service、数据库协议、图形状、SQLite 格式与已保存数据不变。此仓没有已启用的独立版本意图机制，不修改应用或扩展版本号。
验证：
scripts/check.sh通过，含 Swift 格式/lint、脚本测试及 SwiftPM 测试（报告 66 项、11 suites，4 项真实数据库场景跳过）；git diff --check通过。CONFIGURATION=debug bash scripts/build-app.sh已通过，生成 arm64/x86_64 universal App 和 DMG，包含资源、许可与 ad-hoc 签名校验。本地没有执行端到端验收，未连接数据库、启动真实应用旅程或发布生产产物。现有 Keychain deprecation 与 SwiftSoup 未使用返回值的编译 warning 位于未修改的代码。风险：候选源码 API 名称变化，仓库外使用旧接口的消费者需同步替换；编译能直接发现漏改。可整体撤销本提交回滚，无数据迁移或独立清理步骤。
前置 Core/App PR #8 已通过普通 squash 合入
main（e7e8cd3）。本 PR 已重排至该提交，只含一个命名迁移提交d2f19b0，与重排前ebf74b9的代码树完全一致。当前直接面向 main，跨仓交付由 InKCre/docs#55 跟踪。用户已授权整组合并。重排后
d2f19b0已通过完整云端检查（https://github.com/InKCre/impl-swift/actions/runs/42004649856），随后通过普通 squash 合入 main（0ca3d1b）。main 的代码树与已验证提交一致。