vad3x / case-extensions Goto Github PK

"WindowsServer2016R2" is being transformed to "windows-server2016-r-2".
Should be "windows-server-2016-r-2"

see: https://textedit.tools/kebabcase

If managed, submit a pull request for known issues. @vad3x @another-guy

The README indicates that this library is licensed under the MIT license, but no file is included.

This is a great utility that I've been using, but I occasionally run into ALL_CAPS text that I'd like to change case to another format as well. Technically, I can get it working by calling .ToLower() on the text first, but it would be nice to have true bi-directional support for this.

Hello Vadim

First of all thanks a ton for a nice package! I am surprised I was unable to find any alternatives to your NuGet package which was first released in April last year. Good job!

I have a couple of questions. Hopefully, you will not be mad if I don't open an issue per question.

• Are there any plans to support Train-Case? This would make the library a little more complete, IMO. By the way, the style is referred here http://stackoverflow.com/a/17820138/482868

• Are there plans to support netstandard1.6? The compilation fails for one of the projects I'd like to introduce a dependency on CaseExtensions.

error: Package CaseExtensions 1.0.1 is not compatible with netstandard1.6 (.NETStandard,Version=v1.6). Package CaseExtensions 1.0.1 supports: netcoreapp1.0 (.NETCoreApp,Version=v1.0)
error: One or more packages are incompatible with .NETStandard,Version=v1.6.

• You may want to change wording in the documentation to clarify that cross-style translations are possible (i.e. kebab to camel, or camel to snake). It might be obvious from the word any in this sentence (but it was not for me)

The library that allows to change any string case to PascalCase/camelCase/kebab-case/snake_case.

So, I had to depend on CaseExtensions 1.0.1 and run some test code (funny that I did not notice the unit tests in the repo).

-- Igor