Skip to content
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

--to-file option: Explain difference between this option and redirection #672

Open
rsenden opened this issue Jan 26, 2025 · 0 comments
Open
Labels
effort:low Easy to implement/fix enhancement New feature or request fcli-core Generic fcli issues that affect multiple modules prio:low Low priority; nice to have but minimal impact

Comments

@rsenden
Copy link
Contributor

rsenden commented Jan 26, 2025

Enhancement Request

The --to-file option writes pure command output to the given file; any progress messages will still be written to the console. With redirection, both progress messages and pure command output may be written to the same file. For structured output formats like JSON or YAML, such redirected progress messages will break the structured output format syntax.

@rsenden rsenden added effort:low Easy to implement/fix enhancement New feature or request fcli-core Generic fcli issues that affect multiple modules prio:low Low priority; nice to have but minimal impact labels Jan 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort:low Easy to implement/fix enhancement New feature or request fcli-core Generic fcli issues that affect multiple modules prio:low Low priority; nice to have but minimal impact
Projects
None yet
Development

No branches or pull requests

1 participant