openapi-psr7-validator VS Serializer

There is a package within The PHP League that allows validation of an OpenAPI specification: league/openapi-psr7-validator. This package validates requests and responses to the PSR-7 specification.

- https://github.com/thephpleague/openapi-psr7-validator for validation

how does this compare with https://github.com/thephpleague/openapi-psr7-validator

One tool destined for the PHP community and maintained by The PHP League is OpenAPI PSR-7 Message Validator, a package validating PSR-7 HTTP messages against OpenAPI definitions.

Request validation in a middleware layer using thephpleague/openapi-psr7-validator that allows us to validate 99% of an incoming request without the need for boilerplate checks in our handlers/controllers. Business specific checks will still need to be handled in the handler/controller though: eg, make sure user email is unique or validate account ID is still active, etc.

OpenAPI PSR-7 Message (HTTP Request/Response) Validator: It validates PSR-7 messages (HTTP request/response) against OpenAPI specifications.

And, imagine my surprise, even a Symfony-dedicated lib that does the same under the hood: https://github.com/thephpleague/openapi-psr7-validator

Making a class "final" is always a bad decision IMO. You would never know how will other people use your library. For example, we used JMSSerializerBundle and wanted to extend DateHandler to make it not to throw exceptions if a date string is invalid. But the class is final. So we had to just copy-paste it :(

Or this popular alternative: https://jmsyst.com/libs/serializer

JMS Serializer: This library allows you to (de-)serialize data of any complexity. Currently, it supports XML and JSON.

Only took a very brief look, but it looks nice. I like that the DTO class isn't required to extend anything, and that it seems to be for real DTOs used for actual transfer of data between systems - not 'local dtos'. It feels like this might be more comparable to something like schmittjoh/serializer rather than spatie/data-transfer-object.

When it's time to create the PDF, convert the object structure to an XML using an already existing serializer (like JMS or symfony serializer) or do this by hand.

One frequently used serializer is JMS Serializer which allows you to convert JSON or XML to objects (or the other way around if needed). You can then use the objects in your application.