Allow file output directly from cli #2625
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## main #2625 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 163 163
Lines 11904 11915 +11
=========================================
+ Hits 11904 11915 +11
Continue to review full report at Codecov.
|
barrywhart
approved these changes
Feb 13, 2022
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This resolves #2244 and provides a clean solution to sqlfluff/sqlfluff-github-actions#15.
This adds a
--write-outputto thelintandparsecommands so that the commands can write directly to file. In the case that file output is enabled, the stdout logging is re-enabled so that the user can get e.g. yaml output to file and still get human output to stdout.