-
-
Notifications
You must be signed in to change notification settings - Fork 173
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
store last account id in core by using selectAccount (which stores it in account manager/accounts.toml) #4569
Conversation
… in account manager/accounts.toml) This fixes that the update device message is left unread in the wrong account (because that used the value from core already and it wasn't updated by desktop so it was wrong).
/** path to last used/selected Account */ | ||
/** path to last used/selected Account | ||
* | ||
* @deprecated in favor of storing selected account over core account manager in accounts.toml |
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.
In the core we usually add the date when this was deprecated, e.g. 2025-01-27, so this can be completely removed at some point.
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'm not really sure what how much core's select_account()
is responsible for, but this MR makes sense, especially that we're already using getSelectedAccountId()
in the codebase.
This fixes that the update device message is left unread in the wrong account (because that used the value from core already and it wasn't updated by desktop so it was wrong).
closes #4474