Validation improvements, including date checking

[garrett]

• only parse directories starting with 20 (for years), so build directory is not included
• sorts the parsing order (so you won't see errors with 2017 and then 2015, if there were errors spanning years)
• use Ruby's DateTime parsing to validate talk datetimes (which should still allow flexibility AND now with a correctness check)

[garrett]

@rbowen, @duck-rh, @mscherer: This is what we talked about in IRC yesterday. This implementation should work as we had decided (see issue #257). Please feel free to enhance otherwise.

[rbowen]

Thanks. This will be a big help.

…

--Rich

On 01/10/2017 05:18 AM, Garrett LeSage wrote: @rbowen <https://github.com/rbowen>, @duck-rh <https://github.com/duck-rh>, @mscherer <https://github.com/mscherer>: This is what we talked about in IRC yesterday. This implementation should work as we had decided (see issue #257 <#257>). Please feel free to enhance otherwise. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#258 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAPnQHqZiMedoJW7xUJDElkvQGE4ZsgMks5rQ1rngaJpZM4LfO4r>.

-- Rich Bowen - [email protected] - @rbowen http://apachecon.com/ - @apachecon

[garrett]

We can add additional checks, either via the schema or through Ruby (like this check), if you'd like. It should be pretty simple. However, that being said, I think most other things that need to be checked for are done so via the kwalify-based schema (schema.yml).

The datetimes on the talks were the main things lacking, as they had to be string-type (well, strings that match a regular expression). Happy that we now have logic.

---

One oversight, as I look at the code: Timezones (including daylight savings time) aren't checked. They should exist, and be in the correct daylight savings time. (Ruby's DateTime.parse seems to ignore incorrect timezones.)

[garrett]

Added an issue to implement timezone checking: #260.