Picture this, you're happily coding an awesome feature for your product and you have a few VS Code tabs open specific to that feature. Suddenly, yo...
For further actions, you may consider blocking this person and/or reporting abuse
It's almost like an extended functionality added on top of
git stash, but now you get to restore the active tabs as well instead of just the line changes to the files themselves. Cool stuff!Haha when I was telling a teammate about the idea, he replied “oh, like git stash on steroids”.
Yeah. I suppose with VSCode you could accomplish the same thing with just git stash, when you apply the stash then the list of those files will appear in the version control sidebar, but that's kind of janky whereas this allows more precise control. Kudos for writing the extension!
Also, imagine you have a file open that you haven't modified, you have it open just because you're referencing things from there. That file would not show up in
git stash. With the extension you can add those files as well.Found this, just what I was looking to create sets of files I need to work on different pages. Especially when inheriting a project with a disorganized folder structure. Now I can have my routing modules in one place.
One little issue. After painstakingly creating filesets for a project, we completed phase 1 and moved to phase 2, but a different project and repo. Almost the same file and folder structure. How can I most easily copy my working sets to the new project?
Love this idea! Well done. I'm going to try this out tonight.
Awesome! Please do let me know how it goes 😀
Finally got a chance to install it and try it out. Works great! No issues. Nice clean, simple experience. Thanks for building this!
Dude, this is amazing! I spent a lot of time organizing my tabs by working on different ideas and projects at the same time, for me works fantastic.
Thanks! I’m glad somebody else finds it useful 🎉
Looks good. I'll give it a try tomorrow.
Would be cool to somehow manage these by git commit/branches too.
Can you expand a little on what you mean? Sounds interesting, I haven't looked into VS Code's extension API regarding version control, but maybe they provide some events after certain git actions where I can hook into.
I usually do feature branches, and especially as a lead I can be switching between branches often checking others work. So it would be amazing if the sets would change when the branch changes. Especially if that branch touches multiple hands then they get exactly what context needs focus
Of course some way of doing that per commit would be cool, but would be a lot of setup on the user side too. So I think branch based would be more realistic/useful.
I've made a note to look into this. I like the idea of (optionally) associating a working set to a git branch and auto-open it when you switch to that branch.
Awesome love the idea. I'll give it a try.
Its awesome
That's an amazing Idea. I'll check it out. Thanks
Was just like "wouldnt it be nice if you could save all your features editors so you can close and come back to em" to a co-worker and bam, ofc you can, cause of awesome community devs like you! ty!