This is potentially a little vague in its broadness, but here goes.
Say we have a value class like e.g.
@Value
class AccountNumber {
String rawValue;
}
If another class (for which we generate assertions) has a property of this type, we can assert:
assertThat(someObject).hasAccountNumber(new AccountNumber("abc"))
Nicer would be:
assertThat(someObject).hasAccountNumber("abc")
The generator could look for constructors, static _.of methods, and other popular patterns. It's not clear to me if there should be a limit on the length of the parameter list. Anyway, the desired implementation seems straight-forward:
public S hasAccountNumber(String accountNumberRawValue) {
return hasAccountNumber(new AccountNumber(fooRawValue));
}
As an alternative, there could be an annotation like e.g.
@AssertionAlias
static Foo of(String rawValue) { ... }
On a property Foo bar, this would cause additional generation of something like
public S hasBar(String fooRawValue) {
return hasBar(Foo.of(fooRawValue));
}
PS: This is probably easily done for specific use cases in any given project using templates, but I don't see documentation for a way to inject custom templates when using the generator through the Maven plugin.
This is potentially a little vague in its broadness, but here goes.
Say we have a value class like e.g.
If another class (for which we generate assertions) has a property of this type, we can assert:
Nicer would be:
The generator could look for constructors, static
_.ofmethods, and other popular patterns. It's not clear to me if there should be a limit on the length of the parameter list. Anyway, the desired implementation seems straight-forward:As an alternative, there could be an annotation like e.g.
On a property
Foo bar, this would cause additional generation of something likePS: This is probably easily done for specific use cases in any given project using templates, but I don't see documentation for a way to inject custom templates when using the generator through the Maven plugin.