-
-
Notifications
You must be signed in to change notification settings - Fork 876
Closed
Milestone
Description
If you want to build a UI that shows runs across multiple jobs it's difficult because the hooks return no info about the job.
I suggest we return the job "id" from them (which is actually the slug in the database).
{
job {
//note that this is what we call the "slug" in the database
id: "......",
},
//rest of the payload
}This would creating v3 versions of the following API endpoints that return the job.id
- https://github.com/triggerdotdev/trigger.dev/blob/main/apps/webapp/app/routes/api.v2.runs.%24runId.ts
- https://github.com/triggerdotdev/trigger.dev/blob/main/apps/webapp/app/routes/api.v2.runs.%24runId.statuses.ts
- https://github.com/triggerdotdev/trigger.dev/blob/main/apps/webapp/app/routes/api.v2.events.%24eventId.ts
Core schema updates (add job.id)
- GetRunStatusesSchema:
trigger.dev/packages/core/src/schemas/api.ts
Line 1061 in 29edcd3
export const GetRunStatusesSchema = z.object({ - GetRunSchema:
trigger.dev/packages/core/src/schemas/runs.ts
Line 107 in 29edcd3
export const GetRunsSchema = z.object({ - GetEventSchema:
export const GetEventSchema = z.object({
The SDK API client URLs need updating to be v3 instead of v2
getEventgetRungetRunStatuses
https://github.com/triggerdotdev/trigger.dev/blob/main/packages/trigger-sdk/src/apiClient.ts#L446
The React package URLs need updating to be v3 instead of v2:
Metadata
Metadata
Assignees
Labels
No labels