-
Notifications
You must be signed in to change notification settings - Fork 218
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
feat: Change concurrent log to sequential log #679
Conversation
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.
Thanks for your contribution, it looks good!
Could you just add a simple test?
Sure, I'll give it a try! |
@koji-1009 there seems to be a test failing in this PR |
I'm sorry! I had unintentionally changed the label flag to |
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.
Lgtm, thanks for your contribution!
Description
issue #668
Improvements
melos analyse
log so that the output is the same when the-c
option is specified as when it is not specified.The
String? group
property is added for grouping when logging output. In the case of-c 1
, this option is not needed. (Log output is done sequentially.) In the case of-c 2
, all logs are output after the process is complete.Existing buffer-flush was deprecated, so it was named group-buffer for convenience. If that is not good, please point it out. Thanks for the useful tools.
no issue case
main branch log
this branch log
find issue case
main branch log
this branch log
Type of Change
feat
-- New feature (non-breaking change which adds functionality)fix
-- Bug fix (non-breaking change which fixes an issue)!
-- Breaking change (fix or feature that would cause existing functionality to change)refactor
-- Code refactorci
-- Build configuration changedocs
-- Documentationchore
-- Chore