beads

Files

Steve Yegge d45cff5085 feat: Handle FOREIGN KEY constraint violations gracefully during import (bd-koab)

When importing JSONL after merges that include deletions, FK constraint
violations can occur if an issue references a deleted issue. Previously,
import would fail completely. Now it continues and reports skipped dependencies.

Changes:
- Add SkippedDependencies field to Result/ImportResult structs
- Update importDependencies() to detect FK violations using IsForeignKeyConstraintError()
- Log warnings for each skipped dependency with issue IDs and type
- Continue importing remaining dependencies instead of failing
- Display summary of all skipped dependencies at end of import

Example output:
  Warning: Skipping dependency due to missing reference: bd-b → bd-a (blocks)

  ⚠️  Warning: Skipped 2 dependencies due to missing references:
    - bd-b → bd-a (blocks)
    - bd-c → bd-a (parent-child)

  This can happen after merges that delete issues referenced by other issues.
  The import continued successfully - you may want to review the skipped dependencies.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-11-23 23:32:34 -08:00

external_ref_test.go

fix: Add context.Background() to sqlite.New() calls in test files

2025-11-21 14:48:41 -05:00

importer_integration_test.go

Fix test compilation errors: add context.Background() to sqlite.New() calls

2025-11-21 14:57:18 -05:00

importer_test.go

fix: Add context.Background() to sqlite.New() calls in test files

2025-11-21 14:48:41 -05:00

importer.go

feat: Handle FOREIGN KEY constraint violations gracefully during import (bd-koab)