Summary
When Preserve acronyms is enabled in Slugify & Case Converter, the lowercase-oriented kebab-case, snake_case, and dot.case outputs retain uppercase acronym tokens. This conflicts with the usual lowercase naming convention and with the same page's lowercase slug-case output.
Affected tool: Slugify & Case Converter
Route: https://byteflow.tools/en/slugify-case-converter
Status: Needs product confirmation; core conversion works, but the behavior is inconsistent with the documented scope and neighboring output.
Observed: 2026-08-18
Reproduction
- Open the affected route.
- Enter:
- Enable Preserve acronyms.
- Inspect all generated formats.
Actual output
The documented acronym-preserving formats camelCase, PascalCase, and Title Case preserve JSON, API, and URL as expected.
However, the lowercase-oriented outputs also retain the uppercase acronym tokens. One observed output is:
kebab-case: parse-JSON-API-URL-v2-0
The snake_case and dot.case outputs likewise keep the acronym tokens uppercase. At the same time, the slug-case output is lowercase:
slug-case: parse-json-api-url-v2-0
Expected output
The product behavior should be made explicit and consistent. Either:
- Preserve acronyms applies only to the formats documented on the page, in which case kebab-case, snake_case, and dot.case should remain lowercase; or
- Preserve acronyms intentionally applies to every format, in which case the page documentation and naming expectations for the lowercase-oriented formats should be updated.
If lowercase styles are intended, the expected outputs are equivalent to:
kebab-case: parse-json-api-url-v2-0
snake_case: parse_json_api_url_v2_0
dot.case: parse.json.api.url.v2.0
Impact
Users relying on standard lowercase kebab/snake/dot naming may receive identifiers containing uppercase characters, while similar outputs on the same page use lowercase.
Regression coverage
Test Preserve acronyms on and off with JSON/API/URL tokens, and assert the documented behavior separately for camelCase, PascalCase, Title Case, kebab-case, snake_case, dot.case, and slug-case.
Summary
When Preserve acronyms is enabled in Slugify & Case Converter, the lowercase-oriented kebab-case, snake_case, and dot.case outputs retain uppercase acronym tokens. This conflicts with the usual lowercase naming convention and with the same page's lowercase slug-case output.
Affected tool: Slugify & Case Converter
Route: https://byteflow.tools/en/slugify-case-converter
Status: Needs product confirmation; core conversion works, but the behavior is inconsistent with the documented scope and neighboring output.
Observed: 2026-08-18
Reproduction
Actual output
The documented acronym-preserving formats camelCase, PascalCase, and Title Case preserve JSON, API, and URL as expected.
However, the lowercase-oriented outputs also retain the uppercase acronym tokens. One observed output is:
The snake_case and dot.case outputs likewise keep the acronym tokens uppercase. At the same time, the slug-case output is lowercase:
Expected output
The product behavior should be made explicit and consistent. Either:
If lowercase styles are intended, the expected outputs are equivalent to:
Impact
Users relying on standard lowercase kebab/snake/dot naming may receive identifiers containing uppercase characters, while similar outputs on the same page use lowercase.
Regression coverage
Test Preserve acronyms on and off with JSON/API/URL tokens, and assert the documented behavior separately for camelCase, PascalCase, Title Case, kebab-case, snake_case, dot.case, and slug-case.