Christophe Coevoet

I think we should be less strict about forbidding settings that don't apply to a given handler type, to make it easier to change the handler type when merging config.

@dlmanning this issue should be closed as this has been solved in version 6.0

@tgalopin what happen to the doctype when sanitizing a document ? Is it preserved ?

@tgalopin when sanitizing a whole document, it is part of the document. If the input has it, it would be great if the output could preserve it as well.

Another bonus point: once we have the infrastructure to read `url_generating_routes.php`, we might report a deprecation (based on integration with phpstan-deprecation-rules probably) when generating a URL for a name that...

Well, webpack is able to target both of course. Encore is about adding a configuration layer on top of it, and this layer managing part of the config for you...

given that the ORM currently does not allow registering custom boolean functions for instance (see the list of `Configuration::addCustom*Function` methods), adding an explicit cast in StringType could actually break some...

PasswordAuthenticatedUserInterface stores the password **hash**, not the plaintext password, so there is no way to apply the validation constraint there.

@justin-oh there is a way to make the hashing automatic: https://symfony.com/doc/current/reference/forms/types/password.html#hash-property-path Validating automatically for strength would still require an opt-in (as not all projects will want to use this validator...

The difference is that `_locale` exists since the beginning of Symfony. A better example might be to look at how we handled `_fragment`. I'm almost sure we added it later.