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

Consistent use of language in output #598

Open
Xophmeister opened this issue Aug 17, 2023 · 0 comments
Open

Consistent use of language in output #598

Xophmeister opened this issue Aug 17, 2023 · 0 comments
Labels
epic: usability-end-users Relates to the usability of Topiary for endusers to use Topiary as a generic "good enough" formatter good first issue Good for newcomers P3 minor: not priorized type: feature request

Comments

@Xophmeister
Copy link
Member

Is your feature request related to a problem? Please describe.
Topiary's human-readable output -- log messages, errors, etc. -- is not especially consistent. For example:

$ for x in "cannot" "can't" "could not" "couldn't"; do
>   find . -name "*.rs" -exec grep -chiF "${x}" {} \+ \
>   | awk -v x="${x}" '{t += $0} END {print x, t}'
> done
cannot 10
can't 4
could not 20
couldn't 0

Describe the solution you'd like
Consistent use of language.

Describe alternatives you've considered
Being less pedantic 😉

@Xophmeister Xophmeister added good first issue Good for newcomers P3 minor: not priorized type: feature request labels Aug 17, 2023
@ErinvanderVeen ErinvanderVeen added the epic: usability-end-users Relates to the usability of Topiary for endusers to use Topiary as a generic "good enough" formatter label Sep 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic: usability-end-users Relates to the usability of Topiary for endusers to use Topiary as a generic "good enough" formatter good first issue Good for newcomers P3 minor: not priorized type: feature request
Projects
None yet
Development

No branches or pull requests

2 participants