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

Extension details page should be tuned towards runtime info when extension is installed #159786

Closed
isidorn opened this issue Sep 1, 2022 · 3 comments
Assignees
Labels
extensions Issues concerning extensions *out-of-scope Posted issue is not in scope of VS Code under-discussion Issue is under discussion for relevance, priority, approach ux User experience issues

Comments

@isidorn
Copy link
Contributor

isidorn commented Sep 1, 2022

Clicking on an extension opens it's extension details page. This makes sense when an extension is not installed, but for installed extensions we can do better.
I propose that when the user click on an installed extension we still show the extension details page with the same header, but the focused tab is different. Instead we focus the "Runtime Status" tab and this tab should be rich with runtime information. Currently it only shows activation time.

I suggest that this tab has the full functionality of the Running Extensions experience (report issue, disable extension, start EH profile). And has additional useful statistics about runtime. For example number of crashes / detected slowness.

@joaomoreno contributed to the idea
fyi @alexdima @jrieken who I know are passionate about runtime extension info and might have ideas on cool info we could show here
@TylerLeonhardt for ext report issues improvements

Let me know what you think about this

Screenshot 2022-09-01 at 19 29 01

@isidorn isidorn added ux User experience issues extensions Issues concerning extensions under-discussion Issue is under discussion for relevance, priority, approach labels Sep 1, 2022
@TylerLeonhardt
Copy link
Member

Good feedback here: microsoft/vscode-discussions#119 (comment)

@bwateratmsft
Copy link
Contributor

I like it. I would really like to see the breakdown in activation time of code loading / activate call time / activate resolved time. I frequently do report issue just to get those three data points separated from each other.

@isidorn isidorn added this to the Backlog milestone Dec 5, 2022
@daviddossett daviddossett removed their assignment Dec 14, 2022
@isidorn isidorn added the *out-of-scope Posted issue is not in scope of VS Code label Dec 14, 2023
@vscodenpa
Copy link

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!

@vscodenpa vscodenpa closed this as not planned Won't fix, can't repro, duplicate, stale Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
extensions Issues concerning extensions *out-of-scope Posted issue is not in scope of VS Code under-discussion Issue is under discussion for relevance, priority, approach ux User experience issues
Projects
None yet
Development

No branches or pull requests

8 participants