chore: Remove template file copy verbose logs #9409
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 ReportAll modified and coverable lines are covered by tests ✅
📢 Thoughts on this report? Let us know! |
yufeih
pushed a commit
that referenced
this pull request
Nov 13, 2023
chore: remove template file copy verbose logs
p-kostov
pushed a commit
to ErpNetDocs/docfx
that referenced
this pull request
Jun 28, 2024
chore: remove template file copy verbose logs
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.
What's included in this PR
Background
When running
docfx buildcommand with--logLevel Verbose.Too much logs are written relating to template files copy.
Example:
These logs are less important to build document process logging.
And not consistent compared to other file output processing. (e.g. Output HTML files is not logged)
So I've remove these logs in this PR.
I thought these logs should be logged as
Debuglevel. (Currently not supported)And it can be filtered by category with customizable configurations (By using
Microsoft.Extensions.Logging)