-
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
UOL - BidAdapter release candidate #2850
Conversation
This pull request introduces 1 alert when merging fc26641 into ed28094 - view on LGTM.com new alerts:
Comment posted by LGTM.com |
@lotani-uolinc Can you please look into the LGTM error when you get the chance? |
@jsnellbaker, sure thing! Thanks for the feedback. |
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.
@lotani-uolinc While you're looking into the LGTM error, I checked the rest of the adapter code. I found a few areas that should be reviewed further.
Additionally, I noticed in your docs PR you had included the gdpr_supported
flag. However, I don't see the normal code that reads the buildRequest
's bidderRequest.gdprConsent
object and pass it along in your request object. Is this code missing or was the flag set incorrectly in the docs PR? Please confirm.
Thanks.
modules/uolBidAdapter.js
Outdated
@@ -0,0 +1,202 @@ | |||
import * as utils from 'src/utils'; | |||
// import {config} from 'src/config'; |
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 comment can be removed.
modules/uolBidAdapter.js
Outdated
const UOL_LOG_HEADER = 'UOL Bidder Error: ' | ||
export const spec = { | ||
code: BIDDER_CODE, | ||
supportedMediaTypes: ['banner'], // not required since it is default |
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.
Could import/use the defined mediaTypes from src/mediaTypes
. Eg import { BANNER } from 'src/mediaTypes';
This way you can ensure the values are read correctly.
modules/uolBidAdapter.js
Outdated
*/ | ||
getUserSyncs: function(syncOptions, serverResponses) { | ||
const syncs = []; | ||
if (syncOptions.iframeEnabled && serverResponses.body.trackingPixel) { |
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.
serverResponses
is an array of objects, not a single object. This latter half of the code would result in undefined errors. Could you update this logic?
modules/uolBidAdapter.js
Outdated
*/ | ||
onTimeout: function(data) { | ||
// Bidder specifc code | ||
return true; |
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.
Is there any more you would wish to do in the case of a timeout?
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.
For the time being we have no plans hence, Im removing the method call.
@lotani-uolinc I saw your response in github before in regards to GDPR support, but I'm not seeing it anymore (not sure what happened). If you're still not currently planning on supporting GDPR - could you please make a change to your docs PR? The field in the docs PR is an internal variable for the prebid site that will list that adapter in a certain table of GDPR compliant adapters. Until your adapter supports GDPR, can you either remove the variable or set it to |
@jsnellbaker, no problem. We have set it to false and will release it soon. Thanks in advance. |
@jsnellbaker, we have addressed the changes requested. Could you please evaluate? |
@lotani-uolinc Thanks for making the updates. They look fine to me. In addition the test param information seems to be working successfully as well. Something I noticed while testing with browserstack in preparation for the merge were a series of errors from the unit tests. There seemed to be two sets of errors occurring in different browsers (safari mainly) that I've copied down below for reference. Can you take a look and see if something can be done to address these errors?
|
@jsnellbaker, thanks for the review. We are now looking into alternatives for the safari issue. |
@jsnellbaker, as a fix, we disabled geolocation tests for engines that do not implement permission and geolocation APIs. |
@lotani-uolinc That's fine; it looks like everything is settled. |
@jsnellbaker, nice! Thanks for your time. |
Type of change
Description of change
New bidAdapter proposal from UOL - Universo Online.