Closed ghost closed 1 year ago
72ms is les than 1/10th of a second?!
It does quite a bit of set up when it starts up, e.g.
migrateSettings();
validateColours();
validateIcons();
validatePlaceholders();
setButtonsAndContext();
It also doesn't activate until the rest of start up has finished.
I kind of resent the suggestion that it's just a "little extension" - I've been actively working on it for over 5 years and it has grown with features considerably since it started, so it's really not surprising it takes more than 0 milliseconds to start.
Feel free to create a PR, but I'm not likely to merge anything that removes features just to save a fraction of a second.
Oh, don't take me wrong. You put significant effort to create this extension. And I understand that.
I will message back when I detect what ia causing the slow down.
Todo tree makes my VSCode lag while 'scanning the workspace for Git repositories' for a long time. After disabling Todo Tree, it only takes a few seconds.
Todo tree extension seems to be making my VSCode slower to start. By 72 ms, which is not much, but it's a little extension I use every once in a while so, what is causing this delay?
I can make a PR myself, is someone points out what's causing this? I think it may be the activation points :-)