Wouter de Jong

Ok, let's go with an enum option with these conditions (maybe worth calling the middle one `account_status` to be super clear on what errors are exposed). I guess the easiest...

We used to say that Symfony components deserve their own exception hierarchy for runtime exceptions, but not for logic exceptions. The reason being that the latter are a logic error...

Friendly ping @nicolas-grekas The release is out now, but we're still lacking the docs for this big change. Do you have any time, once the conference is over, to write...

I agree with @stof here. We decided against using PHPdoc types that do not represent the 100% use-case, even if it improves the experience for 95% There is no guarantee...

Implementations of this interface will get static analysis errors if they don't guarantee a correct return object type if a class FQCN is passed. That's a regression from the current...

That's a very good point. All static analysers are using our XML dump of the container, which we make specifically for this use-case: mapping magic service ID strings to PHP...

You did it!! This was a massive effort. Thanks a lot @xabbuh! :green_heart:

> Is this true for all parts of the config? Not to all parts, and some parts behave differently. We don't merge configuration from `security.role_hierarchy` and `security.password_hashers`, and we don't...

This is a great feature! And one that was desperately missing in Symfony, I've had lots of DI configuration debugging sessions to make this work in applications before. @HypeMC I'm...

If I'm reading @stof comment correctly, Symfony 7.4 should support FrankenPHP out of the box. So I suspect nothing to be done on this topic. But give it a try...