Merge pull request #7 from bchainhub/test/build

Test/build

Author: rastislavcore

versioned_docs/version-1/config/hardhat.md

@@ -26,7 +26,7 @@ To run Slither on a single file, use this command:
 slither src/Contract.sol
 ```
 
-Note, this requires configuring the [solc version in the foxar config file](https://book.getfoxar.sh/reference/config/solidity-compiler#solc_version).
+Note, this requires configuring the [solc version in the foxar config file](../reference/config/solidity-compiler#solc_version).
 
 You do not need to provide remappings via the `solc_remaps` option as Slither will automatically detect remappings in a Foxar project. Slither will invoke `spark` to perform the build.
 

versioned_docs/version-1/config/static-analyzers.md

@@ -12,9 +12,9 @@ This document will help you get started. Do not let the document intimidate you.
 
 The [dev Telegram](https://t.me/foxar_rs) is available for any concerns you may have that are not covered in this guide.
 
-First check the [Contribution guidelines](https://github.com/foxar-rs/foxar/blob/master/CONTRIBUTING.md)
+First check the [Contribution guidelines](https://github.com/bchainhub/foxar/blob/master/CONTRIBUTING.md)
 
 Some articles to walk you through the first steps:
 
 - [Make a first contribution](https://dev.to/teddav/foxar-open-source-contribution-1k2d)
-- [Add a cheatcode](https://dev.to/teddav/foxar-add-a-cheatcode-5hc8) (outdated, see the [Foxar dev docs](https://github.com/foxar-rs/foxar/blob/master/docs/dev/cheatcodes.md#adding-a-new-cheatcode) for a shorter but up-to-date tutorial)
+- [Add a cheatcode](https://dev.to/teddav/foxar-add-a-cheatcode-5hc8) (outdated, see the [Foxar dev docs](https://github.com/bchainhub/foxar/blob/master/docs/dev/cheatcodes.md#adding-a-new-cheatcode) for a shorter but up-to-date tutorial)

versioned_docs/version-1/contributing.md

@@ -189,7 +189,7 @@ Failed to create artifact parent folder "/.../MyProject/out/IsolationModeMagic.s
 
 Then there's likely a folder permission issue. Ensure `user` has write access in the project root's folder.
 
-It has been [reported](https://github.com/foxar-rs/foxar/issues/3268) that on linux, canonicalizing paths can result in weird paths (`/_1/...`). This can be resolved by nuking the entire project folder and initializing again.
+It has been [reported](https://github.com/bchainhub/foxar/issues/3268) that on linux, canonicalizing paths can result in weird paths (`/_1/...`). This can be resolved by nuking the entire project folder and initializing again.
 
 ### Connection refused when running `spark build`
 
@@ -211,5 +211,5 @@ You could run `export http_proxy=http://127.0.0.1:7890 https_proxy=http://127.0.
 [config]: ./config/configuration
 [spark-build]: ./reference/spark/spark-build.md
 [console-log]: ./reference/spark-std/console-log.md
-[spark-std]: https://github.com/foxar-rs/spark-std
+[spark-std]: https://github.com/bchainhub/spark-std
 [dstestplus]: https://github.com/transmissions11/solmate/blob/19a4f345970ed39ee6369f343d145e0d4071c18a/src/test/utils/DSTestPlus.sol#L10

versioned_docs/version-1/faq.md

@@ -6,12 +6,12 @@ If you face any issues while installing, check out the [FAQ](../faq.md).
 
 ### Precompiled binaries
 
