-
Notifications
You must be signed in to change notification settings - Fork 350
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
Create a button in palette for all schema #906
Conversation
Hmm. The plurality is off. Since namespace names are plural and schema names are singular, I wonder if the namespace name is what is wanted here anyway. Since 2 of the 3 are single-schema namespaces, they just work. The other would should KFP and AIrflow "runtimes" leaving the headings with... Show Code Snippets Actually, the namespace names are lowercase and values like "code-snippets", "runtime-images" and "runtimes". So this is another great example of promoting namespaces to full objects where they too could have display_name values - leading to what I showed above (with proper case and spacing). Until then, I don't think this is going to fly, unfortunately. |
@kevin-bates What if we add 'Widget' after each of them? So "Show Code Snippet Widget" or "Show Runtime Image Widget" |
To show a "widget" sounds odd to me. Also, I think we should forgo using |
@kevin-bates Yeah good point - maybe "browser"? |
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 just have the one comment about using title
over display_name
when dealing with the schema file. We should remove the top-level display_name
property.
My bigger issue is with the plurality of these section headers as noted in the conversation. If we're going to inject a top-level uihints
, then that might as well contain the full widget title(?):
Show Runtime Images
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.
Only managed a partial review, but I agree with what @kevin-bates has said so far
"Manage ..." would probably be more accurate because the metadata widget exposes the entire set of CRUD operations, not just R(ead)/Show. |
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.
Didn't test locally, but code lorn
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.
LGTM :)
Ok while working with this I figured it might be good to also implement that "Close tab" ability for metadata viewers in the left side pane since they can really add up and now it's easy to reopen any of them. Just pushed those changes but if you don't think it's good with this PR I can undo that. Thoughts? |
Just added a small change so that it won't show the "Close tab" option for code snippets or runtimes (because they're supposed to be more permanent). It was causing a small bug of creating a generic metadata widget for code snippets (which doesn't include the coding languages in the display and doesn't include the insert / copy buttons). |
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.
Nice adding a close tab option. Re-ran this locally and looks good.
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.
LGTM - Tested locally and all looks good.
Add new commands to the command palette to enable opening existing metadata UI for all available schemas.
Automatically detects all schema and creates a button to open the widget for a given schema.

Developer's Certificate of Origin 1.1