Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Bidding Signals Format "V1" support #1390

Closed
wants to merge 2 commits into from

Conversation

MattMenke2
Copy link
Contributor

@MattMenke2 MattMenke2 commented Jan 28, 2025

This removes mention of the Trusted Bidding Signals V1 format, as well as the "Bidding-Signals-Format-Version: 2" header, as there's no plan for a version 3, and "version 2" can be easily confused with the KVv2 API. All responses will be assumed to be version 2.


Preview | Diff

This removes mention of the Trusted Bidding Signals V1 format, as well as the "Bidding-Signals-Format-Version: 2" header, as there's no plan for a version 3, and "version 2" can be easily confused with the KVv2 API.  All responses will be assumed to be version 2.
1. [=Assert=] |isBiddingSignal| is true.
1. Let |perInterestGroupData| be |signals|["`perInterestGroupData`"].
1. If |signals|["`keys`"] does not [=map/exist=], return « null, null ».
1. Set |signals| to |signals|["`keys`"].
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is a little awkward, and this entire method has a bunch of bugs (e.g., line 2711 should be before we set signals, a bunch of the returns only return two values instead of three, some places "set |signals| to null and return failure" (signals isn't even being returned, and wasn't passed in by the caller, so setting it to null doesn't do anything), etc.

I think fixing all of that is beyond the scope of this PR.

@MattMenke2 MattMenke2 closed this Jan 28, 2025
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.

1 participant