A toy to mess around Perforce's Helix Command-Line Client (P4).
By installing p4m to PATH and setting alias p4=p4m, p4m can act as a drop-in replacement of the original p4 command-line. The command-line output will be colorized and reorganized.
Currently supported commands are:
p4 add/p4 edit/p4 deletep4 diffp4 shelve/p4 unshelvep4 status
Examples:
$ p4 add test-add-file
[ add] //my-depot/main/test-add-file
/workspace/my-depot/test-add-file - missing, assuming text.
$ p4 status
Changelist #417: My changelist
(use p4 shelve to push them to server)
[ add] //my-depot/main/added-file
[edit] //my-depot/main/edited-file
[ del] //my-depot/main/deleted-file
Untracked files:
(use p4 add/edit/delete/reconcile to track them)
[ add] //my-depot/main/untracked-added-file
[ del] //my-depot/main/untracked-deleted-file
[mdel] //my-depot/main/untracked-moved-file
[madd] //my-depot/main/untracked-moved-new-file
No file(s) to reconcile.
The command handler converts all p4 command outputs to typed objects, making it possible to interact with them programatically. Hopefully, this library can be used in a VS Code plugin or something in the future.
The implementation does not depend on Python, as it parses Python's marshal format in JavaScript.
I'm not quite familiar with NPM so it is not available as a package for now. I will focus on the command-line override part for a while to improve the API design.
You need to install Bun as the JavaScript runtime.
After installing, run bun install and bun build-cli to get the binary.
I chose Bun because it provides cleaner file and child process interfaces. Also I have failed to figure out how Node handles stdio of child processes.
However, except the file part and child process part, most of the code will remain compatible with Node. The unit test should work under Node and Bun environments.