Release 0.3.4

[jplatte]

#27 is not a breaking change, so I'd like to release it as v0.3.4. This means creating a branch for v0.3.x off the "Forbid unsafe code" commit, since the one after that introduced a breaking change.

Additionally to minimize breakage when the current traits are removed in favor of methods on the ConvertCase trait (the more I think about it the more I like that idea), the new methods should immediately be available with the old ones being deprecated. This means that the most obvious upgrade path if one doesn't want deprecation warnings is switching everything to the new trait directly, minimizing the possibility of ambiguity errors for the method calls.

[alex]

There seems to be an 0.3.3 release on crates.io, but I don't see a version change or any other evidence of it in this repo. Is this a legit release?

[jplatte]

It's there, just not on master. See v0.3.x branch. The release fixed #32 (and decreased the crate tarball size by excluding irrelevant files).

[alex]

Ah, this was confusing to me, since master's Cargo.toml still shows 0.3.2, so it didn't occur to me there was a seperate maintenance branch for 0.3.x. Thanks.

[ghost]

@jplatte 👋 would you be able to release another version with everything from development?
I needed the ToUpperCamelCase and ToLowerCamelCase for work on nu shell.
I am attempting to migrate nu shell's string casing functionality to use hecks but cannot target a Git revision:
nushell/nushell#4081 (comment)

[jplatte]

Hi @efx, upper camel case and lower camel case are already supported, just under somewhat weird names: upper camel case is just CamelCase, lower camel case is mixedCase.

The names that you see on the latest state of the git repo will be used starting with 0.4.0, but I want to fix #26 before releasing that and this project is very low on my todo list.

[jplatte]

This didn't happen but 0.4.0 did. I don't think there's a point in having this issue, people can follow the PR if they care about it.