ALSI.CaseConversions 10.0.0

<div align="center">

ALSI.CaseConversions

Convert naming conventions without ceremony.

Small, allocation-conscious .NET string case conversion for identifiers, keys, generated names, and other ASCII-oriented application text.

</div>

ALSI.CaseConversions turns identifier-like strings into the case your boundary needs: JSON property names, route keys, generated code symbols, file names, configuration keys, and similar application text.

using ALSI.CaseConversions;

string routeKey = KebabCase.Convert("CustomerAccountId");
string jsonName = SnakeCase.Convert("CustomerAccountId");
string typeName = PascalCase.Convert("customer_account_id");

Why Use It

<table> <tr> <td><strong>Clear API</strong></td> <td>One static facade per target case, all using <code>Convert(...)</code>.</td> </tr> <tr> <td><strong>Flexible inputs</strong></td> <td>Handles camelCase, PascalCase, snake_case, kebab-case, dot.case, spaces, uppercase runs, and digits.</td> </tr> <tr> <td><strong>Low overhead</strong></td> <td>Uses stack-allocated buffers for short inputs and shared array pool buffers for longer inputs.</td> </tr> <tr> <td><strong>No setup</strong></td> <td>No services, options objects, extension registration, or converter aliases.</td> </tr> </table>

Install

dotnet add package ALSI.CaseConversions

Package Manager Console:

Install-Package ALSI.CaseConversions

Quick Start

using ALSI.CaseConversions;

var jsonProperty = SnakeCase.Convert("CustomerAccountId");
// "customer_account_id"

var routeSegment = KebabCase.Convert("CustomerAccountId");
// "customer-account-id"

var generatedTypeName = PascalCase.Convert("customer_account_id");
// "CustomerAccountId"

SnakeCase.Convert("HelloWorld");      // "hello_world"
CamelCase.Convert("hello-world");     // "helloWorld"
PascalCase.Convert("hello world");    // "HelloWorld"
KebabCase.Convert("XMLRequest");      // "xml-request"
DotCase.Convert("File123Name");       // "file123.name"
MacroCase.Convert("helloWorld");      // "HELLO_WORLD"
SentenceCase.Convert("hello_world");  // "hello world"

Supported Targets

Input Handling

Converters are designed for strings that already behave like identifiers or keys.

They handle:

• Existing separated text: hello_world, hello-world, hello.world, hello world
• PascalCase and camelCase inputs
• Runs of uppercase letters such as XMLRequest
• Digits inside names, for example File123Name
• Leading and trailing separators
• Empty input and null string input, which return string.Empty

For example:

SnakeCase.Convert("PascalCaseInput");      // "pascal_case_input"
SnakeCase.Convert("camelCaseInput");       // "camel_case_input"
SnakeCase.Convert("Hello-World-Example");  // "hello_world_example"
SnakeCase.Convert("Hello.World.Example");  // "hello_world_example"
SnakeCase.Convert("File123Name");          // "file123_name"

Notes and Limits

• Inputs should be limited to characters in the 0x00 to 0xFF range.
• ASCII letters and digits are retained.
• Other characters are treated as delimiters or skipped according to the converter's internal character table.
• Converters are static and configuration-free by design.

Benchmarks

Public benchmark reports are checked into the repository for auditability.

See the latest checked-in report: reports/2026-06-13.

License

This project is licensed under the terms in LICENCE.