What was fixed?

Fixed an issue where if the param of a time.Durtion type is specified
as an integer, denoting nanosecond precision, instead of time duration
string the validation would panic introduced in #642

The fix ensures it falls back to the previous expected behaviour.