Yahoo Bid Adapter: prevent error being thrown if GPP consent module is not enabled #10169
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
slimkrazy
changed the title
ChrisHuie
approved these changes
Jun 30, 2023
ChrisHuie
changed the title
|
will this get included in the next Prebid 8 release? Right now the yahoosspBidAdapter in Prebid 8 do not have these changes Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change
Bugfix
Feature
New bidder adapter
Code style update (formatting, local variables)
Refactoring (no functional changes, no api changes)
Build related changes
CI related changes
Does this change affect user-facing APIs or examples documented on http://prebid.org?
Other
Description of change
This bug was introduced when we started to consume GPP signals. We've been lucky in that not many publishers switched to this bid adapter from the legacy AOL bid adapter. Issue has already been addressed for v8.x, so this fix ensures that any publishers who switch to the yahoossp bid adapter without upgrading to v8 (we are actively encouraging publishers to do this now) will not have this issue.
Other information