-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
How can we make the issue tracker useful? #22632
Comments
One idea: Have "digest" issues that people can subscribe to or comment on so that a) more discussion occurs in centralized locations and b) interested parties can subscribe to notifications to packages they like. Example mockup https://github.com/RyanCavanaugh/DefinitelyTyped/issues/1 |
Worth a try - anything is better than the current quagmire! |
I'm available for issue tracking. Reach me if I can help. Another thing that could help, is find a way to reestructure the types directory, because it has thousands of directories, and it's kinda annoying listing it on github or making contributions. |
A common question/request is asking for adding a new package. i think for these, we should direct users to creating a new PR with a pointer to https://github.com/Microsoft/dts-gen. |
Excellent idea @mhegazy! |
Another idea: write messages on console, asking for people share new typings for missing modules, after installing some
There's a way to create a "PR cli", enabling users to create typings directly from files? I don't know, suppose that I have a |
That’s a great idea, most of us if not all of us have a declarations.ts file in our src folder where we stub out definitions for libraries that don’t have official definitions. Would be great if we could take advantage of this. |
I'd propose writing down some goals and taking small steps: Goals
Steps
|
Hi thread, we're moving DefinitelyTyped to use GitHub Discussions for conversations the To help with the transition, we're closing all issues which haven't had activity in the last 6 months, which includes this issue. If you think closing this issue is a mistake, please pop into the TypeScript Community Discord and mention the issue in the |
We're currently sitting at 1,809 open issues, a number which hasn't really ever been useful to think about. The issue tracker seems to have three kinds of bugs:
As far as I can tell, no one is taking specific action on anything here. The oldest bugs are years old.
Feedback we've heard from contributors is that it's hard to "listen" for discussion or bugs related to .d.ts files they've worked on. And as we can see from the issue tracker, people who don't know how to contribute fixes aren't really getting results from filing issues on the issue tracker.
What would a useful DefinitelyTyped issue tracker look like?
The text was updated successfully, but these errors were encountered: