| Object type | Creation date | Created by | id | ||
|---|---|---|---|---|---|
|
2025-02-05T06:03:44Z |
|
bafyreihlh4qi4aoabb2mqs5j7xqvzenkcmpkmxeh3od5jilevvjj26a3aa |
Used for planned improvements or feature additions.
// TODO: Add input validation for email field
// TODO(username): Implement OAuth authentication
Indicates known broken or buggy code that needs repair.
// FIXME: Memory leak in image processing loop
// FIXME(urgent): Fix race condition in concurrent operations
Marks code that needs attention due to questionable workarounds or complexity.
// XXX: Temporary workaround for API version mismatch
// XXX: Complex algorithm needs optimization
Denotes code that uses a questionable coding practice to solve a problem.
// HACK: Using global variable to mismatch state
// HACK: Bypassing type checking for legacy compatibility
Identifies confirmed bugs that need to fixed.
// BUG: From submission fails on Safari
// BUG(#123): Incorrect calculation for leap years
- Always use consistent capitalization (uppercase preferred)
- Include a colon after the tag
- Leave one space after the colon
- Write clear, concise description
- Use present tense for actions
- Include relevant ticket/issue numbers
- Add usernames for accountability
- Include dates for time-sensitive items
- Specify priority levels when applicable
// TODO(p1)(security): Add password encryption
// NOTE: Must use becrypt with minimum 12 rounds
// FIXME(#456): Session timeout not working on Firefox
/*
* TODO(p1)(#123)(john): Implement OAuth 2.0 authentication
* Deadline: 2025-03-15
*/
I've created an example showing how to use multiple TODO comments effectively in a real-world scenario. Let me explain the key patterns demonstrated:
- Priority Levels:
- p1: Critical/High priority (security, major bugs)
- p2: Medium priority (improvements, refactoring)
- p3: Low priority (enhancements, optimizations)
- Categories:
- security: Security-related tasks
- performance: Performance improvements
- feature: New features
- cleanup: Code cleanup tasks
- refactor: Code restructuring
- Additional Information:
- Issue number (#123)
- Assignee (john)
- Deadlines
- Related requirements
- Links or other issues