Let's speak why I merged JobResult and JobStatus together: Both methods actually called jobqueue.JobStatus(), so performance-wise there's no real difference and it feels to me that it makes the code simpler: You don't have to decide which method to call, you just get all the data about a job in one call. We could split those again when we see some perf issues with retrieving logs on each status check but I don't think we should optimize prematurely. Let's leave some work for the future us. |
||
|---|---|---|
| .. | ||
| client.go | ||
| json.go | ||
| server.go | ||
| server_test.go | ||