Task/flcrm 8530 add apply field effects

[jahndis]

• Add the APPLYFIELDEFFECTS function to expressions.
• Add a basic deploy mechanism
• Move fulcrum-expressions-sandbox stuff into this repo to make it easier to deploy together.
• Move more scripts into package.json scripts

The version of expressions-proxy.coffee in this PR will produce exactly what's deployed in S3 if built in fulcrum-expressions-sandbox. This repo has a different version of browserify which showed a larger diff, but in my testing, the differences don't appear to affect anything. The only missing thing from the original expressions-proxy.coffee was a try/catch:

diff --git a/expressions-proxy.s3.formatted.js b/expressions-proxy.sandbox.formatted.js
index b310c05..fe4116f 100644
--- a/expressions-proxy.s3.formatted.js
+++ b/expressions-proxy.sandbox.formatted.js
@@ -39,10 +39,7 @@ e.prototype.onMessage=function(e){
 var r;
 this.source=e.source;
 this.origin=e.origin;
-try{
-r=JSON.parse(e.data)}
-catch(e){
-return}
+r=JSON.parse(e.data);
 this.id=r.id;
 return this[r.name](e,r)}
 ;

Once the try catch was added, the output was the same.

To test:

• Run yarn deploy (may need USER=). This will deploy expressions to your preview env's S3 bucket.
• In fulcrum's skaffold.yaml setValueTemplates block add fulcrum.rails.config.expression_sandbox_url: "https://fulcrumapp-world-{{.USER}}.s3.amazonaws.com/expv1/expressions.html"
  • Skaffold and make sure data events/calculations work.
  • Create a form with a classification field with data name type and using the issues classification field (or use a choice field or whatever you want, just make sure the FieldEffects json matches), as well as a text field with data name text.
  • Try out the new APPLYFIELDEFFECTS function in a data event for that form like:

    APPLYFIELDEFFECTS({
    effects: [
    {
    event: { name: 'change', field: 'type' },
    conditions: [
    { field: 'type', operator: 'equals', value: ['Hazard'] }
    ],
    actions: [
    { type: 'setvalue', field: 'text', value: 'Hazard text' }
    ]
    }
    ]
    })

  • Preview the form and verify that changing the classification field value to Hazard (or whatever) changes the text field value