Details
-
Type:
Improvement
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Stack Documentation and UX
-
Labels:
-
Story Points:1
-
Epic Link:
-
Sprint:Alert Production S17 - 3
-
Team:Alert Production
Description
Following discussion on RFC-307, this ticket adds the following rule to the Python style guide:
To-do comments SHOULD include a Jira issue key
If the commented code is a workaround for a known issue, this rule makes it easier to find and remove the workaround once the issue has been resolved. If the commented code itself is the problem, this rule ensures the issue will be reported on Jira, making it more likely to be fixed in a timely manner.
# TODO: DM-12345 is triggered by this line
|
# TODO: workaround for DM-6789
|
and the following rule to the C++ style guide:
6-26. To-do comments SHOULD include a Jira issue key
If the commented code is a workaround for a known issue, this rule makes it easier to find and remove the workaround once the issue has been resolved. If the commented code itself is the problem, this rule ensures the issue will be reported on Jira, making it more likely to be fixed in a timely manner.
// TODO: DM-12345 is triggered by this line
|
// TODO: workaround for DM-6789
|
Attachments
Issue Links
- is triggered by
-
RFC-307 Discourage use of @todo Doxygen tag
- Implemented
Activity
Field | Original Value | New Value |
---|---|---|
Epic Link |
|
Description |
Following discussion on h3. To-do comments SHOULD include a Jira issue ID If the commented code is a workaround for a known issue, this rule makes it easier to find and remove the workaround once the issue has been resolved. If the commented code itself is the problem, this rule ensures the issue will be reported on Jira, making it more likely to be fixed in a timely manner. {code} # TODO: {code} {code} # TODO: workaround for {code} ---- and the following rule to the C++ style guide: h4. 6-26. To-do comments SHOULD include a Jira issue ID If the commented code is a workaround for a known issue, this rule makes it easier to find and remove the workaround once the issue has been resolved. If the commented code itself is the problem, this rule ensures the issue will be reported on Jira, making it more likely to be fixed in a timely manner. {code} // TODO: {code} {code} // TODO: workaround for {code} |
Following discussion on h3. To-do comments SHOULD include a Jira issue key If the commented code is a workaround for a known issue, this rule makes it easier to find and remove the workaround once the issue has been resolved. If the commented code itself is the problem, this rule ensures the issue will be reported on Jira, making it more likely to be fixed in a timely manner. {code} # TODO: {code} {code} # TODO: workaround for {code} ---- and the following rule to the C++ style guide: h4. 6-26. To-do comments SHOULD include a Jira issue key If the commented code is a workaround for a known issue, this rule makes it easier to find and remove the workaround once the issue has been resolved. If the commented code itself is the problem, this rule ensures the issue will be reported on Jira, making it more likely to be fixed in a timely manner. {code} // TODO: {code} {code} // TODO: workaround for {code} |
Rank | Ranked higher |
Sprint | Alert Production S17 - 4 [ 610 ] |
Rank | Ranked higher |
Status | To Do [ 10001 ] | In Progress [ 3 ] |
Reviewers | Kian-Tat Lim [ ktl ] | |
Status | In Progress [ 3 ] | In Review [ 10004 ] |
Status | In Review [ 10004 ] | Reviewed [ 10101 ] |
Sprint | Alert Production S17 - 4 [ 610 ] | Alert Production S17 - 3 [ 605 ] |
Resolution | Done [ 10000 ] | |
Status | Reviewed [ 10101 ] | Done [ 10002 ] |
Hi Kian-Tat Lim, could you please review
DM-7892andDM-9966? These are the final changes to the dev guide needed to closeRFC-225andRFC-307, and they're fairly small updates.