winnow-rfc9557, making parsing RFC9557 dates a breeze

About

This library contains parsers for parsing RFC9557 dates and their various components built off the winnow-datetime parsers

Parsing

Complete

If you have all the data you need, you can just pass along the input directly.

let datetime = opt(datetime)
    .parse_next(&mut "2015-06-26 16:43:23+0200"));

// the above will give you:
Some(DateTime {
    date: Date::YMD {
        year: 2015,
        month: 6,
        day: 26,
    },
    time: Time {
        hour: 16,
        minute: 43,
        second: 23,
        tz_offset_hours: 2,
        tz_offset_minutes: 0,
    },
});

Partial

For partial data the only difference is wrapping input in Partial and handling incomplete errors correctly, which is documented in winnow partial docs.

pub type Stream<'i> = Partial<&'i [u8]>;

let datetime = opt(datetime)
    .parse_next(&mut Stream::new("2015-06-26 16:43:23+0200").as_bytes()));

// the above will give you:
Some(DateTime {
    date: Date::YMD {
        year: 2015,
        month: 6,
        day: 26,
    },
    time: Time {
        hour: 16,
        minute: 43,
        second: 23,
        tz_offset_hours: 2,
        tz_offset_minutes: 0,
    },
});

Caveats

Timezone Suffixes

The critical flag for suffixes are parsed according to the spec and saved in the AST but don't have an effect on exports to jiff (the only crate that currently handles timezones correctly). At the moment, if the offset or timezone was set in the suffix it simply takes precedence.

Calendar Suffixes

Per the spec, multiple calendar suffixes are allowed, but only the first one is parsed and used. The rest are ignored even if the critical flag is set.

Contributors

winnow-rfc9557 is the fruit of the work of many contributors over the years, many thanks for your help!

Documentation

Documentation is online.

License

MIT Licensed. See LICENSE