Add prettier and format everything

Author: jderochervlk

.github/ISSUE_TEMPLATE/documentation_issue.md

@@ -1,9 +1,7 @@
 ---
 name: 🚨 Documentation issue
 about: Create an issue to help us improve the rescript-lang.org documentation website
-title: ''
-labels: ''
-assignees: ''
-
+title: ""
+labels: ""
+assignees: ""
 ---
-

.prettierrc

@@ -0,0 +1,3 @@
+semi: false
+plugins:
+  - "@prettier/plugin-oxc"

CHANGELOG.md

@@ -1,6 +1,5 @@
 # Changelog
 
-
 This changelog documents significant changes that caused a new version in the manual, or other related resources.
 
 We don't create a version fork for every minor release, and try to make docs "append only" as much as possible. Usually when we introduce a new feature we add a `since 9.0` annotation to a specific section, and be done with it.
@@ -13,8 +12,7 @@ Here are the notes on major changes we did, and how the version corresponds to s
 
 ### latest
 
-- 9.1 related
-  -
+- ## 9.1 related
 
 ### v9.0 (v8.3 - v9.0)
 
@@ -34,5 +32,3 @@ Here are the notes on major changes we did, and how the version corresponds to s
 ### v8.0.0 (v6 - v8.3)
 
 - Docs with Reason / OCaml syntax before the new syntax
-
-

README.md

@@ -1,4 +1,5 @@
 # rescript-lang.org
+
 [![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-v1.4%20adopted-ff69b4.svg)](CODE_OF_CONDUCT.md)
 
 This is the official documentation platform for the [ReScript](https://rescript-lang.org) programming language.

_blogposts/2020-08-10-bucklescript-is-rebranding.mdx

@@ -21,13 +21,15 @@ We're pleased to announce that BuckleScript is getting a brand new name: **ReScr
 ## Community Situation
 
 BuckleScript started with the idea that **JavaScript programmers deserved a great typed language with a fast and lean toolchain**. This idea took root and, over the years, we've gradually accomplished feats such as:
+
 - a state of the art compiled JavaScript output that rivals hand-written JS,
 - a fast & reliable toolchain much needed in front-end and Node development,
 - various JS interop features that spawned an ecosystem of well typed libraries,
 - a production-ready standard library,
 - [and recently](/blog/bucklescript-8-1-new-syntax), a fresh syntax made by a major contributor of Reason's old syntax.
 
 These developments have attracted many people into our community. But one bigger challenge persisted: newcomers dropped out at the sheer amount of extra incongruent tools and learning overhead from having to understand OCaml concepts, Reason concepts, and BuckleScript's concepts. Take, for example, what's required to make a React app using BuckleScript:
+
 - Knowledge of React.
 - Knowledge of JS.
 - Knowledge of BuckleScript's specific bindings to React (that we've tried hard to keep to a minimum).
@@ -43,6 +45,7 @@ The adoption barrier is real, and it's about time we finally solve it.
 ## The Rebranding
 
 Today, we'll start to truly unify the various BuckleScript-related projects under the ReScript umbrella. This includes:
+
 - The compiler, build system and the new syntax unified under a single installation.
 - Doubling down on editor tooling for ReScript usage.
 - A single documentation site (this one), which unifies all the docs and greatly trims down on redundant and stale info.

_blogposts/2020-08-28-new-rescript-logo.mdx

@@ -7,43 +7,52 @@ description: |
   Today, our resident designer Bettina is unveiling to us the fresh new ReScript branding we've been long waiting for. We hope you're as excited about the result as us!
 ---
 
-import Image from "src/components/Image";
+import Image from "src/components/Image"
 
 ## Why the Rebranding?
 
 ReScript is the evolution and fusion of Reason and BuckleScript. As we're a design-minded community, we'd like to convey this new identity not only through new technical changes as we've done so far, but also through a proper, more professionally crafted logo, color scheme and font. At the same time, we'd like to do so while recalling our roots.
 
 Here it is!
 
-
-<Image withShadow={false} src="/static/blog/rescript-launch/ReScript-1.jpg" caption="Comparison between the Reason, BuckleScript and ReScript logos"/>
-
+<Image
+  withShadow={false}
+  src="/static/blog/rescript-launch/ReScript-1.jpg"
+  caption="Comparison between the Reason, BuckleScript and ReScript logos"
+/>
 
 The old Reason and BuckleScript logo had many limitations:
