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
Developers often add comments to code which is not complete or needs review. Most likely you want to fix or review the code, and then remove the comment, before you consider the code to be production ready.
The Pepr team already shares this value and avoids the use of TODO statements. This setting would act as a backstop for code reviewers during PR reviews.
Additional context
As of 8c466da, there are only 3 TODO statements in the code:
src/cli/init/index.ts
39:7 warning Unexpected 'todo' comment: 'TODO: Overrides for testing. Don't be so...' no-warning-comments
40:7 warning Unexpected 'todo' comment: 'TODO: See pepr/#1140' no-warning-comments
src/sdk/cosign.ts
180:1 warning Unexpected 'todo' comment: 'TODO: should support using certs too' no-warning-comments
The text was updated successfully, but these errors were encountered:
Describe what should be investigated or refactored
We could apply the eslint rule no-warning-comments to the project.
The Pepr team already shares this value and avoids the use of TODO statements. This setting would act as a backstop for code reviewers during PR reviews.
Additional context
As of 8c466da, there are only 3 TODO statements in the code:
The text was updated successfully, but these errors were encountered: