Skip to content

Commit 306a889

Browse files
committed
done?
1 parent 235926e commit 306a889

File tree

16 files changed

+92
-122
lines changed

16 files changed

+92
-122
lines changed

src/content/docs/d1/tutorials/build-an-api-to-access-d1/index.mdx

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -223,15 +223,15 @@ Make a note of the displayed `database_name` and `database_id`. You will use thi
223223
1. From your `d1-http` folder, open the [Wrangler configuration](/workers/wrangler/configuration) file, Wrangler's configuration file.
224224
2. Add the following binding in the file. Make sure that the `database_name` and the `database_id` are correct.
225225

226-
import { WranglerConfig } from "~/components";
226+
import { WranglerConfig } from "~/components";
227227

228228
<WranglerConfig>
229229

230-
````toml
231-
[[d1_databases]]
232-
binding = "DB" # i.e. available in your Worker on env.DB
233-
database_name = "d1-http-example"
234-
database_id = "1234567890"
230+
```toml
231+
[[d1_databases]]
232+
binding = "DB" # i.e. available in your Worker on env.DB
233+
database_name = "d1-http-example"
234+
database_id = "1234567890"
235235
```
236236

237237
</WranglerConfig>
@@ -483,4 +483,7 @@ In this tutorial, you have:
483483
## Next steps
484484

485485
You can check out a similar implementation that uses Zod for validation in [this GitHub repository](https://github.com/elithrar/http-api-d1-example). If you want to build an OpenAPI compliant API for your D1 database, you should use the [Cloudflare Workers OpenAPI 3.1 template](https://github.com/cloudflare/workers-sdk/tree/main/templates/worker-openapi).
486-
````
486+
487+
```
488+
489+
```

src/content/docs/durable-objects/get-started/tutorial-with-sql-api.mdx

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -205,13 +205,6 @@ import { WranglerConfig } from "~/components";
205205
[[durable_objects.bindings]]
206206
name = "MY_DURABLE_OBJECT"
207207
class_name = "MyDurableObject"
208-
209-
# or
210-
211-
[durable_objects]
212-
bindings = [
213-
{ name = "MY_DURABLE_OBJECT", class_name = "MyDurableObject" }
214-
]
215208
```
216209

217210
</WranglerConfig>

src/content/docs/durable-objects/get-started/walkthrough.mdx

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -201,13 +201,6 @@ import { WranglerConfig } from "~/components";
201201
[[durable_objects.bindings]]
202202
name = "MY_DURABLE_OBJECT"
203203
class_name = "MyDurableObject"
204-
205-
# or
206-
207-
[durable_objects]
208-
bindings = [
209-
{ name = "MY_DURABLE_OBJECT", class_name = "MyDurableObject" }
210-
]
211204
```
212205

213206
</WranglerConfig>

src/content/docs/durable-objects/reference/durable-objects-migrations.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -106,6 +106,8 @@ The new beta version of Durable Objects is available where each Durable Object h
106106

107107
To allow a new Durable Object class to use a SQLite storage backend, use `new_sqlite_classes` on the migration in your Worker's [Wrangler configuration](/workers/wrangler/configuration) file:
108108

109+
<WranglerConfig>
110+
109111
```toml
110112
[[migrations]]
111113
tag = "v1" # Should be unique for each entry

src/content/docs/kv/get-started.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -171,11 +171,11 @@ To bind your KV namespace to your Worker:
171171
<Steps>
172172
1. In your [Wrangler configuration](/workers/wrangler/configuration) file, add the following with the values generated in your terminal from [step 2](/kv/get-started/#2-create-a-kv-namespace):
173173

174-
import { WranglerConfig } from "~/components";
174+
import { WranglerConfig } from "~/components";
175175

176176
<WranglerConfig>
177177

178-
````toml
178+
```toml
179179
[[kv_namespaces]]
180180
binding = "<BINDING_NAME>"
181181
id = "<BINDING_ID>"
@@ -240,7 +240,7 @@ Instead of using `--binding`, you can also use `--namespace-id` to specify which
240240

241241
```sh
242242
npx wrangler kv key put --namespace-id=<BINDING_ID> "<KEY>" "<VALUE>"
243-
````
243+
```
244244

245245
```sh output
246246
Writing the value "<VALUE>" to key "<KEY>" on namespace <BINDING_ID>.
@@ -355,7 +355,7 @@ To have `wrangler dev` connect to your Workers KV namespace running on Cloudflar
355355
let value = await env.BINDING_NAME.get("KEY");
356356
```
357357

358-
</Steps>
358+
</Steps>
359359

360360
Your Worker code should look like this:
361361

src/content/docs/pages/functions/wrangler-configuration.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -218,6 +218,8 @@ Unlike [Workers Environments](/workers/wrangler/configuration/#environments), `p
218218

219219
Refer to the following [Wrangler configuration](/workers/wrangler/configuration) file for an example of how to override preview deployment configuration:
220220

221+
<WranglerConfig>
222+
221223
```toml
222224
name = "my-pages-site"
223225
pages_build_output_dir = "./dist"

src/content/docs/pub-sub/examples/connect-rust.mdx

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,6 @@ pcx_content_type: example
44
type: example
55
summary: Connect to a Broker using a Rust-based MQTT client.
66
description: Connect to a Broker using a Rust-based MQTT client.
7-
87
---
98

109
Below is an example using the [paho.mqtt.rust](https://github.com/eclipse/paho.mqtt.rust) crate with the TOKEN authentication mode configured on a Broker.

src/content/docs/queues/tutorials/web-crawler-with-browser-rendering/index.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -155,6 +155,8 @@ Adding the `max_batch_timeout` of 60 seconds to the consumer queue is important
155155

156156
Your final [Wrangler configuration](/workers/wrangler/configuration) file should look similar to the one below.
157157

158+
<WranglerConfig>
159+
158160
```toml
159161
#:schema node_modules/wrangler/config-schema.json
160162
name = "web-crawler"

src/content/docs/workers/configuration/compatibility-dates.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ However, even though you do not need to update the `compatibility_date` field, i
2525

2626
#### Via Wrangler
2727

28-
The compatibility date can be set in a Worker's [[Wrangler configuration](/workers/wrangler/configuration) file](/workers/wrangler/configuration/) file.
28+
The compatibility date can be set in a Worker's [Wrangler configuration](/workers/wrangler/configuration) file.
2929

3030
import { WranglerConfig } from "~/components";
3131

@@ -107,6 +107,8 @@ As additional Node.js APIs are added, they will be made available under the `nod
107107

108108
The Node.js `AsyncLocalStorage` API is a particularly useful feature for Workers. To enable only the `AsyncLocalStorage` API, use the `nodejs_als` compatibility flag.
109109

110+
<WranglerConfig>
111+
110112
```toml title="wrangler.toml"
111113
compatibility_flags = [ "nodejs_als" ]
112114
```

src/content/docs/workers/observability/logs/workers-logs.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ You must add the observability setting for your Worker to write logs to Workers
3232

3333
<WranglerConfig>
3434

35-
````toml
35+
```toml
3636
[observability]
3737
enabled = true
3838
head_sampling_rate = 1 # optional. default = 1.
@@ -115,7 +115,7 @@ export default {
115115
});
116116
},
117117
};
118-
````
118+
```
119119

120120
</TabItem> <TabItem label="Service Worker" icon="seti:javascript">
121121

0 commit comments

Comments
 (0)