effects-as-data-server
Advanced tools
Comparing version 0.0.6 to 0.0.7
{ | ||
"name": "effects-as-data-server", | ||
"version": "0.0.6", | ||
"version": "0.0.7", | ||
"description": "A simple server for effects-as-data", | ||
@@ -5,0 +5,0 @@ "main": "src/index.js", |
@@ -7,3 +7,3 @@ # Effects-as-data server | ||
1. Routes should be functions take JSON and return JSON, not functions that accept a `ctx` object and "return" by settings properties on that object. | ||
1. Routes should be functions that take JSON and return JSON, not functions that accept a `ctx` object and "return" by settings properties on that object. | ||
2. Routes should be easy to unit test thoroughly. | ||
@@ -10,0 +10,0 @@ 3. Rapid development with `effects-as-data`. This means rapid development and clean code. In my experience, web servers have a way of turning into spaghetti quickly. |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
21398