When adding the jakarta-validation plugin, the defaultArbitraryContainerInfo setting does not work properly about fixture-monkey HOT 6 CLOSED

@doljae
Ok, I think it is not a tough issue. Thank you.

I think that it is better to remove a field defaultArbitraryContainerInfo in GenerateOptions.
Maybe defaultArbitraryContainerSize too.
Using ArbitraryContainerInfoGenerator instead.

But should remain LabMonkey's defaultArbitraryContainerInfo option.

from fixture-monkey.

@doljae
In GenerateOptions, it returns defaultArbitraryContainerInfo when no proper ArbitraryContainerInfoGenerator exists.
I think returning default ArbitraryContainerInfoGenerator is more better instead of defaultArbitraryContainerInfo.

So what we have to do is removing defaultArbitraryContainerInfo option and making defaultArbitraryContainerInfoGenerator option

from fixture-monkey.

@doljae
It is a bug.

Javax-validation ,Jakarata-validation modules changes ArbitraryContainerInfoGenerator for handling @NotEmpty, @Size annotations.

You could resolves this problem temporary as below

.pushArbitraryContainerInfoGenerator(
                MatcherOperator(
                    { true },
                    ArbitraryContainerInfoGenerator { ArbitraryContainerInfo(minSize, maxSize, false) }
                )
            )

Thank you for reporting, we resolve this issue as soon as possible!

from fixture-monkey.

@seongahjo
Can I fix this bug?

It might be a little more complicated than this issue, but if it's not too difficult, I'll give it a try 🙂

If the size is too large or already in the works, you, the maintainer, please fix it 🙏

from fixture-monkey.

@seongahjo ,
Could you explain a bit more on what I need to do?
I've done some work on my own, but I think I'm not understanding it very well 😓

from fixture-monkey.

@seongahjo ,
I created a PR for this issue.
I'm not sure I work well, so if you think there's not enough time to fix it myself, then please take this issue.

from fixture-monkey.