peczenyj / GDPR-IAB-TCFv2 / 25432091306

96%

main: 96%

Build Type

push

github

Committed by web-flow

Commit Message

Phase 1: TCF v2.3 Support & Logic Alignment (Re-issue) (#44)

* docs: update TCF version mentions to v2.3 in constants

* feat: Phase 1 implementation (predicates, vendor_id filter, CLI options)

* feat: enforce TCF v2.2/v2.3 legal restrictions on Legitimate Interest

* feat: add --strict option to CLI dump and enforce TCF v2.3 rules

* chore: prepare for v0.350 release (Phase 1)

* chore: consolidate documentation to README.md and remove README.pod

* chore: simplify docker tagging (version and latest only)

* chore: final Phase 1 refinements (POD, logic fixes, golden file)

* chore: establish strict operational boundaries for agents in AGENTS.md

* feat: add automated release workflow for CPAN and GitHub Releases

* docs: update AGENTS.md with automated release flow and Phase 1 features

* fix: improve TO_JSON isolation and fix predicates tests

* fix: robust regex for CLI isolation test

* fix: satisfy perl critic and tidy in CI

* Vendor segment parser cleanup (stacked on #44) (#45)

* fix: align core bitfield/range data_size to slice length

Both _parse_bitfield and _parse_range_section previously passed the
full core_data bit-length as data_size while passing a sliced \$data.
This made the BitField/RangeSection size validation lenient for
truncated cores: malformed inputs would stumble forward and croak deep
in _parse_publisher_section with a misleading "missing 'core_data'"
error instead of failing fast at the bitfield boundary.

Align with the pattern already used in _parse_vendor_bitfield_or_range
so data_size faithfully describes what the callee receives.

* feat: defensive segment-type check in vendor-segment helper

_parse_vendor_bitfield_or_range now accepts an expected_segment_type
argument and croaks if the payload header disagrees. Brings parity
with PublisherTC->Parse and protects against future refactors that
might bypass _decode_tc_string_segments routing.

* docs: explain single-return shape of vendor-segment helper

* fix: short-c... (continued)

Coverage Stats

91 of 105 new or added lines in 5 files covered. (86.67%)

2 existing lines in 1 file now uncovered.

738 of 772 relevant lines covered (95.6%)

11622.52 hits per line