-
Notifications
You must be signed in to change notification settings - Fork 738
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
Fix: Use request alias as adaptercode #3587
Fix: Use request alias as adaptercode #3587
Conversation
@@ -379,14 +379,20 @@ func (bidder *bidderAdapter) requestBid(ctx context.Context, bidderRequest Bidde | |||
} | |||
} | |||
|
|||
alternateBidderCode := "" | |||
if !strings.EqualFold(bidderRequest.BidderName.String(), bidderName.String()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a test in place where bidderRequest.BidderName
is different from bidderName.string
I can't seem to find it, but just want to ensure we're testing the main case of this PR that you laid out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In case of aliase bidder its possible to have bidderRequest.BidderName is different that bidderName.
For example groupm is alias/alternate bidder code of pubmatic. So in this case bidderRequest.BidderName will be pubmatic and bidderName will be groupm. We are expecting adaptercode as pubmatic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, is it possible to add a json test of some kind where we can have this situation covered?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AlexBVolcy Added json test file alternate-bidder-codes-aliase.json
…ver into Fix_3363_adaptercode
…ver into Fix_3363_adaptercode
@Pubmatic-Supriya-Patil Hello! Just checking in to see if you've been able to see my feedback? |
Closing as this has been handled with a slightly different approach in #3661. |
This PR solves issue mentioned in #3363