Open yurunsun opened 8 years ago
When someone implements them. The most likely scenario at this point is that someone who is using Pash (e.g. it actually has real-world usage already in SharpDevelop's nuget console) needs those cmdlets to continue integration and thus implements them. There are currently few active developers who are able to devote much time into the project and in the past two years most development effort stemmed from exactly that: Having a use-case for Pash that couldn't be met yet, but has subsequently been implemented.
There isn't a fixed roadmap as far as I know and implementing cmdlets has been a lower priority than implementing the engine for quite a while now. But if you're willing to contribute, you'd be welcome :-)
@yurunsun We love pull requests!
Thank you guys!
I'll try my best to contribute something. Maybe starting from those JSON related cmdlets is a good choice. :+1:
@yurunsun: One word of advice I should probably take to heart as well: Maybe don't bother implementing all parameters to the cmdlets yet. Those could come in later iterations.
I started implementing two or three cmdlets by now where I thought »Oh well, but this parameter has to work as well. And this one.« and in consequence there are a bunch of half-finished things lying around here somewhere, waiting for me to finish them.
Like:
ConvertFrom-Json ConvertTo-Json