How can easily toggle problems reported by fallow in VSCode? (Hide squiggly lines)

[FunctionDJ]

fallow is very useful, but when working on duplicate code, the problems it reports can span many lines that I now want to work on.

In VSCode, this is shown with blue squiggly lines by default, which can be distracting, especially when syntax, logic (TypeScript) or other linting problems (ESLint) problems are also being reported. Those other reports can be harder to spot and read, and the entire editor becomes a bit messy.

There's problems.visibility in .vscode/settings.json, but it's not (easily) toggle-able with shortcuts, and will hide all problems in editors, which includes the other problem categories I've listed.

Is there a solution for the fallow VSCode extension? Something as simple as "Fallow: Toggle problems" would work, but maybe something else already exists that I don't know of.

[BartWaardenburg]

Released in v2.66.0. Thanks @FunctionDJ. The new Fallow: Mute / Unmute Diagnostic commands let you toggle individual issue types from the editor (no .fallowrc.jsonc round-trip), and the issue-type list is now populated dynamically from the language server.

[danielo515]

Is this version already published? Is also in alternative marketplaces?

[danielo515]

Something I will also like is the ability to "pause" the reporting. Sometimes I want to just explore the codebase without all the noise of fallow, but I don't want to have to enable/disable the extension just for this.

[BartWaardenburg]

@danielo515 yes, it’s published now:

• VS Code Marketplace: https://marketplace.visualstudio.com/items?itemName=fallow-rs.fallow-vscode
• Open VSX: https://open-vsx.org/extension/fallow-rs/fallow-vscode

For the pause use case: that’s covered by Fallow: Toggle Mute All Findings. It hides only Fallow diagnostics in the editor, so TypeScript/ESLint/etc. problems remain visible, and it does not affect CI or fallow check.

[danielo515]

For some reason, I install the latest version and it keeps reverting back to this one

This is windsurf, I'll report it there

[danielo515]

I tried installing it manually, and it fails to install because "incompatibilities" but it doesn't say why. NOt sure if there is anything you can do from your side to make this work

Installing extensions...
Error: Unable to install extension 'fallow-rs.fallow-vscode' as it is not compatible with Windsurf '1.110.1'.
    at to.install (file:///Applications/Windsurf.app/Contents/Resources/app/out/vs/code/node/cliProcessMain.js:432:39083)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async Or.installVSIX (file:///Applications/Windsurf.app/Contents/Resources/app/out/vs/code/node/cliProcessMain.js:425:1087)
    at async file:///Applications/Windsurf.app/Contents/Resources/app/out/vs/code/node/cliProcessMain.js:424:2216
    at async Promise.all (index 0)
    at async Or.installExtensions (file:///Applications/Windsurf.app/Contents/Resources/app/out/vs/code/node/cliProcessMain.js:424:2153)
    at async file:///Applications/Windsurf.app/Contents/Resources/app/out/vs/code/node/cliProcessMain.js:462:56312
    at async Module.Dq (file:///Applications/Windsurf.app/Contents/Resources/app/out/vs/code/node/cliProcessMain.js:462:60290)
    at async _s (file:///Applications/Windsurf.app/Contents/Resources/app/out/cli.js:405:51383)
Failed Installing Extensions: file:///Users/danielo/Downloads/installers/fallow-rs.fallow-vscode-2.71.1.vsix

[BartWaardenburg]

Thanks @danielo515, this one was on my side.

The v2.71.1 VSIX had its VS Code engine floor raised too high, so Windsurf 1.110.1 rejected it as incompatible. Released v2.72.0 with the extension floor lowered back to ^1.96.0 and a regression test so future dependency bumps don’t silently break Cursor/Windsurf installs again.

Please try v2.72.0 from the VS Code Marketplace or Open VSX after Windsurf refreshes its extension cache. If it still shows 2.71.1 or still rejects the VSIX, please reply here with the new error and I’ll follow up in this discussion.

[danielo515]

Hey! I tried it and now it works and installs the right version. Thank you very much! Too bad the editor didn't surfaced the actual error and asked for my input, rather than doing it's own thing.

Thanks again!

[VariableVince]

@BartWaardenburg After disabling the squiggly lines and Problems output using the command "Fallow: Toggle hide all findings", i cannot for the life of me get them back. Disabling "Fallow: Toggle hide all findings", reinstalling the extension, restarting VSCode, removing the ".fallow" folder, etc, nothing helps. No output in Problems and no squiggly lines. The only thing Fallow does is highlight ('select') affected code in the currently opened file. Is this a known issue?

edit: i also disabled the extension for a few days after enabling "Fallow: Toggle hide all findings", maybe that has something to do with it no idea

[BartWaardenburg]

@VariableVince this is fixed in v2.96.0 (update the VS Code extension). "Fallow: Toggle Hide All Findings" was not reversible because, after the extension moved open-file diagnostics to the LSP pull path, the toggle only updated the push collection (which the server keeps empty for open files), so un-hiding never re-pulled and findings stayed hidden across restarts. Toggling now re-pulls open documents, so hide/show works instantly again; we also fixed double-rendered squiggles after a toggle and the Manage picker silently re-hiding categories. Thanks for the detailed repro.

[VariableVince]

@BartWaardenburg Thanks for the quick reply and update! Sadly it didn't seem to fix it for me. Not even after uninstalling the extension, removing the .fallow folder from the workspace (that it still puts there btw), restarting VSCode, and installing fallow again. The blue squiggly lines aren't back, neither is the output in Problems.

Also, when hiding using the toggle, the highlighted/selected code is unhighlighted. But not re-highlighted when enabling it again. Only by closing and re-opening the file, is the code highlighted again. No blue squiggles either way though as said.

[VariableVince]

@BartWaardenburg In Fallow 2.99 the Problems and blue squiggle lines are still not back for me in VSCode. Updated the extension, restarted VSCode. Tried with the Knip extension and it has output in the Problems tab and (in their case red) squiggly lines right away. Not sure if this is a very local problem but i'd be curious if anyone else (still) has issues after using the "Fallow: Toggle hide all findings" setting.