Comment 2 for bug 1477910

Yep, I got this issue...

My opinion is rejecting schema validation by default for image-list is okay, especially for the reason that it almost doesn't work now (only for the first image in a batch). But I think we can add a flag (like --validate-schema) to make users decide if they want validation or not. And it will apply to all images in a batch, not only for the first one, even regardless the performance of the operation.
But it's just a workaround... I think about if it feasible to fix it on the server side. We can't change v1 api, so restricting of those parameters to strings only (not ints or bools) is not possible.
What about to convert those types during serialisation in v2 (ie setting their type to 'string')?