Skip to content
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

More parsable format #4

Closed
kitagry opened this issue Jun 19, 2022 · 1 comment · Fixed by #5
Closed

More parsable format #4

kitagry opened this issue Jun 19, 2022 · 1 comment · Fixed by #5

Comments

@kitagry
Copy link
Contributor

kitagry commented Jun 19, 2022 •
edited

I think parsable error format is important to use some useful tools ex) reviewdog
For example,

$ golint
comment_iowriter.go:11:6: exported type CommentWriter should have comment or be unexported

I want some option which change error format, or default format should be changed.
If you like this idea, I'll create PR.
@hirosassa
Copy link
Owner

hirosassa commented Jun 19, 2022 •
edited

@kitagry
Thanks for your suggestion!
I agree with you.

default format should be changed

I prefer this idea.

If you like this idea, I'll create PR

Yeah, go ahead👍

@kitagry kitagry mentioned this issue Jun 23, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

More parsable message kitagry/bqvalid
2 participants
@hirosassa @kitagry