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.
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
Add
pub struct Formatter
todefmt_decoder::log
. #781Add
pub struct Formatter
todefmt_decoder::log
. #781Changes from 10 commits
88e79db
f2faf16
2daf2c5
a060524
ce93caa
133594c
6ba4b29
cb63a91
da03a4b
7f394b5
52b2e3b
d524e43
44a6d1b
9fb5392
d48b739
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it makes sense to move all of the formatting logic to
Formatter
and pass aFormatter
instead toPrinter::new()
. What do you think?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking about that. But the Printer holds a reference to the record aka. the log frame. So you basically have one Printer per log frame, which makes sense because it uses this reference in almost all methods.
The Formatter should not keep a reference to the record, but just receive it for the method call.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The name
Printer
does not really make sense anymore. I thinkSingleRecordFormatter
would be the most correct, but maybe a bit bulky. But I'd like to pull the naming discussion out of this PR.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I have written as a
TODO
in code, I think theStdoutLogger
should use twoFormatters
instead of just storing two log_formats. So the hierachy would be:But I'd also like to do that in a separate PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I disagree, the purpose of
Printer
after this PR should not be to format, but to print. The only reason whySingleRecordFormatter
would make sense after this PR, is because you addedformat_frame
toPrinter
. I thinkformat_frame
should be the responsibility ofFormatter
.I agree, then in
print_frame
thePrinter
would just need to callYeah, I think that makes sense.