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

fixed bug with sortByDealAndPriceBucketOrCpm #5504

Merged
merged 2 commits into from
Jul 31, 2020

Conversation

ghost
Copy link

@ghost ghost commented Jul 16, 2020

Type of change

  • Bugfix

Description of change

Fixes a bug related to sortByDealAndPriceBucketOrCpm when sendBidsControl.dealPrioritization = true

Other information

#5424

@lgtm-com
Copy link

lgtm-com bot commented Jul 16, 2020

This pull request fixes 1 alert when merging 697613f into 1049d07 - view on LGTM.com

fixed alerts:

  • 1 for Invocation of non-function

Copy link
Contributor

@FilipStamenkovic FilipStamenkovic left a comment

Choose a reason for hiding this comment

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

Fix looks ok, but it should be covered with test case.

Also, please rebase/merge your branch with origin/master, currently you are 350+ commits behind

src/targeting.js Show resolved Hide resolved
@FilipStamenkovic FilipStamenkovic added needs update needs 2nd review Core module updates require two approvals from the core team labels Jul 21, 2020
@ghost ghost force-pushed the bugfix/biddealprioritization branch from 697613f to d06c7fc Compare July 22, 2020 12:26
@lgtm-com
Copy link

lgtm-com bot commented Jul 22, 2020

This pull request fixes 1 alert when merging d06c7fc into 3a8f5cd - view on LGTM.com

fixed alerts:

  • 1 for Invocation of non-function

@FilipStamenkovic
Copy link
Contributor

FilipStamenkovic commented Jul 29, 2020

I still don't see that fix is covered by a test case, can you add test case that will cover it?
Also, since this is change in prebid core, you will need 2nd reviewer to approve MR.

@ghost ghost force-pushed the bugfix/biddealprioritization branch from d06c7fc to b269d69 Compare July 29, 2020 11:23
Copy link
Contributor

@FilipStamenkovic FilipStamenkovic left a comment

Choose a reason for hiding this comment

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

LGTM

@ghost ghost requested a review from mkendall07 July 29, 2020 11:33
@lgtm-com
Copy link

lgtm-com bot commented Jul 29, 2020

This pull request fixes 1 alert when merging b269d69 into f9631fb - view on LGTM.com

fixed alerts:

  • 1 for Invocation of non-function

@@ -240,13 +240,13 @@ export function newTargeting(auctionManager) {
let targetingMap = Object.keys(targetingCopy).map(adUnitCode => {
return {
adUnitCode,
adUnitTargeting: targetingCopy[adUnitCode]
adserverTargeting: targetingCopy[adUnitCode]
Copy link
Member

Choose a reason for hiding this comment

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

curious why this name was changed?

Copy link
Author

Choose a reason for hiding this comment

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

The sortByDealAndPriceBucketOrCpm is now also used in getHighestCpmBidsFromBidPool and the bids received object has the original name of adserverTargeting. If we want to leave the adUnitTargeting name for that cloned targeting map I could change it to work a different way. Just felt it made sense to go with the same name and went with the original adserverTargeting name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs 2nd review Core module updates require two approvals from the core team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants