4/?

Takes a string, array of strings, a .NET DirectoryInfo object, array of DirectoryInfo objects, a mixed array of strings/DirectoryInfo objects, or an array of arrays of the above as input. I'm now working on the reverse functionality (POSIX -> Win).

What in the everliving fuck is wrong with me?

3/?

1. Is 300+ lines long
2. Has two mutually-exclusive parameter sets
3. A truth table
4. A nested function that recursively calls itself to parse arrays (with a stopwatch in case of infinite recursion)
5. A return object with its own attached functions
6. Auto output copy-to-clipboard by switch

2/?

This is an easy problem. It can be accomplished in just one or two lines of PowerShell if you don't care about errors or accuracy.

It's now two days later, and this function now is/has:

This is amazing and I'm stealing it.

Witchcraft.

I NEVER trust anything that works on the first try.

I'll give it suspicious side-eye until the day I decommission it.

Now rewrite it to be more efficient and close the holes, document how you did it, and then upload the new version and vanish into the aether.

Refuse to elaborate.

Pancakes. I will not elaborate.

🥞

I didn't know that I needed something like this in my life until just now.

Never had to deal with the raging garbage fire that is HP Enterprise's site, eh?

I feel seen

This is fucking creepy.

That's a little horrifying. Never been bit by that before, thankfully.

I'm a big fan of making the config files for work scripts in JSON just because of the good integration in Python & PowerShell.

Gonna have to keep that in mind in the future.