JSON to Python dataclass

Python has no anonymous record type, so every object needs a name. Each nested object becomes a class named after the field holding it, declared before the class that uses it.

The original JSON key, kept where the Python name had to differ. isPro becomes is_pro to read as Python, and the comment is what lets you match it back to the payload when you write the parsing layer.

A dataclass may not place a field with a default before one without, so the generator sorts required fields first. That is a language rule rather than a style choice.