h1v3 0.14.0 → 0.15.0

package/README.md

@@ -194,6 +194,12 @@ export const team_membership = configureEventStore(h1v3.teamMembership.store);
 export const team_details = configureEventStore(h1v3.teamDetails.store, teamDetailsSchema);
 ```
 
+I usually put these in a file called "h1v3.config.js" and then remember to export these from my top-level index.js (as shown above):
+
+```javascript
+export * from "h1v3.config.js";
+```
+
 ### Defining schemas
 
 Schemas for the two built-in event stores user_profile and team_details expect a schema defined using a javascript prototype as shown below. Note that there is no required constraint. Instead the schema is a white-list of keys along with the expected type for the associated value.
@@ -274,6 +280,13 @@ function buildEmulated() {
 }
 ```
 
+## Database rules
+
+Once you have defined your configuration (`h1v3.config.js`) you can generate your databse.rules.json file:
+```sh
+cd functions
+npx h1v3 rules --output ../database.rules.json
+```
 
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "h1v3",
-  "version": "0.14.0",
+  "version": "0.15.0",
   "description": "",
   "license": "MIT",
   "author": "",

package/src/commands/generate-rules.js

@@ -85,7 +85,11 @@ const addRulesForPath = (existingRules, [
             )
         }
         // stick the rules here
-        : rules(config);
+        : {
+            ...existingRules,
+            ...rules(config)
+        }
+        ;
 
 const parseConfig = ([_name, config]) => [
     // 0: the path

package/src/exec-eventstore.js

@@ -77,5 +77,3 @@ main({
     }
 
 });
-
-