Which fff frontend(s)?
Node SDK (@ff-labs/fff-node)
What problem are you trying to solve?
Love fff, currently using the node implementation to power my pi extension.
My concrete use case is my Pi configuration. I manage it with GNU Stow from my dotfiles repo so I can share the same setup across machines:
~/.pi/agent/... # live config path, symlink/stow layout
~/.dotfiles/pi/.pi/agent/... # canonical tracked files
This includes my fff/Pi extension setup and many other Pi config files.
When I’m working on the Pi setup itself, fff-backed find/grep can miss or fail
to reason about files correctly because the files are behind the stowed/symlinked layout. In practice, this makes agents fall back to shell find/grep,
which is exactly what I’m trying to avoid by using fff.
I noticed fff.nvim already has a follow_symlinks option, which seems like prior art for this behavior. I’d love to have similar support available in
the agent/SDK-facing paths, namely @ff-labs/fff-node and the bun implementation.
I’m willing to try making a PR, but I have little experience thinking through the broader implications of a feature like this: watcher behavior,
cycles, indexing outside the repo, defaults, API compatibility, etc. So I wanted to ask first rather than guess.
Proposed solution
No response
Which fff frontend(s)?
Node SDK (@ff-labs/fff-node)
What problem are you trying to solve?
Love fff, currently using the node implementation to power my pi extension.
My concrete use case is my Pi configuration. I manage it with GNU Stow from my dotfiles repo so I can share the same setup across machines:
This includes my fff/Pi extension setup and many other Pi config files.
When I’m working on the Pi setup itself, fff-backed find/grep can miss or fail
to reason about files correctly because the files are behind the stowed/symlinked layout. In practice, this makes agents fall back to shell find/grep,
which is exactly what I’m trying to avoid by using fff.
I noticed fff.nvim already has a follow_symlinks option, which seems like prior art for this behavior. I’d love to have similar support available in
the agent/SDK-facing paths, namely @ff-labs/fff-node and the bun implementation.
I’m willing to try making a PR, but I have little experience thinking through the broader implications of a feature like this: watcher behavior,
cycles, indexing outside the repo, defaults, API compatibility, etc. So I wanted to ask first rather than guess.
Proposed solution
No response