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

Autogenerated issue bodies for command exceptions #3527

Open
2 tasks done
ZacSharp opened this issue Jun 26, 2022 · 0 comments · May be fixed by #3557
Open
2 tasks done

Autogenerated issue bodies for command exceptions #3527

ZacSharp opened this issue Jun 26, 2022 · 0 comments · May be fixed by #3557
Labels
enhancement New feature or request

Comments

@ZacSharp
Copy link
Collaborator

Describe your suggestion

You can prefill new issues with parameters from the url and when a Baritone command throws an exception the ExampleBaritoneControl outputs a link to the GitHub issues tab. In that situation nearly all information requested by our bug template is easily available so we could use it to fill in and output an url like this template.
There's also the "issue forms" beta feature which allows creating forms (with dropdown selections, text fields, etc.), which can also be prefilled using url parameters and have the benefit of not needing to hardcode the issue template in the Baritone source code.
Alternatively we could just use their input validation to force users to input at least something without helping them with automatically collected information.

Context

Basically I'm tired of people opening variations of "an unhandled exception occured" or even "Please add a brief but descriptive title" with (nearly) no further information provided because they simply clicked on the link in the error message, then on "New issue" and "Submit new issue".

Problems

Duplicates.
The only reason why I haven't opened a pr on this right now is that I haven't found a solution on how to prevent duplicates. With this suggestion people don't even get to see the page where they would have to search, so there's a chance that even those that previously did search for duplicates won't do so anymore.
Since I don't think we want to do the check ourselves via the GitHub API, something like this would be feasible but probably not as effective and I'm not quite convinced it would be good enough for this suggestion to be a real improvement over the status quo.

Final checklist

  • I know how to properly use check boxes
  • I have not actively added any OwO's or UwU's to this issue.
@ZacSharp ZacSharp added the enhancement New feature or request label Jun 26, 2022
@wagyourtail wagyourtail linked a pull request Jul 12, 2022 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant