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

Improve new issue template selection - reorder and handle "this is crash" check better #58052

Closed
1 task done
rubiesonthesky opened this issue Apr 3, 2024 · 3 comments
Closed
1 task done

Comments

@rubiesonthesky
Copy link

Acknowledgement

  • I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

Comment

I propose that templates would be reordered so that "Types not correct in/with callback" would be first one. It may first feel unnecessary to have it as first but I think it would get people to use it more when it's applicable. -> Meaning those could be handled quickly differently

About "Bug report", I think it would be good to separate compiler / language server crash to different template than the other problems. Or alternatively, improve "This is crash" text to make it clear that what it means. Now so many type error issues are flagged as "this is crash" because people do not understand what it means. :)

@RyanCavanaugh
Copy link
Member

I'm pretty happy with the templates as-is

@fatcerberus
Copy link

Types not correct in/with callback
get people to use it more when it's applicable

The whole point of that template is that it's never applicable - it only exists to tell you that the behavior it describes (which people tend to assume is a bug) is by design/design limitation and you shouldn't post the issue at all because it will just be duped to #9998.

@rubiesonthesky
Copy link
Author

Types not correct in/with callback
get people to use it more when it's applicable

The whole point of that template is that it's never applicable - it only exists to tell you that the behavior it describes (which people tend to assume is a bug) is by design/design limitation and you shouldn't post the issue at all because it will just be duped to #9998.

Well, that is what I kinda mean. When you start by that you will filter a lot issues that will not be even created then :D that side, I don’t think that this has been really a problem because those gets closed quickly.

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

3 participants