k3nny a0e2582cf1 fix(linter): support bare true/false and integer literals in rules:if: ...

GitLab CI expressions allow unquoted true, false, and integers as
comparison operands (all treated as their string representations):

  $GATEWAY_ENABLED == true    (equivalent to == "true")
  $FEATURE_FLAG == false      (equivalent to == "false")
  $PARALLEL == 4              (equivalent to == "4")
  $ENABLED == 1 / == 0

Previously these fell through to permissive true because parseValue
only recognised $VAR, "${VAR}", quoted strings, and null. Added:
  - true/false keyword branch → returns "true"/"false"
  - integer literal branch (digits only) → returns decimal string

All three new forms are correctly excluded from longer identifier
prefixes (identByte boundary check). Adds 8 new unit tests.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-06-11 22:20:59 +02:00

..

context.go

feat(gitlab-sim): 🚀 branches support

2026-06-07 23:13:52 +02:00

eval_test.go

fix(linter): support bare true/false and integer literals in rules:if:

2026-06-11 22:20:59 +02:00

eval.go

fix(linter): support bare true/false and integer literals in rules:if:

2026-06-11 22:20:59 +02:00

reachability.go

fix(project): rename tool to glint

2026-06-10 22:40:42 +02:00