Eric Hripko

Hi @Download 👋 Thank you for sharing this feedback. Please note that the recommendation for Compose file names does not automatically apply to all YAML files. The files you highlighted...

That's a very interesting idea - thank you for suggesting it @avgas3 👍

I am quite new to this discussion, so apologies if this was brought up before (couldn't pinpoint this aspect of discussion after reading through the linked thread). The use cases...

Hi @pchico83 👋 Thank you for suggesting this idea! This is potentially a rather big breaking change, since it makes service names more restrictive. What's more, there's at least one...

> However, this is incompatible with most other common .env format specifications, which usually will use quotes to appropriately escape strings, and thus allow for multi-line strings. Could you please...

It appears that `compose-go` library currently rolls it's [own parser](https://github.com/compose-spec/compose-go/blob/3eee68c9fd46f0b8bcc594f582d09515f9966d5a/envfile/envfile.go) while `docker-compose` indeed uses [dotenv](https://github.com/docker/compose/blob/b01601a53cc8839afbe332f00d0d1b8165012e7b/compose/config/environment.py#L38). It does look like there's a need to define this behaviour better - otherwise, we...

Hi @SoerenHenning and thank you for sharing this feedback 👍 From what I can see, it is correct that [scale is a number](https://github.com/compose-spec/compose-spec/blob/master/spec.md#scale). Could it be that the VS Code...

@AkihiroSuda could you please bring your branch/PR up to date with the base branch? This will enable us to land this.

Lovely, thank you very much 👍

Thanks for submitting the issue - I've got a quick question. It appears that the spec already defines these as `string` types - what is the difference in UX for...