yukon
Advanced tools
Comparing version 0.1.1 to 0.1.4
{ | ||
"name": "yukon", | ||
"version": "0.1.1", | ||
"description": "Self-discovering component-based API-driven framework based on express", | ||
"version": "0.1.4", | ||
"description": "Self-discovering API-driven web components", | ||
"main": "yukon.js", | ||
"keywords": [ | ||
"parallel", | ||
"parallel API", | ||
"API", | ||
"nodule", | ||
"nodulejs", | ||
"self-discovering", | ||
"framework", | ||
"component-based", | ||
"component-based framework" | ||
], | ||
"scripts": { | ||
@@ -7,0 +18,0 @@ "test": "echo \"Error: no test specified\" && exit 1" |
@@ -110,8 +110,9 @@ # yukon API framework | ||
``` | ||
Download yukon - https://github.com/jackspaniel/yukon/archive/master.zip | ||
$ npm install | ||
$ make test | ||
``` | ||
## To Do | ||
1. Stop populating res.locals and res.renderData with API response data. All API response data and errors should be tacked on to the req.nodules.callArgs[namespace] object. (Maybe rename callArgs to something a little less arg-y?) An app can add these convenience shortcuts if desired. | ||
2. Reconside stub behavior. Should all stubs move to apiSim behavior? What about brand new nodules where nothing is known about the API yet? | ||
2. Get demoApp working as standalone. | ||
@@ -118,0 +119,0 @@ 3. Write more detailed unit tests? |
29940
300