peczenyj / GDPR-IAB-TCFv2 / 25480754647
96%
main: 96%

LAST BUILD BRANCH: devel
DEFAULT BRANCH: main
Ran
Jobs 1
Files 13
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 94.398%. Remained the same
25480754647

push

github

web-flow 
feat(constants): TCF v2.3 spec-aligned long-form aliases (#59)

* feat(constants): add TCF v2.3 spec-aligned long-form aliases

Phase 3 / "Alignment & Cleanup" deliverable: every Purpose and
SpecialFeature constant now has a long-form alias that mirrors the
canonical wording from the IAB Global Vendor List for TCF v2.3.

Both names resolve to the same integer and are interchangeable
everywhere a constant is accepted (is_purpose_consent_allowed,
is_vendor_consent_allowed, is_special_feature_opt_in, etc.).  The
existing short names remain the established working forms and are
supported indefinitely.

Mapping (short -- long):

  InfoStorageAccess        -- StoreAndOrAccessInformationOnDevice         (1)
  BasicAdserving           -- UseLimitedDataToSelectAdvertising           (2)
  PersonalizationProfile   -- CreateProfilesForPersonalisedAdvertising    (3)
  PersonalizationSelection -- UseProfilesToSelectPersonalisedAdvertising  (4)
  ContentProfile           -- CreateProfilesToPersonaliseContent          (5)
  ContentSelection         -- UseProfilesToSelectPersonalisedContent      (6)
  AdPerformance            -- MeasureAdvertisingPerformance               (7)
  ContentPerformance       -- MeasureContentPerformance                   (8)
  MarketResearch           -- UnderstandAudiences                         (9)
  DevelopImprove           -- DevelopAndImproveServices                  (10)
  SelectContent            -- UseLimitedDataToSelectContent              (11)

  Geolocation              -- UsePreciseGeolocationData                   (1)
  DeviceScan               -- ActivelyScanDeviceCharacteristicsForIdentification (2)

A new t/13-constants-aliases.t exercises every alias against its
canonical counterpart and verifies the parser API treats both names
as drop-in equivalents.

RestrictionType already uses spec-aligned wording (NotAllowed,
RequireConsent, RequireLegitimateInterest); no new aliases needed there.

Note: this supersedes the bulk of P... (continued)

910 of 964 relevant lines covered (94.4%)

12095.49 hits per line

Jobs
ID Job ID Ran Files Coverage
1 25480754647.1 13
94.4
 GitHub Action Run
Source Files on build 25480754647