Hit Markdown and JSON files with the prettier hammer

README.md

@@ -36,9 +36,9 @@ your dev browser of choice:
 
 - [Firefox instructions](https://extensionworkshop.com/documentation/develop/temporary-installation-in-firefox/)
 - [Chrome, Brave, and Opera instructions](https://developer.chrome.com/docs/extensions/mv3/getstarted/#manifest)
-    * Note that these instructions are for Chrome, but substituting
-      `brave://extensions` or `opera://extensions` for `chrome://extensions`
-      depending on browser should get you to the same buttons.
+  - Note that these instructions are for Chrome, but substituting
+    `brave://extensions` or `opera://extensions` for `chrome://extensions`
+    depending on browser should get you to the same buttons.
 
 Extension bundles for each browser are in `dist/<browser>`.
 

api/keys/README.md

@@ -5,4 +5,3 @@ the keys api should store keys of these types:
 metamask style 12 words
 bip39 24 words generated keys
 read only keys/public addresses
-

manifest/manifest.development.json

@@ -1,7 +1,5 @@
 {
   "background": {
-    "scripts": [
-      "dev-utils/extension-reload.js"
-    ]
+    "scripts": ["dev-utils/extension-reload.js"]
   }
 }

manifest/manifest.json

@@ -39,8 +39,6 @@
 
   "background": {
     "persistent": true,
-    "scripts": [
-      "background.js"
-    ]
+    "scripts": ["background.js"]
   }
 }

package.json

@@ -25,7 +25,7 @@
     "lint:docs": "prettier -c '**/*.md'",
     "lint:docs:fix": "prettier -w '**/*.md'",
     "lint:js": "eslint .",
-    "lint:js:fix": "eslint .",
+    "lint:js:fix": "eslint . --fix",
     "test": "echo \"nothing to do\""
   },
   "workspaces": [

ui/README.md

@@ -1,4 +1,5 @@
 # Tally Extension Frontend 🐕
+
 ![Screen + Browser Mock](https://user-images.githubusercontent.com/1918798/125732391-29da0e00-0796-49bb-895d-35de187b141d.png)
 
 Welcome to the frontend portion of the Tally browser extension. This is the React portion of the codebase which handles UI related states, and communicates with the background script API `@tallyho/tally-api`. The intent is for all communication with outside APIs to strictly happen within `@tallyho/tally-api`, not here. This frontend only contains what's needed to provide the visual goodness!
@@ -7,15 +8,16 @@ Welcome to the frontend portion of the Tally browser extension. This is the Reac
 
 Make sure to have these installed,
 
-* [Git](https://git-scm.com/)
-* [Node](https://nodejs.org/en/) (Tested on v12.17.0)
-* [Yarn](https://yarnpkg.com/)
+- [Git](https://git-scm.com/)
+- [Node](https://nodejs.org/en/) (Tested on v12.17.0)
+- [Yarn](https://yarnpkg.com/)
 
 Check out these docs,
-* [Redux Toolkit](https://redux-toolkit.js.org/api/configureStore)
-* [react-chrome-extension-router](https://github.com/kelsonpw/react-chrome-extension-router)
-* [styled-jsx](https://github.com/vercel/styled-jsx)
-* [Airbnb JavaScript Style Guide](https://github.com/airbnb/javascript)
+
+- [Redux Toolkit](https://redux-toolkit.js.org/api/configureStore)
+- [react-chrome-extension-router](https://github.com/kelsonpw/react-chrome-extension-router)
+- [styled-jsx](https://github.com/vercel/styled-jsx)
+- [Airbnb JavaScript Style Guide](https://github.com/airbnb/javascript)
 
 ## Running in development 🚀
 
@@ -24,6 +26,7 @@ First, install the node modules:
 ```bash
 yarn install
 ```
+
 If you run into `The engine "node" is incompatible with this module.`, try adding `--ignore-engines` for now.
 
 Then, start up the dev server:
@@ -43,6 +46,7 @@ Load the unpacked extension for your web browser via the `/build` directory. Cur
 3. To make this page available to the router links, register the route at the end of the file
 
 For example,
+
 ```
 import { registerRoute } from '../config/routes';
 import CorePage from '../components/Core/CorePage';
@@ -56,7 +60,7 @@ export default function ExamplePage() {
       <style jsx>
         {`
           .example_class {
-            color: 
+            color:
           }
         `}
       </style>
@@ -66,6 +70,7 @@ export default function ExamplePage() {
 
 registerRoute('earn', Earn);
 ```
+
 ⚠️ Styles are inside of the jsx via [styled-jsx](https://github.com/vercel/styled-jsx)
 
 ### How to link/navigate to a page
@@ -86,9 +91,11 @@ import { routes } from '../../config/routes';
   />
 </Link>
 ```
+
 ⚠️ The key used in the routes object is set at the end of a page file with `registerRoute('example', Example);`. Typically the key name is page's name but in camel case.
 
 ## Primary file structure 📁
+
 ```
 /pages
 # Folder for components that serve the components for pages, primarily tabs