Bug: validation: "strict"does not work

[Sommerregen]

Dear Grav Team,

I'm pretty sure this bug was introduced a while ago (when re-factoring the Blueprint classes). But today I noticed that validation: "strict" cannot be "switched on", i.e., $blueprint->validate() never throws an error even if you provide data that do not exists in the blueprint definition. MWE:

form:
  validation: strict

  fields:
    test:
      type: text
      label: "Test"

Then with PHP:

$blueprint = new Blueprint("blueprints://...");
$blueprint->validate(['wrong' => 'field']);

[rhukster]

Passed this along to matias, as Forms/Blueprints are his speciality :)

[mahagr]

Note that blueprints need to be loaded and initialized now:

$blueprint = new Blueprint($filename);
$blueprint->load()->init();
$blueprint->validate(['wrong' => 'field']);
``

[mahagr]

@Sommerregen Unfortunately we have to revert this change from Grav 1.6 because of too many plugins and forms break because of the fix. :(

[mahagr]

@Sommerregen We decided to put this feature under a configuration option as way too many forms stop working because of devtools added a bad configuration option which people forgot to remove.