### Problem Statement 是否考虑增加对FreeMarker(.ftl)的审查流程 ### Proposed Solution 或者考虑扩展名白名单放开,可以自己扩展 ### Alternatives Considered _No response_ ### Affected Area Review Rules ### Additional Context _No response_
Activity
lizhengfeng101 commentedon Jul 15, 2026
感谢反馈 🙏
关于内置 FreeMarker 评审规范:目前开发者团队对 FreeMarker(.ftl)的研发规范还不太熟悉,暂时不方便直接内置一套高质量的默认评审规范。我们非常期待熟悉该语言特性的开发者能贡献对应的评审规范(欢迎提 PR)。
关于"放开扩展名白名单、可自行扩展":其实这个能力现在已经可以实现了。虽然
.ftl不在内置的扩展名白名单中,但你可以在项目的.opencodereview/rule.json里通过include字段把它纳入审查范围,include命中的路径会绕过内置扩展名白名单的过滤:{ "include": ["**/*.ftl"] }这样所有
.ftl文件都会进入代码审查流程。配合你自定义的规则,就能对 FreeMarker 模板做针对性的评审。相关说明可参考 README 中 include/exclude 的过滤优先级章节。feat(rules): add FreeMarker (.ftl) review support
feat(rules): add FreeMarker (.ftl/.ftlh/.ftlx) review support
fix(scan): check user include patterns before the extension allowlist
feat(rules): add FreeMarker (.ftl/.ftlh/.ftlx) review support (alibab…
fix(scan): check user include patterns before the extension allowlist (…
feat(rules): add FreeMarker (.ftl/.ftlh/.ftlx) review support (alibab…
fix(scan): check user include patterns before the extension allowlist (…