Skip to content

LT-22738: Change the default restore option for Send/Receive data - #1125

Open
jasonleenaylor wants to merge 1 commit into
mainfrom
LT-22738-restore-sr-default
Open

LT-22738: Change the default restore option for Send/Receive data#1125
jasonleenaylor wants to merge 1 commit into
mainfrom
LT-22738-restore-sr-default

Conversation

@jasonleenaylor

@jasonleenaylor jasonleenaylor commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

The Send/Receive checkbox in the restore dialog now follows the restore
target instead of the backup contents. Restoring over the original name
forces it on, because that project keeps its repository history, and
restoring to a different name leaves it unchecked until the user asks for it.
It stays unavailable when the backup holds no Send/Receive data.

Why it needed changing

LT-22629 made the checkbox editable, but it still started checked whenever the
backup happened to contain S/R data, so the narrow expert scenario was the
default for everyone.

Simply defaulting it off would have been worse:
RestoreProjectPresenter.IsOkayToRestoreProject refuses to restore over a
project that is using Send/Receive when the option is off, and its message
gives no hint that ticking the box would let the restore through. Forcing the
option on for an original-name restore keeps that path working and confines
the choice to restores under a new name, which is the case the ticket is
about.

Validation

  • .\build.ps1 -CommentHygiene - clean.
  • .\test.ps1 -CommentHygiene -TestProject Src/FwCoreDlgs/FwCoreDlgsTests -TestFilter FullyQualifiedName~RestoreProjectPresenterTests - 3 passed.
  • The dialog itself has no automated coverage; checkbox states were verified
    by reading the code paths.

The backup-side default is untouched; that is LT-22783.


This change is Reviewable

The Send/Receive checkbox in the restore dialog now follows the restore
target instead of the backup contents. Restoring over the original name
forces it on, because that project keeps its repository history, and
restoring to a different name leaves it unchecked until the user asks
for it. It stays unavailable when the backup holds no Send/Receive data.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown

NUnit Tests

    1 files  ±0      1 suites  ±0   12m 36s ⏱️ +3s
6 023 tests ±0  5 942 ✅ ±0  81 💤 ±0  0 ❌ ±0 
6 032 runs  ±0  5 951 ✅ ±0  81 💤 ±0  0 ❌ ±0 

Results for commit 37c77f2. ± Comparison against base commit 2518431.

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 0% with 8 lines in your changes missing coverage. Please review.
✅ Project coverage is 38.58%. Comparing base (17cdfba) to head (37c77f2).
⚠️ Report is 19 commits behind head on main.

Files with missing lines Patch % Lines
Src/FwCoreDlgs/BackupRestore/RestoreProjectDlg.cs 0.00% 6 Missing and 2 partials ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1125      +/-   ##
==========================================
+ Coverage   38.34%   38.58%   +0.24%     
==========================================
  Files        1507     1514       +7     
  Lines      350586   351039     +453     
  Branches    40294    40360      +66     
==========================================
+ Hits       134432   135465    +1033     
+ Misses     186927   186359     -568     
+ Partials    29227    29215      -12     
Files with missing lines Coverage Δ
Src/FwCoreDlgs/BackupRestore/RestoreProjectDlg.cs 0.00% <0.00%> (ø)

... and 76 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants