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

Remove min from buckets propType #72

Merged
merged 2 commits into from
Sep 20, 2022
Merged

Conversation

JavierMartinz
Copy link
Contributor

https://docs.prebid.org/dev-docs/publisher-api-reference/setConfig.html

Warning: As of Prebid.js 3.0, the ‘min’ parameter is no longer supported in custom granularities.

Also note an important idiosyncracy of the way that price ranges are supported: the interval starts at the min value, and the max of one range defines the min of the next range. So if the second interval defines an implicit min of 0.99 and goes to 5 with an increment of 0.05, Prebid.js will generate the values: 0.99, 1.04, 1.09, etc.

This implies that ranges should have max values that are really the min value of next range.

Warning: As of Prebid.js 3.0, the ‘min’ parameter is no longer supported in custom granularities.

Also note an important idiosyncracy of the way that price ranges are supported: the interval starts at the min value, and the max of one range defines the min of the next range. So if the second interval defines an implicit min of 0.99 and goes to 5 with an increment of 0.05, Prebid.js will generate the values: 0.99, 1.04, 1.09, etc.

This implies that ranges should have max values that are really the min value of next range.
@pahund pahund merged commit 10c91f8 into KijijiCA:master Sep 20, 2022
kristapsPelna added a commit to kristapsPelna/react-advertising that referenced this pull request Nov 9, 2022
PR KijijiCA#72 (KijijiCA#72) broke a test where
```
priceGranularity: { buckets: [{ max: 3, increment: 4 }] }
```
Was left as `expectToPass: false` while in reality it should have been changed to valid or preferably removed since the value is identical to the use case directly above it.
jdw1996 pushed a commit that referenced this pull request Nov 9, 2022
PR #72 (#72) broke a test where
```
priceGranularity: { buckets: [{ max: 3, increment: 4 }] }
```
Was left as `expectToPass: false` while in reality it should have been changed to valid or preferably removed since the value is identical to the use case directly above it.
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.

None yet

2 participants