factor/basis/calendar/format/format-tests.factor

USING: accessors calendar calendar.format io io.streams.string
kernel math.order sequences tools.test ;
IN: calendar.format.tests

{ } [ now timestamp>rfc3339 drop ] unit-test
{ } [ now timestamp>rfc822 drop ] unit-test

{ }
[ { 2008 2009 } [ year. ] each ] unit-test


{ "03:01:59" } [
    3 hours 1 >>minute 59 >>second duration>hms
] unit-test
basis: Cleaning up tests using lists and IN: forms. 2016-03-30 23:04:14 -04:00			`USING: accessors calendar calendar.format io io.streams.string`
			`kernel math.order sequences tools.test ;`
calendar.format: moving parsing words to a new vocab calendar.parser The vocab was getting big so the idea is to have all the time parsing in calendar.parsing and only keep formatting words in calendar.format. 2017-01-04 02:50:24 -05:00			`IN: calendar.format.tests`
calendar.format: run dos2unix on calendar.format 2013-04-24 11:22:33 -04:00
factor: second stab at [ ] [ ] unit-test -> { } [ ] unit-test 2015-07-03 12:39:59 -04:00			`{ } [ now timestamp>rfc3339 drop ] unit-test`
			`{ } [ now timestamp>rfc822 drop ] unit-test`
calendar.format: run dos2unix on calendar.format 2013-04-24 11:22:33 -04:00
factor: second stab at [ ] [ ] unit-test -> { } [ ] unit-test 2015-07-03 12:39:59 -04:00			`{ }`
calendar.format: run dos2unix on calendar.format 2013-04-24 11:22:33 -04:00			`[ { 2008 2009 } [ year. ] each ] unit-test`
calendar.*: replacing hms>timestamp and timestamp>hms with duration variants hms>duration is better because a timestamp without a date is invalid. This also makes it so the SQL TIME column maps to duration. Now we can add some validation so that you aren't allowed to create invalid timestamps. 2017-01-04 06:47:45 -05:00

			`{ "03:01:59" } [`
			`3 hours 1 >>minute 59 >>second duration>hms`
			`] unit-test`