summaryrefslogtreecommitdiff
path: root/util
diff options
context:
space:
mode:
authorYorhel <git@yorhel.nl>2015-09-20 16:14:59 +0200
committerYorhel <git@yorhel.nl>2015-09-20 16:14:59 +0200
commited86cfd12b0bed7352e2be525b8e63cb4d6d5448 (patch)
tree321f346791cbff80c8355a736e6f4ecb90084d49 /util
parentbb7a7cc178144457d401c3c6479a41788cf681dd (diff)
formValidate: Add json template and remove json_validate() function
This is less convenient than I had expected, because all the form handling code is designed to work with plain strings rather than any scalar. This means the json data has to be encoded again to get into $frm (not doing this means that, if the form didn't validate, the field won't be filled out correctly). And then decoded for validation, and then encoded again for comparison. I suspect the better solution is to fix the form handling code to handle arbitrary data structures: comparison can be done by deep comparison rather than a simple string compare, and the form generator can auto-encode-to-json if it sees a complex object. Another advantage of this solution is that the comparison function can be less strict with respect to number formatting. In the current scheme you have to be very careful that numbers are not automatically coerced into string format, otherwise the comparison will fail. Either way, that's an idea for the future...
Diffstat (limited to 'util')
-rwxr-xr-xutil/vndb.pl25
1 files changed, 24 insertions, 1 deletions
diff --git a/util/vndb.pl b/util/vndb.pl
index 9a3663a9..fd70e564 100755
--- a/util/vndb.pl
+++ b/util/vndb.pl
@@ -15,8 +15,9 @@ BEGIN { ($ROOT = abs_path $0) =~ s{/util/vndb\.pl$}{}; }
use lib $ROOT.'/lib';
-use TUWF ':html';
+use TUWF ':html', 'kv_validate';
use VNDB::L10N;
+use VNDB::Func 'json_encode', 'json_decode';
use VNDBUtil 'gtintype';
use SkinFile;
@@ -54,6 +55,7 @@ TUWF::set(
uname => { regex => qr/^[a-z0-9-]*$/, minlength => 2, maxlength => 15 },
gtin => { func => \&gtintype },
editsum => { maxlength => 5000, minlength => 2 },
+ json => { func => \&json_validate, inherit => ['json_fields'], default => [] },
},
);
TUWF::load_recursive('VNDB::Util', 'VNDB::DB', 'VNDB::Handler');
@@ -131,3 +133,24 @@ sub logformat {
$self->authInfo->{id} ? 'u'.$self->authInfo->{id} : '-', $msg;
}
+
+# Special validation function for simple JSON structures as form fields. It can
+# only validate arrays of key-value objects. The key-value objects are then
+# validated using kv_validate.
+sub json_validate {
+ my($val, $opts) = @_;
+ my $fields = $opts->{json_fields};
+ my $data = eval { json_decode $val };
+ return 0 if $@ || ref $data ne 'ARRAY';
+ my %known_fields = map +($_->{field},1), @$fields;
+ for my $i (0..$#$data) {
+ return 0 if ref $data->[$i] ne 'HASH';
+ # Require that all keys are known and have a scalar value.
+ return 0 if grep !$known_fields{$_} || ref($data->[$i]{$_}), keys %{$data->[$i]};
+ $data->[$i] = kv_validate({ field => sub { $data->[$i]{shift()} } }, $TUWF::OBJ->{_TUWF}{validate_templates}, $fields);
+ return 0 if $data->[$i]{_err};
+ }
+
+ $_[0] = json_encode $data;
+ return 1;
+}