Repository navigation
Conversation
Code coverage summaryNote:
flippRefer here for heat map coverage report |
Flipp's Mobile Swipe format can be requested per placement via
options.mobileSwipe, which our ad service now accepts. The option
cannot reach it through this adapter today: ImpExtFlippOptions is a
typed struct and jsonutil.Unmarshal is non-strict, so an unknown key in
imp.ext.bidder.options is silently discarded and the struct is
re-marshalled into the outgoing body without it:
in: {"startCompact":true,"mobileSwipe":true}
out: {"startCompact":true}
static/bidder-params/flipp.json does not set additionalProperties to
false, so the param passes schema validation first and then vanishes.
A publisher sets it, receives no error, and nothing happens.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
a6cc9f7 to
06eaaf9
Compare
Code coverage summaryNote:
flippRefer here for heat map coverage report |
|
Thanks @przemkaczmarek for taking care of this PR! Do you know when we will merge this into master? Thanks! |
|
Looks good. Could you open a docs PR adding Do not forget upgrade your branch: |
Thanks! Docs PR is up: prebid/prebid.github.io#6796. I’ll update the branch with master as well. |
Code coverage summaryNote:
flippRefer here for heat map coverage report |
Code coverage summaryNote:
flippRefer here for heat map coverage report |
Code coverage summaryNote:
flippRefer here for heat map coverage report |
Adds
mobileSwipeto the Flipp adapter'soptionsbidder param, so publishers can request Flipp's Mobile Swipe format per placement.The key cannot reach our endpoint today:
ImpExtFlippOptionsis a typed struct andjsonutil.Unmarshalis non-strict, so it is dropped without an error and the struct is re-marshalled into the outgoing request without it.Adds the struct field, the schema property, param tests, and an exemplary case covering the forwarding. No change to the outgoing body when the option is absent.
🤖 Generated with Claude Code