I am not sure, but this sounds like a bug to me 🧐 it should not matter in which order you define your services.

@nicolas-grekas can you please give your opinion on this? Thanks

The last comment of the default services.yaml already explains this.

Indeed 👍

# add more service definitions when explicit configuration is needed# please note that last definitions always *replace* previous ones

Well I didn't have this comment in my default one 😕

But I still think this comment is also not explicit enough because it's not really clear that the service would be replaced byApp: because they don'texplicitly have the same name and it takes some brainstorming to understand thatApp: is in fact creating one service for each of it's matched files in it's place (one of which having the same name as a previously defined service)

@Tofandel thanks for this contribution. However, instead of adding this message in one of the many articles that show service config, we've decided to add that message in the main article about service config. That's why we've created#17385 to replace this PR.

But your PR was great because it made us rethink about this. Thanks!