fj workflow init: cache completion result #18

Open
opened 2026-05-17 08:42:31 +02:00 by heiko · 1 comment
Owner

Follow-up to the fj workflow init feature.

Tab completion for <name> currently hits the Forgejo contents API on every press. That is one HTTP call per tab and noticeable when typing quickly or when offline.

Cache the listing locally (e.g. ~/.cache/fj/workflows-<host>-<owner>-<repo>.json) with a short TTL (a few minutes). Refresh on miss / expiry, fall back to the cache on network error.

Follow-up to the `fj workflow init` feature. Tab completion for `<name>` currently hits the Forgejo contents API on every press. That is one HTTP call per tab and noticeable when typing quickly or when offline. Cache the listing locally (e.g. `~/.cache/fj/workflows-<host>-<owner>-<repo>.json`) with a short TTL (a few minutes). Refresh on miss / expiry, fall back to the cache on network error.
Author
Owner

AI attribution comment added per repository instruction for this open issue.\n\n(co)authored by ai:gpt-5-codex

AI attribution comment added per repository instruction for this open issue.\n\n(co)authored by ai:gpt-5-codex
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
heiko/fj#18
No description provided.