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

Add ticks around error messages more consistently #3004

Merged
merged 1 commit into from
Apr 22, 2024
Merged

Conversation

charliermarsh
Copy link
Member

Summary

I found some of these too bare (e.g., when they just show a package name with no other information). For me, this makes it easier to differentiate error message copy from data. But open to other opinions. Take a look at the fixture changes and LMK!

@charliermarsh charliermarsh added the error messages Messaging when something goes wrong label Apr 12, 2024
@charliermarsh charliermarsh marked this pull request as ready for review April 12, 2024 00:42
@konstin
Copy link
Member

konstin commented Apr 12, 2024

Style-wise my favorite would be any quotes (backticks count) and no colon

@charliermarsh charliermarsh enabled auto-merge (squash) April 22, 2024 23:53
@charliermarsh charliermarsh merged commit 14f05f2 into main Apr 22, 2024
39 checks passed
@charliermarsh charliermarsh deleted the charlie/ticks branch April 22, 2024 23:58
konstin added a commit that referenced this pull request Apr 23, 2024
Mostly a small refactor, adds backticks to be coherent with #3004.
konstin added a commit that referenced this pull request Apr 23, 2024
Mostly a small refactor, adds backticks to be coherent with #3004.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
error messages Messaging when something goes wrong
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants