Refactor Currency and Pair Management to Use New Services #250
Conversation
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
…sed on language
… for stats display
…ency details from service
…currency details from service
…ls from service
… and pending settlement balances
…ncy with precisionØØ
Benyamin001
approved these changes
Feb 18, 2025
Hossein-ab99
deleted the
246/feature/refactor-currency-pair-management
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Transition the client-side management of currencies and pairs to align with the updated backend services. This will streamline currency and pair information handling, remove hardcoded values, and make the system more dynamic and admin-configurable.
Currency Integration:
Replace hardcoded currency definitions with data from the new currency service.
Fetch and implement currency details such as names, symbols, decimal precision, and active/inactive status dynamically.
Pair Management:
Replace hardcoded pair information with data fetched from the updated pair service.
Dynamically map pairs with associated currency details.
Ensure compatibility between the pair service and the currency service for data consistency.