docs(skills): tighten nix let rule
This commit is contained in:
@@ -8,7 +8,6 @@ Do not add a `let` binding only to let sibling values share one expression.
|
||||
When one sibling value owns the concept, reference that sibling value directly.
|
||||
When a flake output owns the public value, reference that output through `self`.
|
||||
Do not make an output attrset recursive only to reference sibling outputs.
|
||||
Use a `let` binding when it names an internal concept or avoids repeated complex code.
|
||||
|
||||
### Rationale
|
||||
|
||||
|
||||
Reference in New Issue
Block a user