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
When we expect a vararg collection of events or commands, we want them rendered nicely in the jgiven report.
Current Behaviour
with #161 we removed the @table annotation because it could not (out of the box?) deal with different types.
So with version 0.2.0 we just get a string listing all events/commands by toString() and joinToString()
Wanted Behaviour
It would be nice to quickly see from a jgiven report which events/commands where used to have a table like rendering.
We should explore if we can achieve this by using custom formatters in jgiven.
Problem: We know nothing about the expected events/commands up front, so the approach will probably have to be very generic like | type | toString-value |
Possible Workarounds
leave as is
The text was updated successfully, but these errors were encountered:
Scenario
When we expect a vararg collection of events or commands, we want them rendered nicely in the jgiven report.
Current Behaviour
with #161 we removed the @table annotation because it could not (out of the box?) deal with different types.
So with version 0.2.0 we just get a string listing all events/commands by
toString()
andjoinToString()
Wanted Behaviour
It would be nice to quickly see from a jgiven report which events/commands where used to have a table like rendering.
We should explore if we can achieve this by using custom formatters in jgiven.
Problem: We know nothing about the expected events/commands up front, so the approach will probably have to be very generic like
| type | toString-value |
Possible Workarounds
leave as is
The text was updated successfully, but these errors were encountered: