-
Notifications
You must be signed in to change notification settings - Fork 210
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: show plugins and clients in panel #5784
base: main
Are you sure you want to change the base?
Conversation
…tps://github.com/microsoft/kiota into task/extension/show-plugins-and-clients-in-panel
Signed-off-by: Vincent Biret <[email protected]>
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.
also, now that we have a unit test infrastructure in place, we should make it a habit to include unit tests to get at least a basic coverage.
} | ||
|
||
private async deletePlugin(pluginName: string): Promise<KiotaLogEntry[] | undefined> { | ||
const result = await vscode.window.withProgress({ |
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.
lots of duplication between the two methods, I think we have an opportunity to refactor and reduce duplication here.
} | ||
return element; | ||
} | ||
|
||
public loadWorkspaceContent(): void { |
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 believe we're mixing concerns here, and reducing testability in the process.
The tree view providers are responsible for managing the state of the tree view, not for getting the data in the first place. I think we should split things 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 makes sense. I've separated these concerns
Overview
Closes #5715
Demo
Tasks
Clients
component when there is at least 1 client in the current context. If no client was found, the node shouldn't be displayed.Plugins
component when there is at least 1 plugin in the current context. If no plugin was found, the node shouldn't be displayed.Clients
andPlugins
components must to be expandable/collapsible.{ }
icon in any existing plugin/client, we should show the textSelect
. When clicking on it, the API Explorer should be loaded with the right client/plugin and right selected paths (same as theEditPaths
codelense action)Delete
. When clicking on it for any existing plugin/client, the plugin remove should be performed.Future work