You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if the flake8-todo rules affecting TODO formatting (TD002-7) supported the lint.task-tags setting rather than just the hard-coded "directives" supported by the original rules in flake8-todo. As it stands, there's no way to add enforcement for custom tags, which would be helpful for teams which use them and want to make sure they're used consistently. It also "incorrectly" flags my maybe-todo comments (e.g. # TODO?: switch to using fooble instead) as missing a colon. 🙂
The text was updated successfully, but these errors were encountered:
Ah! You're right, TD001 doesn't make sense that way; my mistake, I'll fix the description.
No, I was indeed referring to e.g. being able to require # TECHDEBT(author) instead of just # TECHDEBT if TD002 is selected or, in my case, # TODO?: some rationale instead of just # TODO? with TD004, TD005, and TD007.
I think being able to keep track of when task tags are being used inconsistently would be a "nice to have" feature for projects which use multiple tags with different meanings.
It would be nice if the flake8-todo rules affecting TODO formatting (TD002-7) supported the
lint.task-tags
setting rather than just the hard-coded "directives" supported by the original rules in flake8-todo. As it stands, there's no way to add enforcement for custom tags, which would be helpful for teams which use them and want to make sure they're used consistently. It also "incorrectly" flags my maybe-todo comments (e.g.# TODO?: switch to using fooble instead
) as missing a colon. 🙂The text was updated successfully, but these errors were encountered: