todo
@mappum, it's okay to make it a read TODO. in fact, it's a really nice practice since it's standard and we can grep it. When someone who has an answer for the concern comes across the standard TODO breadcrumb, he/she can address it. Using the conventional TODO improves discoverability.
Brian Tiger Chow committed
Nov 11, 2014 at 21:45 UTC
45526224e40a9f1daf8ddd569f88bbd1bdfb57e2
1 file changed
+1
-1
core/commands2/config.go
+1
-1
@@ -140,7 +140,7 @@ func setConfig(filename string, key, value string) (*ConfigField, error) {
140
}
141
142
func showConfig(filename string) (io.Reader, error) {
143
- // MAYBE_TODO: maybe we should omit privkey so we don't accidentally leak it?
143
+ // TODO maybe we should omit privkey so we don't accidentally leak it?
144
145
file, err := os.Open(filename)
146
if err != nil {