fix: historical rates regression & other fixes #656
Merged
Conversation
This file contains 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
Syn-McJ
commented
Jun 6, 2024
| let currentAccount = DWEnvironment.sharedInstance().currentAccount | ||
| let account = accounts.contains(where: { ($0 as! DSAccount) == currentAccount }) ? currentAccount : nil | ||
|
|
||
| return account != nil ? chain.direction(of: self) : .notAccountFunds |
There was a problem hiding this comment.
This doesn't seem necessary as chain.direction checks all accounts anyway and returns notAccountFunds for unrelated accounts.
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.
Issue being fixed or feature implemented
Transaction history should show "not available" for fiat values where rates weren't saved in the DB
What was done?
How Has This Been Tested?
QA
Breaking Changes
Checklist:
For repository code-owners and collaborators only