Issue about time rule about relate HOT 7 CLOSED

I see there's a parse_date_spec function with return_now_on_error default True. Seems the reason is parse_date_spec failed to parse the time and return now() as the results.

from relate.

Right. The reason for this whole mess is that when you first create a course that relies on a bunch of events, all of these events are not known, because the course needs to exist first in order for you to create the events. On the other hand, the course content doesn't make sense without the events in place. That's a circular dependency, and it needs to be broken somehow.

The way I chose to do that was by parsing unknown events as "right now" (the flag you found) and letting the user check which date/time fields encountered an error while parsing. (Content > Check Events) If you've got a better suggestion, I'd be happy to hear it.

But even with the existing feature, I think the UI could stand to be renamed and reshuffled a bit. (Possibly: Check date validity?) I'll work on that.

from relate.

47a5b91 should significantly improve the usability of this. Unrecognized date/time specifications now generate warnings during update, which is more natural (and more visible) than the hidden "check events" feature.

from relate.

Validation failed for course content for flows using time with the ISO format since your latest commit. Maybe I should dive into the logic and relationships between events and time setting. Thank you.

from relate.

Should be fixed in 2e1426e, tested in sample content:

inducer/relate-sample@03f9f6c

from relate.

Now I can be confident to say I understand the relationship between events and time rule, I think it's really a good idea! Thank you. Now the problem is, under what circumstance will the ISO format time function?

from relate.

It'll be viewed as an ISO timestamp if YAML parses it as one.

See example 2.22 here:
http://www.yaml.org/spec/1.2/spec.html#id2761292

from relate.