Design Patterns

Open

#16 opened on Apr 27, 2015 0 comments 0 reactions 1 assignee View on GitHub

@pixelknitter is already working on this.

Since Aug 21, 2015.

Assessment

This issue has not been assessed yet.

help wanted

require at top (core, package, file) then variables
sync only during first tick => mark as Sync
use promises => nodeify(), done(), return
app as dependency injection
middleware
small modules
export at top (single value) or bottom (multiple values)
avoid parasitic (monkey patching the environment / runtime) code, except at app (top) level
use js instead of JSON for configs (for comments)
don't store state at the module level!!!! (export a constructor and store state in the instance)
app lifecycle: require, configure, initialize, run (first tick contains: require, configure, start of initialize)

What success looks like: Succinctness and clarity. Less is more.
Reference Wikis: Modules & Packages

Open separate issues for required links to community sources if you're having trouble finding any.

Please assign to yourself before working on this.

No contributing guide indexed for this repository

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.