Skip to content

docs: expand anti-patterns with private state access guidance #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
colombod wants to merge 1 commit into from
+1 −0
Closed

docs: expand anti-patterns with private state access guidance #8

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/DESIGN_PHILOSOPHY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -286,6 +286,7 @@ When faced with implementation decisions, ask:
### In Module Development

❌ Depending on kernel internals (use protocols only)
❌ Bypassing public interfaces to access internal state (extend the interface instead)
❌ Inventing ad-hoc event names (use canonical taxonomy)
❌ Private log files (write via `context.log` only)
❌ Failing to emit events for observable actions
Expand Down