Repository navigation
fix(import): validate export rows before mutating the store - #496
Merged
Merged
Conversation
Reject malformed sections and indexing fields before replacement. Keep\nlegacy keyless rows skippable under all import strategies. Refs: #436 Generated-By: gpt-6.2-sol
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.
Intent
Closes #436
Validate export sections and fields used by indexing before an import changes the store, so malformed keyed records cannot interrupt a replace after deletion starts.
Read first
src/functions/export-import.ts— import preflight.test/export-import.test.ts— checks that invalid input leaves existing rows intact.Decisions
Out of scope
Verified
Not verified
Merge danger
Door: Reverting restores prior input handling; it cannot undo a replace import.
Blast radius: Export imports via REST and MCP.