From 5bc33247eeba8166b3dd0b7b5fa60f89e9b8dc05 Mon Sep 17 00:00:00 2001
From: Arya Irani <arya.irani@unison.cloud>
Date: Wed, 22 Nov 2023 16:31:05 -0500
Subject: [PATCH] initial failing transcript

---
 .../transcripts/update-type-add-new-record.md | 14 ++++++
 .../update-type-add-new-record.output.md      | 45 +++++++++++++++++++
 2 files changed, 59 insertions(+)
 create mode 100644 unison-src/transcripts/update-type-add-new-record.md
 create mode 100644 unison-src/transcripts/update-type-add-new-record.output.md

diff --git a/unison-src/transcripts/update-type-add-new-record.md b/unison-src/transcripts/update-type-add-new-record.md
new file mode 100644
index 0000000000..6ac9955ddf
--- /dev/null
+++ b/unison-src/transcripts/update-type-add-new-record.md
@@ -0,0 +1,14 @@
+```ucm:hide
+.lib> builtins.merge
+```
+
+```unison
+unique type Foo = { bar : Nat }
+```
+
+This shouldn't be an error.
+
+```ucm:error
+.> update
+.> view Foo
+```
diff --git a/unison-src/transcripts/update-type-add-new-record.output.md b/unison-src/transcripts/update-type-add-new-record.output.md
new file mode 100644
index 0000000000..73961f6a21
--- /dev/null
+++ b/unison-src/transcripts/update-type-add-new-record.output.md
@@ -0,0 +1,45 @@
+```unison
+unique type Foo = { bar : Nat }
+```
+
+```ucm
+
+  I found and typechecked these definitions in scratch.u. If you
+  do an `add` or `update`, here's how your codebase would
+  change:
+  
+    ⍟ These new definitions are ok to `add`:
+    
+      unique type Foo
+      Foo.bar        : Foo -> Nat
+      Foo.bar.modify : (Nat ->{g} Nat) -> Foo ->{g} Foo
+      Foo.bar.set    : Nat -> Foo -> Foo
+
+```
+This shouldn't be an error.
+
+```ucm
+.> update
+
+  Okay, I'm searching the branch for code that needs to be
+  updated...
+
+  That's done. Now I'm making sure everything typechecks...
+
+  Everything typechecks, so I'm saving the results...
+
+  I couldn't complete the update because I couldn't find 0
+  constructor(s) for Foo where I expected to. I found: []
+  
+  You can use `view Foo` and
+  `alias.term <hash> Foo.<ConstructorName>` to give names to
+  each constructor, and then try again.
+
+.> view Foo
+
+  ⚠️
+  
+  The following names were not found in the codebase. Check your spelling.
+    Foo
+
+```