Commmit current datetime parsing work

This commit is contained in:
2023-07-21 23:35:41 -05:00
parent ffde9e68e0
commit 8dc13f29ad
4 changed files with 284 additions and 1 deletions

View File

@@ -18,4 +18,49 @@ My first Rust project, intended to offer a simple way to display the current tim
- `/svg/2023-06-14-3PM-CST`
- `2023-06-14-3PM-CST.svg`
- `/jpeg/2023.06.14.33` (14th of June, 2023, 2:33 PM UTC)
- `/jpeg/2023.06.14.33T-5` (14th of June, 2023, 2:33 PM UTC-5)
- `/jpeg/2023.06.14.33T-5` (14th of June, 2023, 2:33 PM UTC-5)
## Structure
1. Routing
- Handle different input formats at the route layer
2. Parsing
- Module for parsing input
3. Cache Layer
- Given all route options, provide a globally available cache for the next layer
4. SVG Template Rendering
- Template rendering based on parsed input
5. (Optional) Rasterization
- If rasterization is requested, render SVG to PNG
6. (Catch-all) Error Handling
- All errors/panics will be caught in separate middleware
## Input Parsing
- Separators can be any of the following: `.`, `,`, `-`, `:` and ` `.
- They must be consistent through the date section and the time section (they can be different between the two).
- Date order can be modified with `?date=[YMD|DMY|MDY]`. By default, it is `YMD`.
- Time is not required, but will default each value to 0 (except HOUR, which is the minimum specified value).
- Millisecond precision is allowed, but will be ignored in most outputs. Periods or commas are allowed as separators.
- Timezones can be qualified in a number of ways, but will default to UTC if not specified.
- Fully qualified TZ identifiers like "America/Chicago" are specified using the `tz` query parameter.
- Abbreviated TZ identifiers like "CST" are specified inside the time string, after the time, separated by a dash.
- Abbreviated terms are incredibly ambiguous, and should be avoided if possible. For ease of use, they are
available, but several of them are ambiguous, and the preferred TZ has been specified in code.
- Full table available in [`abbr_tz`](./src/abbr_tz). Comments designated with `#`. Preferred interpretation
designated arbitrarily by me. Table sourced
from [Wikipedia](https://en.wikipedia.org/wiki/List_of_time_zone_abbreviations)
```shell
2023-06-14-3 # 3AM UTC
2023-06-14-3-45 # 3:45AM UTC
2023-06-14-3PM-CST
2023.06.14.15-CST # 3PM CST
2023.06.14.15-45-CST # 3:45PM CST
2023.06.14.15-45-30-CST # 3:45:30PM CST
2023.06.14.15-45-30.123-CST # 3:45:30.123PM CST
2023.06.14.15-45-30,123-CST # 3:45:30.123PM CST
```
## Output Formats