You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has the disadvantage of leaving the interpretation of the output to the user, leading in a lot of boilerplate code that all users of docker-compose have to write. Instead it would be better to provide more introspective into the result by typing it:
export interface IDockerComposeResult<T> {
exitCode: number | null;
out: string;
err: string;
result: T | null;
}
This should be given for every mapped subcommand of docker-compose. An example for the port subcommand:
The current implementation exposes very low-level information on the result of a command with the interface
This has the disadvantage of leaving the interpretation of the output to the user, leading in a lot of boilerplate code that all users of docker-compose have to write. Instead it would be better to provide more introspective into the result by typing it:
This should be given for every mapped subcommand of docker-compose. An example for the
port
subcommand:If an error occurs, the result should be null, since the error output will already be present in the
err
key.We should use github's project to track, which subcommands have already been enhanced.
Originally posted by @stefanmeschke in #52 (comment)
The text was updated successfully, but these errors were encountered: