Audience Network: ensure interpretResponse can handle both string and array based sizes #1873
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also ensures pageurl encoding is consistently applied
This was referenced Nov 22, 2017
jaiminpanchal27
approved these changes
Nov 27, 2017
mkendall07
approved these changes
Nov 27, 2017
dluxemburg
pushed a commit
to Genius/Prebid.js
that referenced
this pull request
Jul 17, 2018
…ebid#1873) Also ensures pageurl encoding is consistently applied
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change
Description of change
Hello, this is the fix for #1851, which includes an update to the unit tests that would have caught the problem.
It also ensures
pageurlencoding is consistently applied. This recently came up as a comment on a previous PR #1502 (comment)This work was commissioned and paid for by Facebook.