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

fix(bidcaching):remove teads from bidcaching #54

Merged

Conversation

raquelyustemrf
Copy link

No description provided.

src/targeting.js Outdated
bidsToProcess = bidsToFilter.filter(bid => isBidSizeAllowed(bid, allowedSizes));
bidsToProcess = bidsToFilter
.filter(bid => isBidSizeAllowed(bid, allowedSizes))
.filter(bid => !(isBidCached(bid) && getBidName(bid) === 'teads'));

Choose a reason for hiding this comment

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

I would set an array of blacklisted bidders in order to make it easier add new ones to the black list if we don't want to perform bid caching on them. Moreover, what do you think to gather it on a different function? Something like:

isBidAllowed = () => !(isBidCached(bid) && blacklistedCacheBidders.includes(getBidName(bid)))

Choose a reason for hiding this comment

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

Besides that, we could add a test to cover it.

Copy link
Author

Choose a reason for hiding this comment

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

Cool!

oscarmarimrf
oscarmarimrf previously approved these changes Mar 18, 2020
@oscarmarimrf oscarmarimrf dismissed their stale review March 18, 2020 18:13

I approved it too early, we still need the tests 😅

@raquelyustemrf raquelyustemrf merged commit d5205a3 into marfeel-master Mar 19, 2020
@raquelyustemrf raquelyustemrf deleted the MRF-67621/remove-teads-from-bid-caching branch March 19, 2020 10:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants