docs: --save option for the poly info, deps and libs commands (#21)

* docs: --save option for the poly info, deps and libs commands

* docs: configurable command output paths

Author: DavidVujic

docs/commands.md

@@ -255,6 +255,8 @@ poly info
 ### Options
 `--short` Display a view that is better adjusted to Workspaces with many projects.
 
+`--save` Store the contents of this command to file.
+
 ## Diff
 Shows what has changed since the most recent stable point in time.
 
@@ -367,6 +369,7 @@ The poly libs command will likely report the "cv2" as a missing dependency.
 
 Using `--alias opencv-python=cv2` will make the command treat the alias as a third-party import.
 
+`--save` Store the contents of this command to file.
 
 ## Check
 Validates the Polylith workspace, checking for any missing dependencies (bricks and third-party libraries):
@@ -514,6 +517,8 @@ Show brick depencencies for a specific project.
 `--brick`
 A detailed view for a single brick and the dependent bricks: used by, and uses.
 
+`--save` Store the contents of this command to file.
+
 ## Test
 Polylith doesn't have its own test runner. Use your favorite testing tool, such as `pytest`.
 

docs/configuration.md

@@ -52,3 +52,23 @@ When `brick_docs_enabeld = true`, a README is added when creating a component or
 
 ### Testing
 The create component and brick [commands](commands.md) will also create corresponding unit tests when `enabled = true` in the test section of the workspace configuration.
+
+
+### Custom command output path
+The `poly info`, `poly deps` and `poly libs` commands have support for a `--save` option.
+By default, the command output will be saved to `development/poly/<the command>.txt`.
+But you can configure it, if you want to store the output in a different location.
+
+Example configuration:
+
+``` toml
+[tool.polylith.commands]
+output = "somewhere/else"
+```
+
+Or, configure output location by command:
+
+``` toml
+[tool.polylith.commands.deps]
+output = "somewhere/else"
+```