mjcrouch
commented
1 year ago Hi,
Thanks for the comment - I wasn't aware that SD is still in use at MS! I removed it because it was making the code more complicated and I didn't think it was still used.
I would like to be able to support your use case, however I don't really have a way of testing it and I suspect there will be many more features that just break because of not being supported - so it's unlikely I'll be able to do it myself.
So, other than reverting to the slevesque version, I can only recommend making a fork of this extension and re-adding it to see how much is broken, then we can consider merging it back in if it's working well enough.
Is your feature request related to a problem? Please describe. I work on a team at MSFT that still uses Source Depot. While most engineering orgs have moved to Git, many internal platform/fleet management tools are still on SD and will remain "on" until all of our customers can migrate to Git as well.
While I previously used stef-levesque/vscode-perforce, this extension has been deprecated within VSCode Marketplace and users are now directed to install this fork.
I see that #8/#31 removed the compatibility mode with Source Depot, so presumably this hasn't been around for a fair while in this fork of the extension.
Describe the solution you'd like Re-add a backwards compatibility mode for SD. Broadly speaking, this means skipping explicit
logincalls (SD does Kerberos SSO or calls to an external UI for providing other authN methods), but other parts of P4 may not directly translate to SD either.Describe alternatives you've considered I can go back to stef-levesque/vscode-perforce, but VSCode is becoming more and more insistent on users migrating away from deprecated extensions. I can't imagine this is a tractable solution for much longer.