Skip to content
This repository has been archived by the owner on Jul 15, 2022. It is now read-only.

LL-4373 Discard existing ops on sync if blacklist has changed #1010

Merged
merged 6 commits into from
Jan 15, 2021

Conversation

juan-cortes
Copy link
Contributor

Since the js bridge rewrite blacklisted tokens could no longer be shown without a clear cache, since we wo uld only fetch from a given block height. This addresses that by setting a cache id at the account level and dismissing the existing ops if it doesnt match the blacklist settings.

https://ledgerhq.atlassian.net/browse/LL-4373

@vercel
Copy link

vercel bot commented Jan 12, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/ledgerhq-old/ledger-live-common/cgw2rce1j
✅ Preview: https://ledger-live-common-git-fork-juan-cortes-ll-4373.ledgerhq-old.now.sh

@gre
Copy link
Contributor

gre commented Jan 12, 2021

LGTM to me. 2 things to polish as we discussed:

  • no need to do this for cross.js
  • add a test, similar ideas as in compound.resilience.test.js

@juan-cortes
Copy link
Contributor Author

Should be fine now, I added test coverage for the blacklistedTokenids functionality

@juan-cortes juan-cortes requested a review from gre January 13, 2021 11:05
@gre
Copy link
Contributor

gre commented Jan 13, 2021

we'll merge #963 first and then we'll regen the snapshots here.

@gre
Copy link
Contributor

gre commented Jan 13, 2021

we can actually move on at putting the latest snapshots of the CI. the other PR is not ready yet. lemme do it

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants