Paulo Ribeiro 55cdb6dcd0 Add a check for size field in custom format string ... This fix addresses an issue where including the `{{.Size}}` format field in conjunction with `docker ps --format`, without the `--size` flag, would not correctly display the size of containers. This is done by doing a check on the custom format string, and setting the size flag on the options struct if the field is found. This struct gets passed to the engine API which then generates the correct query. An integration test is included which runs `docker ps --format "table {{.Size}}"` without `--size`, and checks that the returned output is not `0 B`. Fixes #21991 As suggested by @cpuguy83, a parser is implemented to process the format string as a template, and then traverses the template tree to determine if `.Size` was called. This was then reworked by making use of template execution with a pre-processor struct that will set the `--size` option if the template calls for the field. The pre-processor now also sets a boolean in the context passed to the writer. There is an integration test for this that calls `docker ps --size --format "{{.Size}}"` and then checks that `size: {{.Size}}` is not appended, as it would with previous behavior. Finally, a change was made to the formatter to not automatically add a `{{.Size}}` if a custom format is provided. Signed-off-by: Paulo Ribeiro <paigr.io@gmail.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl>		2016-06-03 21:59:10 +02:00
..
custom.go	do not trim one char from {{.Names}} each time it is used in --format	2016-04-06 11:04:13 -07:00
custom_test.go	Try to fix #20942 TestContainerPsContext unit test	2016-03-04 14:20:41 +01:00
formatter.go	Add a check for size field in custom format string	2016-06-03 21:59:10 +02:00
formatter_test.go	Add a check for size field in custom format string	2016-06-03 21:59:10 +02:00