Skip to content

Add a contributor line on relying on contracts #49

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

Merged
lloydevans merged 1 commit into from
Oct 8, 2026
Merged

Add a contributor line on relying on contracts #49

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 CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ See [README.md](README.md) for requirements and commands.

- Give every fact one home, in code, comments or documents, and refer to it from elsewhere. A copy has to be maintained and goes stale.
- Avoid repeating code, within reason. Consider extracting anything likely to be duplicated.
- Rely only on what a function's contract promises, whether a result or an effect. An extra call, delay or retry used to make something else work without that promise relies on incidental behaviour and adds an unrelated way to fail.
- Use `.mts` wherever a repository-owned file would otherwise be `.mjs`, so the TypeScript configuration covers it.
- Prefer a built-in array method, such as `.map`, `.filter` or `.reduce`, to a hand-written loop wherever one expresses the transformation.
- Separate a function's logical blocks with a blank line, such as between checking input, computing a result and writing it out.
Expand Down
Loading