-
Notifications
You must be signed in to change notification settings - Fork 769
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
Rubicon: Remove imp.ext.context references #3918
Conversation
Code coverage summaryNote:
rubiconRefer here for heat map coverage report
|
imp.ext.context
referencesimp.ext.context
references
@MaksymTeqBlaze can you please review once conflicts have been resolved? |
This branch has conflicts that must be resolved
@CTMBNara please resolve conflicts |
adapters/rubicon/rubicon.go
Outdated
return contextData.AdServer.AdSlot | ||
} else if data.AdServer.Name == "gam" && data.AdServer.AdSlot != "" { | ||
func extractDfpAdUnitCode(data rubiconData) string { | ||
if data.AdServer.Name == "gam" && data.AdServer.AdSlot != "" { |
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.
How about if strings.ToLower(data.AdServer.Name) == "gam"
to make sure "GAM" is also a valid Ad Server Name?
Optional: && len(data.AdServer.AdSlot) != 0
, it just looks cleaner to me.
Also please sync this branch with the latest PBS main branch.
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.
"gam": this is exactly how it works in PrebidJava, not sure if case matters but i would prefer to copy java logic
@CTMBNara when you get a minute, please resolve conflicts and address the outstanding comment. Thanks! |
imp.ext.context
references…ext-references # Conflicts: # adapters/rubicon/rubicon.go
Code coverage summaryNote:
rubiconRefer here for heat map coverage report
|
"data": { | ||
"adserver": { | ||
"name": "gam", | ||
"adslot": "adSlotFromData" | ||
} | ||
"adslot": "adSlotFromContextData" |
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.
Nitpick: would it be more appropriate if the references to "adSlotFromContextData"
in this file were "adSlotFromData"
?
"data": { | ||
"adserver": { | ||
"name": "gam", | ||
"adslot": "adSlotFromData" | ||
} | ||
"adslot": "adSlotFromContextData" |
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.
Nitpick: would it be more appropriate if the references to "adSlotFromContextData"
in this file were "adSlotFromData"
?
Code coverage summaryNote:
rubiconRefer here for heat map coverage report
|
No description provided.