Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Declarative Construciton of Objects. It offers type checking, triggers, wrappers, required, builders, default values, lazy builders and cooerciens. Doesn't force you to use it on every attribute in your object or every object in your application. Modeled loosly after MOOSE (perl) and JOOSE (javaScript). Make your code clearer. expound it. Design…
tag: v0.2.1

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.


The purpose of 'expound' is to be able to construct your objects in a declarative fashion. This allows all of the relavant code to be logically near each other in the codebase as well making convenient functionailty for things you do anyways. Type checking, triggers, wrappers, private variables etc.

It uses the new ecma script 5 property descriptors to works its mojo. Normally, property descriptors can be either data descriptors or accessor descriptors - but not both. 'expound' enables you to have the functionailty of both in a familiar syntax.

Because it uses ECMAScript 5, it's not yet safe to use in the browser world, but should be fine to use in a firefox or chrome extension. It has been primarialy designed for use with node.js.

expound provides around 10 attributes useful for quickly defining an attribute. It also has a handful of functions useful fordefining types at both an object and a "global" level.

As a side note, asynchronous assignments can easily be handled through using a module like async.js or other asynchronous tool. Application level type constraints can easily be added by subclassing expound to your own local version, adding types at the global level, and then exporting the localized expound to your various modules.

Quick Examples

    var expound = require(expound);
    // expound is a useful word that can be used as either to define or describe.

        name: 'foo',
        value: 42,
        writable: true,
        enumerable: true,
        configurable: false,
        required: true,
        lazy: true,
        trigger: function (newValue, oldValue) {
            console.log('other important function to run after this value is set');
        wrap: function (next, assignmentValue) {
            var returnValue;
            console.log('things to do before setting the value');
            returnValue = next();
            console.log('print the returnValue' + returnValue);
        builder: function () {//runs to build the value if not passed in or, if lazy, on initial get
        type: 'isArray',

    //To add a new type, "globally"
    expound.addType('isLessThanTen', function (value) {
        return (expound.types.isNumber(value) && value < 10) ? true: false;

In the above example, running = 43; will run like this:

  1. things to do before setting the value or running a function
  2. value actually set to 43
  3. print thereturnValue 43
  4. other important function to run after this value is set or function run


Releases are available for download from GitHub. Alternatively, you can install using Node Package Manager (npm):

npm install expound



These are the attributes for the property() method


Road Map



Specifies the property name as in the 'bar' part of


Specifies the value of the property. If not passed in, specify a builder to build the value immediately (like a default) or -- if lazy is true builds the first time its value is called. See lazy below fir more info.

writable (default: true)

Boolean to set whether or not you may change the value of the property

enumerable (default: true)

Same as ECMAScript 5: True if and only if the type of this property descriptor may be changed and if the property may be deleted from the corresponding object.

configurable (default: false)

Same as ECMAScript 5: True if and only if this property shows up during enumeration of the properties on the corresponding object.

required (default: false)

Boolean stating whether the value is required at construction. If required, a value must be passed in or it must have a builder method.


The builder method, if defined, is called in the context of the attribute's object. When the value has never been set to populate the value of the attribute. The builder method is called either immediately, if lazy:false and serves to assign default values.

However, to delay building until needed, you can set lazy=true and the value is not built until the value is required. This is handy if the buildtime of the value is heavy and perhaps isn't often needed. Like an md5 sum. It's generally a good practice to move build methods to the lazy state.

lazy (default: true)

Defines when the builder method runs if an attribute is created without a value. Immediately upon creating it (like a default value) if lazy=false or only upon retrieving the value if lazy=true.

Object constructors should always have lazy builders. If not, the builder will throw an error and the attribute will force itself into lazy mode, setting the correct value when the value is retrieved.



The trigger option is a CODE reference which will be called after the value of the attribute is set. The function is called in the context of the attribute's object and is passed the updated value, and the old value. Triggers are not fired at object creation. Triggers do not alter the return value or the value. Attempting to set the attribute that the trigger is tied to within the trigger function will cause an infinite recursion. I don't think anyone has time for that.


The wrap function is called in the context of the calling object and allows you to run code and possibly alter the input (right hand value of the assigment - so the '37' in obj.a=37). Although you have access to the returnValue of the assignment, you can not change the return value from the assignment. Further, re-setting the value of the attribute within the attributes wrap function may easily cause an infinite recursion.

In most cases it is better to use a coercion to augment the right-hand value on the way in, a type to validate a right-hand value and a trigger to enact some form of code on the way out.



Used to create a meta-object handle on an object. All locally defined types will bind to this object alone. The handle can be used to add properties to the same object using the same scope.


  • OBJ - The object to bind the meta-object handle to.


An expound meta-object. You can call other methods against this. It is chaninable.



    var meta_myObj = expound(myObj);

    //Then later


Used to define an objects property. See the documentation above at attributes for details.


  • SPEC - An attributes spec as defined above.


An expound meta-object. You can call other methods against this. It is chaninable.



    var meta_myObj = expound(myObj).property({
        name: ('a'),
        type: 'isArray'


Used to addTypes to either the "Global" expound instance or a local meta-object handle of an object.


  • NAME - A Unique Name to add as a type. Names are stored in a hash, and handle types descend from the global type, so you can overwrite them.
  • FUNCTION (VALUE) - The function should parse the value and return true if it passes, false otherwise.




    //To add a new type, "globally"
    expound.addType('isLessThanTen', function (value) {
        return (expound.types.isNumber(value) && value < 10) ? true: false;
    var meta_myObj = expound(myObj);

On the RoadMap

    //coerce: Takes a value and uses the defined type to create the property.  for example, pass in the user ID, but have it auto and build the user object and store that in the property
    //delgates: useful for calling other methods in the context of this attribute
    //enableRollback:  Allows attribute values to be rolled back.  Takes integer (0++).  Zero means no rollback.  Keeps history up to value given. keyword 'forever' keeps indefinate history until you run out of memory...
    //rollback: takes an integer.  Rolls back the value to the nth previous version.  Fails if version doesn't exist.  enableRollback must be true.  Rollbacks will be wrapped and trigger.  Not available for functions.

ALSO coming....

Meta information about properties...

expound(myObj).hasBeenSet("a") -> returns whether the myObj.a has ever been set.;
expound(myObj).clear("a") -> sets value to undefined and hasBeenSet to false.;
expound(myObj).history("a") -> returns an array of the stored history of the properties values.;

You can see where this is going....

Something went wrong with that request. Please try again.