-
Notifications
You must be signed in to change notification settings - Fork 405
RI-7106: additiona data in config databases open database #4539
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
KIvanow
merged 8 commits into
release/2.70.0
from
fe/feature/RI-7106-additiona-data-in-CONFIG_DATABASES_OPEN_DATABASE
May 23, 2025
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
36f811d
add additional info to getRedisNodeGeneralInfo
pd-redis 70fb469
refactor calls to api in instances.ts, add instancesService.ts, add i…
pd-redis c78474d
updated tests
pd-redis ba483e4
fix double onClick handling
pd-redis 643edea
Merge branch 'release/2.70.0' into fe/feature/RI-7106-additiona-data-…
pd-redis e7a6eb5
fix InstancePage.spec.tsx
pd-redis ab41382
fix database-info.provider.spec.ts
pd-redis 17298ba
added RedisDatabaseStatsDto
pd-redis 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
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
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
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
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
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
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
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
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
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,27 @@ | ||
export const MOCK_INFO_API_RESPONSE = { | ||
version: '7.4.0', | ||
usedMemory: 1234, | ||
connectedClients: 2, | ||
totalKeys: 123, | ||
stats: { | ||
uptime_in_days: '2', | ||
maxmemory_policy: 'allkeys-lru', | ||
instantaneous_ops_per_sec: 123, | ||
instantaneous_input_kbps: 123, | ||
instantaneous_output_kbps: 123, | ||
numberOfKeysRange: '0-123', | ||
}, | ||
} | ||
|
||
export const MOCK_ADDITIONAL_INFO = { | ||
connected_clients: 2, | ||
instantaneous_input_kbps: 123, | ||
instantaneous_ops_per_sec: 123, | ||
instantaneous_output_kbps: 123, | ||
maxmemory_policy: 'allkeys-lru', | ||
numberOfKeysRange: '0-123', | ||
redis_version: '7.4.0', | ||
totalKeys: 123, | ||
uptime_in_days: '2', | ||
used_memory: 1234, | ||
} |
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.
why this is deleted?
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.
because if it is left, it registers twice
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.
Doesn't the itemContent have onclick only in the if statement? What else is triggering the same onclick?
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.
From what I saw, there are 2 inner components based on the props:
Probably this is the reason that there were 2 invocations on the handler. The tricky part is the
if (isDisabled || onClick) {
condition, but if it's disabled, we probably don't want to invoke the handler, so we're safe. I'd guard it with a test, tho.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.
If there is on click handler provided, the button that handles it is rendered, if no onClick is provided, nothing needs to handle it