fix: docker-compose file decoding

[n1ru4l]

Closes #183

[n1ru4l]

@erikengervall Let me know what you think :)

[n1ru4l]

@erikengervall ping :)

[erikengervall]

@erikengervall Let me know what you think :)

Sorry for the late reply - been a busy few weeks 🙂

I'll take a look tonight! 🙌

[erikengervall]

Ran the unit tests as a sanity check and it produces these changes for me locally:

I'm running docker desktop 2.4.0.0

Perhaps we should update the snapshots to the most recent version? WDYT?

[n1ru4l]

@erikengervall yes! I actually thought that I did update them already 😅

[n1ru4l]

It seems like the port format got reverted to in 1.27.4: docker/compose@1.27.3...1.27.4 (https://docs.docker.com/compose/release-notes/#1274)

I would stay we should steel keep the decoding, as it gives another layer of confidence. Please let me know what you think!

[n1ru4l]

@erikengervall Any ideas what's wrong with the unit tests? Some checks are not reported but required? I would love to see this merged quickly! Gonna pick up and finish #167 afterwards 🙂

[erikengervall]

@erikengervall Any ideas what's wrong with the unit tests? Some checks are not reported but required? I would love to see this merged quickly! Gonna pick up and finish #167 afterwards 🙂

I'll take a look when I get home later today :)

[erikengervall]

@erikengervall Any ideas what's wrong with the unit tests? Some checks are not reported but required? I would love to see this merged quickly! Gonna pick up and finish #167 afterwards 🙂

I'll take a look when I get home later today :)

Alright idk why GitHub Actions are acting up, the tests are seemingly passing and I've tried running them locally with the most recent changes.

I'll merge this and create a new release 🙂

[erikengervall]

@n1ru4l changes included in 2.1.0 🙂