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

Analysis view is not opened on initial load #425

Open
ibolton336 opened this issue Mar 6, 2025 · 3 comments
Open

Analysis view is not opened on initial load #425

ibolton336 opened this issue Mar 6, 2025 · 3 comments
Labels
priority/minor triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@ibolton336
Copy link
Member

  • There is no intuitive way to open the analysis page when a user is first setting up the IDE extension. We should display the analysis page by default when the konveyor kai sidebar menu item is clicked.
  • Currently, we have to find the book icon and click that from the side issues pane to open up the analysis page.
@fabianvf fabianvf added this to the v0.1.0 milestone Mar 6, 2025
@sjd78
Copy link
Member

sjd78 commented Mar 6, 2025

Also -- when the extension is reloaded, I've ended up collecting a number of analysis views open.

Closing any of the editor views when the extension is deactivated / reloaded would also be a good thing.

@pranavgaikwad
Copy link
Contributor

@sjd78 @ibolton336 The issue I am about to describe sounds very similar to this. When I click "Start Analyzer", it doesn't navigate me to the analysis view. Unsure if it's a bug... it'd be great if navigation worked.

Screen.Recording.2025-03-06.at.8.35.28.PM.mov

@jwmatthews
Copy link
Member

Moving this off v0.1.0, we have a partial fix in #433, there is likely a bit more we want to handle but don't plan to have that in 0.1.0

@jwmatthews jwmatthews modified the milestones: v0.1.0, v0.2.0 Mar 7, 2025
sjd78 pushed a commit that referenced this issue Mar 10, 2025
…gh (#433)

- Addresses the comment from 
[@pranav](https://redhat-internal.slack.com/team/UJVF3G38W) on
#425 - the
walkthrough button isn’t stateful so we were able to start the server
but there were no notifications or button state on the walkthrough that
let us know that the server was starting/initializing. You could click
it a bunch of times and kick off several instances of the server. The
fix in PR 433 just ushers the user to the analysis page and encourages
the user to start the server from there.


<img width="1447" alt="Screenshot 2025-03-07 at 2 31 35 PM"
src="https://github.com/user-attachments/assets/ca975d14-6e10-4911-b2fb-f0cb2e40fade"
/>

---------

Signed-off-by: Ian Bolton <[email protected]>
@djzager djzager marked this as a duplicate of #389 Mar 19, 2025
@djzager djzager added priority/minor triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Mar 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/minor triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: Todo
Development

Successfully merging a pull request may close this issue.

6 participants