Closed mgaitan closed 1 year ago
Hello there! Thank you for reporting this issue. Can you have a look at the PR and see if this resolves your issue?
@derlin thanks for working on a fix. I'm a python developer and my knowledge of the kotlin ecosystem is really limited. The patch seems trivial and I can interpret it as semantically correct, but I don't know really how to compile/test it. Is there a jar file including that change available?
Anyway, if your fix solves my original example I guess it's done then.
Consider this compose file with a ports definition in extended format
It's a valid file as you can see
However, the app fails parsing the
published
port as a stirng value.If I change the value as a integer it works, but a string is the normalized value (according to the spec) as it could be a port range. Thus
docker compose config
generates it a string. (see #9 )