local-it/mitgliederverwaltung
2
3
Fork 0
Code Issues 67 Pull requests 6 Projects 3 Releases Packages 1 Activity Actions

Fix remaining runtime guard references in CODE_GUIDELINES

Browse source 
Remove mentions of runtime guards - only compile-time config is used.
Clarify that production safety comes from config defaults.
This commit is contained in:
Moritz 2026-01-22 23:12:33 +01:00
parent f32324d942
commit d114554d52
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
CODE_GUIDELINES.md
View file

@ -1672,7 +1672,7 @@ end
- Allows CRUD operations without an actor in **test environment only** - Allows CRUD operations without an actor in **test environment only**
- Denies all operations without an actor in **production/dev** (fail-closed) - Denies all operations without an actor in **production/dev** (fail-closed)
- Uses both compile-time and runtime guards to prevent accidental production use - Uses compile-time config check to prevent accidental production use (release-safe)
**Security Guards:** **Security Guards:**
@ -1720,8 +1720,8 @@ Ash.create!(Member, attrs, actor: system_actor)
**Testing:** **Testing:**
- NoActor tests verify both compile-time and runtime guards - NoActor tests verify the compile-time config guard
- Tests ensure NoActor returns `false` in non-test environments - Production safety is guaranteed by config (only set in test.exs, defaults to false)
- See `test/mv/authorization/checks/no_actor_test.exs` - See `test/mv/authorization/checks/no_actor_test.exs`
### 5.2 Password Security ### 5.2 Password Security