This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
) is private.
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon () is public.
Every repository with this icon (
) is public.
Uncommunicative Name
An Uncommunicative Name is a name that doesn’t communicate its intent well enough.
Poor names make it hard for the reader to build a mental picture of what’s going on in the code. They can also be mis-interpreted; and they hurt the flow of reading, because the reader must slow down to interpret the names.
Current Support in Reek
Currently Uncommunicative Name checks for
- 1-character names
- names consisting of a single character followed by a number
Configuration
Reek’s Uncommunicative Name detector supports the Basic Smell Options, plus:
| Option | Value | Effect |
|---|---|---|
reject |
array of regular expressions | The set of regular expressions that Reek uses to check for bad names. Defaults to [/^.[0-9]*$/]. |
accept |
array of strings or regular expressions | Names that will be accepted (not reported) even if they match one of the reject expressions. |
Pages
- Attribute
- Basic Smell Options
- Class Variable
- Code Smells
- Command-Line Options
- Configuration Files
- Control Couple
- Data Clump
- Duplication
- Feature Envy
- Getting Started
- Home
- Installation
- Large Class
- Long Method
- Long Parameter List
- Mailing List
- Nested Iterators
- Non-ASCII source files
- Project Dashboard
- Rake Task
- RDoc
- Reek-Driven Development
- Ruby 1.9
- Simulated Polymorphism
- Uncommunicative Name
- Utility Function
- Working with Rails
