Format

Author: fhammerschmidt

markdown-pages/blog/release-12-0-0.mdx

@@ -50,24 +50,29 @@ The deprecated `*Exn` variants remain available in v12 to ease the transition, a
 Note that `Result.getOrThrow` now throws a JavaScript exception, so please update any exception-handling logic that relied on OCaml exception names. We also revamped the API around JS exceptions and errors.
 
 We’ve renamed JS errors to `JsError.t` to better distinguish them from the `Result.Error` variant. Since JavaScript allows throwing anything (not only proper Error objects), the previous way of catching JS exceptions was unsafe:
+
 ```res
 let foo = switch myUnsafeJsResult() {
 | exception Exn.Error(e) => Error(e->Error.message)
   // ☝️ this will crash if `e` is undefined or null
 | myRes => Ok(myRes)
 }
 ```
+
 Additionally, the coexistence of `Result.Error` and the `Error` module caused confusion.
 
 The new recommended pattern is:
+
 ```res
 let foo = switch myUnsafeJsResult() {
 | exception JsExn(e) => Error(e->JsExn.message))
 // ☝️ this is now safe even `e` is undefined or null
 | myRes => Ok(myRes)
 }
 ```
+
 Utility helpers for working with JS errors are now in `JsError`, eg:
+
 ```res
 JsError.throw(JsError.RangeError.make("the payload should be below 16"))
 ```