Repository navigation
VPR-218 fix(phone): add dept code to SVMUnit EF - #362
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (2)
Included review availability: This review used your included allowance. 4 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour. 📝 WalkthroughWalkthroughSVMUnit now has a nullable ChangesSVMUnit department code
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~4 minutes Change: Feature Merge Risk: ⚪ Minimal · up to This adds an optional DeptCode mapping. The reviewed evidence establishes no concrete application failure or actionable merge blocker. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
🧰 Additional context used📚 Code guidelines (1)Comment |
Bundle ReportBundle size has no change ✅ |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #362 +/- ##
=======================================
Coverage 45.70% 45.70%
=======================================
Files 954 954
Lines 49809 49810 +1
Branches 6750 6750
=======================================
+ Hits 22765 22766 +1
Misses 26071 26071
Partials 973 973
Flags with carried forward coverage won't be shown. Click here to find out more.
|
This PR updates the EF for SVMUnit to include a new column needed for joining the new tables into
vw_CurrentAffiliatesForPF. The new column is not used in the Personnel section at this time. The change in the view itself is documented in Viper 1.0.Schema Change
This requires a schema change to be executed before deploying the code. This adds the DeptCode column for lookup and populates it from the legacy data.