Serde VS data-transfer-object

In PHP there is a lib that draws inspiration from serde https://github.com/Crell/Serde

Guzzle for the actual connection. Get back JSON. Use https://github.com/Crell/Serde to map that JSON into classed objects. Do as you will with the objects. (You can also do the same the other way around to create a message object with all the type safety and builder functionality you want, Serde it to JSON/array, and then send the message through Guzzle.)

I even have a very nice library to make that dead simple for you: https://github.com/Crell/Serde

Sounds a lot like Serde. :-)

Sounds a bit like Serde: https://github.com/crell/serde

Speaking of… https://github.com/spatie/data-transfer-object is dead, does doctrine offer similar functionality?

Once you are confident in the argument types, add them to the methods. If there are too many, create a Data Transfer Object. Also add method return types.

The benefits of using DTOs are numerous, there's even a package from Spatie for them. See the package's release post and this awesome DTO explanation for a more in-depth take and how to implement and use them in a more sensible way.

I opted to use Spatie's DTO package and a bit of additional custom code for easy casting. I decided to map each JSON column to its own DTO, so I created two classes for land and for army.

When possible, I surely will try using the spatie/data-transfer-object with attributes to see if I like it.

Open Source projects using this Action. Mostly my own projects, as I just released the Action. However, Spatie, a huge contributor to open source PHP packages recently added the workflow to their PHP package template; which makes me super proud ♥️

This spatie lib looks neat too, though it might not be all that static analysis friendly. I guess this doesn't save you from having two classes with the same properties. Seems like it could be worth a shot. Short of inventing a code generation tool I don't know how much better I can do.