-
Notifications
You must be signed in to change notification settings - Fork 57
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
[Feature] Data sources associated objects tab #1470
[Feature] Data sources associated objects tab #1470
Conversation
Signed-off-by: Ryan Liang <jiallian@amazon.com>
Signed-off-by: Ryan Liang <jiallian@amazon.com>
Signed-off-by: Ryan Liang <jiallian@amazon.com>
public/components/datasources/components/manage/data_connection.tsx
Outdated
Show resolved
Hide resolved
public/components/datasources/components/manage/associated_objects_tab.tsx
Outdated
Show resolved
Hide resolved
<EuiInMemoryTable | ||
items={associatedObjects} | ||
columns={columns} | ||
search={search} |
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.
May need to move this out for an external search bar component since the EuiInMemoryTable
doesn't have support for search bar and filters, but that can be done in a future 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.
lets do this as a follow up
public/components/datasources/components/manage/associated_objects_tab.tsx
Outdated
Show resolved
Hide resolved
@RyanL1997 can you please fix linting and test apart from the above comments. Thanks! |
In order to fix test and build workflows, |
Signed-off-by: Ryan Liang <jiallian@amazon.com>
Signed-off-by: Ryan Liang <jiallian@amazon.com>
Signed-off-by: Ryan Liang <jiallian@amazon.com>
Signed-off-by: Ryan Liang <jiallian@amazon.com>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1470 +/- ##
==========================================
- Coverage 56.49% 56.38% -0.12%
==========================================
Files 320 322 +2
Lines 11739 11766 +27
Branches 3055 3059 +4
==========================================
+ Hits 6632 6634 +2
- Misses 5053 5078 +25
Partials 54 54
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
@RyanL1997 For the below lint error let's add a console.error
to log the error whenever it occurs.
136:15 error 'err' is defined but never used. Allowed unused args must match /^_/u
Thanks! for quick the updates on the PR
Signed-off-by: Ryan Liang <jiallian@amazon.com>
database: string; | ||
type: string; | ||
createdByIntegration: string; | ||
accelerations: string; |
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.
would any of these fields be a smaller type than string
, or all of them can be arbitrary strings?
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 for now they should be all strings.
<AccelerationsRecommendationCallout /> | ||
<EuiSpacer /> | ||
{associatedObjects.length > 0 ? ( | ||
<EuiInMemoryTable |
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.
would there be a case that associatedObjects
gets large and doesn't fit in memory?
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 point, I think for the memory fitting issue, we may need to do something like virtualization with react-window to limit the size of the list. However, since this this is a skeleton for now, and lets just leave like this. I will test it when we connect the actual data content, so that we can decide which approaches we need for addressing the memory issue. I will not resolve this comment btw until we have a concrete solution on this.
name: string; | ||
database: string; | ||
type: string; | ||
createdByIntegration: string; |
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 know if createdByIntegration
is a field that AssociatedObject
would contain, I'd expect this to be queried from the integrations that store all the contained object information. Do you see us modifying Integrations to add fields like this to arbitrary objects? If so, it might be worth adding this requirement in #1442
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.
Transferring some of the discussion over here: for now, since we should able to have this field with the source of integration, lets have this field for now for this skeleton PR. We can sync up on this again when we actually do the connection of actual data content.
Signed-off-by: Ryan Liang <jiallian@amazon.com> (cherry picked from commit 187b112) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Signed-off-by: Ryan Liang <jiallian@amazon.com>
… (opensearch-project#1486) Signed-off-by: Ryan Liang <jiallian@amazon.com> (cherry picked from commit 7eaa762)
Description
Add Data sources associated objects tab
Issues Resolved
[List any issues this PR will resolve]
Demo
Without data:
With data:
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.