Skip to content

Add 'not a request for a utility type' to the feature issue template #55746

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

Merged
merged 3 commits into from
Nov 2, 2023

Conversation

jakebailey
Copy link
Member

Please do bikeshed the wording, but I think we should probably have a checklist item for this given a non-trivial amount of asks for this which we immediately decline unless it's paired with some other need.

@fatcerberus
Copy link

fatcerberus commented Sep 15, 2023

I probably laughed harder at the title of this PR than I want to admit. 😄 It's definitely true, asks for new utility types are right up there with 9998 dupes and bug reports about type narrowing not working for dynamically keyed objects.

And yeah, there should probably be a contributor FAQ for this kind of thing (assuming there isn't already). It's like how people aren't supposed to submit typo fixes, it doesn't really seem to be documented except in other issues and maybe the issue template, so the usual recourse is just to dupe to a random rejected issue of the same type, which isn't really an ideal way to communicate policy.

@RyanCavanaugh RyanCavanaugh merged commit cf73e5a into microsoft:main Nov 2, 2023
@jakebailey jakebailey deleted the utility-type-request branch November 16, 2023 00:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Author: Team For Uncommitted Bug PR for untriaged, rejected, closed or missing bug
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants