Could we separate dynamic state settings (e.g., recentCommandLaunchCounts and rootSearchRanking) from the main settings.json?
I manage my SuperCmd config via a dotfiles repo, and these fields constantly trigger untracked changes in Git when no actual configuration has modified. Moving this state data to a separate file would prevent this noise.
Could we separate dynamic state settings (e.g.,
recentCommandLaunchCountsandrootSearchRanking) from the mainsettings.json?I manage my SuperCmd config via a dotfiles repo, and these fields constantly trigger untracked changes in Git when no actual configuration has modified. Moving this state data to a separate file would prevent this noise.