Cover of the book Symfony 5: The Fast Track

Symfony 5: The Fast Track is the best book to learn modern Symfony development, from zero to production. +300 pages showcasing Symfony with Docker, APIs, queues & async tasks, Webpack, SPAs, etc.

New in Symfony 3.4: Deprecate configuration options

Contributed by
in #22382.

Symfony project follows the semantic versioning strategy and a backward compatibility promise to ensure smooth upgrades of your projects. The main piece of this strategy are the deprecation messages, which warn you when using features that will be removed or changed in the next major Symfony version.

Deprecations are not only important for code changes. When using semantic configuration in your applications, it's also important to warn users about any future change in the config options. That's why in Symfony 3.4 we added a feature to simplify the deprecation of config nodes:

// ...
    // this outputs the following generic deprecation message:
    // The child node "config_option_1" at path "acme_root" is deprecated.
    // you can also pass a custom deprecation message (%node% and %path% placeholders are available):
    ->setDeprecated('The "%node%" option is deprecated. Use "new_config_option" instead.')
Help the Symfony project!

As with any Open-Source project, contributing code or documentation is the most common way to help, but we also have a wide range of sponsoring opportunities.

New in Symfony 3.4: Deprecate configuration options

Tweet this


This will be useful. Thanks.
Thank you 👍🏻
Awesome \o/

Comments are closed.

To ensure that comments stay relevant, they are closed for old posts.