Skip to content
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

Tremor Video Bid Adapter #1552

Merged
merged 5 commits into from
Sep 11, 2017
Merged

Tremor Video Bid Adapter #1552

merged 5 commits into from
Sep 11, 2017

Conversation

tremorvideo
Copy link
Contributor

@tremorvideo tremorvideo commented Aug 31, 2017

Type of change

  • New bidder adapter

Description of change

Tremor video bid adapter.

  • test parameters for validating bids
{
  bidder: 'tremor',
  params: {
    adCode: "ssp-!demo!-lufip",
    supplyCode: "ssp-%21demo%21-rm6rh"
  }
}

Other information

…with what we use at tremor.

- Changed a test to look for document.location.href instead of a hardcoded localhost url.
Copy link
Collaborator

@matthewlane matthewlane left a comment

Choose a reason for hiding this comment

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

Thanks for the PR, tests are passing and validated bid responses. One comment for review below

bid.crid = response.crid;
bid.vastXml = response.adm;
// This is a dummy vast URL, Tremor sends back the vast XML (the line above).
bid.vastUrl = 'http://cdn.tremorhub.com/static/dummy.xml';
Copy link
Collaborator

Choose a reason for hiding this comment

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

Bid responses with a vastXml property will now pass validation with #1556 in master, so if Tremor sends xml and not a vast url, this line can be dropped

@@ -1945,7 +1945,7 @@ d@1:
dependencies:
es5-ext "^0.10.9"

"dargs@github:christian-bromann/dargs":
dargs@christian-bromann/dargs:
Copy link
Contributor

@dbemiller dbemiller Sep 7, 2017

Choose a reason for hiding this comment

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

This doesn't look intentional... not sure why it changed?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Running yarn install on current master resulted in this update to the lockfile for me too. I tried deleting node_modules then yarn install again with this changed lockfile and things still build out properly

Copy link
Contributor

Choose a reason for hiding this comment

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

ahh... common mistake. I ran into this recently, and it's just a weird API on their part.

yarn install pulls the latest dependencies which package.json allows. This might change your yarn.lock, if someone released a new version of a package recently.

yarn install --pure-lockfile installs the dependencies from yarn.lock without changing them.

Very unlikely to do any real harm, though.

@dbemiller dbemiller merged commit 27944ac into prebid:master Sep 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants