feat: update api binding to use new fees#16
Merged
Luisfc68 merged 6 commits intoflyover-2.2.0from Mar 21, 2025
Merged
Conversation
Luisfc68
requested review from
AndresQuijano,
Dominikkq,
MaximStanciu8 and
gsoares85
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files |
MaximStanciu8
approved these changes
Mar 7, 2025
AndresQuijano
approved these changes
Mar 21, 2025
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
3 participants
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
Why
Even tho the API still returning the fee field in the provider details endpoint, we still need to expose the new fee fields
Task
https://rsklabs.atlassian.net/browse/GBI-2501