mjcrouch
Urgent Need for Active Changelist Selection Support
I'm writing to express my frustration with the current behavior of the Perforce extension for VS Code. It’s incredibly irritating that every change is forced into the default changelist, causing a chaotic mix that makes it nearly impossible to keep track of updates. I've tried 100 times and there is no workaround. This lack of active changelist support is unacceptable—it leads to lost edits, overlooked updates, and thus crashes due to the files that aren't uploaded. Please address this issue and implement active changelist support promptly. I would appreciate that a lot.
This lack of active changelist support is unacceptable
please bear in mind this is a free open source extension that I (and others) occassionally spend some free time on to improve the project (even though I don't personally use perforce any more). If you feel something is unacceptable then you're welcome to contribute changes to the extension or create another extension.
Having an active/target changelist selection was an idea I've mentioned before in #185 and I think overall it would be a good thing, it's still a fairly big project that needs some thought to produce a consistent and reliable experience for users, and as far as I can recall among the thousands of users this is the first request specifically for this feature - so I have not had much of a reason to work on it and it's unlikely I'll have time to do so soon
As mentioned pull requests are welcome if you are able to contribute this feature.
Hi mjcrouch,
Thank you so much for your prompt response and for taking the time to explain the situation. I completely understand and appreciate that this is a free and open-source extension, and that you and others contribute your valuable time to it. My apologies if my initial message came across too strongly – "unacceptable" was definitely an overreaction born out of frustration with my workflow being disrupted.
I saw your mention of this similar idea in #185 , and I'm actually quite interested in exploring how I might be able to contribute to this feature myself. While I can't promise immediate results, I'd be willing to look into how this could be implemented and potentially contribute to the codebase. : )