Skip to content
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

Show "Generate" or "Regenerate" button in the API Explorer based on the user flow #5800

Open
Tracked by #5713
maisarissi opened this issue Nov 19, 2024 · 0 comments
Open
Tracked by #5713
Labels
status:waiting-for-triage An issue that is yet to be reviewed or assigned type:feature New experience request vscode-extension Work related to the vscode-extension

Comments

@maisarissi
Copy link
Contributor

Challenge

As part of our integrated history with Teams Toolkit when generating API Plugin for existing APIs, we are seeing a drop in how many users go back to TTK after landing in Kiota.
One of our assumptions is that folks are lost and don't know what to do to complete the flow. To increase the number of users being successful when coming from TTK, we should do some adjustments in the UI to try to make things clearer, even more for new users.\

Proposal

Add a label after the Generate/Regenerate button and show the right button based on the user flow.

When the user is loading a new API in the API Explorer, we should show the Generate button and label like the image below:
Image

When the user is editing an existing plugin/client, we should replace the Generate with a Regenerate button and label.
Image

Acceptance Criteria

  1. The Generate/Regenerate button should only be enabled and there is at least one endpoint selected.
  2. When there is no plugin/client loaded in the API Explorer, we should show the Generate button and label.
  3. When selecting an existing plugin/client to edit it, we should show a Regenerate button and label rather than Generate. The regenerate icon should perform the plugin generation with the new parameters based on the user selection.
  4. All the existing regeneration behaviors and features, as an example the Kiota should warn the user when re-generating that all changes did manually by them will be overridden #5303), should continue the same.
@maisarissi maisarissi added status:waiting-for-triage An issue that is yet to be reviewed or assigned type:feature New experience request labels Nov 19, 2024
@github-project-automation github-project-automation bot moved this to Needs Triage 🔍 in Kiota Nov 19, 2024
@maisarissi maisarissi added the vscode-extension Work related to the vscode-extension label Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:waiting-for-triage An issue that is yet to be reviewed or assigned type:feature New experience request vscode-extension Work related to the vscode-extension
Projects
Status: Needs Triage 🔍
Development

No branches or pull requests

1 participant