Can it normalize capitalization?

[Jaykul]

Would it be possible to have the case of the token change the case of the output? I was surprised this week when I tried to generate something, that [color] values are all lower-case, while adjectives are Title Case capitalized. I guess I'd never used colors before. Personally, I would love it if the case of the token affected the case of the word, so if I put [Adjective] I might get "Bawdy" but if I put [adjective] it would be guaranteed to be lower-case.

Alternatively, could it be added as a sort-of common parameter case with options for Title and lower? Maybe even throw in UPPER or camel and Pascal 😉

[dfinke]

@Jaykul what's your take for a Get-StringCasing that returns title, camel, upper, or lower result on a target string? Saw some python examples, not covering all of those.

[Jaykul]

I wouldn't think detecting the case of text would be too useful ... except in this case of detecting token case, obviously 😁
Are you trying to get it, or convert it?

For what it's worth, I'm honestly not sure what it would meant to include camel and pascal case. I mean, for example, would it remove spaces from names and phrases, or would it only work to convert from PascalCase to camelCase and back?

Is going to do this:

Convert-Case "Joel Bennett" -Camel
joelBennett

Convert-Case ThisIsATest -Title
This Is A Test

Convert-Case "This Is A Test" -Sentence
This is a test

Convert-Case "This is a test" -Pascal
ThisIsATest

And if so, do we want it on individual tokens, or do we just want a -Captialization enum for the whole cmdlet output? 😉

And of course, if all of the above do ... that, then which of these is right:

Convert-Case ThisIsATest -UpperCase
THIS IS A TEST
Convert-Case ThisIsATest -UpperCase
THISISATEST

I guess I'd have to vote for a switch to allow choosing one of those outputs, and have the space-separated output be default 🤔

[dfinke]

Reading your initial comment, I thought you were suggesting to detect the case. Adding switches should be doable. Different languages were added for some options. Title case for [color ja] will be interesting.

I like the idea.

[Jaykul]

Well, I do think it would be cool to detect the case, so we could write [Color] [Person] and have it come out "Blue Bob Smith" or Thanks, [adjective] [Person] and have it come out as "Thanks, friendly Bob Smith" ...

But I'm not bothered if I need to write [adjective -lower] instead.

For what it's worth ...

function Measure-StringCase {
    [CmdletBinding()]
    param(
        [Parameter(Mandatory,ValueFromPipeline)]
        [string]$InputObject
    )
    process {
        $HasSpaces = $InputObject -cmatch "\s"
        $HasUpperCaseWords = $InputObject -cmatch "\s\p{Lu}"
        $HasLowerCaseWords = $InputObject -cmatch "\s\p{Ll}"
        $StartsLowerCase = $InputObject -cmatch "^\p{Ll}"
        # $StartsUpperCase = $InputObject -cmatch "^\p{Lu}"
        $HasLower = $InputObject -cmatch "\p{Ll}"
        $HasUpper = $InputObject -cmatch "\p{Lu}"

        if ($StartsLowerCase) {
            if (-not $HasUpper) {
                "LowerCase"
            } else { # if ($HasLower)
                if (-not $HasSpaces) {
                    "CamelCase"
                } else {
                    Write-Verbose "It's sentence case, but doesn't start with a capital"
                    "MixedCase"
                }
            }
        } else { # if ($StartsUpperCase) {
            if (-not $HasLower) {
                "UpperCase"
            } elseif (-Not $HasSpaces -and $HasUpper) { #  -and $HasLower
                "PascalCase"
            } elseif ($HasLowerCaseWords) {
                "SentenceCase"
            } elseif ($HasUpperCaseWords) {
                "TitleCase"
            } else {
                Write-Verbose "It's sentence case, with only one word"
                "PascalCase"
            }
        }
    }
}


Describe Measure-StringCase {

    $StringCases = @(
        @{ Case = "PascalCase"; Sample = "First"}
        @{ Case = "PascalCase"; Sample = "ThisIsATest"}
        @{ Case = "camelCase"; Sample = "thisWasATest"}
        @{ Case = "UPPERCase"; Sample = "THISISANOTHERTEST"}
        @{ Case = "Titlecase"; Sample = "This Is A Test"}
        @{ Case = "Sentencecase"; Sample = "This is also a test"}
        @{ Case = "lowercase"; Sample = "last"}
    )

    It "Detects the case of '<Sample>' as '<Case>'" -TestCases $StringCases {
        param($Sample, $Case)
        Measure-StringCase $Sample | Should -eq $Case
    }
}

[dfinke]

Cool, yeah, was going down the regex path. Just came across the {Ll} approach when investigating this option.

[compwiz32]

...and I just submitted a PR for improved wordlists...one of which is a bigger list of colors.
However, before I submitted, I converted all the colors to TitleCase ... never considered the possibility of the source not mattering and changing the output to match one's preference...