Add named cases for convenience to the --keywordize / -k switch

[aschofie]

Add named cases for convenience to the --keywordize / -k switch

[borkdude]

What about:

$ echo '{"anApple": 1}' | jet -i json -k '(comp keyword csk/->kebab-case)'
{:an-apple 1}

Is this not short enough?

[aschofie]

It's not as short as I would like. The real advantage (other than ergonomics), is that you may not remember that the naming scheme follows actual case of: csk/->PascalCase csk/->camelCase csk/->SCREAMING_SNAKE_CASE csk/->snake_case csk/->kebab-case csk/->Camel_Snake_Case csk/->HTTP-Header-Case Having the most commonly used cases right there in the switch documentation saves you a couple of unsuccessful runs followed by a trip to google when you give up experimenting.

[borkdude]

Alright, but one thing I might want to change is the use of simple symbols as they might conflict with regular Clojure functions. Also, I think the names should reflect their shape, like in the csk library: SCREAMING_SNAKE_CASE, such that they are self-documenting. Perhaps we can use keywords:

--keywordize :SCREAMING_SNAKE_CASE

[aschofie]

@borkdude Happy to make whatever changes necessary to get this in. I had thought about using the csk names but didn't because the case endings added ~33 chars to the line width compared to leaving it off, and doing so took away the self-documenting ability from "camel", so I just made everything consistent and the easiest to type, but I have no strong feelings here, and will change it back to the csk names if you like that best. With regards to needing keywords though-- what mechanisms could you use to make -k SCREAMING_SNAKE_CASE mean something else? By having SCREAMING_SNAKE_CASE defined in user.clj or another place?

[borkdude]

Maybe the same mechanism as you had it in the original PR, special cases?

[borkdude]

So my proposal would be -k :SCREAMING_SNAKE_CASE

[aschofie]

Created new #145 with the csk keyword cases.