Stash work on onm.Store.injectComponent.
Stash
+onm.Store.injectComponent
Stash work on onm.Store.createComponent optional in-param support.
First cut at supporting component key overrides via onm.Store.createComponent...

... it is sometimes useful to be able to manually override onm's default component key resolution behavior and supply key(s) directly to onm.Store.createComponent to be applied to the onm.Address. This implementation allows for an optional array of component keys strings to be passed to onm.Store.createComponent. If key(s) are specified, they are applied in order to the unresolved _tail_ of the onm.Address prior to resolution.
A few more tests for onm.Store.createComponent.
Stash work on onm.Store.createNamespace construction options object.
First cut at supporting hierarchical data objects on onm.Store.createComponent...

... The supplied data object is optional and is not applied directly to the store. Rather, the data model declaration is used to cherry pick namespace property values and subnamespace names in cases where the onm data component being created comprises a component root and some number of child and extension point namespaces.
Restabilize tests after modifying the test data model.
Merge pull request #30 from Encapsule/chris/develop

Chris/develop
onm v0.2.5 ...
... fixes for issues #2 and #22 (component key and property value data override on onm.Store.createComponent), addition of onm.Store.injectComponent API, additional test coverage.