Run pre-commit on everything

Kami1920 · Aug 29, 2020 · e8295dc · e8295dc
1 parent 6f8fd14
commit e8295dc
Show file tree

Hide file tree

Showing 6 changed files with 85 additions and 85 deletions.
diff --git a/.github/dependabot.yml b/.github/dependabot.yml
@@ -1,50 +1,50 @@
 version: 2
 updates:
-- package-ecosystem: npm
-  directory: "/packages/arb-provider-ethers"
-  schedule:
-    interval: daily
-  open-pull-requests-limit: 10
-  target-branch: develop
-- package-ecosystem: gomod
-  directory: "/packages/arb-validator"
-  schedule:
-    interval: daily
-  open-pull-requests-limit: 10
-  target-branch: develop
-- package-ecosystem: gomod
-  directory: "/packages/arb-validator-core"
-  schedule:
-    interval: daily
-  open-pull-requests-limit: 10
-  target-branch: develop
-- package-ecosystem: gomod
-  directory: "/packages/arb-avm-cpp"
-  schedule:
-    interval: daily
-  open-pull-requests-limit: 10
-  target-branch: develop
-- package-ecosystem: npm
-  directory: "/packages/arb-provider-web3"
-  schedule:
-    interval: daily
-  open-pull-requests-limit: 10
-  target-branch: develop
-- package-ecosystem: gomod
-  directory: "/packages/arb-avm-go"
-  schedule:
-    interval: daily
-  open-pull-requests-limit: 10
-  target-branch: develop
-- package-ecosystem: gomod
-  directory: "/packages/arb-util"
-  schedule:
-    interval: daily
-  open-pull-requests-limit: 10
-  target-branch: develop
-- package-ecosystem: gomod
-  directory: "/packages/arb-provider-go"
-  schedule:
-    interval: daily
-  open-pull-requests-limit: 10
-  target-branch: develop
+  - package-ecosystem: npm
+    directory: '/packages/arb-provider-ethers'
+    schedule:
+      interval: daily
+    open-pull-requests-limit: 10
+    target-branch: develop
+  - package-ecosystem: gomod
+    directory: '/packages/arb-validator'
+    schedule:
+      interval: daily
+    open-pull-requests-limit: 10
+    target-branch: develop
+  - package-ecosystem: gomod
+    directory: '/packages/arb-validator-core'
+    schedule:
+      interval: daily
+    open-pull-requests-limit: 10
+    target-branch: develop
+  - package-ecosystem: gomod
+    directory: '/packages/arb-avm-cpp'
+    schedule:
+      interval: daily
+    open-pull-requests-limit: 10
+    target-branch: develop
+  - package-ecosystem: npm
+    directory: '/packages/arb-provider-web3'
+    schedule:
+      interval: daily
+    open-pull-requests-limit: 10
+    target-branch: develop
+  - package-ecosystem: gomod
+    directory: '/packages/arb-avm-go'
+    schedule:
+      interval: daily
+    open-pull-requests-limit: 10
+    target-branch: develop
+  - package-ecosystem: gomod
+    directory: '/packages/arb-util'
+    schedule:
+      interval: daily
+    open-pull-requests-limit: 10
+    target-branch: develop
+  - package-ecosystem: gomod
+    directory: '/packages/arb-provider-go'
+    schedule:
+      interval: daily
+    open-pull-requests-limit: 10
+    target-branch: develop
diff --git a/.prettierrc.js b/.prettierrc.js
@@ -6,17 +6,17 @@ module.exports = {
   tabWidth: 2,
   arrowParens: 'avoid',
   bracketSpacing: true,
-  "overrides": [
+  overrides: [
     {
-      "files": "*.sol",
-      "options": {
-        "printWidth": 80,
-        "tabWidth": 4,
-        "useTabs": false,
-        "singleQuote": false,
-        "bracketSpacing": true,
-        "explicitTypes": "always"
-      }
-    }
-  ]
+      files: '*.sol',
+      options: {
+        printWidth: 80,
+        tabWidth: 4,
+        useTabs: false,
+        singleQuote: false,
+        bracketSpacing: true,
+        explicitTypes: 'always',
+      },
+    },
+  ],
 }
