Skip to content

Commit dce9054

Browse files
jzakijzaki
committed
Move snippets all versions
1 parent 489c6cf commit dce9054

File tree

13 files changed

+48
-48
lines changed

13 files changed

+48
-48
lines changed

‎docs/docs/aztec/concepts/fees.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ sidebar_position: 4
44
tags: [fees]
55
---
66

7-
import { Why_Fees } from '/components/snippets';
7+
import { Why_Fees } from '@site/src/components/Snippets/snippets';
88

99
<Why_Fees />
1010

@@ -46,7 +46,7 @@ More information about the design/choices can be found in the fees section of th
4646

4747
As part of a transaction the follow gas settings are available to be defined by the user.
4848

49-
import { Gas_Settings_Components, Gas_Settings, Tx_Teardown_Phase } from '/components/snippets';
49+
import { Gas_Settings_Components, Gas_Settings, Tx_Teardown_Phase } from '@site/src/components/Snippets/snippets';
5050

5151
<Gas_Settings />
5252

‎docs/docs/developers/getting_started.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ You'll know the sandbox is ready to go when you see something like this:
8080
8181
## Using the sandbox test accounts
8282
83-
import { CLI_Add_Test_Accounts } from '/components/snippets';
83+
import { CLI_Add_Test_Accounts } from '@site/src/components/Snippets/snippets';
8484
8585
<CLI_Add_Test_Accounts />
8686

‎docs/docs/developers/guides/js_apps/pay_fees.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ import { FeeJuicePaymentMethod } from "@aztec/aztec.js";
8686

8787
**The equivalent to specify fees via CLI...**
8888

89-
import { CLI_Fees } from '/components/snippets';
89+
import { CLI_Fees } from '@site/src/components/Snippets/snippets';
9090

9191
<CLI_Fees />
9292

@@ -201,7 +201,7 @@ The `paymentMethod` is an object for the type of payment. Each of the implementa
201201

202202
#include_code gas_settings_vars yarn-project/stdlib/src/gas/gas_settings.ts javascript
203203

204-
import { Gas_Settings_Components, Gas_Settings } from '/components/snippets';
204+
import { Gas_Settings_Components, Gas_Settings } from '@site/src/components/Snippets/snippets';
205205

206206
<Gas_Settings />
207207

