docs(requirements): add rings to laws
Add explicit northstar rings to the law requirements so redgate no longer reports missing-ring warnings for the first rows. req: laws/001 req: laws/002 req: laws/003 req: laws/004 req: laws/005
This commit is contained in:
+5
-5
@@ -12,19 +12,19 @@ client app state framework.
|
||||
## laws
|
||||
|
||||
### req: law/001
|
||||
001 A feature belongs in core only if it can be expressed as typed resources plus EffectBatch ops.
|
||||
0 001 A feature belongs in core only if it can be expressed as typed resources plus EffectBatch ops. [north_star]
|
||||
|
||||
### req: law/002
|
||||
002 A feature belongs in an integration crate if it depends on transport, framework, auth, storage, browser capability, or deployment policy.
|
||||
0 002 A feature belongs in an integration crate if it depends on transport, framework, auth, storage, browser capability, or deployment policy. [north_star]
|
||||
|
||||
### req: law/003
|
||||
003 A feature belongs in generated API if it improves author ergonomics without adding runtime semantics.
|
||||
0 003 A feature belongs in generated API if it improves author ergonomics without adding runtime semantics. [north_star]
|
||||
|
||||
### req: law/004
|
||||
004 A feature belongs in user code if it is business logic, domain validation, routing policy, authorization policy, persistence, or layout choice.
|
||||
0 004 A feature belongs in user code if it is business logic, domain validation, routing policy, authorization policy, persistence, or layout choice. [north_star]
|
||||
|
||||
### req: law/005
|
||||
005 Add one primitive only if it removes at least five special cases.
|
||||
0 005 Add one primitive only if it removes at least five special cases. [north_star]
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user