diff --git a/docs/Ethereum_Interoperability.md b/docs/Ethereum_Interoperability.md
@@ -42,12 +42,12 @@ function depositERC721Message(
 
 ### Withdrawing funds from Arbitrum to Ethereum
 
--   Eth: The ArbSys library can be used to withdraw Eth, `ArbSys(100).withdrawEth(destAddress, amount)`
--   ERC-20 and ERC-721: The system generated token contracts in Arbitrum contain a withdraw method
-    ```
-    function withdraw(address account, uint256 amount) public; // ERC-20
-    function withdraw(address account, uint256 tokenId) public; // ERC-721
-    ```
+- Eth: The ArbSys library can be used to withdraw Eth, `ArbSys(100).withdrawEth(destAddress, amount)`
+- ERC-20 and ERC-721: The system generated token contracts in Arbitrum contain a withdraw method
+  ```
+  function withdraw(address account, uint256 amount) public; // ERC-20
+  function withdraw(address account, uint256 tokenId) public; // ERC-721
+  ```
 
 In all cases, withdrawing is similar to a transfer, except the balance is burned on the Arbitrum side, and eventually those funds away become available to their destination on the Ethereum side.
 

diff --git a/docs/Finality.md b/docs/Finality.md
@@ -31,8 +31,8 @@ On-chain confirmation is typically slower than the other types.
 The ArbChain's validators will all place stakes on proposed future histories of the chain.
 Arbitrum enforces two rules regarding those stakes:
 
--   If a validator is staked on a correct future history, it can force that history to be confirmed by the system eventually.
--   If a validator is staked on a history that is not confirmed, that validator will lose its stake.
+- If a validator is staked on a correct future history, it can force that history to be confirmed by the system eventually.
+- If a validator is staked on a history that is not confirmed, that validator will lose its stake.
 
 You can choose to treat a transaction as final when a validator of your choice is staked on a history containing that transaction.
 

diff --git a/docs/Glossary.md b/docs/Glossary.md
@@ -4,18 +4,18 @@ title: Glossary of Arbitrum Terms
 custom_edit_url: https://github.com/OffchainLabs/arbitrum/edit/master/docs/Glossary.md
 ---
 
-* Assertion: A claim, made by a validator, about what the contracts on a chain will do. An assertion is considered _pending_ until it is confirmed.
-* Arbitrum Chain: A chain running on Arbitrum, containing some contracts. Many Arbitrum chains can exist at the same time.
-* Arbitrum executable file: The output of the Arbitrum compiler, usually in a file with the .ao file extension. An Arbitrum executable has all of the information needed to launch an Arbitrum Chain.
-* AVM: The Arbitrum Virtual Machine
-* Chain factory: A contract running on Ethereum which, when called, creates a new Arbitrum Chain.
-* Chain state: A particular point in the history of an Arbitrum Chain. A chain state corresponds to a sequence of assertions that have been made, and a verdict about whether each of those assertions was accepted.
-* Challenge: When two stakers disagree about the correct verdict on an assertion, those stakers can be put in a challenge. The challenge is refereed by the EthBridge. Eventually one staker wins the challenge. The loser forfeits their stake. Half of the loser's stake is given to the winner, and the other half is burned. 
-* Client: A program running on a user's machine, often in the user's browser, that interacts with contracts on an Arbitrum chain and provides a user interface.
-* Compiler: A part of the Arbitrum toolchain that takes a set of Solidity contracts and compiles them into an Arbitrum executable file.
-* Confirmation: The final decision by an Arbitrum chain to accept a node as being a settled part of the chain's history. When a node is confirmed, any funds paid out by the chain to the main Ethereum chain are transferred.
-* EthBridge: A group of contracts running on the Ethereum chain, which act as a record-keeper and rule enforcer for Arbitrum chains.
-* Inbox: Holds a sequence of messages sent by clients to the contracts on an Arbitrum Chain. Every chain's inbox is managed by the on-chain EthBridge. Every message to a chain is timestamped with the Ethereum block number when it was put into the chain's inbox.
-* Staker: A party who deposits a stake, in Eth, to vouch for a particular node in an Arbitrum Chain. A party who stakes on a false node can expect to lose their stake. An honest staker can recover their stake once the node they are staked on has been confirmed.
-* Validator: A party who keeps track of the state of an Arbitrum Chain, and possibly acts to ensure the chain makes progress correctly.
-* Virtual Machine (VM): A program that "runs" on the Arbitrum chain, which tracks the states of all of the contracts on the chain and all of the Eth and tokens deposited into the chain.
+- Assertion: A claim, made by a validator, about what the contracts on a chain will do. An assertion is considered _pending_ until it is confirmed.
+- Arbitrum Chain: A chain running on Arbitrum, containing some contracts. Many Arbitrum chains can exist at the same time.
+- Arbitrum executable file: The output of the Arbitrum compiler, usually in a file with the .ao file extension. An Arbitrum executable has all of the information needed to launch an Arbitrum Chain.
+- AVM: The Arbitrum Virtual Machine
+- Chain factory: A contract running on Ethereum which, when called, creates a new Arbitrum Chain.
+- Chain state: A particular point in the history of an Arbitrum Chain. A chain state corresponds to a sequence of assertions that have been made, and a verdict about whether each of those assertions was accepted.
+- Challenge: When two stakers disagree about the correct verdict on an assertion, those stakers can be put in a challenge. The challenge is refereed by the EthBridge. Eventually one staker wins the challenge. The loser forfeits their stake. Half of the loser's stake is given to the winner, and the other half is burned.
+- Client: A program running on a user's machine, often in the user's browser, that interacts with contracts on an Arbitrum chain and provides a user interface.
+- Compiler: A part of the Arbitrum toolchain that takes a set of Solidity contracts and compiles them into an Arbitrum executable file.
+- Confirmation: The final decision by an Arbitrum chain to accept a node as being a settled part of the chain's history. When a node is confirmed, any funds paid out by the chain to the main Ethereum chain are transferred.
+- EthBridge: A group of contracts running on the Ethereum chain, which act as a record-keeper and rule enforcer for Arbitrum chains.
+- Inbox: Holds a sequence of messages sent by clients to the contracts on an Arbitrum Chain. Every chain's inbox is managed by the on-chain EthBridge. Every message to a chain is timestamped with the Ethereum block number when it was put into the chain's inbox.
+- Staker: A party who deposits a stake, in Eth, to vouch for a particular node in an Arbitrum Chain. A party who stakes on a false node can expect to lose their stake. An honest staker can recover their stake once the node they are staked on has been confirmed.
+- Validator: A party who keeps track of the state of an Arbitrum Chain, and possibly acts to ensure the chain makes progress correctly.
+- Virtual Machine (VM): A program that "runs" on the Arbitrum chain, which tracks the states of all of the contracts on the chain and all of the Eth and tokens deposited into the chain.
diff --git a/docs/Rollup_basics.md b/docs/Rollup_basics.md
@@ -88,5 +88,5 @@ The client program will then read the call's result from the log item.
 
 There are some other topics that have documentation pages of their own:
 
--   [Ethereum interoperability](Ethereum_Interoperability.md)
--   [Finality and confirmation in Arbitrum](Finality.md)
+- [Ethereum interoperability](Ethereum_Interoperability.md)
+- [Finality and confirmation in Arbitrum](Finality.md)