symfony/http-kernel

This system is a PHP web framework component that manages the full lifecycle of HTTP requests, from routing and controller resolution to response generation and caching. It provides a modern, attribute-driven approach to handling request data, exceptions, and event listeners, while offering robust tools for debugging, profiling, and cache management. The architecture emphasizes decoupling and extensibility through dedicated interfaces and a comprehensive set of value resolvers and data collectors.

This period focused on the major upgrade to Symfony 8.0, characterized by extensive internal refactoring and the removal of legacy code. Key changes include the introduction of PHP 8 attributes for controller and request mapping, the separation of HttpKernel responsibilities into dedicated classes, and the modernization of caching, logging, and profiling systems.

16 changes

This period focused on expanding unit test coverage for the HttpKernel component, including its cache, controller, and event listener subsystems. Additionally, new debug and profiling utilities were introduced to enhance error handling and request tracing capabilities.

14 changes

This period focused on modernizing the HttpKernel's controller argument resolution by introducing a comprehensive, attribute-driven value resolver system and a new ControllerMetadata component for structured type information. Concurrently, the fragment rendering architecture was refactored to support multiple rendering strategies through a unified interface, accompanied by extensive test coverage for both the new resolvers and the existing exception and logging components.

13 changes

This period focused on introducing a suite of new PHP attributes to the HttpKernel component, enabling declarative configuration for controllers and their arguments. The work included implementing features like cache headers, rate limiting, and request mapping, supported by comprehensive unit tests and test fixtures.

5 changes

symfony/http-kernel was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.