Toshiaki Maki

I don't understand the case where a ViolationMessage with arguments is needed. I think the intended use is to use a CustomConstatraint. Can you provide the full code for your...

I still can't grasp what the pain point is. The `ViolationMessage` class is the place to define static messages. Think of it as a line in `messages.properties`. Messages are resolved...

I'm sorry, but I'm having difficulty understanding what you're proposing here. Perhaps you could provide a more concrete example contrasting the current implementation with your proposed enhancement to help me...

Please don't rely on AI to write your proposal. Think for yourself and carefully review the AI's answers. YAVI automatically adds the field name to the beginning of args and...

I'm always open. I just wanted to understand user's pain points. > You are relying on a a message ViolationMessage.Default.NUMERIC_GREATER_THAN_OR_EQUAL that is from the framework. I want to rely on...

> The way I am using the formatting is not from within the framework itself but rather extracting the information from the `violations` and resolving the messages extracting the messageKey...

Your explanation is just an explanation of the source code, not why you need to pass args. Again, the args contains the field name, constraint parameters, and input values, which...

That sounds more like a violation of a responsibility than flexibility. If you want to give feedback on "possible values", you should use a constraint that checks whether the value...

What I'm saying is that args are determined automatically, and shouldn't be set when defining constraints. If you need something other than what's determined automatically, you should be able to...

> The framework provides its defaults but should allow the user to customise in the any way they intend to. I don't think so. Adding options that lead to incorrect...