-Precompiled binaries are available from the [GitHub releases page](https://github.com/foxar-rs/foxar/releases).
+Precompiled binaries are available from the [GitHub releases page](https://github.com/bchainhub/foxar/releases).
 These are better managed by using [Foxarup](#using-foxarup).
 
 ### Using Foxarup
 
-Foxarup is the Foxar toolchain installer. You can find more about it [here](https://github.com/foxar-rs/foxar/blob/master/foxarup/README.md).
+Foxarup is the Foxar toolchain installer. You can find more about it [here](https://github.com/bchainhub/foxar/blob/master/foxarup/README.md).
 
 Open your terminal and run the following command:
 
@@ -62,7 +62,7 @@ Or, by using a single Cargo command:
 cargo install --git https://github.com/foxar-rs/foxar --profile local --locked spark probe pilot shuttle
 ```
 
-Or, by manually building from a local copy of the [Foxar repository](https://github.com/foxar-rs/foxar):
+Or, by manually building from a local copy of the [Foxar repository](https://github.com/bchainhub/foxar):
 
 ```sh
 # clone the repository

versioned_docs/version-1/getting-started/installation.md

@@ -52,7 +52,6 @@ Guides on configuring Foxar.
 - [Integrating with VSCode](./config/vscode.md)
 - [Shell Autocompletion](./config/shell-autocompletion.md)
 - [Static Analyzers](./config/static-analyzers.md)
-- [Integrating with Hardhat](./config/hardhat.md)
 
 ## Tutorials
 
@@ -75,10 +74,10 @@ References, troubleshooting, and more.
 
 - [FAQ](./faq.md)
 - [CLI Reference](./reference/cli/cli-reference)
-- [spark Commands](./reference/spark/)
-- [probe Commands](./reference/probe/)
-- [shuttle Commands](./reference/shuttle/shuttle-reference)
-- [pilot Commands](./reference/pilot/pilot-reference)
+- [Spark Commands](./reference/spark/)
+- [Probe Commands](./reference/probe/)
+- [Shuttle Commands](./reference/shuttle/shuttle-reference)
+- [Pilot Commands](./reference/pilot/pilot-reference)
 - [Config Reference](./reference/config/config-reference)
 - [Cheatcodes Reference](./reference/cheatcodes/cheatcodes-reference)
 - [Spark Standard Library Reference](./reference/spark-std/spark-standart)

versioned_docs/version-1/intro.md

@@ -15,13 +15,13 @@ Cheatcodes are made available through use of the cheatcode address (`0x7109709EC
 > vm.assume(address_ != 0x7109709ECfa91a80626fF3989D68f67F5b1DD12D);
 > ```
 
-You can also access cheatcodes easily via `vm` available in Spark Standard Library's [`Test`](../spark-std/spark-standart/#spark-stds-test) contract.
+You can also access cheatcodes easily via `vm` available in Spark Standard Library's [`Test`](../spark-std/spark-standart#spark-stds-test) contract.
 
 ### Spark Standard Library Cheatcodes
 
 Spark Std implements wrappers around cheatcodes, which combine multiple standard cheatcodes to improve development experience. These are not technically cheatcodes, but rather compositions of Spark's cheatcodes.
 
-You can view the list of Spark Standard Library's cheatcode wrappers [in the references section](../spark-std/std-cheats). You can reference the [Spark Std source code](https://github.com/foxar-rs/spark-std/blob/master/src/Test.sol) to learn more about how the wrappers work under the hood.
+You can view the list of Spark Standard Library's cheatcode wrappers [in the references section](../spark-std/std-cheats). You can reference the [Spark Std source code](https://github.com/bchainhub/spark-std/blob/master/src/Test.sol) to learn more about how the wrappers work under the hood.
 
 ### Cheatcode Types
 

versioned_docs/version-1/reference/cheatcodes/cheatcodes-reference.md

@@ -10,7 +10,7 @@ function ffi(string[] calldata) external returns (bytes memory);
 
 ### Description
 
-Calls an arbitrary command if [`ffi`](../config/testing/#ffi) is enabled.
+Calls an arbitrary command if [`ffi`](../config/testing#ffi) is enabled.
 
 It is generally advised to use this cheat code as a last resort, and to not enable it by default, as anyone who can change the tests of a project will be able to execute arbitrary commands on devices that run the tests.
 

versioned_docs/version-1/reference/cheatcodes/ffi.md

@@ -37,7 +37,7 @@ function isDir(string calldata) external returns (bool);
 
 ### Description
 
-These cheatcodes provided by [spark-std](https://github.com/foxar-rs/spark-std) can be used for filesystem manipulation operations.
+These cheatcodes provided by [spark-std](https://github.com/bchainhub/spark-std) can be used for filesystem manipulation operations.
 
 By default, filesystem access is disallowed and requires the `fs_permission` setting in `foxar.toml`:
 

versioned_docs/version-1/reference/cheatcodes/fs.md

@@ -70,4 +70,4 @@ assertEq(hex"10b7c11bcb51e6", result);
 
 Spark Config
 
-[Config Reference](../config/testing/#rpc_endpoints)
+[Config Reference](../config/testing#rpc_endpoints)

versioned_docs/version-1/reference/cheatcodes/rpc.md

@@ -39,7 +39,7 @@ Exceptions are:
 
 Configuration files are written in the [TOML format](https://toml.io), with simple key-value pairs inside of sections.
 
-This page describes each configuration key in detail. To see the default values, either refer to the specific key in this document, or see the [default config](../../../static/config.default.toml).
+This page describes each configuration key in detail. To see the default values, either refer to the specific key in this document, or see the [default config](../../../../static/config.default.toml).
 
 ### Configuration keys
 

versioned_docs/version-1/reference/config/overview.md

@@ -106,7 +106,7 @@ Use the Flashbots RPC URL (https://rpc.flashbots.net).
 The Etherscan chain.
 
 `--etherscan-api-key` _key_  
-Etherscan API key, or the key of an [Etherscan configuration table](../config/etherscan#etherscan).  
+Etherscan API key, or the key of an [Etherscan configuration table](../config/etherscan).  
 Environment: `ETHERSCAN_API_KEY`
 
 #### Common Options

versioned_docs/version-1/reference/probe/probe-access-list.md

@@ -118,7 +118,7 @@ Use the Flashbots RPC URL (https://rpc.flashbots.net).
 The Etherscan chain.
 
 `--etherscan-api-key` _key_  
-Etherscan API key, or the key of an [Etherscan configuration table](../config/etherscan#etherscan).  
+Etherscan API key, or the key of an [Etherscan configuration table](../config/etherscan).  
 Environment: `ETHERSCAN_API_KEY`
 
 #### Common Options

versioned_docs/version-1/reference/probe/probe-call.md

@@ -50,7 +50,7 @@ Use the Flashbots RPC URL (https://rpc.flashbots.net).
 The Etherscan chain.
 
 `--etherscan-api-key` _key_  
-Etherscan API key, or the key of an [Etherscan configuration table](../config/etherscan#etherscan).  
+Etherscan API key, or the key of an [Etherscan configuration table](../config/etherscan).  
 Environment: `ETHERSCAN_API_KEY`
 
 #### Common Options

versioned_docs/version-1/reference/probe/probe-estimate.md

@@ -30,7 +30,7 @@ If not provided, the source will be outputted to stdout.
 The Etherscan chain.
 
 `--etherscan-api-key` _key_  
-Etherscan API key, or the key of an [Etherscan configuration table](../config/etherscan#etherscan).  
+Etherscan API key, or the key of an [Etherscan configuration table](../config/etherscan).  
 Environment: `ETHERSCAN_API_KEY`
 
 #### Common Options

versioned_docs/version-1/reference/probe/probe-etherscan-source.md

@@ -47,7 +47,7 @@ Output the contract's JSON ABI.
 The Etherscan chain.
 
 `--etherscan-api-key` _key_  
-Etherscan API key, or the key of an [Etherscan configuration table](../config/etherscan#etherscan).  
+Etherscan API key, or the key of an [Etherscan configuration table](../config/etherscan).  
 Environment: `ETHERSCAN_API_KEY`
 
 #### Common Options

versioned_docs/version-1/reference/probe/probe-interface.md

@@ -109,7 +109,7 @@ Use the Flashbots RPC URL (https://rpc.flashbots.net).
 The Etherscan chain.
 
 `--etherscan-api-key` _key_  
-Etherscan API key, or the key of an [Etherscan configuration table](../config/etherscan#etherscan).  
+Etherscan API key, or the key of an [Etherscan configuration table](../config/etherscan).  
 Environment: `ETHERSCAN_API_KEY`
 
 ### EXAMPLES

versioned_docs/version-1/reference/probe/probe-logs.md

@@ -148,7 +148,7 @@ Use the Flashbots RPC URL (https://rpc.flashbots.net).
 The Etherscan chain.
 
 `--etherscan-api-key` _key_  
-Etherscan API key, or the key of an [Etherscan configuration table](../config/etherscan#etherscan).  
+Etherscan API key, or the key of an [Etherscan configuration table](../config/etherscan).  
 Environment: `ETHERSCAN_API_KEY`
 
 #### Display Options

versioned_docs/version-1/reference/probe/probe-send.md

@@ -8,7 +8,7 @@ Using Spark Std is the preferred way of writing tests with Foxar.
 
 What's included:
 
-- `Vm.sol`: Up-to-date [cheatcodes interface](../cheatcodes/cheatcodes-reference/#cheatcodes-interface)
+- `Vm.sol`: Up-to-date [cheatcodes interface](../cheatcodes/cheatcodes-reference#cheatcodes-interface)
 
   ```solidity
   import "spark-std/Vm.sol";

versioned_docs/version-1/reference/spark-std/spark-standart.md

@@ -150,7 +150,7 @@ Use the Flashbots RPC URL (https://rpc.flashbots.net).
 The Etherscan chain.
 
 `--etherscan-api-key` _key_  
-Etherscan API key, or the key of an [Etherscan configuration table](../config/etherscan#etherscan).  
+Etherscan API key, or the key of an [Etherscan configuration table](../config/etherscan).  
 Environment: `ETHERSCAN_API_KEY`
 
 #### Cache Options

versioned_docs/version-1/reference/spark/spark-create.md

@@ -72,7 +72,7 @@ Note: To set the gas price in the execution environment of the script use `--gas
 The Etherscan chain.
 
 `--etherscan-api-key` _key_
-Etherscan API key, or the key of an [Etherscan configuration table](../config/etherscan#etherscan).
+Etherscan API key, or the key of an [Etherscan configuration table](../config/etherscan).
 Environment: `ETHERSCAN_API_KEY`
 
 #### Verification Options

versioned_docs/version-1/reference/spark/spark-script.md

@@ -166,4 +166,4 @@ The location of the Spark-managed solc binaries.
 
 ### BUGS
 
-See https://github.com/foxar-rs/foxar/issues for issues.
+See https://github.com/bchainhub/foxar/issues for issues.

versioned_docs/version-1/reference/spark/spark.md

@@ -60,7 +60,7 @@ $ spark create --rpc-url <your_rpc_url> \
 ## Verifying a pre-existing contract
 
 It is recommended to use the `--verify` flag with `spark create` to automatically verify the contract on explorer after a deployment.
-Note that for Etherscan [`ETHERSCAN_API_KEY`](../reference/config/etherscan#etherscan_api_key) must be set.
+Note that for Etherscan [`ETHERSCAN_API_KEY`](../reference/config/etherscan) must be set.
 
 If you are verifying an already deployed contract, read on.
 

versioned_docs/version-1/spark/deploying.md

@@ -146,7 +146,7 @@ This is something to be mindful of when designing target contracts, as target co
 
 ### Invariant Test Helper Functions
 
-Invariant test helper functions are included in [`spark-std`](https://github.com/foxar-rs/spark-std/blob/master/src/StdInvariant.sol) to allow for configurable invariant test setup. The helper functions are outlined below:
+Invariant test helper functions are included in [`spark-std`](https://github.com/bchainhub/spark-std/blob/master/src/StdInvariant.sol) to allow for configurable invariant test setup. The helper functions are outlined below:
 
 | Function                                                                   | Description                                                                                                                                                                                         |
 | -------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

versioned_docs/version-1/spark/invariant-testing.md

@@ -4,7 +4,7 @@ title: Writing Tests
 
 Tests are written in Solidity. If the test function reverts, the test fails, otherwise it passes.
 
-Let's go over the most common way of writing tests, using the [Spark Standard Library](https://github.com/foxar-rs/spark-std)'s `Test` contract, which is the preferred way of writing tests with Spark.
+Let's go over the most common way of writing tests, using the [Spark Standard Library](https://github.com/bchainhub/spark-std)'s `Test` contract, which is the preferred way of writing tests with Spark.
 
 In this section, we'll go over the basics using the functions from the Spark Std's `Test` contract, which is itself a superset of [DSTest](https://github.com/dapphub/ds-test). You will learn how to use more advanced stuff from the Spark Standard Library [soon](./spark-std.md).