Adapter Name Case Insensitive: BidAdjustmentFactors Update #3210
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
AlexBVolcy
changed the title
VeronikaSolovei9
approved these changes
Oct 15, 2023
bsardo
changed the title
svamiftah
pushed a commit
to sovrn/prebid-server
that referenced
this pull request
Nov 21, 2023
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.
There was a PR released to allow bidder names defined in
ext.prebid.bidadjustmentfactors.BIDDERto be case insensitive: #3140However, an update PR was needed for scenarios where the case style of a bidder in the
bidadjustmentfactorswas different from the bidder defined in the impression, would lead to thebidadjustmentfactornot being applied.Along with that, extra validation was added, and tests.