summaryrefslogtreecommitdiff
path: root/doc/todo
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2014-10-14 14:10:22 -0400
committerGravatar Joey Hess <joey@kitenet.net>2014-10-14 14:15:07 -0400
commit9f5b8638a990f8d163afaf62e15331515fdcb21f (patch)
tree51584af5c9bfe07e12703bf5dabc45bf776b57e3 /doc/todo
parent9433c62da3d0c7b45ba528f01e000630f999cb27 (diff)
vicfg: Deleting configurations now resets to the default, where before it has no effect.
Added a Default instance for TrustLevel, and was able to use that to clear up several other parts of the code too. This commit was sponsored by Stephan Schulz
Diffstat (limited to 'doc/todo')
-rw-r--r--doc/todo/vicfg_comment_gotcha.mdwn4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/todo/vicfg_comment_gotcha.mdwn b/doc/todo/vicfg_comment_gotcha.mdwn
index 33befd383..910af01a4 100644
--- a/doc/todo/vicfg_comment_gotcha.mdwn
+++ b/doc/todo/vicfg_comment_gotcha.mdwn
@@ -9,8 +9,12 @@ but that way lies madness. Also, it's not at all clear what the "default"
should be in response to such an action. The default varies per type of
configuration, and vicfg does't know about defaults.
+> [[fixed|done]]; this was a job for Data.Default! --[[Joey]]
+
Instead, I think it should detect when a setting provided in the input
version of the file is not present in the output version, and plop the user
back into the editor with an error, telling them that cannot be handled,
and suggesting they instead change the value to the value they now want it
to have.
+
+> Nah, too complicated.