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

[Feature Request] - Extension Dating & Timestamps of last updates. #70736

Closed
SirTwsted opened this issue Mar 19, 2019 · 3 comments
Closed

[Feature Request] - Extension Dating & Timestamps of last updates. #70736

SirTwsted opened this issue Mar 19, 2019 · 3 comments
Assignees
Labels
extensions Issues concerning extensions feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code
Milestone

Comments

@SirTwsted
Copy link

I would like to see on every extension ever created (2) things

    • Data it was created
    • Data of last update

I believe people should know if a extension has not been updated for a very long time.
or if it was recently updated. Also people should know when the extension was first created.
It just basically keeps people informed.

@vscodebot vscodebot bot added the extensions Issues concerning extensions label Mar 19, 2019
@sandy081
Copy link
Member

sandy081 commented Mar 19, 2019

Related to #68527

@sandy081 sandy081 added the feature-request Request for new features or functionality label Mar 19, 2019
@sandy081 sandy081 added this to the Backlog milestone Mar 19, 2019
@Daijobou
Copy link

Daijobou commented Jul 30, 2019

For me only "Data of last update" is of interest in overview of "@installed"-extensions, because I have a extension that not working properly, which working for years correctly and get no updates for months. So here must be a conflict with vscode or a extension that was silent updated? It would help to identify which extension is responsible for this issue, instead of disable all extension and enable each one by one again.

@VSCodeTriageBot
Copy link
Collaborator

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!

@VSCodeTriageBot VSCodeTriageBot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
extensions Issues concerning extensions feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Development

No branches or pull requests

5 participants