Skip to content
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

Lotame ID Module : honor publisher-supplied configuration object #12403

Merged
merged 1 commit into from
Nov 27, 2024

Conversation

Tonsil
Copy link
Contributor

@Tonsil Tonsil commented Nov 4, 2024

Type of change

  • Bugfix

  • Feature

  • New bidder adapter

  • Updated bidder adapter

  • 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

Updates the Lotame User ID module to honor a publisher-supplied storage configuration object, if passed as a parameter. Per Issue 10710, concern was raised that this update was necessary prior to Prebid's 10.0 API Change.

Other information

@Tonsil Tonsil force-pushed the lotameHonorPublisherConfigs branch from 4903995 to 5ee5f03 Compare November 13, 2024 15:04
@Tonsil
Copy link
Contributor Author

Tonsil commented Nov 18, 2024

Any news here? I don't know what the situation is with that ci/circleci: e2etest failure, but I don't think it has anything to do with me.

@ChrisHuie ChrisHuie changed the title Lotame ID - honor publisher-supplied configuration object Lotame ID Module : honor publisher-supplied configuration object Nov 27, 2024
@ChrisHuie ChrisHuie self-assigned this Nov 27, 2024
@ChrisHuie ChrisHuie assigned ChrisHuie and unassigned ChrisHuie Nov 27, 2024
@ChrisHuie ChrisHuie merged commit 789d500 into prebid:master Nov 27, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants