-
Notifications
You must be signed in to change notification settings - Fork 415
RI-7681: Apply new UI changes to DB Info section on Edit modal #5149
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
Merged
+209
−242
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
2835538
Refactor Db Info group styles and extract reusable label component
dantovska 63d927a
handle additional content to label value pair for list group item for…
dantovska b429a60
fix db info section for sentinel
dantovska 83e5864
remove no longer used sentinel host port component
dantovska 36f321a
fix db info section in edit modals for all dbs
dantovska cc60aee
move copy button styled component to different file
dantovska 8f8cf74
use array for db info elements. move the append endpoints outside the…
dantovska 8ab2785
use db info array for sentinel db info elements, move copy icon outsi…
dantovska 717e1df
fix wrong hiding condition
dantovska ab46e31
use simply secondary for label, which is slightly lighter in the ligh…
dantovska File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
10 changes: 10 additions & 0 deletions
10
redisinsight/ui/src/pages/home/components/form/DbInfo.styles.ts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| import styled from 'styled-components' | ||
| import { Group } from 'uiSrc/components/base/layout/list' | ||
|
|
||
| export const DbInfoGroup = styled(Group)` | ||
| background-color: ${({ theme }) => | ||
| theme.semantic.color.background.neutral200}; | ||
| border: 1px solid ${({ theme }) => theme.semantic.color.border.neutral400}; | ||
| padding: ${({ theme }) => theme.core.space.space100}; | ||
| border-radius: 5px; | ||
| ` | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
12 changes: 12 additions & 0 deletions
12
redisinsight/ui/src/pages/home/components/form/sentinel/DbInfoSentinel.styles.ts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| import styled from 'styled-components' | ||
|
|
||
| import { IconButton } from 'uiSrc/components/base/forms/buttons' | ||
|
|
||
| export const StyledCopyButton = styled(IconButton)` | ||
| margin-bottom: 3px; | ||
| opacity: 0; | ||
|
|
||
| :hover { | ||
| opacity: 1; | ||
| } | ||
| ` |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 think this is starting to get out of hand, we use semantic.color.border in 26 places (at least), 21 are neutral500, one of 400, 600, 800, and one primary600.
This is more like a question to everybody - do you think it makes sense to define the colors we use in RI explicitly? Like borderColor, bgColor etc ?
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 sure keeping our version in sync with redis ui would be easy
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.
Yeah, for sure, it might come with some struggles (keeping them in sync), but also, I see Redis UI introduces major breaking changes, so we're also kind of blocked now (we can't get the latest bug fixes and features because of that).
And I think that soon we'll end up in a state where we don't treat it as a main source of truth, but instead build an intermediate abstract layer that depends on it. Just like we did with our components (
RiIcon,RiTabs, etc.), we might need something similar for the color palette/theme.For sure, it's not something straightforward (maybe), but we should definitely consider it and think more about it, and how we can handle it in an efficient way.
Uh oh!
There was an error while loading. Please reload this page.
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.
@pd-redis I don't know if it will be expected to have the same border everywhere? And we will need an effort to change that. I don't just want to introduce the variable, without changing everywhere and then we will end up like the eui colors that we are trying to get rid off ... borderLight, borderLighter ... It does makes sense if we do a redesign again and want to change border everywhere... Anyway, I don't think it should start in this PR