Select object for hash table

[bgshacklett]

RFC for Extending the Select-Object Cmdlet to facilitate working with Hashtables

[bgshacklett]

This has been sitting for some time with no action, so I'm guessing I put the document into the wrong folder (The instructions were a bit difficult to understand on that point). I just moved the draft document to the 1-Draft folder.

[joeyaiello]

Finally got around to reviewing this with @PowerShell/powershell-committee.

It sounds like the problem that's being solved here is to convert nested hashtables to PSCustomObjects when the keys are all strings (when they're not strings, conversion will likely result in key collision due to ToString() returning type names).

To that end, we think it's more generically useful to build a ConvertFrom-Hashtable cmdlet that would allow more generic and custom conversion of hashtables to PSCustomObjects and potentially other types using constructors that expect specific hashtable "schemas". Another possible implementation is to do a ConvertTo-PSCustomObject that does more custom handling (and these aren't mutually exclusive). Additionally, a ConvertTo-Hashtable is probably useful.

We don't have this on our radar right now, but if someone wants to give a go at a ConvertFrom-Hashtable RFC and implementation, go for it.

[joeyaiello]

Pending quorum from the rest of the committee for voting.

[joeyaiello]

Still no quorum but we do have a 👍 from @HemantMahawar

[SteveL-MSFT]

@PowerShell/powershell-committee had quorum and discussed this and agree not to modify select-object specifically for hashtables, but to introduce new cmdlets to make work with hashtables and pscustomobjects

[bgshacklett]

Shall I just leave this PR open under your control for changes or is it being tracked internally somehow?

[joeyaiello]

To be clear, we believe the correct solution to this scenario is what we described above, but we don't consider it enough of a priority today to write the RFC or implement it ourselves.

To that end, I talked with @daxian-dbw and @SteveL-MSFT about this, we believe the right thing to do here is:

• reject/close the PR
• file an issue linking back to this PR and briefly describing our ideal solution
• mark that issue Up-for-grabs