Indeed, the other way to fix my DX issue here would be to add a second parameter to all() method to manage default values. I can do it aswell, tell me which way you prefer.

I'd prefer to avoid adding a new method.

@fabpot I updated all method to handle default value if provided.

Honestly, I don't see why we should add an API for this when there is already a language construct for it...

all($key, $default)
vs
all($key) ?: $default

better learn the language than a specific API, this makes it easier for everyone, readers and writters.

Honestly, I don't see why we should add an API for this when there is already a language construct for it...

all($key, $default)
vs
all($key) ?: $default

better learn the language than a specific API, this makes it easier for everyone, readers and writters.

@nicolas-grekas It's more about consistency than learn a language, all getters in ParameterBag has a default parameter to handle this behavior that's why I think it's better to keep it the same way there.

It's more about consistency than learn a language, all getters in ParameterBag has a default parameter to handle this behavior that's why I think it's better to keep it the same way there.

mmm, I'm not convinced. All the other methods return single items. all() returns a collection of items. There's no need for consistency here, these are two different beasts.

BTW, the $default arguments were added before the ?: and ?? operators existed. Not sure we would add them if we were to design this again from scratch now (I'm not suggesting deprecating them either - the cost would be too high for too little gain.)

I tend to agree with @nicolas-grekas arguments. Let's close. Thanks for the discussion.