One of the things I appreciate most about maintaining PACX is seeing members of the community actively contribute ideas and code that improve the daily experience of using the tool.
Today I'm happy to announce a new addition to PACX: PowerShell tab completion support, contributed by Keno Schürger. This feature is now documented in the PACX wiki and makes it easier to work with PACX commands directly from the terminal.
First of all, a huge thank you 👏🏻 to Keno for the time, passion, and expertise he is investing in the project. Open source thrives because people decide to contribute their knowledge and help solve problems that benefit the whole community. This feature is a perfect example of that.
💡 How the idea was born
Almost a year ago, during a community discussion about development workflows around PACX, a community member asked whether PACX could eventually support IntelliSense-like capabilities and command completion inside PowerShell. At the time, I wasn't even sure how feasible it would be, and I openly asked for suggestions from the community.
A few months later, another contributor pointed out an existing implementation for the official Power Platform CLI (pac) that could serve as inspiration for PACX. That conversation effectively planted the seed for what is there now.
Open source often works exactly like this:
- Someone identifies a pain point
- Someone else provides inspiration
- A contributor takes ownership
- The entire community benefits
This is exactly the kind of collaboration that makes love working on open source projects.
🤔 Doesn't PACX already provides an interactive mode?
Yes.
PACX already provides an --interactive mode that helps users discover commands and options without having to remember every parameter.
PowerShell completion does not replace that experience, it complements it. Interactive mode works well when you need to launch a single command, or multiple commands in a fire-and-forget way.
Completion, on the other hands, helps a lot when scripting commands for later use. Or even, when we know exactly which commands to use, but don't remember arguments and/or values.
If you're already comfortable working directly from the command line, tab completion can help reduce typing and make command exploration more natural within your existing PowerShell workflow.
Basing on how I use PACX daily, I'm sure I'll use this feature way more than the interactive experience.
🏃🏻➡️ Getting Started
If you'd like to enable PowerShell completion for PACX, you can find the installation instructions in the wiki:
If you're interested in the implementation details, you can also take a look at the contribution itself:
And for a bit of historical context, here's the original discussion that inspired the feature:
👏🏻 Thank You
Once again, a big thank you to Keno for this contribution and for the ongoing support he is providing to the project.
PACX continues to improve thanks to people who not only use it, but also take the time to share ideas, report issues, improve documentation, and contribute code.
Those contributions, large or small, are what keep the project moving forward.
Happy coding! 🚀
Top comments (0)