The other generators fix the field names. This one does not. Write profile.address.city: city and you get that exact nesting; write orders[3].sku: sku and you get three order objects, each with its own generated SKU.
What you can control
- Dots create nested objects to any depth.
[n]repeats a path into an array ofnelements, each generated independently.- Any unrecognised type is treated as a literal, so
role: adminputs the stringadminin every record. - Thirty-three built-in types, matching the field list the other developer tools use.
Testing ideas
- Nesting. Use dots for objects and
[n]for arrays (orders[3].items[2].sku) to reproduce your real payload shape, then test deeply nested rendering. - TypeScript interfaces. Append the generated interface to keep fixtures and types in sync, and let the compiler flag a fixture that drifts.
- Single object. Switch the root to one object for configuration files and detail views.
- Big documents. Generate up to 1,000 records to test virtualised lists and JSON viewers.
What this is not
The syntax is line-based and deliberately small. It has no unions, conditionals or references between fields — if you need those, generate the base records here and post-process them.