Johannes Link
Johannes Link
One more idea. What if `@ForAll` could also resolve Arbitrary types. Like ```java @Provide Arbitrary aString(@ForAll Arbitrary ints) { return ints.map(i -> i.toString()); } ``` This would not hide map/flatMap/combine...
That was so easy to implement that I just did it. Now this works: ```java @Property void test(@ForAll("chessSquares") String square) { System.out.println(square); } @Provide Arbitrary chessSquares( @ForAll Arbitrary rows, @ForAll...
@vlsi Would `@InjectArbitrary` be more understandable than `@ForAll` in this case?
`@Inject` seemed too generic, but I'm unsure.
Currently, I don't see any other types.
What about `@ForArbitrary`?
@mmerdes Can you give a link to a good reference or overview for JSR 303/380? An example to show what you mean would be helpful to the viewer who does...
@mmerdes This makes sense I'll have a look at what Jakarta Bean Validation has in store and identify the low hanging fruits. How useful do you think would a partial...
@mmerdes Would you expect the constraints to always apply or would an annotation like `@ApplyValidations` suite your needs?
The suggested annotation does not work, because annotation attributes cannot be functions, all you can have is a class that implements a function. In that sense @Domain is as good...