Make picker backend requirements explicit, or make them real options #173

Closed
opened 2026-04-12 17:22:09 +00:00 by barrettruth · 0 comments
barrettruth commented 2026-04-12 17:22:09 +00:00

Problem

Right now fzf-lua is effectively required.

The code only knows one picker backend, healthcheck errors without it, and the docs/readme treat it as a requirement.

Expected

Pick one direction and make it consistent:

  • either fzf-lua stays required and we say that plainly, or
  • picker backends become genuinely optional/pluggable and the docs, healthcheck, and architecture all reflect that.
## Problem Right now `fzf-lua` is effectively required. The code only knows one picker backend, healthcheck errors without it, and the docs/readme treat it as a requirement. ## Expected Pick one direction and make it consistent: - either `fzf-lua` stays required and we say that plainly, or - picker backends become genuinely optional/pluggable and the docs, healthcheck, and architecture all reflect that.
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
barrettruth/forge.nvim#173
No description provided.