flexion / ef-cms

An Electronic Filing / Case Management System.
23 stars 10 forks source link

Catching invalid entities after schema changes #10517

Open zachrog opened 1 month ago

zachrog commented 1 month ago

Pre-Conditions

Acceptance Criteria

The below solutions are explored and implemented if they prove to be good options:

Pain Avoided/Frustration Saved

Making schema changes causes existing data in the database to become invalid.

Breadth/Pervasiveness of Problem

Complexity of Problem (Low, Medium, High) and Why it's Complex

High

Notes

This problem has been explored and voted on by the team(10/4/2024). The ideas to solve this problem can be found in this branch devex-auto-detect-validation-errors inside of this markdown file docs/entities/entity-validation.md.

The fingerprinting method has been explored and a partial solution exists. To run checkout devex-auto-detect-validation-errors branch and run npx ts-node --transpile-only scripts/getEntityIdentifiers.ts

These are experiments, not commitments. Let's see what works and eventually get rid of things that don't to reduce complexity.