peczenyj / GDPR-IAB-TCFv2 / 26515230079

96%

main: 96%

Build Type

Pull #138

github

Committed by peczenyj

Commit Message

feat: align v2.3 deadline boundary and flexible-purpose reasons with Go

Resolve the two remaining Validator divergences from the Go lib-gdpr
redesign strict path:

- The date-based v2.3 gates now use a strictly-after comparison
  (created > TCF_V23_DEADLINE), matching Go's created.After(v23Deadline).
  A string created exactly at the deadline instant is no longer enforced.
  The parser's is_v23 keeps >= for its own strict-parse gate (intentional).
- Flexible-purpose rejection reasons now follow Go runFlexibleCheck's
  effective legal basis via _flexible_failure: a spec carve-out (P1, or
  P3-6 at policy >= 4) forces consent, then RequireConsent/RequireLI
  override; NotAllowed surfaces ReasonPublisherRestrictionNotAllowed; the
  carve-out still outranks the generic LI reason. A flexible P1 in the LI
  list now reports ReasonVendorNotAllowedConsent rather than the LI reason.

Extend t/18-go-parity.t with deadline-boundary and effective-basis reason
cases; update t/17's post-deadline stub to created+1. Golden corpus is
unaffected (no boundary-exact strings, no basis-flipping restrictions on
the corpus flex scenarios).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Pull Request Pull Request #138: Feat/cross lang validator parity

Coverage Stats

63 of 63 new or added lines in 2 files covered. (100.0%)

3 existing lines in 1 file now uncovered.

1217 of 1264 relevant lines covered (96.28%)

25316.67 hits per line