defaultNullable() is not respected by fields plugin

[davidkron]

I created a class implementing Validateable and have overridden the default nullable behavior with this code:

static boolean defaultNullable() {
    true
}

The fields plugin doesn't seem to respect this configuration, which results in all fields being required, instead of the opposite.

I am using Grails 3.1.x

[snimavat]

I think this is because, fields plugins doesnt consider validateable but uses the constrait evaluator directly. instead, it can check if the bean is validateable, thn instead of explicitly evaluating constraints, just call validateable.getConstraintsMap

[sbglasius]

In grails/plugin/formfields/BeanPropertyAccessorFactory.groovy:90 it uses the Grails build-in constraintsEvaluator and this evaluator apparently does not look at result from
static boolean defaultNullable() which would explain why the fields plugin does not obey the return value. This needs further investigation

[kevintanhongann]

I have just recently worked on the admin panel and it uses f:all to render the fields. The attributes that are marked as nullable:true is rendered to the display as required fields.