-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
airgridRtdProvider: use provided tag insertion method loadExternalScript
#9901
Merged
Merged
Changes from 14 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
ea68e95
chore: update `getAudiencesAsBidderOrtb2` implementation and test
naripok 56abb14
Merge pull request #1 from AirGrid/chore/update-airgrid-rtd-module
naripok 7b5f106
Merge remote-tracking branch 'upstream/master'
naripok a885439
chore: use provided tag insertion method
naripok b2d56ba
fix: add `airgrid` to `_approvedLoadExternalJSList`
naripok 3209565
fix: use 'sdk' path if no publisherId is provided
naripok d5e12e6
Merge pull request #2 from AirGrid/chore/1459-use-tag-insertion-method
naripok c6d9fdd
Merge branch 'master' of https://github.com/prebid/Prebid.js
naripok 665b1aa
Merge branch 'prebid:master' into master
naripok 7798c95
fix: use accountId as path param for script url
naripok 20a3926
fix: assign edktInitializor props before `loadExternalScript` call
naripok 6cc0ac9
fix: set `edktInitializor.invoked` before calling `loadExternalScript`
naripok 5b0ca57
Merge branch 'prebid:master' into master
naripok b2af960
fix: restore method for setting `user.ext.data`
naripok 7bde0ca
fix: rollback changes to data setting method
naripok c4f8e53
Merge branch 'master' into master
naripok File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
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.
this is out of spec -
data
should be an array, sorry for not catching this earlier.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.
Oh, I saw it and missed anyway...
Thank you for the catch! Let me fix that.
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.
Wait, sorry about the confusion @dgirardi, but we're using
user.ext.data
here, notuser.data
, which is an array.Should we be using
user.data
instead?I saw it was present here as an obj and we were using it also in the previous implementation, but I'm not sure anyway.
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.
user.ext.data
is the safer choice, it has been "promoted" touser.data
in ORTB version 2.6 but afaik that hasn't been widely adopted yet.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.
Thanks for the explanation!
Does this mean that we're good, then? 😅
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.
No objection to forking the PR, but I'd prefer then if you rolled this back to just the
loadExternalScript
change so that the incorrect values inuser.ext
are not forgotten.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.
@dgirardi, I've reverted the data setting changes so this PR includes only the
loadExternalScript
changes.Now, for the data setting method, as per last feedback, I understand that the changes introduced in this PR are bad, and we should revert those to the previous setting method, right?
I'm just a little bit confused with all the back and forth we had, so, I'm sorry to ask, but could you please again be very specific in which should be the desired data setting method you'd like to see for the next PR?
Is this the preferred way to go forward?
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.
the method is the one you just had in the previous commit, with the difference that the data should be formatted as a ORTB
user.data
segment.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.
Oh, alright, got ya!
Thanks!
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.
@dgirardi, I've pushed the data setting changes to a PR in our fork here. I'll open a PR here once I know it is good and we have this PR merged.
Would you mind checking out the question in this comment, please?
I'm doing some guesswork there, and it would be great to have some confirmation that I'm getting it right.
Thank you very much!