-
Notifications
You must be signed in to change notification settings - Fork 812
VISX: Add string support to UID #2501
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
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,7 +5,8 @@ | |
"type": "object", | ||
"properties": { | ||
"uid": { | ||
"type": "integer", | ||
"type": ["integer", "string"], | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @deubaka can we reflect this change in the bid-param section of the docs please? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good catch, thanks! We've added the corresponding updates in this PR, prebid/prebid.github.io#4273. |
||
"pattern": "^\\d+$", | ||
"description": "An ID which identifies this placement of the impression" | ||
}, | ||
"size": { | ||
|
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.
Nitpicks:
int
that comes with achar
in here?string
unit tests on thevalidParams
side?Uh oh!
There was an error while loading. Please reload this page.
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.
Hi @guscarreon,
Thanks for the feedback.
On #1, I'm not sure if it's still necessary given that case would be an invalid JSON altogether, and parsing should fail already, without reaching schema validation.
As for #2, make sense, just to make sure it's covered as well.