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.

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

Output is implementation focused, not human focused #303

Open
epage opened this issue Jan 20, 2023 · 0 comments
Open

Output is implementation focused, not human focused #303

epage opened this issue Jan 20, 2023 · 0 comments
Labels
C-enhancement Category: raise the bar on expectations

Comments

@epage
Copy link
Collaborator

epage commented Jan 20, 2023

Describe your use case

I ran cargo semver-checks on my project (#296) and had a hard time looking through the results

  • Issues related to an API item were scattered by which check they fell into
  • I could easily skim the results to find something I was looking for because they were organized by check
  • The most relevant details don't stand out and are lost in the noise

Describe the solution you'd like

  • Sort the lints by one of
    • (idea) API path, file, line, check
    • file, line, check
  • Format each message in a more traditional diagnostic format, whether brief or long

Alternatives, if applicable

No response

Additional Context

No response

@epage epage added the C-enhancement Category: raise the bar on expectations label Jan 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement Category: raise the bar on expectations
Projects
None yet
Development

No branches or pull requests

1 participant