+
 - The icons didn't really work well on round Social Media profile images (or round shapes at all).
 - There's no guideline on how the logo works inverted, or on colored background.
 - The large red rectangle makes it difficult to balance the logo with other elements.
 - The buckle and belt were a bit too literal and did not convey much.
 
 The new logo addresses all these and more:
 
-<Image withShadow={false} src="/static/blog/rescript-launch/ReScript-2.jpg" caption="Logo comparison on social media"/>
+<Image
+  withShadow={false}
+  src="/static/blog/rescript-launch/ReScript-2.jpg"
+  caption="Logo comparison on social media"
+/>
 
 ## Creating Meaning Through Simple Shapes
 
 A minimal logo design is achieved by putting aside all distractions while focusing on legibility, meaning and small details like clear lines, interesting perspective and depth.
 
-
-<Image withShadow={false} src="/static/blog/rescript-launch/ReScript-4.jpg" caption="ReScript logo variations and usage examples"/>
-
+<Image
+  withShadow={false}
+  src="/static/blog/rescript-launch/ReScript-4.jpg"
+  caption="ReScript logo variations and usage examples"
+/>
 
 **The letter "r"**, composed of two shapes, is inspired by Albers, a german-born American Bauhaus artist and typographer. An object should be simple, beautiful, functional and accessible for everyone - a statement which applies to ReScript's principles perfectly.
 
 **I/O**: The rectangle and circle represent the input / output, recalling the digital nature of a program.
 
 **The red app-shaped background** references the vibrant, playful applications our developers are empowered to create with ReScript.
 
-**The Logotype**  ("rescript") complements the brand mark with its clean look and its embrace of technology while retaining a functional look.
+**The Logotype** ("rescript") complements the brand mark with its clean look and its embrace of technology while retaining a functional look.
 
 We'd like to position ReScript to be a community of product-first developers who care about the fit & finish of their work, while keeping an eye on the quality of their engineering. This interplay of design and engineering is a hard-to-achieve but beautifully worthwhile sweet spot that's frequently been missing in the programmer community; our vibrant logo is our renewed symbolic step toward this mission. Come along with us on our journey!
 

_blogposts/2020-09-25-release-8-3-2.mdx

@@ -74,7 +74,7 @@ To get the build output, instead of communicating through IPC, we adopted a simp
 This makes the editor integration build-system agnostic, it does not need talk to the build system directly.
 
 It also makes our build tool work with other watchers including Facebook's [watchman](https://facebook.github.io/watchman/).
-Watchman is  a more scalable watcher tool for some specific platforms and less memory hungry, however, we still need a watchman-client to get the output of triggered job.
+Watchman is a more scalable watcher tool for some specific platforms and less memory hungry, however, we still need a watchman-client to get the output of triggered job.
 We write the output to `.compiler.log` per each build, allowing clients to read compiler diagnostics when they want.
 
 ## A better algorithm for removing stale outputs
@@ -90,8 +90,8 @@ We scan `lib/bs` directory and check some dangling `cm{i,t,j,ti}` files, if it d
 the current build set, it is considered stale artifacts. If it is `cmt` file, it would trigger some hooks of `genType`, notably -cmt-rm.
 
 - Based on previous build logs
-We store previous compilation stats.  If a file is in the previous compiler output, but no longer in the output of the new build, it is considered stale and can be removed.
-it is considered stale output which can be removed.
+  We store previous compilation stats. If a file is in the previous compiler output, but no longer in the output of the new build, it is considered stale and can be removed.
+  it is considered stale output which can be removed.
 
 In general, strategy two is more reliable and efficient.
 
@@ -100,11 +100,9 @@ In general, strategy two is more reliable and efficient.
 
 However, strategy one is easier for tooling like `genType`. Not every tool has knowledge of the build system.
 
-
 Sometimes a combination of both strategies is needed.
-- When removing .cm* files, we use the first strategy.
-- When removing generated javascript, we use strategy two,
-
 
+- When removing .cm\* files, we use the first strategy.
+- When removing generated javascript, we use strategy two,
 
 Happy Hacking!

_blogposts/2020-09-25-release-8-3.mdx

