-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Core: add PUC version in targeting keys #13885
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
Conversation
|
Tread carefully! This PR adds 1 linter error (possibly disabled through directives):
|
Pull Request Test Coverage Report for Build 17651753938Details
💛 - Coveralls |
| UUID: 'hb_uuid', | ||
| CACHE_HOST: 'hb_cache_host' | ||
| CACHE_HOST: 'hb_cache_host', | ||
| VERSION: 'hb_ver' |
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 do not think we'd want this to be a default targeting key if we're not recommending the puc?
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.
what should the default behavior be on setting this key? should we put out the docs release before we close the issue?
|
Including it by default makes it a bit easier to transition away from |
|
that's reasonable, advanced users on the new methods can easily also remove a key they don't want. |
Type of change
Description of change
This adds the
hb_verkey-value to all targeting, controllable withtargetingControls.versionand containing the PUC version to use,so that creatives using PUC can avoid pointing to
@latest(see prebid/prebid-universal-creative#187)Other information
Closes prebid/prebid-universal-creative#187