Open boubbin opened 6 years ago
Hey @boubbin, I have just run into same problem - have you ever managed to get it working somehow?
Hey @boubbin, I have just run into same problem - have you ever managed to get it working somehow?
No. I did not.
We are still using this library extensively and I haven't encountered this problem in a long time. My guess is that we only had one constraint using propertyPath.
I suggest that you look into transferring the constraint into callback constraint (if possible) since they work very nicely with the library. They are a bit more work but once you have some ground work in place they come easy. We have currently multiple dozen different callback constraints implemented client-side.
One option is also to disable the validation for this field in the client-side. You will sooner or later need this kind of mechanism anyway where you can easily just not validate some constraints.
For example this annotation
Will be processed with GreaterThan like it should be:
but
this.value
is always null here and therefor the field is never valid.I could not find any references in the code to
propertyPath
but it is parsed correctly to the client side, just never used. Anyway you will never know what is the actual element in this case