peczenyj / GDPR-IAB-TCFv2 / 25867061852

96%

main: 96%

push

github

refactor!: split parser into GDPR::IAB::TCFv2::Parser + add iabtcfv2 short-alias (#129)

* refactor!: split parser into GDPR::IAB::TCFv2::Parser

Move all parser code and per-method POD from GDPR::IAB::TCFv2 to a
new GDPR::IAB::TCFv2::Parser subpackage. GDPR::IAB::TCFv2 becomes the
documentation hub for the distribution (parser, validator,
CMP-validator, CLI, Docker) with a thin Parse delegate. The
pre-parse sniff function looksLikeIsConsentVersion2 stays at the hub
(where it logically belongs).

BREAKING CHANGE: GDPR::IAB::TCFv2->Parse(...) now returns an object
blessed into GDPR::IAB::TCFv2::Parser. Code relying on
ref($obj) eq 'GDPR::IAB::TCFv2' or $obj->isa('GDPR::IAB::TCFv2')
must use the ::Parser namespace. All method calls, TO_JSON output,
and CLI behavior are unchanged.

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

* feat: add iabtcfv2 short-alias module for one-liner use

Add lib/iabtcfv2.pm as a pure-exporter shortcut module. Exports
tcf($tc_string) (returns a GDPR::IAB::TCFv2::Parser) and
validator(%opts) (returns a GDPR::IAB::TCFv2::Validator) so
`perl -Miabtcfv2 -E '...'` one-liners are concise:

    perl -Miabtcfv2 -E 'say tcf(shift)->cmp_id' "$tc"

No @ISA, no class methods, no glob aliases - one obvious way to do
things. Users wanting OO invocation in full scripts call the
GDPR::IAB::TCFv2 hub directly.

Also pin the parser-split BC contract and the looksLikeIsConsentVersion2
placement in t/00-load.t with explicit subtests.

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

* docs(roadmap): add v0.510 Validator->Validate help-wanted item

Record a tiny follow-up phase between v0.500 and v0.600: add a
class-method front door Validator->Validate($tc_string, %opts) as
shorthand for new(%opts)->validate($tc_string). Mirrors the
Parser->Parse(...) shape and prepares the symmetry that the v0.600
Parser/VendorConsent refactor will complete.

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

* docs: regenerate README.... (continued)

313 of 318 new or added lines in 3 files covered. (98.43%)

1174 of 1219 relevant lines covered (96.31%)

24295.33 hits per line