‎docs/docs/developers/reference/environment_reference/cli_wallet_reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ You can create arbitrary aliases with the `alias` command. For example `aztec-wa
4343

4444
## Paying Fees
4545

46-
import { Why_Fees, CLI_Fees } from '/components/snippets';
46+
import { Why_Fees, CLI_Fees } from '@site/src/components/Snippets/snippets';
4747

4848
<Why_Fees />
4949

‎docs/components/snippets.js renamed to ‎docs/src/components/Snippets/snippets.js

File renamed without changes.

‎docs/versioned_docs/version-v0.85.0-alpha-testnet.0/aztec/concepts/fees.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ sidebar_position: 4
44
tags: [fees]
55
---
66

7-
import { Why_Fees } from '/components/snippets';
7+
import { Why_Fees } from '@site/src/components/Snippets/snippets';
88

99
<Why_Fees />
1010

@@ -46,13 +46,13 @@ More information about the design/choices can be found in the fees section of th
4646

4747
As part of a transaction the follow gas settings are available to be defined by the user.
4848

49-
import { Gas_Settings_Components, Gas_Settings, Tx_Teardown_Phase } from '/components/snippets';
49+
import { Gas_Settings_Components, Gas_Settings, Tx_Teardown_Phase } from '@site/src/components/Snippets/snippets';
5050

5151
<Gas_Settings />
5252

5353
These are:
5454

55-
```javascript title="gas_settings_vars" showLineNumbers
55+
```javascript title="gas_settings_vars" showLineNumbers
5656
/** Gas usage and fees limits set by the transaction sender for different dimensions and phases. */
5757
export class GasSettings {
5858
constructor(

‎docs/versioned_docs/version-v0.85.0-alpha-testnet.0/developers/getting_started.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ You'll know the sandbox is ready to go when you see something like this:
8080
8181
## Using the sandbox test accounts
8282
83-
import { CLI_Add_Test_Accounts } from '/components/snippets';
83+
import { CLI_Add_Test_Accounts } from '@site/src/components/Snippets/snippets';
8484
8585
<CLI_Add_Test_Accounts />
8686

‎docs/versioned_docs/version-v0.85.0-alpha-testnet.0/developers/guides/js_apps/pay_fees.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ One way of bridging of tokens is described fully [here](../../../developers/tuto
4444

4545
First get the node info and create a public client pointing to the sandbox's anvil L1 node (from foundry):
4646

47-
```javascript title="get_node_info_pub_client" showLineNumbers
47+
```javascript title="get_node_info_pub_client" showLineNumbers
4848
const info = await pxe.getNodeInfo();
4949
const publicClient = getPublicClient({
5050
l1RpcUrls: ['http://localhost:8545'],
@@ -62,7 +62,7 @@ import { L1FeeJuicePortalManager } from "@aztec/aztec.js";
6262

6363
Create a new fee juice portal manager and bridge fee juice publicly to Aztec:
6464

65-
```javascript title="bridge_fee_juice" showLineNumbers
65+
```javascript title="bridge_fee_juice" showLineNumbers
6666
const portal = await L1FeeJuicePortalManager.new(pxe, publicClient, walletClient, log);
6767
const claim = await portal.bridgeTokensPublic(recipient, amount, true /* mint */);
6868
```
@@ -95,7 +95,7 @@ Note: this example is a public token transfer call, but can equally be a private
9595
import { FeeJuicePaymentMethod } from "@aztec/aztec.js";
9696
```
9797

98-
```javascript title="pay_fee_juice_send" showLineNumbers
98+
```javascript title="pay_fee_juice_send" showLineNumbers
9999
const paymentMethod = new FeeJuicePaymentMethod(aliceAddress);
100100
const { transactionFee } = await bananaCoin.methods
101101
.transfer_in_public(aliceAddress, bobAddress, 1n, 0n)
@@ -107,7 +107,7 @@ const { transactionFee } = await bananaCoin.methods
107107

108108
**The equivalent to specify fees via CLI...**
109109

110-
import { CLI_Fees } from '/components/snippets';
110+
import { CLI_Fees } from '@site/src/components/Snippets/snippets';
111111

112112
<CLI_Fees />
113113

@@ -119,7 +119,7 @@ Here we will use the `claim` object previously from the bridging section, and th
119119
import { FeeJuicePaymentMethodWithClaim } from "@aztec/aztec.js";
120120
```
121121

122-
```javascript title="claim_and_deploy" showLineNumbers
122+
```javascript title="claim_and_deploy" showLineNumbers
123123
const wallet = await account.getWallet();
124124
const paymentMethod = new FeeJuicePaymentMethodWithClaim(wallet, claim);
125125
const sentTx = account.deploy({ fee: { paymentMethod } });
@@ -138,7 +138,7 @@ Claiming bridged fee juice and using it to pay for transaction fees results in f
138138

139139
Calling a function, in this case checking the balance of the fee juice contract:
140140

141-
```javascript title="claim_and_pay" showLineNumbers
141+
```javascript title="claim_and_pay" showLineNumbers
142142
const paymentMethod = new FeeJuicePaymentMethodWithClaim(bobWallet, claim);
143143
const receipt = await feeJuiceContract
144144
.withWallet(bobWallet)
@@ -176,7 +176,7 @@ await pxe.registerContract(fpcContract);
176176

177177
The fee payment method is created and used as follows, with similar syntax for private or public fee payments:
178178

