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

Sort extensions by extension update date #53405

Closed
janderudder opened this issue Jul 1, 2018 · 28 comments
Closed

Sort extensions by extension update date #53405

janderudder opened this issue Jul 1, 2018 · 28 comments
Assignees
Labels
extensions Issues concerning extensions feature-request Request for new features or functionality on-testplan

Comments

@janderudder
Copy link

janderudder commented Jul 1, 2018

It's in the title : I could use the possibility to browse installed extensions sorted by installation update date.

I often install a batch of extensions at a time, for a given language, or about a given feature. Some times I find unrelated extensions during the search and install them too.
So I restart the editor with a whole bunch of new extensions, and its behavior may be quite different compared to last reload.

I don't necessarily remember the names of all the newly installed extensions, and after restarting the editor sometimes I wish to go back to the extension read-me to see the how-to again, or just get the extension's name to use its commands.

When you have a lot of extensions installed it may be hard to browse through to find the new ones.
It would be nice to have a way to discriminate the latest installed extensions.

Thank you for this great editor anyway :)

@vscodebot vscodebot bot added the extensions Issues concerning extensions label Jul 1, 2018
@roblourens roblourens assigned sandy081 and ramya-rao-a and unassigned sandy081 Jul 2, 2018
@sandy081 sandy081 added the feature-request Request for new features or functionality label Jul 2, 2018
@sandy081 sandy081 added this to the Backlog milestone Jul 2, 2018
@robertopc
Copy link

I want this feature too.

@cacheflow
Copy link

I'll take this.

@ramya-rao-a
Copy link
Contributor

ramya-rao-a commented Sep 11, 2018

We do not store any data around install timestamps. All information we show around extensions are coming from the marketplace. We could use at the timestamps of the directory for the extension, but for every extension update, a new folder is created and the older one is deleted.

So there is no way at the moment to get the install date.

If anyone is really interested in getting a solution for this, they may try it via extensions. You could have an extension that watches the directory where the extensions are stored and keeps list of extensions and the first time they were installed. See https://aka.ms/vscodewritingextensions for getting started with extensions

@ramya-rao-a ramya-rao-a added the *out-of-scope Posted issue is not in scope of VS Code label Sep 11, 2018
@vscodebot vscodebot bot closed this as completed Sep 11, 2018
@ramya-rao-a ramya-rao-a reopened this Sep 11, 2018
@microsoft microsoft deleted a comment from vscodebot bot Sep 11, 2018
@ramya-rao-a ramya-rao-a added *extension-candidate Issue identified as good extension implementation and removed *out-of-scope Posted issue is not in scope of VS Code labels Sep 11, 2018
@vscodebot
Copy link

vscodebot bot commented Sep 11, 2018

We try to keep VS Code lean and we think the functionality you're asking for is great for a VS Code extension. Maybe you can already find one that suits you in the VS Code Marketplace. Just in case, in a few simple steps you can get started writing your own extension. See also our issue reporting guidelines.

Happy Coding!

@KillyMXI
Copy link
Contributor

KillyMXI commented Sep 24, 2018

We could use at the timestamps of the directory for the extension, but for every extension update, a new folder is created and the older one is deleted.

In my ticket I was asking about install OR UPDATE dates, so this way, although shakey, would've worked for me fine.

Even sort by version update in Marketplace will be useful in some cases (more useful than outdated filter). Although it doesn't solve first install issue, it is useful with following updates.

@ramya-rao-a
Copy link
Contributor

In my ticket I was asking about install OR UPDATE dates

Thanks for clarifying. That was not clear to me initially.
This does simplify things.

@ramya-rao-a ramya-rao-a reopened this Sep 24, 2018
@ramya-rao-a ramya-rao-a removed the *extension-candidate Issue identified as good extension implementation label Sep 24, 2018
@KillyMXI
Copy link
Contributor

KillyMXI commented Sep 24, 2018 via email

@ghost
Copy link

ghost commented Sep 25, 2018

@KillyMXI I don't think janderudder was referring to the original date an extension was installed. Since every update requires an extension to be reinstalled, he was most likely asking for a way to organize the last date an extension was updated or installed for the first time. I mean, I don't think anyone would want to only keep track of when they first installed an extension.

Anyways, I really hope we get some sorting options for dates because figuring out the latest extension settings is a hassle.

@MeikTranel
Copy link

MeikTranel commented Sep 25, 2018

I would say (given the nature of the install/update process) showing installdate by listing the LastChanged-Date of the directory or the vsixmanifest would be sufficient information to support sorting without adding additional state to the extension directory

@janderudder
Copy link
Author

janderudder commented Sep 25, 2018

@KillyMXI I don't think janderudder was referring to the original date an extension was installed.

Actually I was. I am not familiar with how VS Code extensions work. Anyway, the purpose of this feature, as I see it, would be to have a view of newest installed extensions so we can easily find the cause of a change in the UI for instance, after installing a bunch of extensions and not paying much attention to the names and details.

I guess it would cover this use case to sort extensions by update date, even better.

@ramya-rao-a
Copy link
Contributor

ramya-rao-a commented Sep 25, 2018

Copying @MeikTranel's comment from #59315 as I think it provides yet another scenario where this feature is useful i.e reading of the changelog

As a user, who enjoys reading patch notes it'd be cool if there was a way to sort an extension by the date of the update/install. That way i can still use autoupdate and in the event of an error that suddenly erupts i could help extension authors by providing context, when the issues first appeared and if its correlating with the installation or update of an extension.

