Book Image

ReasonML Quick Start Guide

By : Raphael Rafatpanah, Bruno Joseph D'mello
Book Image

ReasonML Quick Start Guide

By: Raphael Rafatpanah, Bruno Joseph D'mello

Overview of this book

ReasonML, also known as Reason, is a new syntax and toolchain for OCaml that was created by Facebook and is meant to be approachable for web developers. Although OCaml has several resources, most of them are from the perspective of systems development. This book, alternatively, explores Reason from the perspective of web development. You'll learn how to use Reason to build safer, simpler React applications and why you would want to do so. Reason supports immutability by default, which works quite well in the context of React. In learning Reason, you will also learn about its ecosystem – BuckleScript, JavaScript interoperability, and various npm workflows. We learn by building a real-world app shell, including a client-side router with page transitions, that we can customize for any Reason project. You'll learn how to leverage OCaml's excellent type system to enforce guarantees about business logic, as well as preventing runtime type errors.You'll also see how the type system can help offload concerns that we once had to keep in our heads. We'll explore using CSS-in-Reason, how to use external JSON in Reason, and how to unit-test critical business logic. By the end of the book, you'll understand why Reason is exploding in popularity and will have a solid foundation on which to continue your journey with Reason.
Table of Contents (10 chapters)

Pipe operators

Reason has two pipe operators:

|> (pipe)
-> (fast pipe)

Both pipe operators pass arguments to functions. The |> pipe operator pipes to a function's last argument and the -> fast pipe operator pipes to a function's first argument.

Take a look at these:

three |> f(one, two)
one -> f(two, three)

They are equivalent to this:

f(one, two, three)

If the function only accepts one argument, then both pipes work the same, since the function's first argument is also the function's last argument.

Using these pipe operators is quite popular, since, once you get the hang of it, it makes the code a lot more readable.

We don't need to use this:

Belt.List.(reduce(map([1, 2, 3], e => e + 1), 0, (+)))

We can write it in a way that doesn't require the reader to read it inside out:

Belt.List.(
[1, 2, 3]
->map(e => e + 1)
->reduce...