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.
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.
Questions
How do I nest an object?
Use dots in the path. user.contact.email: email produces { user: { contact: { email: "…" } } }.
How do arrays work?
Append [n] to a path segment. tags[3].name: title creates a three-element tags array, each element with its own generated name.
What happens with an unknown type?
It becomes a literal string. That is how you pin a constant — status: active gives every record the same status.