commit 037996cee61d3968d7c8cd58b4ecce82e9b757a1
parent 53522d8374146e0dd288f42e6c2636e9b7628cda
Author: Florian Dold <florian@dold.me>
Date: Mon, 5 Jun 2023 11:22:22 +0200
DD37: document future 'revive' option
Diffstat:
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/design-documents/037-wallet-transactions-lifecycle.rst b/design-documents/037-wallet-transactions-lifecycle.rst
@@ -1089,9 +1089,6 @@ Alternatives
not ask again."). Probably at best a post-1.0 feature.
-Drawbacks
-=========
-
Discussion / Q&A
================
@@ -1099,7 +1096,11 @@ Discussion / Q&A
has created the transaction. It is possible that network requests
are happening before that, but they are not considered to be part
of the transaction.
-* We have decided against a `cancel` state, because it resulted
- in too much complexity. Instead of doing a direct `cancel`,
+* We have decided against a ``cancel`` state, because it resulted
+ in too much complexity. Instead of doing a direct ``cancel``,
the user has to go to the transaction and abort and/or delete
it.
+* We might add a ``revive`` action in the future that allows
+ to go from ``aborting`` back to ``pending`` for transactions
+ where this makes sense. We're not doing it right now
+ to simplify things.
+\ No newline at end of file
