feat: Update GraphQL schema to create or update charges #405
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
We want to introduce a new charge model to charge users based on a consumed volume.
The existing graduated pricing does not fit this need because it creates tier, and each tier has its own price.
The volume price works differently, it creates tiers, but the whole number of units is multiplied by the current tier. Then, the number of units consumed determine the total price for each unit.
Description
This PR updates the GraphQL schema to allow creation, update and query of the Volume charge model.
VolumeRange
type is added to handle range definition. Attributes arefromValue
,toValue
,perUnitAmount
andflatAmount
Charge
type is updated to add a newvolumeRanges
attribute as an array ofVolumeRange
VolumeRangeInput
type is added to handle range creation and update. Arguments arefromValue
,toValue
,perUnitAmount
andflatAmount
ChargeInput
type used increatePlan
andupdatePlan
is also updated to handle a new argumentvolumeRangeInput
as an array ofVolumeRangeInput
Related Task
This PR follows #394 and #404