-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rm for single container #111
Comments
Did you try putting the service name at the last entry of Would you mind sending a PR including a test?
Maybe it might make sense to allow 1..n @Steveb-p Thoughts/Comments? |
Sure, why not. export const rm = function (options?: IDockerComposeOptions, ...services: string[]): Promise<IDockerComposeResult>; or export const rm = function (options?: IDockerComposeOptions, services: string | string[]): Promise<IDockerComposeResult>; or export const rm = function (options?: IDockerComposeOptions, services: string[]): Promise<IDockerComposeResult>; depending on your preference. Destructuring seems more |
No, this not expected behavior Maybe?
@Steveb-p suggested a more flexible solution. |
I would prefer the destructuring approach. |
There were not tests against |
@Steveb-p thanks for your PR. 📦 docker-compose@0.23.4 is released on npm. |
Hi!
Usage rm:
rm [options] [SERVICE...]
Why not?
The text was updated successfully, but these errors were encountered: