-
Notifications
You must be signed in to change notification settings - Fork 72
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
Added user settings part 1 - setting SSH key and impersistent blocking toast notifications #1088
Conversation
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.
It looks great!!
@bond95 - CI is failing on an i18n test that is checking to make sure all keys in the translations exist as English keys. In other words, existing keys were removed or renamed. Easiest fix is to remove the offending keys from the translation file. Or if the keys are a rename, and you're feeling nice, adjust the translation key names. |
@bond95 Is it ready for updated screenshots yet? Just saw that it's waiting for my review but I'm just waiting for updated screenshots of it. We can also do a demo of it so we can review the behavior when it's ready. |
@lwrigh |
@bond95 Awesome this is looking great! My only comment is that I would make the dropdown and text fields a bit less wide. They could probably be half the width. |
6701940
to
f606dc1
Compare
@lwrigh updated width of settings: WDYT? |
The fields are still a bit too wide, I would recommend it be half the width so it looks like something like this: |
The dropdowns look good! Ah sorry if I wasn't communicating clearly, the text for the checkboxes should be on all one line and should only go to two lines when it gets closer to the edge of the card. Generally when it comes to sentences they should try to extend the width of the container but with components like the dropdowns the width is usually determined by the content. |
@lwrigh fixed: |
They seem to appear in Web Admin so I would keep them here too.
Fixed. Instead of auto-removing we now acknowledge old entries. |
Why removing and not fixing? Isn't it a bug?
I know but we can't merge this PR (with a very very long conversation list :)) without specifying exactlly what's merged and what is the context of this PR. No one will understand/remember that from reading all long conversations. |
ac910e4
to
098dba8
Compare
User email is fetched using
Done. Please check the current PR title.
Done. |
+1
What I meant on my original comment is to emphasize the fact that all vms/pools are affected since you can't filter by vms/pools for now. So maybe just consider adding "all": ...(including all vms and pools notifications).
The problem is that session for web-ui terminology is referring to user session. Check for example the config value: https://zipur.ca/knowledgebase/stop-engine-webui-session-time-logging-out/
Great, thanks! Can you please just add "impersistent" to the "blocking toast notifications" part on title. ===================== |
098dba8
to
13e9bc2
Compare
Done. Additionally, I've extended the tooltip to explain that the settings are not persisted. This is true for the entire section so section tooltip seems the best place
I've changed this label to "until next page reload". This seems the most self explanatory term. It does sounds strange when you read it together with the dropdown label ("Do not disturb for until next page reload") but as confirmed with @sjd78 it's not that bad. Web Admin uses similar wording here ("until next Log in"). |
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.
Changes look good to me.
13e9bc2
to
243abea
Compare
Rebased on top of #1334 (version with improved logging) |
CounterAlert: 1. onDismiss prop - callback fired when alert is closed 2. children prop - rendered below title
Summary: 1. Remove existing Options dialog a) move SSH Key to Account Settings b) continue using existing REST endpoint: users/${id}/sshpublickeys 2. support following (local) settings via Redux-store: a) showNotifications (do not disturb) b) notificationSnoozeDuration (do not disturb for) 3. add typing for user settings related entities 4. in Settings use data-driven 3-way diff for change detection. Change is detected by comparing current content of Redux store with user changes(draft values) and base values(store content before at the beginning of user settings updates)
Allow user to block system notifications via Account Settings: 1. each change to the snooze duration resets the snooze timer 2. notification settings are not persisted - page reload clears them. 3. only displaying is blocked - logs continue to be accumulated in the store (userMessages -> records)
243abea
to
ae9a27c
Compare
Rebased on top of #1334 (after merge GH reported conflicts in this PR) |
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
LGTM |
Main page for global settings:
Confirmation modal:
Main page for VM settings:
Save confirmation notification:
Error notification: