https://github.com/damonoehlman/registry

DEPRECATED: Define things and retrieve them using wildcard rules (and more)
https://github.com/damonoehlman/registry

Last synced: 7 days ago
JSON representation

DEPRECATED: Define things and retrieve them using wildcard rules (and more)

• Host: GitHub
• URL: https://github.com/damonoehlman/registry
• Owner: DamonOehlman
• Created: 2012-02-13T06:26:53.000Z (almost 13 years ago)
• Default Branch: master
• Last Pushed: 2012-08-24T03:51:05.000Z (about 12 years ago)
• Last Synced: 2024-10-20T02:53:37.611Z (26 days ago)
• Language: JavaScript
• Homepage: registry.rtfd.org
• Size: 326 KB
• Stars: 6
• Watchers: 3
• Forks: 5
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Registry

Registry is designed to be a useful helper for managing definitions of JS modules, classes, functions, etc.  It provides the ability to define a "thing" using a string identifier and then

retrieve it at later date using [wildcard](/DamonOehlman/wildcard) matching.



## Why Use Registry?

Registry attempts to provide some of the benefits that you find using an [IoC](http://en.wikipedia.org/wiki/Inversion_of_control) in an OO programming environment, but does not force OO patterns into JS like many other Class Helper libraries.

When using registry you should be able to define things in much the same way you are used to.  You simply provide them a name that can be wildcard matched in a similar way to [eve](/DmitryBaranovskiy/eve) and retrieved later.  Using this technique you can either specifically target a particular thing by using a specific name or a more generalized instance using a more generalized namespace.

Primarily, Registry has been designed for use in the browser but will also work quite happily in a CommonJS environment (such as Node).

## Example Usage

At the moment, the tests contain some of the best examples of how Registry can be used, but you should also check out the docs (see below).

## Registry Documentation

Emerging documentation is available at: