Skip to content

Commit d0d5a69

Browse files
committed
Added versions to Supabase management docs examples that are missing them
1 parent ee033a1 commit d0d5a69

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

docs/integrations/apis/supabase/management.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -125,6 +125,7 @@ Now, you can use the `db` instance to add a trigger to run a job when a row is i
125125
client.defineJob({
126126
id: "supabase-trigger",
127127
name: "Supabase Trigger",
128+
version: "1.0.0",
128129
trigger: db.onInserted({
129130
table: "todos",
130131
}),
@@ -140,6 +141,7 @@ You can add additional filters to the trigger by passing a `filter` object:
140141
client.defineJob({
141142
id: "supabase-trigger",
142143
name: "Supabase Trigger",
144+
version: "1.0.0",
143145
trigger: db.onUpdated({
144146
table: "todos",
145147
// Only trigger if the todo is marked as completed
@@ -164,6 +166,7 @@ You can also listen for multiple different events using the `on` trigger:
164166
client.defineJob({
165167
id: "supabase-trigger",
166168
name: "Supabase Trigger",
169+
version: "1.0.0",
167170
trigger: db.on({
168171
table: "todos",
169172
events: ["INSERT", "UPDATE"] // Trigger on both insert and update events
@@ -206,6 +209,7 @@ const db = supabase.db<Database>("https://<your project id>.supabase.co");
206209
client.defineJob({
207210
id: "supabase-trigger",
208211
name: "Supabase Trigger",
212+
version: "1.0.0",
209213
trigger: db.onUpdated({
210214
table: "todos",
211215
}),

0 commit comments

Comments
 (0)