You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
The configuration seems very specific, though; on first glance, I don't see how to tell the generator "if the property has type X, use this template instead/also".
I think #220 would be a neater, more generally applicable alternative. Of course, we couldn't get back to the original Assert once we "descend" into the one of the property, so there may be independent value of unwrapping single-property classes/records.
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
_.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: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.
The text was updated successfully, but these errors were encountered: