Tools used in the development of Phorge itself
Details
Sat, Feb 22
I'd be very much in favor and I'd be happy to contribute changes for this. I've added type hints in my local fork to assist in development. Especially for core utility functions like idx and id which otherwise completely hide type information.
Fri, Feb 21
The code to select which tests to run by default is in ArcanistWorkflow::selectPathsForWorkflow().
Jan 7 2025
Suggested meme for closing: "yesyes"
Dec 31 2024
Dec 30 2024
Dec 28 2024
Dec 26 2024
Dec 25 2024
How an extension can have their unit tests then? 🤔
Nov 28 2024
Aug 24 2024
Jun 23 2024
Apr 8 2024
I wonder if xhpast can be ditched. Eg:
For linters, use something off-the-shelf such as phpcs (https://github.com/squizlabs/PHP_CodeSniffer)
For diviner parsing of PHP code, I look at the class documentation (eg https://we.phorge.it/book/libphutil/class/ArcanistConduitCallFuture/) and question as to whether this provides anyone with any benefit.
Mar 4 2024
Mar 3 2024
Jan 22 2024
Jan 18 2024
Jan 13 2024
I've created R10 PhorgeIt Extension for this, with a little bit of content. I'll load it to the server shortly.