I’ve been analyzing this with a MuleSoft engineer that is more experienced than me. We suspect that you are correct and it is a bug. It looks like it might not be supported till the next version of the runtime/Studio. Neither is released yet to the public, so releasing the Anypoint Cloud-based validation before the dev tools were ready was probably an oversight.
By trial and error, we did wire a simple datatype together that seems to behave (in the current runtime) the way we require. I hope we’re not “coding to a bug” such that it will break later!!
#%RAML 1.0 DataType
description: non-zero two-decimal place values (positive and negative)
For some reason, the min/max seem to allow 0, 0.0, 0.00 as values, even though they are not considered multiples of 0.01 (which is again arguable). We did both positive and negative testing and it seems to allow everything it should and prevent what it should. So for the moment, life is good.
Thanks for your help!
P.S. my Studio is v. 7.2.3 and my runtime is v. 4.1.2.