-
Notifications
You must be signed in to change notification settings - Fork 182
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
Add output explorer #2337
base: main
Are you sure you want to change the base?
Add output explorer #2337
Conversation
This is extremely high-quality output-explorer-demo.mp4 |
type Item = { | ||
key: string | ||
name: string | ||
type: string | ||
modifyTime: number | ||
size: number | ||
} |
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 it's best to adjust the associated backend PR to return items using an extension of ResultItem
, for consistency.
We can create a more generalized version of the current ResultItemImpl
class that excludes properties like nodeId
and vhsAdvancedPreviewUrl
. This class can serve as a base for both result items and output items.
Then we can move ResultGallery
to common components and it can be used by OutputExplorerSidebarTab
.
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.
Do you mean I need to create a new ResultItemImpl
class or just improve the current one is OK?
┆Issue is synchronized with this Notion page by Unito