-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Add account edit save settings screen #7272
Conversation
…onsumed for simpler test setup
a8426e8
to
7415955
Compare
Currently, `useCompression` and `isSendClientIdEnabled` are not part of `ServerSettings` in `Account` (and storage, and settings files, etc). We need to fix this eventually. But it's a larger change. For now we convert between the `ServerSettings` variants at the edges.
Scaffold( | ||
topBar = { | ||
AccountTopAppBarWithBackButton( | ||
title = "Edit Server Settings", |
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.
Hardcoded text. However, right now the validation screen and the saving screen have different looking headers. We should talk about cleaning this up in the design meeting. We might end up removing this string anyway.
LaunchedEffect(key1 = Unit) { | ||
dispatch(Event.SaveServerSettings) | ||
} |
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.
This will trigger an additional save operation e.g. after a configuration change. We have the same problem in a couple of other places. I'll create an issue for that.
Add account edit save settings screen
Manually rebased and merged via 4d14362 to preserve the history in this branch/pull request. |
This finalises the account server settings editing feature. I removed use of Result/Outcome and used exceptions instead.