mukimovd/tercul-backend
1
0
Fork 0
mirror of https://github.com/SamyRai/tercul-backend.git synced 2025-12-27 01:41:34 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
85d036330c
tercul-backend/api
History
google-labs-jules[bot] 85d036330c fix: handle fatal worker startup error gracefully 
Replaces a raw `panic` in the `asynq` server startup with a call to `log.Fatalf`.

If the job server fails to start, it is an unrecoverable, fatal error. Using `log.Fatalf` ensures the application exits with a clear error message and a non-zero status code, which is a more conventional and robust way to handle fatal startup errors than panicking.
2025-10-05 11:11:40 +00:00
..
.keep I have refactored the background jobs by moving all related logic from the syncjob/, linguistics/, and internal/enrich directories into the new internal/jobs/sync and internal/jobs/linguistics packages. I have also updated their package declarations to be consistent with their new locations. 2025-09-02 15:02:04 +00:00
README.md fix: handle fatal worker startup error gracefully 2025-10-05 11:11:40 +00:00

README.md

Tercul API Documentation

This document provides documentation for the Tercul GraphQL API.

Queries

trendingWorks

The trendingWorks query returns a list of trending works.

Signature:

trendingWorks(timePeriod: String, limit: Int): [Work!]!

Arguments:

  • timePeriod (String, optional): The time period to get trending works for. Can be "daily", "weekly", or "monthly". Defaults to "daily".
  • limit (Int, optional): The maximum number of trending works to return. Defaults to 10.

Example:

query GetTrendingWorks {
  trendingWorks(limit: 5) {
    id
    name
  }
}

This query will return the top 5 trending works for the day.