Deptrac
Serializer
Deptrac | Serializer | |
---|---|---|
16 | 9 | |
2,559 | 2,302 | |
1.3% | - | |
6.2 | 7.9 | |
15 days ago | about 2 months ago | |
PHP | PHP | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Deptrac
- Microservices aren't the problem. Incompetent people are
-
Enforce architecture rules with Deptrac
Deptrac
-
PHP libraries and tools
Deptrac: Keep your architecture clean.
-
Enforcing module boundaries in a large php app
So far I've found some tools which I could piece together to accomplish enforcing module boundaries, probably run as part of an automated github action. - https://github.com/qossmic/deptrac Uses YAML to define any boundary, you can also use @internal to hide implementation classes. Seems like a good way to achieve what I want.
- Deptrac - architectural code analysis
- Deptrac - architectural static code analysis
- Deptrac, the is a static code analysis tool to enforce architectural decisions had version 1.0.0 released!
-
Best way to check custom coding conventions
How about https://qossmic.github.io/deptrac/ ?
-
The use of `class` for things that should be simple free functions (2020)
>I wonder: Is automatic DI even helpful? You save some lines of boilerplate but sacrifice control over the initialization-order and get a flat, messy, implicit dependency graph
Initialization order doesn't matter if your services are stateless. At least in our codebase, all of them are stateless, as it greatly simplifies reasoning about concurrent code (both in-process and between servers). Yes, it's easy to end up with a very a convoluted dependency graph under the hood, but I don't think it's a problem you really should care about. I mean, your code most likely already compiles to a very convoluted mess of machine code under the hood (with all the optimizations, ABI quirks etc.) and I doubt it matters to you much, as long as it does its job well and doesn't hinder your productivity.
If you are talking about messy dependency graphs from the architectural standpoint (someone can easily add a dependency in the constructor without thinking about the consequences), we use deptrac for our PHP monolith which can validate your architecture is clean at build time [0]
However, for our microservices written in Go, we decided to use manual DI to stimulate developers to prefer simpler design, otherwise our microservices could quickly turn to monoliths again.
[0] https://github.com/qossmic/deptrac
-
The 4 basic libraries every Symfony Project needs to improve code quality
Deptrac is a static code analysis tool for PHP that helps you communicate, visualize and enforce architectural decisions in your projects.
Serializer
- Data-Mapper: A package for fast mapping of strong-typed objects
- brick/json-mapper: map JSON data to strongly typed PHP DTOs
-
Design Decisions: Why use final classes
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 :(
- Symfony serializer is tedious
-
Array -> Entity
Or this popular alternative: https://jmsyst.com/libs/serializer
-
PHP libraries and tools
JMS Serializer: This library allows you to (de-)serialize data of any complexity. Currently, it supports XML and JSON.
-
Yet another Data-Transfer-Object package
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.
-
PHP foreach loop to XML
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.
-
Is there a better way to connect to an API?
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.
What are some alternatives?
PHP Architecture Tester - PHP Architecture Tester - Easy architecture testing for PHP :heavy_check_mark:
Fractal - Output complex, flexible, AJAX/RESTful data structures.
modular-laravel - Modular Laravel - Boilerplate project starter
JsonMapper - Map nested JSON structures onto PHP classes
phpstan-rules - 👓 Provides a composer package with rules for phpstan/phpstan.
data-transfer-object - Data transfer objects with batteries included
phpstan-magento - Magento specific extension for PHPStan
Ardent - A Collections library for PHP.
phparch
Arrayy - 🗃 Array manipulation library for PHP, called Arrayy!
GrumPHP - A PHP code-quality tool
CRUDlex - CRUDlex is an easy to use CRUD generator for Symfony 4 and Silex 2 which is great for auto generated admin pages