Symfony 7.2: What's New, Release History & Support Lifecycle

What Is New in Symfony 7.2

Symfony 7.2 brings a focused set of enhancements and new features, primarily improving developer experience for HTTP interactions, console commands, and service configuration. The release continues the framework's modernization efforts with useful attributes and quality-of-life improvements.

How does Symfony 7.2 improve mapping HTTP query parameters?

The new #[MapQueryParameter] attribute is a game-changer for controller methods. It lets you automatically map individual query string parameters to typed arguments, eliminating the need to manually fetch from the request bag.

You can define optional defaults, apply PHP type casting, and even handle arrays with a specific format. This makes controller signatures more explicit and your code cleaner by leveraging Symfony's argument resolvers.

public function index(
    #[MapQueryParameter]
    string $q = '',
    #[MapQueryParameter]
    int $page = 1,
    #[MapQueryParameter('filters', filter: FILTER_VALIDATE_BOOL)]
    array $filters = []
) {}

What console command enhancements were added?

Symfony 7.2 introduces autocompletion for command arguments, not just options. When you define a #[AsCommand] attribute, you can now implement the CompleteInterface to provide suggested values for any argument, improving the CLI experience.

The CommandTester class also gets a new assertCommandIsSuccessful() helper. This provides a more readable and intuitive way to write tests for your console commands compared to checking the status code manually.

// In your command's configure() method
$this->addArgument('branch', InputArgument::REQUIRED);

// Then implement CompleteInterface
public function complete(CompletionInput $input, CompletionSuggestions $suggestions): void
{
    if ($input->mustSuggestArgumentValuesFor('branch')) {
        $suggestions->suggestValues(['main', 'next', 'wip']);
    }
}

Are there new interfaces for modern PHP practices?

Yes, a new LazyEventDispatcherInterface has been added. This interface extends the core event dispatcher and is designed for use with lazy event listeners. It signals that the dispatcher can handle the proxying logic required for lazy-loaded services.

In practice, this is an internal improvement that solidifies the contract for dependency injection containers when dealing with event listeners marked as lazy. It ensures better integration and clarity within the service layer.

What HttpClient improvements should I know about?

The HttpClient component received practical additions. The toArray() and toArray() methods now accept a throw parameter. This gives you finer control over error handling when decoding JSON responses, allowing you to choose between getting a null value or throwing an exception on bad data.

Additionally, the TraceableHttpClient now provides the total number of requests made during a trace via a getTracedRequestsCount() method, which is useful for profiling and debugging.

$response = $client->request('GET', '...');
// Decode JSON, but don't throw on invalid JSON
$data = $response->toArray(throw: false);

What new constraints and utilities are available?

A new Number constraint has been introduced to validate that a value is a numerically valid string. It's more flexible than Type constraint for strings that represent numbers and complements the existing Range constraint.

The Uid component gets static factory methods like Uid::fromString(), Uuid::fromString(), and Ulid::fromString(). These provide a more object-oriented and unified way to instantiate UID objects compared to using constructors directly.

use Symfony\Component\Validator\Constraints\Number;
// Validates strings like "12.5", "-100", "1.2e3"
#[Number]
private string $numericString;