Yanick Witschi

I also think the "maintained package versions only" mode should become default in version 2 and instead of an `--include-non-maintained-versions` flag which would again load half of the Internet, exceptions...

## The additional "maintenance-exceptions" section > Instead of an extra section one could introduce special syntax for the version constraint: "some/package": "4.1.*!". Easier on my mind instead of scrolling around...

Yeah I guess my maintained approach is a paradigm shift and you guys are probably right about it being to aggressive. Even though I think it would be the correct...

Plus, it should do root dependency optimizations as explained earlier. So if I have ``` { "require": { "symfony/messenger": "4.3.*" } } ``` Then there sure is no need to...

I guess if we filter out everything that does not match our root requirements, the whole abandoned stuff would not be needed in the first place. I guess it would...

Thank you Jordi for taking the time to reply, highly appreciated :) I do understand your point of view but you know me: I still wanted to see what I...

@nicolas-grekas care to give https://github.com/composer/composer/pull/8275 a try? 😊

I like the idea, however, it won't work with nested entities of different types. What might work is some kind of mapper. So instead of `#type` you store `#mapKey` (or...

What do you think about by `typeMapping` solution? If that would solve your problem (and there are a few thumb ups so probably it would for others), why not make...

Should be doable, yes. Although we need to make sure it can still handle the nested ones for BC reasons. I don't feel like migrating all the old data 😄