Skip to content

Conversation

@HeinzBaumann
Copy link
Collaborator

@HeinzBaumann HeinzBaumann commented Jun 2, 2025

initial code to support TCF 2.2

  • suppress direct access to TCF data using getField
  • added special handling for exceptions based on TCF policy
  • Incremented the policy version to 5
  • updated list of supported languages
  • updated test

Initial code to support TCF 2.3

  • support latest spec changes to support TCF 2.3
  • update and fixed test cases

@HeinzBaumann HeinzBaumann changed the title initial code to support TCF 2.2 initial code to support TCF 2.2 (no yet redy for review) Jun 2, 2025
@HeinzBaumann HeinzBaumann changed the title initial code to support TCF 2.2 (no yet redy for review) initial code to support TCF and 2.3 (no yet ready for review) Jun 2, 2025
@HeinzBaumann HeinzBaumann changed the title initial code to support TCF and 2.3 (no yet ready for review) Initial code to support TCF v2.3 (no yet ready for review) Jun 2, 2025
Comment on lines +101 to +103
if (segments.length >= 3) {
encodedSegments.push(segments[3].encode());
}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Technically the ENUM value for VendorsDisclosed is 1 and PublisherPurposes is 3...so shouldn't the segments switch order? I know their first field indicates their segment type, and it doesn't REALLY matter, so I'm fine with just doing it this way. I mean, it's been in the wrong order for this long right?

Comment on lines +144 to +148
private updateDateStamp(): void {
const date = new Date();
const utcDate = new Date(Date.UTC(date.getUTCFullYear(), date.getUTCMonth(), date.getUTCDate()));
super.setFieldValue(TcfEuV2Field.CREATED, utcDate);
super.setFieldValue(TcfEuV2Field.LAST_UPDATED, utcDate);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉 THANK YOU! Only using Year, Month, Date is the correct implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants