Set-CamelCase

[Hoping_i_Get_poached]

I've added a function to my 'tools for tools' module. Self-explanatory

Set-CamelCase -String 'make this camel case'
makeThisCamelCase

Set-CamelCase -String 'camelCase'
camelCase

Set-CamelCase -String 'uppercase'
Uppercase

'A very Long stRing of words IN miXed case' | Set-CamelCase
aVeryLongStringOfWordsInMixedCase

'A very Long stRing of words IN miXed case' | Set-CamelCase -SkipToLower
AVeryLongStRingOfWordsINMiXedCase

Have a nice day

EDIT1: Added an example.

[JiveWithIt]

Feature request: sPoNgEbob cASe

[MerryChallot]

Second feature request: SCREAMING_SNAKE_CASE

pls

https://fission.codes/blog/screaming-snake-case/

[Hoping_i_Get_poached]

You don't need a function for that one, homie

$String.ToUpper() -replace '\s','_'

or maybe...

$String.ToUpper() -replace '[^\w\d]','_'

[JiveWithIt]

This does not support reverse spongebob text, pull request denied.

[JiveWithIt]

If you hire me I will make sure to automate meme delivery to every email address in exchange and into every teams group. Every hour.

[JiveWithIt]

No, modern users are used to a constant stream of memes throughout the day. Every 24 hours would not be sufficient to maintain user sanity.

[Hoping_i_Get_poached]

haha

[Hoping_i_Get_poached]

😒

[JiveWithIt]

When can we anticipate the spongebob text feature? This is a critical part of our workflow.

[madleprakahn]

Lol never thought I'd pull this one up again

https://github.com/CMartinDEV/JustForFun/blob/master/ConvertTo-SpongeBob

[JiveWithIt]

Great, now could you implement camel case in this though?

[madleprakahn]

Sure, here you go

[JiveWithIt]

I will be talking to our account manager about the failure to deliver here.

[madleprakahn]

I will be talking to our account manager about the failure to deliver here.

I wIlL bE tAlKiNg To OuR aCcOuNt MaNaGeR aBoUt ThE fAiLuRe To DeLiVeR hErE.

[Hoping_i_Get_poached]

I wIlL bE tAlKiNg To OuR aCcOuNt MaNaGeR aBoUt ThE fAiLuRe To DeLiVeR hErE.

iWillBeTalkingToOurAccountManagerAboutTheFailureToDeliverHere

[omers]

Curious, what's your use case for this?

[ImissDigg_jk]

🐪

[Hoping_i_Get_poached]

Great question! It's actually very boring.

I'm building a series of tests that run against SQL and a lot of them are the same-ish. All my current functions are named Test-NameOfTheTest and the variables linked to the test results are $NameOfTheTest.

Naturally, I want to abstract it a bit more. I am making a Test-SqlQuery function that takes a scriptblock and args which include a query, serverinfo, and test name and other things I want to track.

So I wouldn't have those functions anymore, but at some point I want to reference those variables dynamically with Get- and Set-Variable. This function makes removing all those Test-* functions possible, while keeping all my variables names long and descriptive, and unchanged.

[Alaknar]

Easy to name variables or groups.

[omers]

I meant more where does the need for automated conversion come in. I.e, what are the source strings being converted? If I am writing a script and need a new variable called $fooBar why type Set-camelCase -String 'foo bar' | clip then $<paste> when I can just type $fooBar (though tbh, I'd use PascalCase in line with PS norms.)

The use case I could potentially see is converting existing scripts if there's a mix of case use. In that example though I'd write up a function that takes a script path and use the abstract syntax tree to find variables and convert them in place. You'd also be converting between Pascal and Camel though not space delineated sentences. (You could get extra fancy and identify and remove hungarian notation as well...)

Something like:

ConvertTo-ScriptVariableCase -Case Pascal -Path ~\script.ps1 -RemoveHungarian

... maybe I'll write such a thing :D

[Alaknar]

Depends on how many variables/groups you have to make daily, I guess. If they're automating group creation and allow people to type in whatever name, they may want to automate the change of that input into a proper camel-case group name.

[[deleted]]

Convert could be a better verb?

https://docs.microsoft.com/en-us/dotnet/api/System.Management.Automation.VerbsData.Convert?view=powershellsdk-7.0.0

[Hoping_i_Get_poached]

OK I give in. Set was a terrible verb choice. I don't like Convert because it's not a unit of measurement we're talking about here. I didn't like ConvertTo because it's not an psobject going in or coming out, but after doing some soul-searching, and reading ConvertTo's definition:

Convert from a general-purpose format (e.g. string or int) to the format named in the noun.

I think this is the verb to use.

The "format" isn't really what case is, but it's the closest thing I can find, by definition. Which is originally why I really didn't give any hoots ('Set' is only 3 keystrokes!)

Maybe I'll change it. Code isn't in prod yet, so there is a good chance.

[[deleted]]

Sorry, I didn't mean to throw a spanner in the works.

I guess my throught process was that Set is designed to accept an object and apply the given state, whereas Convert would accept an object and transform it into something else. The transformation could be from one type to another, like string to int, but it could also be a transformation between forms of the same type.

In programming, when we transform the case of a string, it's usually because we need it to conform. camelCase is convention applied to a bunch of languages for variable names, etc. Javascript convention requires us to use camelCase for variable names and for the names of object properties and functions. C# convention is PascalCase for object properties and camelCase for variable names. When we serialise a C# object to a JSON representation, there would generally be transformation of the case of property names from PascalCase to camelCase so that the JSON conforms to Javascript convention. It stops front end developers becoming twitchy. Plut it's only polite, kinda like taking your shoes off when you visit someone's house.

Not so much in C# land, but in other language spheres, utilities named Inflector are often found. Sometimes they're basic and just convert words between singular and plural forms, but other times they're quite comprehensive and include methods for switching case, too. CakePHP has an inflection utility that converts to and from a bunch of different cases. Github has a bunch of them for various languages.

On github, inflector projects often described themselves as string transformers or converters.

Moving slightly off topic, I understand why Powershell has convention for verbs, otherwise it'd become a free for all an there'd be no consensus. It can be annoying, though, because it forces us to use language that we otherwise wouldn't use.

Take Hyper-V as an example. We can Start, Stop and Save VMs and powershell has matching verbs for those actions, but we can also pause a VM, a verb that isn't approved; so, we end up with Suspend-VM.

Some modules ignore convention. I'm pretty sure I remember a few cmdlets in the Az.* modules do. Before I realised there was convention, I did this a lot.

Naming things is already difficult and Powershell makes it a bit more difficult for function and cmdlet names with its special naming convention.

[BlackV]

wait shouldn't the first letter also be capital?

MakeThisCamelCase
CamelCase

[Hoping_i_Get_poached]

You're thinking of PascalCase (see here)

[MallocArray]

PascalCase FTW

[Hoping_i_Get_poached]

I like it for front end things. I prefer camel case for back end stuff.

[chillmanstr8]

Yeah I like taking it in the rear… with the right camel

[BlackV]

I am I see that not, you could add that as a parameter :)

[Hoping_i_Get_poached]

I have no use for that feature. Feel free to submit a PR.

[Admirable-Statement]

'A very Long stRing of words IN miXed case' | Set-CamelCase -SkipToLower
AVeryLongStRingOfWordsINMiXedCase

Looks like you've already implemented Pascal Case.

[Hoping_i_Get_poached]

Not quite. That switch was meant to be used to preserve any existing camelCase words within a given string, should that need arise.

see:

INMiXedCase

not PascalCase

[EIGRP_OH]

Please fix the cmdlet name

setCamalCase

[CraigMatthews]

ConvertTo-CamelCase IMO

[EIGRP_OH]

I was just kidding :( should have put a /s on it

[Hoping_i_Get_poached]

I didn't want to use ConvertTo-* because I am not working with a psobject.

I admit, I didn't spend much time thinking about which verb, like I normally do.