-
Notifications
You must be signed in to change notification settings - Fork 918
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
[MD] Address UX comments for index pattern pages #2505
Conversation
...ponents/create_index_pattern_wizard/components/step_data_source/components/header/header.tsx
Outdated
Show resolved
Hide resolved
Codecov Report
@@ Coverage Diff @@
## main #2505 +/- ##
==========================================
- Coverage 66.78% 66.76% -0.03%
==========================================
Files 3201 3201
Lines 60913 60943 +30
Branches 9254 9258 +4
==========================================
+ Hits 40683 40689 +6
- Misses 18018 18039 +21
- Partials 2212 2215 +3
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
9b07fb6
to
0caf256
Compare
@kristenTian Can you please provide a full screen screenshot? I am not understanding the context of the radio button. Please also see : opensearch-project/ux#40 |
Updated |
Signed-off-by: Kristen Tian <tyarong@amazon.com>
if (fetchedDataSources?.length) { | ||
setDataSources(fetchedDataSources); | ||
} |
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.
Is it guarantied that the backend will throw if no data sources are available? If not, shouldn't we show something when no data sources are returned?
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 don't think backend will throw. Current behavior is the drop down will show as empty. in later phases, UX designed an empty state to show.
.find<DataSourceAttributes>({ | ||
type: 'data-source', | ||
fields: ['title', 'type'], | ||
perPage: 10000, |
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.
Is there any precedence for this 10000
? Does it need to exist? Does it have to be hardcoded? Can it be configurable? Can it be read from a common config?
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.
+1
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 is referenced from the how other places are using this method in the repo:
OpenSearch-Dashboards/src/plugins/data_source_management/public/components/utils.ts
Line 14 in 890a4b6
perPage: 10000, |
Line 157 in 890a4b6
perPage: 10000, |
I am also not a fan of this approach. We can add an action item to add pagination supported client wrapper as an action item?
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.
10000
is a commonly used value in the OpenSearch/osd world, it's the default max OS search hits, see reference here. Tho it's not a good practice to use hardcode, but sadly this value is used everywhere in the codebase. My suggestion is we can add an OSD global config such as savedObjects.PaginationSize
, it could be tracked as a new issue
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.
Good to know 😊
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-2505-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 4095e123d77182bed213fedf41be00ccaffd34a7
# Push it to GitHub
git push --set-upstream origin backport/backport-2505-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-2505-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 4095e123d77182bed213fedf41be00ccaffd34a7
# Push it to GitHub
git push --set-upstream origin backport/backport-2505-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x Then, create a pull request where the |
…2505) (opensearch-project#2525) Signed-off-by: Kristen Tian <tyarong@amazon.com> (cherry picked from commit 4095e12)
…2505) (opensearch-project#2525) Signed-off-by: Kristen Tian <tyarong@amazon.com> (cherry picked from commit 4095e12)
…2505) Signed-off-by: Kristen Tian <tyarong@amazon.com> Signed-off-by: Kristen Tian <tyarong@amazon.com> Signed-off-by: Sergey V. Osipov <sipopo@yandex.ru>
Signed-off-by: Kristen Tian tyarong@amazon.com
Description
Address UX comments for index pattern pages
Issues Resolved
UX
opensearch-project/ux#42
Check List