v1.1 Preview Feedback

[ethanbergstrom]

Started porting my existing modules from Crescendo 0.4.1. to the 1.1 preview, and had some feedback:

• Export-CrescendoModule in the new version is definitely not a drop-in replacement vs older versions. It doesn't seem to like the object-to-JSON mechanism I used previously.
• The documented approach for chaining New-CrescendoCommand, Export-CrescendoCommand, and Export-CrescendoModule at https://learn.microsoft.com/en-us/powershell/utility-modules/crescendo/advanced/using-crescendo-cmdlets was very helpful to get a feel for how they are envisioned to worked together
• Export-CrescendoCommand is a little lacking in it's chaining ability. It can emit a bundle of JSONs, but it doesn't tell you what the JSON filenames it generated are in stdout, which means I cant chain it directly to Export-CrescendoModule.
  • Emitting the corresponding System.IO.FileInfo objects of the files it generated by default would be nice, so that I can Export-CrescendoCommand | Export-CrescendoModule or Export-CrescendoModule -ConfigurationFile (Export-CrescendoCommand)
• A minor thing, but the parameters -targetDirectory, -fileName, and -command on Export-CrescendoModule aren't capitalized to PowerShell conventions
• The issue described in JSON created by Export-CrescendoCommand can not be read by Export-CrescendoModule #155 doesn't seem to be completely fixed. The JSON emitted by using -fileName to designate an output works just fine, but the per-command JSONs generated by the -targetDirectory behavior still use the previous JSON schema, which the new Export-CrescendoModule cannot read.
• No behavior changes (as best as I can tell) to my in-line output handlers to parse WinGet's messy stdout, which is a huge relief.

Example changes I had to make to adapt to Crescendo can be found here: ethanbergstrom/Cobalt#21 and the final result can be found here: https://www.powershellgallery.com/packages/Cobalt/0.4.0

Nice work!