v0.200

0.200

• refactor constants, stop use dualvars
• validate parameters on method check_publisher_restriction
• add method publisher_restrictions by vendor id
• add prefetch option to cache vendor ids when the consent string is range based.
  It is 2x faster check consent on a prefetched vendor than a regular one if the consent is range based.
  Without increase the Parsing time.

v0.100

first "stable" release

0.100

• parse publisher tc section if available #13
• add strict mode (disabled by default) to validate the consent string version

v0.084

0.084

• fix a bug while parsing valid consent strings range-based, see #20

v0.083

0.083

• refactor on Publisher Restriction parsing.
• small fixes about data and offset.
• performance improvement: when we parse a range-based consent string now the Parse method is 23% faster, TO_JSON is 9% faster and check vendor consent or legitimate interest is between 122% and 137% faster than the previous version
• remove GDPR::IAB::TCFv2::RangeConsent package

v0.082

• increase TO_JSON performance by 76% on bitfields and 3116% on range based vendor section
• add json section 'publisher' and include all publisher restriction, if any, per purpose id, vendor id and restriction type

0.081

Changes:

• reorganize JSON output (group sections vendor and purpose )
• small fixes in pod

v0.0.8

0.08

• add TO_JSON method #5
• substitute offset numbers by constants
• fix typos in pod documentation
• test tests for pod

v0.07

0.07

• add check for publisher restrictions #11
• validate if string is a valid base64 url encoded string #3

v0.06

include fixes for

• #2
• #7

changelog

• add special features as constants
• add purpose ids as constants
• add missing methods on pod documentation
• on list context methods created and last_updated should return epoch in seconds + nanoseconds

v0.051

small document fixes