-
Notifications
You must be signed in to change notification settings - Fork 393
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
Validate if work is needed for closed TODO issues #4061
Comments
I've pushed a branch, todone, which adds a comment If you don't want to search the codebase yourself, you can run |
This list was generated from the todone branch using |
That's an error output; running eslint caused the node process to crash. I'm not sure why that would happen; you may want to re-install your dependencies and try again: In any case, it turns out that I had not actually committed the "TODOne" comments before, but now I have! 🚀 |
Here's a list of all the current TODOs in published packages.
|
Currently, we have 33
// TODO
* comments in the codebase that reference 21 issues that have been closed. We should re-visit those comments to assess whether the work has been done, or, if not, whether it is unblocked and/or still something we want to do.To generate the list of closed issues:
* Technically one is a
/* TODO
, so keep an eye out for that if you're wielding the regex hammer! Also, issue #1234 is a false positive.The text was updated successfully, but these errors were encountered: