Skip to content
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

Jump to bottom

XS✔ ◾ ✏️ Added authors #9600

Closed
wants to merge 2 commits into from
Closed

XS✔ ◾ ✏️ Added authors #9600

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a1af669
Added authors
jeoffreyfischer Nov 21, 2024
c5001cb
Auto-fix Markdown files
github-actions[bot] Nov 21, 2024
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
5 changes: 5 additions & 0 deletions rules/verbs-for-method-names/rule.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,10 @@ created: 2024-11-05T00:00:00.0000000Z
authors:
- title: Matt Goldman
url: https://ssw.com.au/people/matt-goldman
- title: Jeoffrey Fischer
url: https://ssw.com.au/people/jeoffrey-fischer
- title: Daniel Mackay
url: https://ssw.com.au/people/daniel-mackay
related:
- clear-meaningful-names
- nouns-for-class-names
Expand All @@ -26,6 +30,7 @@ Code becomes easier to understand when names align closely with their meaning. S
<!--endintro-->

## What is a verb?

A verb is a word that describes an action or process—something that’s done. Examples include walk, run, think, listen, and breathe, as well as process, calculate, send, and save. While your method names shouldn’t all be single verbs (since that’s often too vague), they should be verb-based, using a verb as the foundation of their meaning.

:::greybox
Expand Down