DockerCLI/cli/command/task/testdata
Vincent Demeester 69fdd2a4ad
formatter package heavy refactoring
- make it possible to extract the formatter implementation from the
  "common" code, that way, the formatter package stays small
- extract some formatter into their own packages

This is essentially moving the "formatter" implementation of each type
in their respective packages. The *main* reason to do that, is to be
able to depend on `cli/command/formatter` without depending of the
implementation detail of the formatter. As of now, depending on
`cli/command/formatter` means we depend on `docker/docker/api/types`,
`docker/licensing`, … — that should not be the case. `formatter`
should hold the common code (or helpers) to easily create formatter,
not all formatter implementations.

Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2018-10-23 17:05:44 +02:00
..
task-context-write-table-custom.golden formatter package heavy refactoring 2018-10-23 17:05:44 +02:00
task-print-with-global-service.golden add unit tests to task package 2017-06-29 17:57:31 -04:00
task-print-with-indentation.golden Update stack and task command tests to new golden 2017-08-16 14:23:28 -04:00
task-print-with-no-trunc-option.golden add unit tests to task package 2017-06-29 17:57:31 -04:00
task-print-with-quiet-option.golden add unit tests to task package 2017-06-29 17:57:31 -04:00
task-print-with-replicated-service.golden add unit tests to task package 2017-06-29 17:57:31 -04:00
task-print-with-resolution.golden add unit tests to task package 2017-06-29 17:57:31 -04:00