Closed
Description
As of v4.3, it is possible to create a JobParameter
with a null
value. Unless I'm missing something, I see no valid use case for that. Moreover, this might cause issues like #834 and makes the code defensive for no added value. Like other domain objects where passed parameters are validated at creation time, job parameter values should be validated at construction time to be non null.
This is breaking change, so I will schedule it for v5.