From 5c456bf059bca42c508b979f8ca427a0d244f9e2 Mon Sep 17 00:00:00 2001 From: Marco Perone Date: Thu, 26 Jan 2023 11:15:18 +0100 Subject: [PATCH] Improve wording on identity transitions decision log Co-authored-by: Alex --- .../2023-01-13-always-allow-identity-transitions.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/decision-log/2023-01-13-always-allow-identity-transitions.yaml b/decision-log/2023-01-13-always-allow-identity-transitions.yaml index 2a473f9..055ca57 100644 --- a/decision-log/2023-01-13-always-allow-identity-transitions.yaml +++ b/decision-log/2023-01-13-always-allow-identity-transitions.yaml @@ -1,13 +1,13 @@ name: Always allow identity transitions date: 2023-01-13 context: > - The topology of a state machine describes which are the allowed transitions. + The topology of a state machine lists its allowed transitions. Sometimes (like in the implementation of the `Choice` typeclass) we would simply like to say that we are not changing state. This is still seen as a transition by our current implementation. decision: > - We decide to consider everytime not changing state as a valid transition. + We will always consider not changing state as a valid transition. consequences: > We create a new instance of our `AllowedTransition` typeclass which searches for a proof term indicating that a transition is allowed. Such an instance