@@ -17,28 +17,27 @@ It's focused on type safety, performance and JS interop. It used to be called Bu
 npm i [email protected]
 ```
 
-The changes are listed [here](https://github.com/rescript-lang/rescript/blob/master/Changes.md#83), this is a large release,  and we will go through some highlighted changes.
-
-
+The changes are listed [here](https://github.com/rescript-lang/rescript/blob/master/Changes.md#83), this is a large release, and we will go through some highlighted changes.
 
 ## Lightweight FFI attributes without `bs.` prefix
 
 In this release, we make the `bs.` prefix optional, this will make the FFI less verbose.
 
 For example, the old externals for `readFileAsUtf8Sync` used to be written like this
 
-
 <CodeTab labels={["ReScript", "Reason (Old Syntax)", "ML Syntax"]}>
 
 ```res
 @bs.val @bs.module("fs")
 external readFileAsUtf8Sync: (string, @bs.as("utf8") _) => string = "readFileSync"
 ```
+
 ```reason
 [@bs.val] [@bs.module "fs"]
 external readFileAsUtf8Sync: (string, [@bs.as "utf8"] _) => string =
   "readFileSync";
 ```
+
 ```ocaml
 external readFileAsUtf8Sync : string -> (_[@bs.as "utf8"]) -> string = "readFileSync" [@@bs.val] [@@bs.module "fs"]
 ```
@@ -52,11 +51,13 @@ It can now be simplified as
 ```res
 @val @module("fs") external readFileAsUtf8Sync: (string, @as("utf8") _) => string = "readFileSync"
 ```
+
 ```reason
 [@val] [@module "fs"]
 external readFileAsUtf8Sync: (string, [@as "utf8"] _) => string =
   "readFileSync";
 ```
+
 ```ocaml
 external readFileAsUtf8Sync : string -> (_[@as "utf8"]) -> string = "readFileSync"
 [@@val] [@@module "fs"]
@@ -70,8 +71,7 @@ with the exception of the following two that don't have abbreviations:
 - `bs.send.pipe` : this attribute was deprecated in favor of `bs.send`; you can still use the existing one for backward compatibility.
 
 - `bs.splice` : this attribute was deprecated in favor of `bs.variadic`; you can still use the existing one for
-backward compatibility.
-
+  backward compatibility.
 
 ## default import in Es6 support
 
@@ -84,11 +84,13 @@ If you use es6 module output, the default bindings will be compiled properly now
 
 let a = input("hello")
 ```
+
 ```reason
 [@module "hello"] external input: string => string = "default";
 
 let a = input("hello");
 ```
+
 ```ocaml
 external input : string -> string = "default" [@@module "hello"]
 
@@ -100,11 +102,10 @@ let a = input "hello"
 Will now be compiled properly under es6 format as below:
 
 ```js
-import Hello from "hello";
-var a = Hello("hello");
+import Hello from "hello"
+var a = Hello("hello")
 ```
 
-
 ## Customized js file extension support
 
 Now user can pick up their js file extension support per module format:
@@ -126,8 +127,6 @@ To have better integration with other [JS infrastructures](https://github.com/re
 for example, Next.js/React Native, we allow file names like `404.res`,
 `Button.Android.res` so that it can just be picked up by those tools
 
-
-
 ## Better type based inference for pattern `let {a,b,c} = value`
 
 Previously, for code like this:
@@ -144,6 +143,7 @@ let f = (u: N.t) => {
   x + 1
 } /* type error */
 ```
+
 ```reason
 module N = {
   type t = {x: int};
@@ -154,6 +154,7 @@ let f = (u: N.t) => {
   x + 1;
 }; /* type error */
 ```
+
 ```ocaml
 module N = struct
     type t = {

_blogposts/2020-11-17-editor-support-custom-operators-and-more.mdx

@@ -8,7 +8,7 @@ description: |
   Update on what we're doing around the end of 2020 and early next year.
 ---
 
-import Video from "src/components/Video";
+import Video from "src/components/Video"
 
 ## Upcoming Improvements
 

_blogposts/2020-11-26-editor-support-release-1-0.mdx

@@ -9,12 +9,12 @@ description: |
   Type hints, jump to definition, error diagnostics, and more.
 ---
 
-
 ## Editor Integration Has Finally Landed
 
 Thank you so much for the wait!
 
 **Here are all the features:**
+
 - Highlighting
 - Formatting
 - Diagnostics
@@ -32,4 +32,8 @@ We'll keep on iterating on the polish of the plugins, and release better [Sublim
 
 Happy thanksgiving!
 
-<Image withShadow={false} src="/static/blog/editor_support_article.jpg" caption="ReScript now offers autocompletion for VSCode and neovim (Sublime coming soon)"/>
+<Image
+  withShadow={false}
+  src="/static/blog/editor_support_article.jpg"
+  caption="ReScript now offers autocompletion for VSCode and neovim (Sublime coming soon)"
+/>