Add DateTime ranged relay #1162
Conversation
| return new DateTime((long)ticksInRange); | ||
| } | ||
|
|
||
| private struct DateTimeRange |
There was a problem hiding this comment.
Nit: We could also make it a readonly struct, as it's not supposed to be mutated.
There was a problem hiding this comment.
Will the TimeSpanRange also need to be updated?
|
Not a maintainer. Would it be possible to add a way to control which culture is used in the parsing process? It could be helpful to be explicit in a multi-culture environment where developers have their machine with one locale (e.g. it-it) and the build server uses something else (e.g. en-us). In this case parsing 1/12/1997 might work on a dev machine (where it's read as December 1st) but not on the build server (read as January 12th) |
|
Can you show me how the range attribute can be setup to parse the datetime explicitly? |
|
Looks like there is no way to override the parse for the range attribute at this time so the current implementation will cover all uses |
| return RandomizeDateTimeInRange(range, context); | ||
| } | ||
|
|
||
| private static DateTimeRange ParseTimeSpanRange(RangedRequest rangedRequest) |
Allows The ability to Parse Range Attributes for the type DateTime and create a valid DateTime within the specified range