Skip to content

Sovrn adapter updates: schain, digitrust, pixel syncing, and 3.0 upgrades #4385

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

Merged

Conversation

aprakash-sovrn
Copy link
Contributor

Type of change

  • Bugfix
  • Feature
  • New 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

Sovrn bid adapter changes:

  • Added forwarding of schain and digitrust ID's to bid request

  • Supporting pixel syncing fro bid responses

  • Prebid.js 3.0 compliance updates

  • contact email of the adapter’s maintainer: [email protected]

  • official adapter submission

@aprakash-sovrn
Copy link
Contributor Author

addressing backwards-compatibility issue discussed on #4376. still not sure if anything has to change with pixel syncing implementation?

@aprakash-sovrn aprakash-sovrn changed the title Many sneks schain digitrust pixel beacons Sovrn adapter updates: schain, digitrust, pixel syncing, and 3.0 upgrades Oct 28, 2019
expect(returnStatement).to.be.empty;
});

it.only('should include pixel syncs', () => {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be reverted to it(...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch, sorry about that

Copy link
Collaborator

@jsnellbaker jsnellbaker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @aprakash-sovrn

Can you please take a look at the feedback below and make the requested updates?

In addition, can you please remove the package-lock.json changes?

Thanks.

Comment on lines 63 to 65
const el = document.createElement('a');
el.href = page;
const domain = el.hostname;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of doing this (which isn't really ideal), can you use the parse function from the url.js file to read the page variable; it'll provide the hostname in the returned object.

@@ -73,7 +76,7 @@ describe('sovrnBidAdapter', function() {
expect(payload.imp[0].banner.h).to.equal(1)
})

it('accepts a single array as a size', function() {
it('accepts a single array as a size', () => {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please change this back to function() { here (and in other parts of the test file)? We want to keep it this style to better conform for Mocha.

@jsnellbaker jsnellbaker removed the request for review from GLStephen November 7, 2019 20:47
@jsnellbaker jsnellbaker assigned jsnellbaker and unassigned GLStephen Nov 7, 2019
@aprakash-sovrn aprakash-sovrn force-pushed the many_sneks_schain_digitrust_pixel-beacons branch from 3b2e522 to 5cab28c Compare November 7, 2019 22:01
@s-nikulin-lineate s-nikulin-lineate deleted the many_sneks_schain_digitrust_pixel-beacons branch June 20, 2022 14:00
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.

6 participants