English
Hello, and thank you very much for building and maintaining CodeGraph. After submitting the initial version of this report, I re-checked the documentation and the installed v1.4.1 package. CodeGraph already honors root and nested .gitignore files, and codegraph.json already provides gitignore-style exclude and include patterns that apply to index, sync, and watch. Those existing capabilities address the directory-name keyword part of my use case, so I apologize for the earlier inaccurate request and have narrowed this issue accordingly.
The remaining feature request is an optional file last-modified date range filter for codegraph init / codegraph index. For the current API migration, I need the intersection of the existing directory include/exclude rules and files whose filesystem modification time lies within an explicit start/end interval. A one-sided --changed-since option would not be sufficient because the migration needs both bounds. If feasible, could CodeGraph support an opt-in modifiedAfter / modifiedBefore pair in codegraph.json, equivalent CLI options, or another documented mechanism with the same semantics? The filter should apply before parsing, leave current behavior unchanged when absent, and ideally be shown by status together with included/skipped file counts. This would make short-lived, date-bounded investigations possible while retaining CodeGraph's existing and already well-designed path scope controls. Thank you for considering this smaller request.
中文
您好，感谢您开发并持续维护 CodeGraph。在提交此 Issue 的初版后，我重新核对了官方文档和本机安装的 1.4.1 包：CodeGraph 已经支持项目根及嵌套 .gitignore，并且 codegraph.json 已提供 gitignore 风格的 exclude 与 include 规则，且会用于 index、sync 和 watch。这些既有能力已经解决了我场景中的目录名称关键词范围问题，因此我为先前不准确的请求致歉，并已将本 Issue 收窄。
余下的功能请求仅是：为 codegraph init / codegraph index 提供可选的文件最后修改日期区间过滤。当前 API 迁移需要的是既有目录包含/排除规则与“文件系统修改时间位于明确开始/结束区间”的交集。单向的 --changed-since 不足以满足需求，因为迁移同时需要上下两个日期边界。若实现成本允许，是否可以在 codegraph.json 中支持 modifiedAfter / modifiedBefore 字段、提供语义等价的 CLI 参数，或以其他已文档化方式实现相同行为？该过滤应在解析前应用、未配置时完全保持现有行为，并最好由 status 同时显示生效条件以及已包含/已跳过的文件数量。这样可以在保留 CodeGraph 现有且设计完善的路径范围能力前提下，支持短期、受日期边界约束的分析任务。感谢您考虑这一更小且更准确的建议。
English
Hello, and thank you very much for building and maintaining CodeGraph. After submitting the initial version of this report, I re-checked the documentation and the installed v1.4.1 package. CodeGraph already honors root and nested
.gitignorefiles, andcodegraph.jsonalready provides gitignore-styleexcludeandincludepatterns that apply to index, sync, and watch. Those existing capabilities address the directory-name keyword part of my use case, so I apologize for the earlier inaccurate request and have narrowed this issue accordingly.The remaining feature request is an optional file last-modified date range filter for
codegraph init/codegraph index. For the current API migration, I need the intersection of the existing directory include/exclude rules and files whose filesystem modification time lies within an explicit start/end interval. A one-sided--changed-sinceoption would not be sufficient because the migration needs both bounds. If feasible, could CodeGraph support an opt-inmodifiedAfter/modifiedBeforepair incodegraph.json, equivalent CLI options, or another documented mechanism with the same semantics? The filter should apply before parsing, leave current behavior unchanged when absent, and ideally be shown bystatustogether with included/skipped file counts. This would make short-lived, date-bounded investigations possible while retaining CodeGraph's existing and already well-designed path scope controls. Thank you for considering this smaller request.中文
您好，感谢您开发并持续维护 CodeGraph。在提交此 Issue 的初版后，我重新核对了官方文档和本机安装的 1.4.1 包：CodeGraph 已经支持项目根及嵌套
.gitignore，并且codegraph.json已提供 gitignore 风格的exclude与include规则，且会用于 index、sync 和 watch。这些既有能力已经解决了我场景中的目录名称关键词范围问题，因此我为先前不准确的请求致歉，并已将本 Issue 收窄。余下的功能请求仅是：为
codegraph init/codegraph index提供可选的文件最后修改日期区间过滤。当前 API 迁移需要的是既有目录包含/排除规则与“文件系统修改时间位于明确开始/结束区间”的交集。单向的--changed-since不足以满足需求，因为迁移同时需要上下两个日期边界。若实现成本允许，是否可以在codegraph.json中支持modifiedAfter/modifiedBefore字段、提供语义等价的 CLI 参数，或以其他已文档化方式实现相同行为？该过滤应在解析前应用、未配置时完全保持现有行为，并最好由status同时显示生效条件以及已包含/已跳过的文件数量。这样可以在保留 CodeGraph 现有且设计完善的路径范围能力前提下，支持短期、受日期边界约束的分析任务。感谢您考虑这一更小且更准确的建议。