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

modify mediago bidder adapter to compatible with version 2.0 and version 3.0 #5680

Closed
wants to merge 15 commits into from
Closed

Conversation

SylviaF
Copy link
Contributor

@SylviaF SylviaF commented Aug 31, 2020

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

modify mediago bidder adapter to compatible with version 2.0 and version 3.0

  • test parameters for validating bids
{
  bidder: 'mediago',
  params: {
          token: '85a6b01e41ac36d49744fad726e3655d'
  }
}

Be sure to test the integration with your adserver using the Hello World sample page.

  • contact email of the adapter’s maintainer
  • official adapter submission

For any changes that affect user-facing APIs or example code documented on http://prebid.org, please provide:

Other information

*/
const getCookie = function(name) {
if (getProperty(window, 'document', 'cookie')) {
let m = window.document.cookie.match('(^|;)\\s*' + name + '\\s*=\\s*([^;]*)\\s*(;|$)');
Copy link
Collaborator

Choose a reason for hiding this comment

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

why did you comment out and bypass storage manager?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I need to compatible with Prebid v2.0 and v3.0.
And the storage manager dosen't be added in v2.0 and v3.0.

@patmmccann
Copy link
Collaborator

patmmccann commented Sep 1, 2020

The 3.27.x legacy branch will not have any more merges

@SylviaF
Copy link
Contributor Author

SylviaF commented Sep 1, 2020

The 3.27.x legacy branch will not have any more merges

Hi, sorry for the trouble.

Because our partners are unwilling to use the new version, if the old version cannot be merged into the new update, I would like to know what other way we can cooperate with those partners who do not want to use the new version Prebid?

@patmmccann
Copy link
Collaborator

patmmccann commented Sep 1, 2020 via email

@SylviaF
Copy link
Contributor Author

SylviaF commented Sep 2, 2020

Perhaps your partners' concerns can be addressed? What are they?

On Tue, Sep 1, 2020, 8:07 AM 方思敏 @.***> wrote: The 3.27.x legacy branch will not have any more merges Hi, sorry for the trouble. Because our partners are unwilling to use the new version, if the old version cannot be merged into the new update, I would like to know what other way we can cooperate with those partners who do not want to use the new version Prebid? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5680 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAM25Z6R2OTGHEMJBYAKVSDSDTPYZANCNFSM4QQO2A4A .

Not all SSP partners have the latest adapter; updating to the latest prebid breaks functionality for some partners, different wrapper partners only support certain adapter versions

@patmmccann
Copy link
Collaborator

patmmccann commented Sep 2, 2020

If functionality is breaking on a recent version, I'd encourage you to open an issue. However, your adapter needs to follow rules that are built with publisher trust in mind. One of these is using the storage manager.

@SylviaF
Copy link
Contributor Author

SylviaF commented Sep 3, 2020

If functionality is breaking on a recent version, I'd encourage you to open an issue. However, your adapter needs to follow rules that are built with publisher trust in mind. One of these is using the storage manager.

If it is not merged into the master, but only added to the old version branch, For example, is it allowed if I only change the code and merge some specific branches, such as v3.2.

@patmmccann
Copy link
Collaborator

We don't do merges to old branches except near the time of major version releases. 3.27.1 was the last 3.x release and there are no more planned.

@patmmccann
Copy link
Collaborator

Also, your PR is against master and not against legacy anyways

@SylviaF
Copy link
Contributor Author

SylviaF commented Sep 4, 2020

We don't do merges to old branches except near the time of major version releases. 3.27.1 was the last 3.x release and there are no more planned.

OK, sorry for the trouble and thanks for your answer. I think this PR can be dropped now.

But I found that our mediago bid adapter seems to be released in version 4.5.
I would like to know if there is a chance to update to at least to version 4.0 - version 4.5?

@patmmccann
Copy link
Collaborator

patmmccann commented Sep 4, 2020 via email

@SylviaF
Copy link
Contributor Author

SylviaF commented Sep 7, 2020

You're welcome to submit changes to your adapter against the master branch. There are not separate branches for each minor version change that you can commit against and that are maintained independently. If you make commits now, your existing adapter would be in 4.5 and your changes would likely be in 4.7 or 4.8. The version that is in 4.5 now will never change. Every week the number increments, with any change to 4.x

On Thu, Sep 3, 2020 at 11:48 PM 方思敏 @.***> wrote: We don't do merges to old branches except near the time of major version releases. 3.27.1 was the last 3.x release and there are no more planned. OK, sorry for the trouble and thanks for your answer. I think this PR can be dropped now. But I found that our mediago bid adapter seems to be released in version 4.5. I would like to know if there is a chance to update to at least to version 4.0 - version 4.5? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#5680 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAM25Z634YLESU4RWJ357YTSEBPR5ANCNFSM4QQO2A4A .

Got it. Thanks for your patience and answer.

@smenzer smenzer mentioned this pull request Sep 8, 2020
10 tasks
@stale
Copy link

stale bot commented Oct 4, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Oct 4, 2020
@stale stale bot closed this Oct 11, 2020
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.

2 participants