Skip to content

feat(rules): add FreeMarker (.ftl/.ftlh/.ftlx) review support - #5

Open
chethanuk wants to merge 1 commit into
mainfrom
feat/issue-371-freemarker-rules
Open

feat(rules): add FreeMarker (.ftl/.ftlh/.ftlx) review support#5
chethanuk wants to merge 1 commit into
mainfrom
feat/issue-371-freemarker-rules

Conversation

@chethanuk

@chethanuk chethanuk commented Jul 15, 2026

Copy link
Copy Markdown
Owner

Description

Adds first-class review support for Apache FreeMarker templates, as requested in alibaba#371:

  • Extension allowlist: .ftl, .ftlh, and .ftlx added to internal/config/allowlist/supported_file_types.json (.ftlh/.ftlx are FreeMarker's official extensions for HTML- and XML-auto-escaping output formats, so all three are covered).
  • System review rules: new internal/config/rule_docs/freemarker.md rule layer wired into internal/config/system_rules.json with glob **/*.{ftl,ftlh,ftlx}. The rules focus on template-specific pitfalls: XSS/escaping (?html vs ftlh auto-escape, noautoesc), null-safety (! default and ?? existence operators), heavy logic in templates, and include/import hygiene.
  • Docs: supported-file-type tables updated in the English, Japanese, and Chinese documentation pages.

Type of Change

  • New feature (non-breaking change that adds functionality)

How Has This Been Tested?

  • make test passes locally
  • Manual testing (describe below)

allowed_ext_test.go and system_rules_test.go extended to cover the three new extensions, including glob-match verification for root-level and nested template paths. make check (tidy + fmt + vet) passes.

Checklist

  • My code follows the project's coding style (go fmt, go vet)
  • I have performed a self-review of my code
  • I have added tests that prove my fix is effective or my feature works
  • New and existing unit tests pass locally with my changes
  • I have updated the documentation accordingly (if applicable)

Related Issues

Closes alibaba#371

@codeant-ai codeant-ai Bot added the size:M This PR changes 30-99 lines, ignoring generated files label Jul 15, 2026
gemini-code-assist[bot]

This comment was marked as outdated.

@chethanuk
chethanuk force-pushed the feat/issue-371-freemarker-rules branch from b46e102 to 913b329 Compare July 15, 2026 08:31
Adds the FreeMarker template extensions to the supported-file-type
allowlist and introduces a freemarker.md system rule layer (glob
**/*.{ftl,ftlh,ftlx}) covering SSTI (?new()/Execute/ObjectConstructor,
?eval/?api), output escaping vs the ftlh/ftlx auto-escape formats,
null/missing-value handling, logic-in-template smells, include/import
hygiene, and locale-sensitive formatting. Extends the allowlist and
system-rules tests and documents the new mapping in the en/ja/zh pages.

