Update TODO list and refine selection logic in Confirming page

- Removed outdated tasks from the TODO list related to one-shot mode changes, streamlining focus on current issues.
- Enhanced the selection logic in the Confirming page to prevent auto-selection of new items when changes are detected, improving user experience during updates.

These changes aim to clarify task management and enhance the handling of user selections in the application.
This commit is contained in:
Joe 2026-03-01 06:51:30 -06:00
parent 118c195e64
commit 7d08b8990f
2 changed files with 2 additions and 6 deletions

View file

@ -334,11 +334,6 @@ when you commit changes on git, it's considered unchanged. we need send prior gi
right now i believe we are calculating the hashes manually, we CAN use the git hash since our hash schema matches it 1:1.
this would be a nice optimization, too.
[one shot mode change]
new changes that come in / out during the pathc visualizer menu on the plugin is really disorienting.
if a new change comes in mid-visualizer syncing, we need to unselect the change completely - not even permitting auto selections or whatever the user had selected (ONLY if that specific file was changed, of course)
this applies to all sync mode which that GUI is being used
[syncback]
detect when the output file hash is the same, and dont write to it.
because have already loaded it, we can detect this.

View file

@ -211,7 +211,8 @@ function ConfirmingPage:didUpdate(prevProps)
-- Merge with any new default selections (new items get nil = unselected)
for id, selection in pairs(newSelections) do
if updatedSelections[id] == nil then
local wasChanged = self.props.changedIds and self.props.changedIds[id]
if updatedSelections[id] == nil and not wasChanged then
updatedSelections[id] = selection
end
end