-
Notifications
You must be signed in to change notification settings - Fork 362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weโll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: decoupled {unit, starred, name} fields away from Account model #6796
Conversation
The latest updates on your projects. Learn more about Vercel for Git โ๏ธ 5 Ignored Deployments
|
820bf77
to
82d65d8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have still some files to review (all the coin families at least), but right now 2 things:
coin-framework
must not have anylive-wallet
logic inside. It's purpose is UI-agnostic.AccountRaw
should reflect whatAccount
is, not whatAccount
+AccountUserData
. We need to isolate backward compatibility issue in dedicated function, not in DataModel, as much as possible.
libs/ledger-live-common/src/exchange/platform/transfer/completeExchange.ts
Show resolved
Hide resolved
notes after testing LLM:
now this seems to be purely intentional to not take the account unit into account, because before it wasn't even shared at the currency level, so we will not address this in this rework I think, but i'll ask product team.
|
82d65d8
to
2d01ba7
Compare
2d01ba7
to
7389559
Compare
7389559
to
5c65a61
Compare
5c65a61
to
383e4cb
Compare
383e4cb
to
4cd5f96
Compare
4cd5f96
to
b2c2f84
Compare
...ktop/src/renderer/families/elrond/components/Modals/Claim/fields/DelegationSelectorField.tsx
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
๐ for Coin Integ team ownership.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM tested mobile and desktop locally too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reviewed mainly the device experience team scope and it's all good ๐
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a ๐ or ๐ |
can't be related |
โ Checklist
npx changeset
was attached.๐ Description
This PR mashups many iterations on our Account model rework. some of these PRs were incrementally reviewed, so we now hope for a final review on this PR ๐ ๐ NB: on this big mashup PR: it is easier to refactor the Account model in one batch and also with this one squashed commit, especially how it is complex to rebase with develop when changes are made there. see respective PRs for extended documentations:
user impact
per the PR comment below, this PR will however not address yet the usage of the currency unit in the "currency level features" like the account distributions or the assets screens.
That said, we removed the inconsistency behaviour of our app that was allowing to have different unit on different accounts ๐
the other user benefits is that, since we moved the unit from account unit to global currency unit, the global UX will be improved, notably this will fixed bugs related to unit lagging in the UI to be changed until the app is restarted (fixes https://ledgerhq.atlassian.net/browse/LIVE-12288 & https://ledgerhq.atlassian.net/browse/LIVE-11956 )
mini guide for developers
before this PR:
after this PR: we have a true decoupling of the data (between on chain and off chain data) while keeping the same AccountRaw serialized data
therefore, for developers, the impact is that you no longer have
unit
,starred
,name
fields directly available in Account. Instead you will get it on the end projects (LLD, LLM) with some accessors (selectors or hooks).You will be able to easily switch from one approach to another with these:
โน๏ธ ๐ช on the recent Account model and account management simplifications, see also:
โ Context
๐ง Checklist for the PR Reviewers