FieldVisibilityEventHandler: use new DataValidator API

I updated DataValidator but never updated the caller.  Damnit.  It's
an unfortunate side-effect of dynamic, loosely typed languages and
mitigating it requires what should be boilerplate functional tests (in
this case---functional tests are useful for many other integration
aspects).

* src/event/FieldVisibilityEventHandler.js
  (handle): Use updated DataValidator#clearFailures API, which has
    a different descriptor format.

* test/event/FieldVisibilityEventHandlerTest.js: Update test.

1 files changed, 4 insertions, 3 deletions

diff --git a/test/event/FieldVisibilityEventHandlerTest.js b/test/event/FieldVisibilityEventHandlerTest.js
index 005e0e7..85b07c9 100644
--- a/test/event/FieldVisibilityEventHandlerTest.js
+++ b/test/event/FieldVisibilityEventHandlerTest.js
@@ -96,11 +96,12 @@ describe( 'FieldVisibilityEventHandler', () =>
 
     it( 'clears failures on hidden fields', done =>
     {
-        const name = 'foo_bar';
+        const name         = 'foo_bar';
+        const fail_indexes = [ 0, 3 ];
 
         const hide_data = {
             elementName: name,
-            indexes:     [ 0 ],
+            indexes:     fail_indexes,
         };
 
         Sut(
@@ -108,7 +109,7 @@ describe( 'FieldVisibilityEventHandler', () =>
             createStubDataProvider( failures =>
             {
                 expect( failures )
-                    .to.deep.equal( [ name ] )
+                    .to.deep.equal( { [name]: fail_indexes } );
 
                 // we don't care about the rest of the processing at this
                 // point