Untangle compile cycles #594
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
optional
question
S
security
technical improvement
UX Improvement
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
local-it/mitgliederverwaltung!594
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue/mitgliederverwaltung-538"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
closes #538
Description of the implemented changes
The changes were:
Untangle compile cycles: split
Mv.Configand extract the join-request workflow. The 721-lineMv.Configand the join workflow inside theMv.Membershipdomain tied the domain, its policy checks and the web layer into compile-time cycles, so small edits recompiled large parts of the app. Configuration now lives in per-context modules, the join workflow has its own module outside the domain, and the two remaining edges into the web layer and the OIDC provider switch go through configuration. Measured withmix xref graph: cycles 69 → 49, compile-connected cycles 19 → 3 (the three left are outside this scope: roles/permissions, user/OIDC role sync,Router↔LiveUserAuth). Behaviour is unchanged.What has been changed?
Definition of Done
Code Quality
Accessibility
Testing
Additional Notes
config :mv, :join_notifierand the newconfig :mv, :oidc_provider_observerare required now; a missing entry raises instead of falling back silently. Both are set inconfig/config.exs.test/mv/architecture/) runmix xrefand fail if the settings/ProviderSwitch or domain/mail-layer cycles come back.Mv.Membership) and the JoinFlow reorder (pure move). Most of these diffs are moves.