Repository navigation
Add independent filename-based project revisions - #137
Open
Myuavbug66 wants to merge 1 commit into
Open
Myuavbug66 wants to merge 1 commit into
Myuavbug66 wants to merge 1 commit into
Conversation
Suggest padded revision names from opened or last dispatched project filenames without folder access or save-location dependencies. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
Author
|
I realized this branch is not for everybody. In fact I'm sure some people will absolutely hate this idea. But I'm a revision freak. It's not if or when will you make a mistake But how do you recover from it. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Keep recognizable project revisions
Save suggests
Part-001.scanruler,Part-002.scanrulerand later revisionsinstead of repeating the same suggested filename. Opening
Part-9.scanrulercontinues with
Part-010.scanruler; numbering expands naturally beyond 999.Filename-based, not folder-based: numbering follows the opened file or last
successfully dispatched save in this session. It does not scan a directory for
higher revisions. Browser download settings still control save locations,
cancellation, overwrite prompts and any manually changed filename. ScanRuler
cannot observe those download-dialog changes; reopen the saved file to continue
from its actual name.
Hosted support: works in the normal hosted app after merge/deployment. No
local server, helper or folder permission is required. This branch starts
directly from upstream and does not depend on the separate Save As location
contribution, PR #136.
Usage
-001.Existing files are not renamed. The portable
.scanrulerformat, original scansand alignment are unchanged. Agent commands returning project bytes retain
their existing unnumbered names.
Implementation and validation
opened files, case-insensitive revision matching and safe-integer checks.
dispatch failures do not advance it or mark unsaved changes saved.
synthetic recovery filename.
merge reconciliation if integrated together; neither requires the other's
branch or feature.
Validation on this independent upstream-based worktree:
history (24), recovery (23), imports (18) and CAD undo (9).
downloads, with no source-module or local-writer requests.
of dynamic-import setters that repeatedly encountered Chrome's
Promise was collectedprotocol failure. Assertions remain unchanged.Downloads are intercepted during tests. Native OS dialogs, disk completion,
manual download renames/cancellations and full unit/MCP/end-to-end suites were
not recertified. Dispatch success is not proof of completion on disk.