Skip to content

Friendlier error messages #275

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

Closed
2 of 4 tasks
finnp opened this issue Feb 13, 2018 · 1 comment
Closed
2 of 4 tasks

Friendlier error messages #275

finnp opened this issue Feb 13, 2018 · 1 comment

Comments

@finnp
Copy link

finnp commented Feb 13, 2018

Is there a way to make the error messages friendlier?

Expected Behavior

I expected the lint error messages to be friendly or at least a possibility to make them friendly. Friendly meaning: Someone who doesn't know about the convention will see information how to fix their commit message.

Current Behavior

Here's an example of the error message:

⧗   input: lel
✖   message may not be empty [subject-empty]
✖   type may not be empty [type-empty]
✖   found 2 problems, 0 warnings

It doesn't explain what a type or a message is. I expected it to do that.

Affected packages

  • cli
  • core
  • prompt
  • config-conventional

Possible Solution

Maybe there is a way to configure the output? Or generally make this easier for people to understand.

Context

I'm trying to make sure, coworkers who create a pull request on a specific repository will be informed about the commit message convention when trying to contribute. In a non-confusing way.

@marionebl
Copy link
Contributor

Thanks for reporting. Duplicate of #206, so I am closing this. Please chime in there if you have additional input.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants