Convert naming case and validate as JSON
When generating configuration keys from source-code identifiers, this chain first converts the naming convention (e.g. snake_case to camelCase) and then validates the result as JSON. The validation step catches cases where the conversion produced invalid JSON keys — for example unquoted strings or trailing commas.
What it solves
Convert identifiers to a target naming convention, then validate the output as JSON to confirm structure.
Input → Output
Naming Convention Converter input → JSON Validator output across 2 steps.
Runs in
1–2 minutes · fully local in your browser.
Before you start
- A list of identifiers or a JSON-like string using a source naming convention
The pipeline
-
Convert between camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE. Free, private, 100% client-side.
Params: from=snake, to=camel
-
Validate JSON and pinpoint syntax errors by line and column. Free, private, and 100% client-side.
Runs locally in your browser. The recipe defines the pipeline only — your input never leaves this tab.
▶Run this workflow
Enter your input below and click Run. All processing happens locally in your browser — nothing is uploaded.
Pipeline progress
- Naming Convention Converternaming-convert
- JSON Validatorjson-validate
Sample input
{"user_name":"alice","is_active":true} Expected output
Valid JSON
This pair is executed against the real tools at build time (tests/unit/recipes.test.ts) — the expected output is verified, not illustrative.
Related workflows
You might also need
Workflows sharing tools or topics with this recipe.