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.
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
Bug fix for data-sources page #1830
Bug fix for data-sources page #1830
Changes from 6 commits
93a19a6
810cd75
80a7583
2356b78
967457e
bbd4fd9
6d0aa66
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 47 in public/components/datasources/components/manage/accelerations/acceleration_table.tsx
GitHub Actions / Lint
Check warning on line 78 in public/components/datasources/components/manage/accelerations/acceleration_table.tsx
GitHub Actions / Lint
Check warning on line 118 in public/components/datasources/components/manage/accelerations/acceleration_table.tsx
GitHub Actions / Lint
Check warning on line 132 in public/components/datasources/components/manage/accelerations/acceleration_table.tsx
GitHub Actions / Lint
Check warning on line 139 in public/components/datasources/components/manage/accelerations/acceleration_table.tsx
GitHub Actions / Lint
Check warning on line 320 in public/components/datasources/components/manage/accelerations/acceleration_table.tsx
GitHub Actions / Lint
Check warning on line 84 in public/components/datasources/components/manage/accelerations/create_accelerations_flyout/selectors/source_selector.tsx
GitHub Actions / Lint
Check warning on line 148 in public/components/datasources/components/manage/accelerations/create_accelerations_flyout/selectors/source_selector.tsx
GitHub Actions / Lint
Check warning on line 154 in public/components/datasources/components/manage/accelerations/create_accelerations_flyout/selectors/source_selector.tsx
GitHub Actions / Lint
Check warning on line 160 in public/components/datasources/components/manage/accelerations/create_accelerations_flyout/selectors/source_selector.tsx
GitHub Actions / Lint
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.
Not a blocker: The type for
cacheLoadingHooks: any;
or it's properties shouldn't beany
, it does not tell you the signature of the parameters you should be passing and hence we see such major bugs creeping in.Can we please add correct type annotations here?
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 order change might need a change in workbench? How do we know this is not causing a new regression, do we have test setup for this?
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.
yes same instance with the fix has it
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 meant some cypress tests or jest tests, to catch any regression in workbench. For example in workbench we are passing the params to this function: https://github.com/opensearch-project/dashboards-query-workbench/blob/888a8fe83b5e0a732866aaddb7a229eabed0f150/public/components/SQLPage/SQLPage.tsx#L71 Since, we do not have named params the MDSId will be mapped to
databaseName
now.