fix: add version command and arg

[bassco]

Closes #8

Adds a version command to the tool.

It would need to be manually updated in Application.swift before release.

[Mcrich23]

Hey! Thank you so much for submitting this PR.

I wonder if it would be better to do container-compose --version instead of container-compose version

[bassco]

--version is free from the Framework.
The version command is how upstream docker exposes the versions. Although they have the same value for both outputs.

 $ ./.build/arm64-apple-macosx/release/Container-Compose version
Container Compose version v0.5.1
$ ./.build/arm64-apple-macosx/release/Container-Compose --version
v0.5.1

$ docker compose version
Docker Compose version v2.23.0-desktop.1
$ docker compose --version
Docker Compose version v2.23.0-desktop.1

I've added a commit to allow for the output to be the same across both invocations.

[bassco]

I wonder if it would be better to do container-compose --version instead of container-compose version

You get both! 😄

Output is now:

$ ./.build/arm64-apple-macosx/release/Container-Compose version
container-compose version v0.5.1

$ ./.build/arm64-apple-macosx/release/Container-Compose --version
container-compose version v0.5.1

[Mcrich23]

Sounds good!

[Mcrich23]

I accidentally approved these changes. Please just fix the things i outlined above and then I will merge it

[AndrewBasson-Makersite]

Not quite following, you only want the --version output and to drop the version command?

[Mcrich23]

No both are great. I just want to keep tight access controls. There isn't a reason for the Version command to be accessible outside the module, so we don't need to make it public. Same for the commandName and version variables, but in that case they should be marked as private.

[bassco]

No both are great. I just want to keep tight access controls. There isn't a reason for the Version command to be accessible outside the module, so we don't need to make it public. Same for the commandName and version variables, but in that case they should be marked as private.

Setting the variables to be private - good call.
Version command changed to internal scope.

[Mcrich23]

Thank you so much for your effort. Just a few small nitpicks and then this can get merged.

[Mcrich23]

No both are great. I just want to keep tight access controls. There isn't a reason for the Version command to be accessible outside the module, so we don't need to make it public. Same for the commandName and version variables, but in that case they should be marked as private.

Setting the variables to be private - good call.

Version command changed to internal scope.

By default, objects are marked as internal, so we can actually not put an access control on the structure or its properties and it will automatically be internal.

[Mcrich23]

Somehow didn't finish the review before, so i'm just doing that

[bassco]

Somehow didn't finish the review before, so i'm just doing that

yeah, the github ui for the "double-submit" for review comments trips me up from time to time too.
Thanks for the scoping insights.

[Mcrich23]

Thank you for taking the time to scope it well.