Repository navigation
Preserve recording titles after failed publishing and local saves - #5
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
An invalid sharing password or failed device-storage write could alter the cached saved title and defeat the unsaved-edit warning. Keep changes in a copied candidate and update selected state only after persistence succeeds; retain the editor on an initial publish-save failure. Also correct sampled muted/accent contrast failures.
Reconciled onto current main 294b986, preserving the newer recording/native recovery work. No recording-limit or Android source changes. The open unmerged revert PR #4 is not acted on.
Validation: 111 Node tests pass, build passes; focused regression covers validation and storage failures. Fresh browser retest and deployment verification are being completed.