concept issue: defining functions for field properties

Great stuff!

However there seems to be an issue with the concept of defining functions for fields properties and validators as standard JSON does not allow / support to generate JSON containing javascript functions like the following:

{
  type: "select",
  label: "Type",
  model: "type",
  values: [
    { id: "personal", name: "Personal" },
    { id: "business", name: "Business" }
   ]
},{
  type: "text",
  label: "Company name",
  model: "company.name",
  visible: function(model) {
    return model && model.type == "business";
  }
}

The workaround from #149 does not work in version 3.

Is there any know way to solve this??

[DelfsEngineering]

I also handled this in a similar fashion. Although a bit more work but very flexible. I have a parser that finds any key with the _calc extension and converts the value to an evaluated function and added as a getter. This way it works with all keys anywhere in the schema.

eg

visible_calc = "model.sAllowed"
// or 
values_calc = "model.myArrayOfValues"
// or 
styleClasses_calc = "model.isOverdue ? 'warning' : 'information' "

My technique replaces the raw key with the getter function

[zoul0813]

I’m not a big fan of evaluating a function like that… what I did was created the functions in my code, and just passed Paramus to them from the Json schema.

A quick look … seems your code should work though. I haven’t touched VFG in a few months though, so don’t have a project handy to test on at the moment (switched jobs back in March).