- Output: interface or type alias?
- Toggle between both. Interfaces support declaration merging; type aliases support unions and mapped types. Pick per project convention.
- Does it detect optional fields?
- Fields missing from any sample record become `?:` (optional). Always-present fields are required. Verify the output with a fuller sample set.
- What about discriminated unions?
- Not auto-detected. For JSON with a 'type' field discriminator, you'll need to manually combine the generated interfaces into a union.
- How is this different from json-to-typescript-types?
- Same core engine; this tool's output always uses `interface`. json-to-typescript-types has more output options (types, Zod schemas). Use either; the output is equivalent.