Skip to content

compatible with the message output to stdout when stderr has no message #30

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.

Sign up for GitHub

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

Jump to bottom
Merged
huan merged 2 commits into from
Apr 20, 2022
Merged

compatible with the message output to stdout when stderr has no message #30

huan merged 2 commits into from
Apr 20, 2022

Conversation

@binsee
Copy link
Member

@binsee binsee commented Apr 20, 2022 •
edited
Loading

Fixes #29

@binsee binsee changed the title Binsee/issue29 compatible with the message output to stdout when stderr has no message Apr 20, 2022
@binsee binsee mentioned this pull request Apr 20, 2022
Closed
huan
huan approved these changes Apr 20, 2022
View reviewed changes
Copy link
Member

@huan huan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@huan huan merged commit 67b2522 into Chatie:main Apr 20, 2022
@binsee binsee deleted the binsee/issue29 branch April 24, 2022 16:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@huan huan huan approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

npm run lint may not output error messages when running errors

2 participants

@binsee @huan