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)

Summary

As long as we're working within Reason, the type system will prevent you from running into runtime type errors. However, when interacting with the outside world—whether it be JavaScript or external data—we lose those guarantees. To be able to preserve these guarantees within Reason's boundaries, we need to help out the type system when using things outside Reason. We previously learned how to use external JavaScript in Reason, and in this chapter we've learned how to use external data in Reason. Although writing decoders and encoders is more challenging, it's quite similar to writing JavaScript bindings. In the end, we're simply telling Reason the type of something external to Reason. With GraphQL, we can extend the boundaries of Reason to include external data. There are trade-offs, and nothing is perfect, but it's definitely...