docs(fees): describe aggregated Distributions feeCost in FeeSplit.recipients#537
Merged
Merged
Conversation
…ipients Partner distribution recipients are now reported as one aggregated `Distributions` FeeCost (total amount + per-recipient breakdown), with the same shape on quote, route, and status responses — not per-receiver `Fee Forward` entries. Update the FeeSplit.recipients JSDoc accordingly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Update the
FeeSplit.recipientsJSDoc to describe the aggregatedDistributionsfee shape.Partner distribution recipients are now reported as one
FeeCostentry namedDistributions— itsamountis the total distributed andrecipients[]lists each receiver — beside the integrator/LI.FI/intermediary entry. Same shape on quote, route, and status responses.Why
The doc still described the old behavior: per-receiver
Fee Forwardentries at quote time and a merged-on-integrator shape at status time. The backend now emits the single aggregated entry consistently, so consumers reading this contract were misinformed.Doc-only change — no type signature changes.
Related
Backend change: lifinance/lifi-backend#8479 (CORE-513).