unison/unison-src/transcripts/fix5080.output.md
Greg Pfeil 0031542faf
Add a space before code block info strings
This is for consistency with the `cmark` style. Now the blocks we still
pretty-print ourselves will match the bulk of them that `cmark`
produces.
2024-07-10 13:56:07 -06:00

68 lines
1.3 KiB
Markdown

``` unison
test> fix5080.tests.success = [Ok "success"]
test> fix5080.tests.failure = [Fail "fail"]
```
``` ucm
Loading changes detected in scratch.u.
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`:
fix5080.tests.failure : [Result]
fix5080.tests.success : [Result]
Now evaluating any watch expressions (lines starting with
`>`)... Ctrl+C cancels.
1 | test> fix5080.tests.success = [Ok "success"]
✅ Passed success
2 | test> fix5080.tests.failure = [Fail "fail"]
🚫 FAILED fail
```
``` ucm
scratch/main> add
⍟ I've added these definitions:
fix5080.tests.failure : [Result]
fix5080.tests.success : [Result]
scratch/main> test
Cached test results (`help testcache` to learn more)
1. fix5080.tests.success ◉ success
2. fix5080.tests.failure ✗ fail
🚫 1 test(s) failing, ✅ 1 test(s) passing
Tip: Use view 1 to view the source of a test.
```
``` ucm
scratch/main> delete.term 2
Done.
scratch/main> test
Cached test results (`help testcache` to learn more)
1. fix5080.tests.success ◉ success
✅ 1 test(s) passing
Tip: Use view 1 to view the source of a test.
```