Stream: committers
Topic: Standards-appropriate examples
Cooper Thompson (Feb 02 2017 at 22:45):
Why is the year 2364 not considered valid?
[java] ERROR @ Schedule.planningHorizon.start (line 0, col0) schedule-provider-location2-example::Schedule.planningHorizon.start: The value '2364-12-25T09:15:00Z' does not have a valid year (src = InstanceValidator)
In my awesome example of a schedule for Dr. Beverly Crusher on the USS-Enterprise-D, the year 2364 is indeed the appropriate planning horizon. Also, the regex of dateTime appears to accept [0-9]{4} for the year.
This is obviously trivially fixed, but I did have two questions as a new committer:
1. Are fun/humorous examples encouraged or discouraged?
2. Do we have a Y2K-style dateTime validation bug (or intentional restriction) somewhere?
Lloyd McKenzie (Feb 02 2017 at 23:19):
I think we do a sanity check to help avoid typos - intention is that most of the examples should be semi-realistic
Grahame Grieve (Feb 06 2017 at 02:37):
a moderate amount of fun/humour is just fine. That date was disallowed as Lloyd said
Last updated: Apr 12 2022 at 19:14 UTC
