Closed bigboydiamonds closed 2 months ago
The changes involve a modification in the calculation of the bridgeFeeFormatted
value within the bridgeController
. The source of the decimal precision for formatting the bridge fee has shifted from using the toTokenInfo.decimals
to retrieving the decimals
from originQueryTokenOutInfo
. This adjustment introduces a dependency on the originQuery
data, altering how the bridge fee is represented in the response payload while maintaining the overall structure of the payload mapping.
File | Change Summary |
---|---|
packages/rest-api/src/controllers/bridgeController.ts | Updated the calculation of bridgeFeeFormatted to use decimals from originQueryTokenOutInfo instead of toTokenInfo.decimals . |
In the land of code where rabbits play,
A bridge fee change brightens the day.
From tokens to queries, the decimals dance,
Formatting fees now takes a new chance.
Hopping through logic, so clever and neat,
A leap for the future, oh what a treat! 🐰✨
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 37.95009%. Comparing base (
4a0f2e7
) to head (f2e3499
). Report is 16 commits behind head on master.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Latest commit: |
f2e3499
|
Status: | ✅ Deploy successful! |
Preview URL: | https://fe7e4854.sanguine-fe.pages.dev |
Branch Preview URL: | https://fix-bridge-fee-format.sanguine-fe.pages.dev |
Summary by CodeRabbit
New Features
Bug Fixes