Mike Gerwitz

Activist for User Freedom

aboutsummaryrefslogtreecommitdiffstats
path: root/conf
diff options
context:
space:
mode:
authorMike Gerwitz <mike.gerwitz@rtspecialty.com>2019-03-07 16:09:22 -0500
committerMike Gerwitz <mike.gerwitz@rtspecialty.com>2019-03-07 16:13:36 -0500
commit814b0ff3a04fe5e48004937cf7e92b062f6800db (patch)
treea132d2ea3bde46667b7592d85dfbfde2a8d89e50 /conf
parent53078919bba7ff85514b718a845345c5ab2bc948 (diff)
downloadliza-814b0ff3a04fe5e48004937cf7e92b062f6800db.tar.gz
liza-814b0ff3a04fe5e48004937cf7e92b062f6800db.tar.bz2
liza-814b0ff3a04fe5e48004937cf7e92b062f6800db.zip
Client: Fix forward-validation failure messages
Forward validation failures were never updated to use the new Failure object, so they ended up showing the default message. The problem was that `ui.invalidateForm' was replacing the Failure object with a new one with an empty message. This change just does the same thing as the change and save events. * src/client/Client.js (_forwardValidate): Invoke `#_genValidationMessages' and `_dataValidator.updateFailures'. Stop calling `ui.invalidateForm'.
Diffstat (limited to 'conf')
0 files changed, 0 insertions, 0 deletions