canmove, Confirmed users
2,056
edits
Jetpack/Design Guidelines: Difference between revisions
Jump to navigation
Jump to search
add recommendation around naming of things
(explicitly label as a draft) |
(add recommendation around naming of things) |
||
| Line 116: | Line 116: | ||
Interfaces should take advantage of composition to reduce repetition and complexity. For example, interfaces that display a panel should solicit it from their consumers in the form of a property that accepts a Panel object. | Interfaces should take advantage of composition to reduce repetition and complexity. For example, interfaces that display a panel should solicit it from their consumers in the form of a property that accepts a Panel object. | ||
The names of modules, singletons, constructors, properties, and methods should be the simplest distinct word or phrase that accurately describes the thing being named, with single full words being preferable to acronyms (e.g. Request rather than XHR), abbreviations (e.g. Separator instead of Sep), and phrases (e.g. <code>persistent</code> rather than <code>alwaysDisplay</code> and <code>precede</code> instead of <code>insertBefore</code>). | |||
= References = | = References = | ||