fix: register NormalizationRun model in package exports and Alembic#14
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthrough
Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
5ca54e9 to
eb69f3c
Compare
Fixes CatholicOS#12 — NormalizationRun was not exported from the models package or imported in alembic/env.py, causing lazy-load resolution failures in standalone scripts and silent migration drift. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
eb69f3c to
ceeb607
Compare
Summary
NormalizationRuntoontokit/models/__init__.pyimport and__all__NormalizationRuntoalembic/env.pymodel imports for autogenerateFixes #12 — the model was referenced by
Project.normalization_runsbut never registered, causing lazy-load name resolution failures in standalone scripts and invisible migration drift in Alembic autogenerate.Test plan
Project(e.g., benchmark) — should no longer fail withexpression 'NormalizationRun' failed to locate a namealembic revision --autogenerate— should detectnormalization_runstable🤖 Generated with Claude Code
Summary by CodeRabbit