fix: correct field filtering logic in writeFields #680
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.
ConsoleWriter.Write
processes custom fields specified inPartsOrder
to output only their values instead of the key-value pairs. In practice:Actual output:
The field
k1
is duplicated, and the expected output is:This is due to a bug in
ConsoleWrite.writeFields
where it filters fields based on the defaultPartsOrder
rather than the currentPartsOrder
.