-
Notifications
You must be signed in to change notification settings - Fork 2
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
Comments
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. |
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. |
^ 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. |
And one new ticket for CMS6, probably. |
PRs merged and new issues triaged |
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
PRs
The text was updated successfully, but these errors were encountered: