👍

To keep BC, I would keep thecanBeUnset() call as well.

@fabpot in case someone uses the FrameworkBundle'sConfiguration class and check if keys exist ?
OtherwisecanBeEnabled threatfalse so it should not change anything to the actual configurations.

@Ener-Getick I know that the BC break would be small, but as it does not cost us anything to not break BC, I prefer to.

@fabpot well having both options wouldn't change theConfiguration output.
(allowFalse is checked afterequivalentValues, seehere).
The only thing changing would be thatArrayNode::setAllowFalse() would be called. Is this what you want ?

ok, fair enough, 👍

Thank you @Ener-Getick.

You're welcome :-)

And I see one solution to keepcanBeUnset but I don't know if that's not durty...

->arrayNode()    ->canBeEnabled()    ->canBeUnset()    ->threatFalseLike(false)