create-cloesce 0.3.2 → 0.3.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -2,14 +2,14 @@
|
|
|
2
2
|
// It does not replace the wrangler config, but does result in a generated version.
|
|
3
3
|
env {
|
|
4
4
|
// The `d1` block describes all D1 database bindings
|
|
5
|
-
d1 {
|
|
6
|
-
db
|
|
5
|
+
d1 {
|
|
6
|
+
db
|
|
7
7
|
// db2
|
|
8
8
|
}
|
|
9
|
-
|
|
9
|
+
|
|
10
10
|
// The `r2` block describes all R2 bucket bindings
|
|
11
|
-
r2 {
|
|
12
|
-
bucket
|
|
11
|
+
r2 {
|
|
12
|
+
bucket
|
|
13
13
|
// bucket2
|
|
14
14
|
}
|
|
15
15
|
}
|
|
@@ -26,7 +26,7 @@ model WeatherReport {
|
|
|
26
26
|
primary {
|
|
27
27
|
id: int
|
|
28
28
|
}
|
|
29
|
-
|
|
29
|
+
|
|
30
30
|
// A `nav` block describes a relationship between two models.
|
|
31
31
|
// In this case, it is a one-to-many relationship between WeatherReport and Weather,
|
|
32
32
|
// where WeatherReport has many Weathers.
|
|
@@ -35,11 +35,11 @@ model WeatherReport {
|
|
|
35
35
|
// references the `id` field in the WeatherReport model.
|
|
36
36
|
//
|
|
37
37
|
// This will resolve to a navigation field named `weatherEntries` in the WeatherReport model,
|
|
38
|
-
//which is an array of Weather objects.
|
|
38
|
+
// which is an array of Weather objects.
|
|
39
39
|
nav (Weather::weatherReportId) {
|
|
40
40
|
weatherEntries
|
|
41
41
|
}
|
|
42
|
-
|
|
42
|
+
|
|
43
43
|
// All fields that are not apart of a block are just regular fields in the table.
|
|
44
44
|
title: string
|
|
45
45
|
description: string
|
|
@@ -51,21 +51,24 @@ model Weather {
|
|
|
51
51
|
primary {
|
|
52
52
|
id: int
|
|
53
53
|
}
|
|
54
|
-
|
|
54
|
+
|
|
55
55
|
// A `foreign` block describes a one to one relationship between two models.
|
|
56
56
|
// It translates directly to a foreign key constraint in the database (`weatherReportId` references `id` in WeatherReport).
|
|
57
57
|
foreign (WeatherReport::id) {
|
|
58
58
|
weatherReportId
|
|
59
|
-
|
|
59
|
+
|
|
60
|
+
|
|
60
61
|
// A `nav` block inside a `foreign` block generates a navigation field,
|
|
61
62
|
// meaning the backend and client will have a WeatherReport object named `weatherReport` nested inside the Weather model.
|
|
62
|
-
nav {
|
|
63
|
+
nav {
|
|
64
|
+
weatherReport
|
|
65
|
+
}
|
|
63
66
|
}
|
|
64
67
|
|
|
65
68
|
r2 (bucket, "weather/photos/{id}.jpg") {
|
|
66
69
|
photo
|
|
67
70
|
}
|
|
68
|
-
|
|
71
|
+
|
|
69
72
|
dateTime: date
|
|
70
73
|
location: string
|
|
71
74
|
temperature: int
|
|
@@ -83,7 +86,7 @@ api Weather {
|
|
|
83
86
|
// In this case, `uploadPhoto` accepts the Wrangler environment (dependency injected),
|
|
84
87
|
// and a stream (the photo to be uploaded).
|
|
85
88
|
post uploadPhoto(self, e: env, s: stream) -> void
|
|
86
|
-
|
|
89
|
+
|
|
87
90
|
// By default, Cloesce will hydrate a `self` instance with all 1:1, KV, R2,
|
|
88
91
|
// and the near side of 1:M/M:M relationships.
|
|
89
92
|
//
|
|
@@ -98,5 +101,7 @@ api Weather {
|
|
|
98
101
|
//
|
|
99
102
|
// In this case, the include tree has only the `photo` field of `Weather`.
|
|
100
103
|
source R2Only for Weather {
|
|
101
|
-
include {
|
|
104
|
+
include {
|
|
105
|
+
photo
|
|
106
|
+
}
|
|
102
107
|
}
|