Closes alibaba#371
@chethanuk
chethanuk force-pushed the feat/issue-371-freemarker-rules branch from 913b329 to 7b8d823 Compare July 15, 2026 09:14
Repository owner deleted a comment from codeant-ai Bot Jul 15, 2026
Repository owner deleted a comment from codeant-ai Bot Jul 15, 2026
Repository owner deleted a comment from coderabbitai Bot Jul 15, 2026
Repository owner deleted a comment from codeant-ai Bot Jul 15, 2026
Repository owner deleted a comment from gemini-code-assist Bot Jul 15, 2026
Repository owner deleted a comment from gemini-code-assist Bot Jul 15, 2026
Repository owner deleted a comment from gemini-code-assist Bot Jul 15, 2026
Repository owner deleted a comment from gemini-code-assist Bot Jul 15, 2026
Repository owner deleted a comment from gemini-code-assist Bot Jul 15, 2026
Repository owner deleted a comment from gemini-code-assist Bot Jul 15, 2026
Repository owner deleted a comment from gemini-code-assist Bot Jul 15, 2026
@chethanuk chethanuk changed the title feat(rules): add FreeMarker (.ftl) review support feat(rules): add FreeMarker (.ftl/.ftlh/.ftlx) review support Jul 15, 2026
chethanuk pushed a commit that referenced this pull request Jul 30, 2026
…ew.py with unit tests (alibaba#539)

* refactor(examples): extract GitLab CI heredoc into post_review.py with unit tests

Extracts the ~270-line inline heredoc from .gitlab-ci.yml into a standalone,
testable post_review.py module, matching the publish() + make_poster() pattern
established by gerrit_ci/ and gitflic_ci/.

Key design decisions (from spec issue #1 and wayfinder tickets #3, #4, #5):
- publish(result, diff_refs, post, config, sleep) — transport-agnostic
- make_poster(api_base, token, auth_header, config) — GitLab REST transport
- fetch_diff_refs(api_base, token, auth_header, config) — /versions GET with retry
- Single config dict built by main() from env vars; no module-level config state
- post() returns {success, rate_limit_remaining, is_rate_limit_exhausted}
  to preserve failure-pacing behavior (rate-limit vs non-rate-limit delays)
- _sleep = time.sleep module-level pattern for testability

All existing heredoc behavior preserved 1:1:
- GitLab suggestion:-0+0 syntax and <details> fallback format
- Retry on 429/403-rate-limit/5xx/408 with exponential backoff + ±25% jitter
- Retry-After header honoring, MAX_RETRY_DELAY cap
- Proactive RateLimit-Remaining throttling (success path only)
- Failure pacing: rate-limit-exhausted → SUCCESS_DELAY, other → FAILURE_DELAY
- PRIVATE-TOKEN vs JOB-TOKEN auth selection
- Inline → fallback → summary ordering
- Parse failure → post stderr as error note
- All 6 env vars (OCR_RETRY_BASE_DELAY, OCR_MAX_RETRIES, OCR_MAX_RETRY_DELAY,
  OCR_SUCCESS_DELAY, OCR_FAILURE_DELAY, OCR_RATE_LIMIT_THRESHOLD)

48 unit tests (stdlib unittest, no network, no real time.sleep):
- Seam 1: publish() with Recorder fake poster — inline/fallback/summary flow,
  proactive throttling, failure pacing
- Seam 2: make_poster() with mocked urlopen + _sleep — retry/backoff/jitter,
  Retry-After, delay cap, auth headers, is_rate_limit_exhausted classification
- fetch_diff_refs() with mocked urlopen — success/failure/retry
- build_config() defaults and env overrides
- Dry-run poster — no HTTP calls

Implements alibaba#534.

* fix(examples): address code review findings on gitlab_ci post_review

- Add missing-required check for CI_PROJECT_ID and CI_MERGE_REQUEST_IID
  in main(), matching gerrit_ci/gitflic_ci pattern. The heredoc used
  os.environ[...] (KeyError on missing); the extraction silently used
  env.get(..., "") which constructs a malformed API URL. Now fails fast
  with a clear error message.
- Change transient_base_delay from int 2 to float 2.0 to match spec
  config-dict type annotation.
- Add 5 end-to-end tests for main()'s auth-header env resolution:
  PRIVATE-TOKEN when GITLAB_API_TOKEN set, JOB-TOKEN when only
  CI_JOB_TOKEN set, PRIVATE-TOKEN wins when both set, missing CI vars
  fails fast, missing token fails fast.

Addresses review findings: #3 (TP, medium), #4 (Edge), #5 (TP, low).

* fix(examples): handle URLError in gitlab_ci post_review retry logic

_api_request_with_retry only caught HTTPError, not URLError. Network-layer
failures (DNS resolution failure, connection refused, connection reset)
raised URLError which propagated uncaught, crashing the script and losing
all pending review comments.

The original heredoc had the same gap, but the gerrit_ci sibling already
handles this correctly (lines 250-259: retry on connection errors, propagate
timeouts). This fix follows the gerrit_ci pattern adapted to our return-dict
contract:

- Add 'except urllib.error.URLError' handler after HTTPError handler
- Timeout (socket.timeout/TimeoutError): return failure dict, don't retry
  (ambiguous — server may have processed the request)
- Connection errors (DNS, refused, reset): retry with transient_base_delay
  backoff + ±25% jitter, same as 5xx/408 handling
- Exhaustion: return failure dict with is_rate_limit_exhausted=False

3 new tests:
- test_retry_urlerror_then_success: ConnectionRefused → retry → success
- test_urlerror_exhausts_retries: 4 ConnectionRefused → failure after 4 attempts
- test_urlerror_timeout_not_retried: socket.timeout → immediate failure, no retry

Found by OCR (open-code-review) AI code review.

* fix(examples): handle non-UTF-8 HTTP error bodies in gitlab_ci post_review

e.read().decode('utf-8') raises UnicodeDecodeError when the GitLab server
returns a non-UTF-8 error body (e.g., an HTML error page in latin-1 from
a misconfigured proxy or load balancer). This exception propagated uncaught,
crashing the entire posting loop — no further inline comments, fallback notes,
or summary notes would be posted.

Both gerrt_ci (line 242: decode('utf-8', 'replace')) and gitflic_ci (line 344:
decode('utf-8', 'replace')) siblings already handle this correctly. The
original heredoc had the same gap.

Fix: add errors='replace' to both decode() calls (success path line 248 +
error path line 260). For valid UTF-8 input (the normal case), behavior is
identical. The error body is only used for keyword matching and logging,
both of which work fine with replacement characters (U+FFFD).

1 new test:
- test_non_utf8_error_body_does_not_crash: HTTPError with invalid UTF-8 body
  → no crash, returns failure dict

Found by OCR (open-code-review) AI code review on PR alibaba#539.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M This PR changes 30-99 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

是否考虑增加对FreeMarker(.ftl)的审查流程

1 participant