This is a Copilot review comment that is more of a product question: #404 (comment)
I also noticed that the whole area around drift scanning preferences is weird and inconsistent. We have a Homebrew preference in the Settings that governs Homebrew. We also have a "dismiss" for the "system defaults" chip that stores in local storage and once you dismiss, there's no (non-developer) way for the user to get it back.
I'd suggest wire the chip and the filesystem untracked settings tab to the same user-visible preference, either in Settings OR perhaps in the filesystem panel itself somewhere. And we need to decide between having separate Homebrew/defaults/startup items/whatever-all-else checkboxes or just having one unified "scan for drift" setting. It's probably easier to just have one.
@farhankhalaf please comment on the right approach(es). Thanks.
This is a Copilot review comment that is more of a product question: #404 (comment)
I also noticed that the whole area around drift scanning preferences is weird and inconsistent. We have a Homebrew preference in the Settings that governs Homebrew. We also have a "dismiss" for the "system defaults" chip that stores in local storage and once you dismiss, there's no (non-developer) way for the user to get it back.
I'd suggest wire the chip and the filesystem untracked settings tab to the same user-visible preference, either in Settings OR perhaps in the filesystem panel itself somewhere. And we need to decide between having separate Homebrew/defaults/startup items/whatever-all-else checkboxes or just having one unified "scan for drift" setting. It's probably easier to just have one.
@farhankhalaf please comment on the right approach(es). Thanks.