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

UX: On errors, print out command we think they should have run #203

Open
str4d opened this issue Feb 6, 2021 · 1 comment
Open

UX: On errors, print out command we think they should have run #203

str4d opened this issue Feb 6, 2021 · 1 comment

Comments

@str4d
Copy link
Owner

str4d commented Feb 6, 2021

If we are pretty certain we know what they meant, suggest it.

@str4d str4d added this to the rage 0.8.0 milestone Mar 16, 2022
@str4d str4d modified the milestones: rage 0.8.0, rage 0.9.0 Apr 30, 2022
@str4d str4d modified the milestones: rage 0.9.0, rage 0.10.0 Oct 26, 2022
@str4d str4d modified the milestones: rage 0.10.0, rage 0.11.0 Jan 25, 2024
@str4d
Copy link
Owner Author

str4d commented Sep 4, 2024

Kicking this out yet another release. The main blocker here is going through and compiling a list of which errors we think have trivial solutions, and then writing up the copy for them.

@str4d str4d removed this from the rage 0.11.0 milestone Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant