Validate a feature config
Check common scalar values and a list.
enabled: true
retries: 3
regions:
- india
- europeExpected: A JSON-style object with enabled, retries, and regions is shown.
Try in editorUse the YAML editor online for small config snippets, structured notes, workflow drafts, and simple data checks. ToolerWork validates common YAML patterns locally in your browser.
tool: ToolerWork runsLocally: true languages: - SQL - React
{
"tool": "ToolerWork",
"runsLocally": true,
"languages": ["SQL", "React"]
}Common config-style YAML is parsed locally and shown as a JSON-style result. It is designed for focused snippets and learning tasks where a fast browser workspace is more useful than a full local project.
Start with the built-in project, replace its sample with one of these focused examples, and compare your result with the expected output.
Check common scalar values and a list.
enabled: true
retries: 3
regions:
- india
- europeExpected: A JSON-style object with enabled, retries, and regions is shown.
Try in editorKeep a small flat configuration readable.
name: build
command: npm run build
timeout: 120Expected: The three config values parse successfully.
Try in editorYes. ToolerWork validates common YAML config patterns locally.
The browser MVP focuses on simple config-style YAML, not every advanced YAML feature.
Yes. Preview shows a JSON-style representation.
No. It stays in your browser workspace.
Common config-style YAML is parsed locally and shown as a JSON-style result. The workspace also keeps the active project in local browser storage.
Anchors, aliases, tags, multiline scalars, and deeply nested advanced YAML are outside this lightweight parser. Use a full YAML implementation before shipping a complex production configuration.