A whole number and a decimal do not land the same way on the PHP DTO. On the JSON converter, paste 1 and the property is typed int. Paste 1.5 and it is typed float. TypeScript types both as number. Conversion runs in the browser. Nothing is uploaded.
Same JSON, split types
JSON itself does not separate int from float the way PHP does. The draft still does on the PHP class. That is useful when you want a strict property, and easy to miss when you expected one TypeScript-style number everywhere.
The class name stays DataTransferObject. Treat the output as a starting point. Rename the class, and decide whether int, float, or a wider type belongs in the code you ship.
Keep this separate from a scalar list
A root list such as [1,"a",true,null] is a different case. Laravel prints a PHP list of those four values. TypeScript prints export interface Root {} with nothing inside, because the first item is a number, not an object. The PHP DTO prints the stub class whose only body is the comment Provide a JSON object to generate properties. CSV rejects it with CSV conversion expects an array of objects.
The int/float split above is about a numeric property value on an object the DTO can draft. The scalar list never gets that far on TypeScript or the DTO.
Invalid paste still clears everything
A trailing comma such as {"a":1,} clears every format. Repair broken text in the JSON formatter, then convert again.
Guide: https://kepttools.com/guides/json-to-typescript-php-dto-laravel