fix: add prettier write command (#345)

.circleci/config.yml

@@ -3,7 +3,6 @@ version: 2.1
 orbs:
   frontend-tools: contentful/frontend-tools@1
 
-
 executors:
   default:
     docker:
@@ -12,11 +11,9 @@ executors:
           username: $DOCKERHUB_USERNAME
           password: $DOCKERHUB_PASSWORD
 
-
 cache-key: &cache-key
   key: npm-cache-{{ arch }}-{{ checksum ".nvmrc" }}-{{ checksum "package-lock.json" }}-{{ .Branch }}
 
-
 commands:
   use_npm_token:
     steps:
@@ -41,16 +38,16 @@ jobs:
       - run: npm run test:ci
 
   release:
-      executor: default
-      steps:
-        - checkout
-        - run: git config --global user.email "[email protected]"
-        - run: git config --global user.name "contentful-ecosystem-bot"
-        - npm_install
-        - run: npm run build
-        - run: npm run lerna version --no-private --conventional-commits --create-release github --yes
-        - run: npm run lerna publish from-git --yes
-  
+    executor: default
+    steps:
+      - checkout
+      - run: git config --global user.email "[email protected]"
+      - run: git config --global user.name "contentful-ecosystem-bot"
+      - npm_install
+      - run: npm run build
+      - run: npm run lerna version --no-private --conventional-commits --create-release github --yes
+      - run: npm run lerna publish from-git --yes
+
   compressed-size:
     executor: default
     steps:

CONTRIBUTING.md

@@ -24,7 +24,7 @@ It also explains what to do if you want to set up the project locally and run
 tests.
 
 **Working on your first Pull Request?**
-You can learn how from this *free* series: [How to Contribute to an Open Source
+You can learn how from this _free_ series: [How to Contribute to an Open Source
 Project on GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github)
 
 ## Useful npm scripts
@@ -64,8 +64,8 @@ This should generally only happen at publishing time, but you may want to run
 
 For example, let's say you're working on a pull request that
 
-1) adds support for a type in `rich-text-types`, and
-2) adds behavior to handle that type in `rich-text-html-renderer`.
+1. adds support for a type in `rich-text-types`, and
+2. adds behavior to handle that type in `rich-text-html-renderer`.
 
 If changes in the latter are dependent upon changes in the former, you'll need
 to run `npm run build` to update the referenced vendored files in

README.md

@@ -30,7 +30,7 @@ Text documents.
   - Flutter renderer for the Contentful rich text field type (work in progress)
 - [`ngx-contentful-rich-text`](https://github.com/kgajera/ngx-contentful-rich-text)
   - Angular renderer for the Contentful rich text field type
-  
+
 ## About Rich Text
 
 - [Rich Text Concept](https://www.contentful.com/developers/docs/concepts/rich-text/)

bin/benchmark/index.ts

@@ -28,12 +28,7 @@ if (!packageNameArg) {
  */
 const packageName = packageNameArg.replace(/^@contentful\//, '');
 
-const paths = [
-  __dirname,
-  '../../packages',
-  packageName,
-  'bin/benchmark'
-];
+const paths = [__dirname, '../../packages', packageName, 'bin/benchmark'];
 
 const benchmarkPath = resolve(...paths);
 
@@ -55,10 +50,7 @@ readdir(benchmarkPath, (err, files) => {
   const benchmarks: Array<[string, Function]> = Object.entries(
     files
       .map((name): { [key: string]: Function } => require(resolve(...paths, name)))
-      .reduce((allBenchmarks, fileBenchmarks) => Object.assign(
-        allBenchmarks,
-        fileBenchmarks
-      ), {})
+      .reduce((allBenchmarks, fileBenchmarks) => Object.assign(allBenchmarks, fileBenchmarks), {}),
   );
 
   for (const [name, benchmark] of benchmarks) {