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

Remove all TODO comments in the code #116

Closed
GuySartorelli opened this issue Sep 20, 2023 · 9 comments
Closed

Remove all TODO comments in the code #116

GuySartorelli opened this issue Sep 20, 2023 · 9 comments

Comments

@GuySartorelli
Copy link
Member

GuySartorelli commented Sep 20, 2023

There are a ton of TODO comments in the code. It's a bad look, and it makes it a lot harder to find temporary TODO comments that are added during development, since a simple search for TODO is polluted by the existing ones.
What's more, a TODO comment in the codebase is never going to be actioned, so they should be replaced with GitHub issues we can track.

Acceptance criteria

  • Any TODO comment that should be actioned has an issue in the appropriate repository
  • All TODO comments are removed from the codebase for all supported and core modules

PRs

@sabina-talipova
Copy link
Contributor

I plan to create a separate epic task for these purposes. This will make it easier to group and track the process of how TODO is performed.

@sabina-talipova
Copy link
Contributor

sabina-talipova commented Oct 10, 2023

TODO tickets list:

This was referenced Oct 10, 2023
@michalkleiner
Copy link
Contributor

I've checked a few of the tickets created from the todo comments but for me in most cases it lacks any context where it comes from, so it could be good to add e.g. a link to the line in file it comes from? Something so that whoever looks at the GH issue doesn't need to spend too much time trying to find those details.

@GuySartorelli
Copy link
Member Author

GuySartorelli commented Oct 17, 2023

e.g. a link to the line in file it comes from?

^ Note that a link to that line of code should use the "permanent" link, so that when your PRs to remove the todo comments are merged, we can still see the context that is required for the issue.

@sabina-talipova
Copy link
Contributor

@sabina-talipova
Copy link
Contributor

@sabina-talipova
Copy link
Contributor

@GuySartorelli
Copy link
Member Author

PRs merged and new issues triaged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants