Skip to content

feat(poly deps, info, libs): save contents to file command option - #372

Merged
DavidVujic merged 17 commits into
mainfrom
poly-command-output-to-file
Aug 31, 2025
Merged

DavidVujic merged 17 commits into
mainfrom
poly-command-output-to-file

Conversation

@DavidVujic

@DavidVujic DavidVujic commented Aug 24, 2025 •

Copy link
Copy Markdown
Owner

Description

Adding a --save option to the poly deps, poly info and poly libs commands. In addition to printing the output (as before) a file will be saved with the contents of the output.

The location is by default in development/poly/<command name>.txt, but is configurable.

Motivation and Context

Saving the result from the deps, info and libs commands is useful during Pull Requests, when reviewing code. Besides the code diff, the changes in saved commands will give the reviewer an overview of the changes such as coupling and dependency changes.

The idea comes from the discussion #365

How Has This Been Tested?

✅ CI
✅ Local run of commands with the new --save option
✅ unit test

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

@DavidVujic DavidVujic changed the title Poly command output to file feat(poly deps, info, libs): save contents to file command option Aug 31, 2025
@sonarqubecloud

Copy link
Copy Markdown

@DavidVujic
DavidVujic marked this pull request as ready for review August 31, 2025 12:05
@DavidVujic
DavidVujic merged commit cdfc820 into main Aug 31, 2025
4 checks passed
@DavidVujic
DavidVujic deleted the poly-command-output-to-file branch August 31, 2025 12:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant