Repository navigation
Limelight: New Alias Datafusion - #15119
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e072d0c865
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| { code: 'pgamrtb' }, | ||
| { code: 'nuclion' } | ||
| { code: 'nuclion' }, | ||
| { code: 'datafusion' } |
There was a problem hiding this comment.
For server-side or hybrid Limelight configurations, this new PBJS alias also needs a matching Prebid Server alias (or a linked companion change) because Limelight is documented as having a Prebid Server adapter and the module rules require bidder codes and aliases to stay consistent across PBJS/PBS. With only this client-side registration, publishers using bidder datafusion in a pure PBS or s2sTesting setup won't have a server-side alias to route those auctions to Limelight.
Useful? React with 👍 / 👎.
Co-authored-by: mderevyanko <mderevyanko24@gmail.com>
Type of change
Bugfix
Feature
New bidder adapter
Updated bidder adapter New Adapter: Datafusion - Limelight alias prebid-server#4825 Limelight: New Adapter Datafusion prebid.github.io#6624
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
Other information