179-
```javascript title="fpc" showLineNumbers
179+
```javascript title="fpc" showLineNumbers
180180
const tx = await bananaCoin.methods
181181
.transfer_in_public(aliceAddress, bobAddress, bananasToSendToBob, 0)
182182
.send({
@@ -238,7 +238,7 @@ You can find the corresponding CLI command info [here](../../reference/environme
238238

239239
Functions pertaining to sending a transaction, such as `deploy` and `send`, each include a `fee` variable defined with the following (optional) parameters:
240240

241-
```javascript title="user_fee_options" showLineNumbers
241+
```javascript title="user_fee_options" showLineNumbers
242242
/** Fee options as set by a user. */
243243
export type UserFeeOptions = {
244244
/** The fee payment method to use */
@@ -260,7 +260,7 @@ export type UserFeeOptions = {
260260

261261
The `paymentMethod` is an object for the type of payment. Each of the implementations can be found [here](https://github.com/AztecProtocol/aztec-packages/blob/v0.85.0-alpha-testnet.0/yarn-project/aztec.js/src/fee). For example:
262262

263-
```javascript title="fee_juice_method" showLineNumbers
263+
```javascript title="fee_juice_method" showLineNumbers
264264
/**
265265
* Pay fee directly in the Fee Juice.
266266
*/
@@ -271,7 +271,7 @@ export class FeeJuicePaymentMethod implements FeePaymentMethod {
271271
272272
### Gas Settings
273273
274-
```javascript title="gas_settings_vars" showLineNumbers
274+
```javascript title="gas_settings_vars" showLineNumbers
275275
/** Gas usage and fees limits set by the transaction sender for different dimensions and phases. */
276276
export class GasSettings {
277277
constructor(
@@ -284,7 +284,7 @@ export class GasSettings {
284284
> <sup><sub><a href="https://github.com/AztecProtocol/aztec-packages/blob/v0.85.0-alpha-testnet.0/yarn-project/stdlib/src/gas/gas_settings.ts#L11-L20" target="_blank" rel="noopener noreferrer">Source code: yarn-project/stdlib/src/gas/gas_settings.ts#L11-L20</a></sub></sup>
285285
286286
287-
import { Gas_Settings_Components, Gas_Settings } from '/components/snippets';
287+
import { Gas_Settings_Components, Gas_Settings } from '@site/src/components/Snippets/snippets';
288288
289289
<Gas_Settings />
290290

‎docs/versioned_docs/version-v0.85.0-alpha-testnet.0/developers/reference/environment_reference/cli_wallet_reference.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ You can create arbitrary aliases with the `alias` command. For example `aztec-wa
4343

4444
## Paying Fees
4545

46-
import { Why_Fees, CLI_Fees } from '/components/snippets';
46+
import { Why_Fees, CLI_Fees } from '@site/src/components/Snippets/snippets';
4747

4848
<Why_Fees />
4949

@@ -91,15 +91,15 @@ In the sandbox pre-loaded test accounts can be used to cover fee juice when depl
9191

9292
First import them:
9393

94-
```bash title="import-test-accounts" showLineNumbers
94+
```bash title="import-test-accounts" showLineNumbers
9595
aztec-wallet import-test-accounts
9696
```
9797
> <sup><sub><a href="https://github.com/AztecProtocol/aztec-packages/blob/v0.85.0-alpha-testnet.0/yarn-project/cli-wallet/test/flows/basic.sh#L9-L11" target="_blank" rel="noopener noreferrer">Source code: yarn-project/cli-wallet/test/flows/basic.sh#L9-L11</a></sub></sup>
9898
9999

100100
Then use the alias (test0, test1...) when paying in fee juice. Eg to create accounts:
101101

102-
```bash title="declare-accounts" showLineNumbers
102+
```bash title="declare-accounts" showLineNumbers
103103
aztec-wallet create-account -a alice --payment method=fee_juice,feePayer=test0
104104
aztec-wallet create-account -a bob --payment method=fee_juice,feePayer=test0
105105
```
@@ -112,7 +112,7 @@ aztec-wallet create-account -a bob --payment method=fee_juice,feePayer=test0
112112

113113
First register an account, mint the fee asset on L1 and bridge it to fee juice:
114114

115-
```bash title="bridge-fee-juice" showLineNumbers
115+
```bash title="bridge-fee-juice" showLineNumbers
116116
aztec-wallet create-account -a main --register-only
117117
aztec-wallet bridge-fee-juice 1000000000000000000 main --mint --no-wait
118118
```
@@ -122,7 +122,7 @@ aztec-wallet bridge-fee-juice 1000000000000000000 main --mint --no-wait
122122
You'll have to wait for two blocks to pass for bridged fee juice to be ready on Aztec.
123123
For the sandbox you do this by putting through two arbitrary transactions. Eg:
124124

125-
```bash title="force-two-blocks" showLineNumbers
125+
```bash title="force-two-blocks" showLineNumbers
126126
aztec-wallet deploy counter_contract@Counter --init initialize --args 0 accounts:test0 -f test0 -a counter
127127
aztec-wallet send increment -ca counter --args accounts:test0 accounts:test0 -f test0
128128
```
@@ -131,7 +131,7 @@ aztec-wallet send increment -ca counter --args accounts:test0 accounts:test0 -f
131131

132132
Now the funded account can deploy itself with the bridged fees, claiming the bridged fee juice and deploying the contract in one transaction:
133133

134-
```bash title="claim-deploy-account" showLineNumbers
134+
```bash title="claim-deploy-account" showLineNumbers
135135
aztec-wallet deploy-account -f main --payment method=fee_juice,claim
136136
```
137137
> <sup><sub><a href="https://github.com/AztecProtocol/aztec-packages/blob/v0.85.0-alpha-testnet.0/yarn-project/cli-wallet/test/flows/create_account_pay_native.sh#L25-L27" target="_blank" rel="noopener noreferrer">Source code: yarn-project/cli-wallet/test/flows/create_account_pay_native.sh#L25-L27</a></sub></sup>

‎docs/versioned_docs/version-v0.85.0/aztec/concepts/fees.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ sidebar_position: 4
44
tags: [fees]
55
---
66

7-
import { Why_Fees } from '/components/snippets';
7+
import { Why_Fees } from '@site/src/components/Snippets/snippets';
88

99
<Why_Fees />
1010

@@ -46,13 +46,13 @@ More information about the design/choices can be found in the fees section of th
4646

4747
As part of a transaction the follow gas settings are available to be defined by the user.
4848

49-
import { Gas_Settings_Components, Gas_Settings, Tx_Teardown_Phase } from '/components/snippets';
49+
import { Gas_Settings_Components, Gas_Settings, Tx_Teardown_Phase } from '@site/src/components/Snippets/snippets';
5050

5151
<Gas_Settings />
5252

5353
These are:
5454

55-
```javascript title="gas_settings_vars" showLineNumbers
55+
```javascript title="gas_settings_vars" showLineNumbers
5656
/** Gas usage and fees limits set by the transaction sender for different dimensions and phases. */
5757
export class GasSettings {
5858
constructor(

‎docs/versioned_docs/version-v0.85.0/developers/getting_started.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ You'll know the sandbox is ready to go when you see something like this:
8080
8181
## Using the sandbox test accounts
8282
83-
import { CLI_Add_Test_Accounts } from '/components/snippets';
83+
import { CLI_Add_Test_Accounts } from '@site/src/components/Snippets/snippets';
8484
8585
<CLI_Add_Test_Accounts />
8686

‎docs/versioned_docs/version-v0.85.0/developers/guides/js_apps/pay_fees.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ One way of bridging of tokens is described fully [here](../../../developers/tuto
4444

4545
First get the node info and create a public client pointing to the sandbox's anvil L1 node (from foundry):
4646

47-
```javascript title="get_node_info_pub_client" showLineNumbers
47+
```javascript title="get_node_info_pub_client" showLineNumbers
4848
const info = await pxe.getNodeInfo();
4949
const publicClient = getPublicClient({
5050
l1RpcUrls: ['http://localhost:8545'],
@@ -62,7 +62,7 @@ import { L1FeeJuicePortalManager } from "@aztec/aztec.js";
6262

6363
Create a new fee juice portal manager and bridge fee juice publicly to Aztec:
6464

65-
```javascript title="bridge_fee_juice" showLineNumbers
65+
```javascript title="bridge_fee_juice" showLineNumbers
6666
const portal = await L1FeeJuicePortalManager.new(pxe, publicClient, walletClient, log);
6767
const claim = await portal.bridgeTokensPublic(recipient, amount, true /* mint */);
6868
```
@@ -95,7 +95,7 @@ Note: this example is a public token transfer call, but can equally be a private
9595
import { FeeJuicePaymentMethod } from "@aztec/aztec.js";
9696
```
9797

98-
```javascript title="pay_fee_juice_send" showLineNumbers
98+
```javascript title="pay_fee_juice_send" showLineNumbers
9999
const paymentMethod = new FeeJuicePaymentMethod(aliceAddress);
100100
const { transactionFee } = await bananaCoin.methods
101101
.transfer_in_public(aliceAddress, bobAddress, 1n, 0n)
@@ -107,7 +107,7 @@ const { transactionFee } = await bananaCoin.methods
107107

108108
**The equivalent to specify fees via CLI...**
109109

110-
import { CLI_Fees } from '/components/snippets';
110+
import { CLI_Fees } from '@site/src/components/Snippets/snippets';
111111

112112
<CLI_Fees />
113113

@@ -119,7 +119,7 @@ Here we will use the `claim` object previously from the bridging section, and th
119119
import { FeeJuicePaymentMethodWithClaim } from "@aztec/aztec.js";
120120
```
121121

122-
```javascript title="claim_and_deploy" showLineNumbers
122+
```javascript title="claim_and_deploy" showLineNumbers
123123
const wallet = await account.getWallet();
124124
const paymentMethod = new FeeJuicePaymentMethodWithClaim(wallet, claim);
125125
const sentTx = account.deploy({ fee: { paymentMethod } });
@@ -138,7 +138,7 @@ Claiming bridged fee juice and using it to pay for transaction fees results in f
138138

139139
Calling a function, in this case checking the balance of the fee juice contract:
140140

141-
```javascript title="claim_and_pay" showLineNumbers
141+
```javascript title="claim_and_pay" showLineNumbers
142142
const paymentMethod = new FeeJuicePaymentMethodWithClaim(bobWallet, claim);
143143
const receipt = await feeJuiceContract
144144
.withWallet(bobWallet)
@@ -176,7 +176,7 @@ await pxe.registerContract(fpcContract);
176176

177177
The fee payment method is created and used as follows, with similar syntax for private or public fee payments:
178178

179-
```javascript title="fpc" showLineNumbers
179+
```javascript title="fpc" showLineNumbers
180180
const tx = await bananaCoin.methods
181181
.transfer_in_public(aliceAddress, bobAddress, bananasToSendToBob, 0)
182182
.send({
@@ -238,7 +238,7 @@ You can find the corresponding CLI command info [here](../../reference/environme
238238

239239
Functions pertaining to sending a transaction, such as `deploy` and `send`, each include a `fee` variable defined with the following (optional) parameters:
240240

241-
```javascript title="user_fee_options" showLineNumbers
241+
```javascript title="user_fee_options" showLineNumbers
242242
/** Fee options as set by a user. */
243243
export type UserFeeOptions = {
244244
/** The fee payment method to use */
@@ -260,7 +260,7 @@ export type UserFeeOptions = {
260260

261261
The `paymentMethod` is an object for the type of payment. Each of the implementations can be found [here](https://github.com/AztecProtocol/aztec-packages/blob/v0.85.0/yarn-project/aztec.js/src/fee). For example:
262262

263-
```javascript title="fee_juice_method" showLineNumbers
263+
```javascript title="fee_juice_method" showLineNumbers
264264
/**
265265
* Pay fee directly in the Fee Juice.
266266
*/
@@ -271,7 +271,7 @@ export class FeeJuicePaymentMethod implements FeePaymentMethod {
271271
272272
### Gas Settings
273273
274-
```javascript title="gas_settings_vars" showLineNumbers
274+
```javascript title="gas_settings_vars" showLineNumbers
275275
/** Gas usage and fees limits set by the transaction sender for different dimensions and phases. */
276276
export class GasSettings {
277277
constructor(
@@ -284,7 +284,7 @@ export class GasSettings {
284284
> <sup><sub><a href="https://github.com/AztecProtocol/aztec-packages/blob/v0.85.0/yarn-project/stdlib/src/gas/gas_settings.ts#L11-L20" target="_blank" rel="noopener noreferrer">Source code: yarn-project/stdlib/src/gas/gas_settings.ts#L11-L20</a></sub></sup>
285285
286286
287-
import { Gas_Settings_Components, Gas_Settings } from '/components/snippets';
287+
import { Gas_Settings_Components, Gas_Settings } from '@site/src/components/Snippets/snippets';
288288
289289
<Gas_Settings />
290290

0 commit comments

Comments
 (0)