Advanced conditions with mwater-expressions

[grassick]

Will allow conditioning on matrix answers, roster aggregate data, "or" conditions, site types, distance between, etc, etc.

The converse is mwater-expression-ization of existing conditions. This will allow calculating number of times an answer was asked.

Problem: site data is asynchronous, which means that expression evaluation, the entire visibility calculation has to be async as well, and thus cleaning of data too.

• [x] expression evaluation needs to a) become async and b) support aggregation
• [x] conditionExpr has to be added to schema, calculation and designer
• [x] legacy conditions need to be compilable to mwater-expressions
• [x] total conditions on a question need to be calculable
• [x] row object needs to support complete set of types (incl location) + matrices + rosters
• [x] row object needs to support joins to entities and sites
• [x] entity objects need to be fully supported
• [x] make visibility calculator async
• [x] Signature of ResponseExprValueUpdater has changed (fillRuleForm in server too!)
• [x] FormComponent requires schema
• [x] Update all calls in form designer
• [x] ResponseAnswers requires schema
• [x] ResponseDisplay requires schema
• [x] Move entity schema generation to mwater-forms

[grassick]

• Testing of condition compiling could be done by running all existing responses through traditional and JsonQL versions of the conditions.
• Testing of row objects could be done by comparing JsonQL versions to dynamic versions