@miguelsolorio
Copy link
Contributor

@johanngerell yes, as @MeikTranel mentioned we have some explorations around updating our UI for extensions and are looking to enable sorting (see #68527). I'm hoping that after we update our iconography (#8017) that we'll be able to tackle this next.

@spartanatreyu
Copy link

Just going to copy my comment into this issue:

Something I've found missing from the current functionality that would be handy to have would be a way to order extensions by install date.

I installed the Trailing Spaces extension to highlight any random trailing spaces that have slipped into the code and it worked great, but randomly a few hours later I encountered a problem with it where it was incorrectly highlighting lines that were had no whitespace issues.

I went to the extensions pane to remove the extension and couldn't remember what it was called. I clicked on the menu button (three dots) in the extension pane, first to show only the installed extensions (which hides the pre-installed and recommended extensions), then again to sort by installation date.

Currently we have:

  • Sort By: Install Count
  • Sort By: Rating
  • Sort By: Name

but no "Sort By: Install Date".

It was only a minor nuisance to re-read all of my installed extensions (25 of them, mainly language syntax support extensions) to find the misbehaving one but this would be a nice quality of life fix to add for devs that are trying new extensions

@RoestVrijStaal
Copy link

RoestVrijStaal commented Oct 10, 2019

Any update about this feature request?

I'm fed up with checking manually the compatibility and vitality of each extension by browsing to its code repository and check on last commit date and its ticket handling.

Sorting (or even better: filtering) them would help me saving time on picking (working!) extensions.

@wctiger
Copy link

wctiger commented Jun 30, 2021

Following up on this feature request.
For me I have ~40 extensions installed and all of sudden some of them is making my intellisense slow (by comparing between all extension disabled and enabled). So it will be really helpful if there is a way to just look at extensions that get updated most recently to help troubleshoot problems like this.

@evanrs
Copy link

evanrs commented Sep 11, 2021

With so many extensions it can be hard to recall their names. The problem starts when installing new extensions — you want to try it, but you can't trust you'll be able to uninstall it. When you can't recall the name, that is.

Sorting by installDate would be quite useful for maintaining ones workspace — and, encouraging a more adventurous use of newer extensions.

@gmccullo
Copy link

I need this too. It would make it a lot easier to figure what newly updated extension is making VS Code run impossibly slow.

@dexterlakin
Copy link

There's a bug with one of my recently installed extensions and this would be useful to figure out which one

@janderudder
Copy link
Author

janderudder commented Jan 18, 2022

After re-reading this whole thread and some of the related threads mentioning this one, I just want to mention that kind of two different features are being talked about. They are similar - indeed in some cases they serve the same purpose - but they are still different enough that it's worth clarifying, IMO.

So, in sorting extensions by update date, the "update date" part may be understood in two ways:

  1. the date the extension source code was updated by its author on the marketplace
  2. the date the extension package was installed locally on the user's machine

Case 2 includes the first installation and subsequent updates. Technically an update is made of deletion + new install of the extension (according to what I read).

Having a way to sort/filter recently updated extensions on the marketplace is cool for discoverability, but the second feature is better adapted to keeping track of one's own workspace state.

  • You want to read the docs of your last installed extensions but don't remember their names? Sort by local install date.
  • Your editor starts being slow all of a sudden? Check the last extensions updated on your machine.

Say you log in after a two months vacation: what's new updates to you is already old news on the marketplace.

To wrap this up, if you want this feature, it seems the way to go is to write an extension that tracks the creation date of each extension's subdirectory on the local machine.

@mattdaviscodes
Copy link

+1 for the usecase in @janderudder's second scenario above. Sometimes I'll notice some new performance degradation and I'll want to figure out what I installed that is causing trouble. In that case, I'd like to sort my extensions in order of their install date so I can work backwards to find the cause.

@Dromantor
Copy link
Contributor

Since my FR was closed as a duplicate to this one, which it barely is but whatever, let me extend this feature request by what I requested:

It would be nice to have some notification which extensions were updated this session so that you don't have to actively scroll through the extensions panel and check if anything has indeed updated. Disable-able through a setting of course bc. it could annoy some users.

Use cases:

  • You have some extension disabled bc. it's broken any you wait for an update to be able to use it again.
  • You know some extensions require a reload after an update to work properly.
  • You want to know when your favourite extension updated to check out the changelog.

This could also help to track down the source of performance problems like mentioned multiple times because the user already knows what updated last.

@heartacker
Copy link
Contributor

heartacker commented Sep 20, 2022

fantastic works
we can see the recently updated exts and also @outdated exts
thanks
image

BTW: we could use one filter to see ext with two groups

and can we have this too

show the installed extensions while searching in another group #142007 (comment)

@benibenj benibenj added the verification-needed Verification of issue is requested label Sep 27, 2022
@RoestVrijStaal
Copy link

Isn't it strange to close the ticket before it has been verified as resolved?

@sandy081
Copy link
Member

We close the issue when it is fixed and get it tested. If there are any issues with the feature we will open new bugs.

@benibenj Is not this covered by a Test Plan Item?

@benibenj
Copy link
Contributor

benibenj commented Sep 27, 2022

This is indirectly covered by a test plan item (updates view test plan item). Verifying this should be enough then.

@sandy081 sandy081 added on-testplan and removed verification-needed Verification of issue is requested labels Sep 27, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Nov 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
extensions Issues concerning extensions feature-request Request for new features or functionality on-testplan
Projects
None yet
Development

No branches or pull requests