As of Composer 2.5.5, `composer config` JSON-encodes boolean values

So you did option 2. I don't think we can expect calling code to keep up with Composer changes. otherwise they would have to update for any changes like this

I would be in favor of 4

I think that it makes sense to continue to expect the calling code to know the "shape" of the value. In this case, the callers know that it's either a boolean (in ComposerSettingsValidator), or a boolean|array (ComposerPluginsValidator). They know what they need, so it makes sense that they should be expected to normalize it.

Looks good if tests pass!

Woah that is unexpected! But … it makes things more consistent in the future, so yay!

What am I'm missing here is a @todo to remove the helper once 2.5.5 is required. 📌 Add @todo for reverting a work-around once Composer 2.5.5 is required Fixed did that too for the other place where we have a <2.5.5-specific work-around.

Bump for #11.

Do we still need this to be open? We now require 2.5.5 at a minimum, and have removed all workarounds, as far as I know.

📌 Drop support for Composer 2.2, require Composer >=2.5.5 Fixed indeed made this obsolete on May 26, which was accelerated due to other circumstances.

It's just that for 1.5 month we should have done #11, but bridge under the water! 👍

Automatically closed - issue fixed for 2 weeks with no activity.