- Notifications
You must be signed in to change notification settings - Fork26
PermalinkChoose a base ref {{ refName }}default Choose a head ref {{ refName }}default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also orlearn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also.Learn more about diff comparisons here.
base repository:uutils/parse_datetime
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
Uh oh!
There was an error while loading.Please reload this page.
base:70d3e53
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}defaultLoading
...
head repository:uutils/parse_datetime
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
Uh oh!
There was an error while loading.Please reload this page.
compare:bed2d16
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}defaultLoading
- 15commits
- 11files changed
- 4contributors
Commits on Jun 3, 2023
Add a relaxed datetime parser. This datetime parser functions by using `chrono`sown parsing utilities and a try/succeed approach to parsing.This implementation of the datetime parser has some drawbacks and somepositives. On the positive side:- it was easy to implement- it is easy to add more datetime formats toIn order to add additionally supported formats, a developer can add therequired format string to the `format` mod in `parse_datetime.rs`, andthen add it as a potential format to the relevant `fmts` vec.On the negative:- It is not easily customiseable beyond the supported `chrono` parsing formats. E.g., `chrono` does not currently support parsing offsets without trailing zeros. `from_str("UTC+1")` should return a valid response but `chrono` fails to parse this.- Because it is an attempt driven parser, it is likely not that performant. I have not done any performance testing as part of thischange, but I would expect a custom parser to perform much better.
Benjscho committedJun 3, 2023
Commits on Jun 5, 2023
- Benjscho committed
Jun 5, 2023 Co-authored-by: Sylvestre Ledru <sledru@mozilla.com>
Commits on Jun 6, 2023
Update the README and add a test module to parse_datetime for anyexamples presented in the README.
Benjscho committedJun 6, 2023
Commits on Jun 7, 2023
add a fuzzer for parse_datetime_from_str
sylvestre committedJun 7, 2023 - sylvestre committed
Jun 7, 2023 - sylvestre authored
Jun 7, 2023
Commits on Jun 8, 2023
Merge pull request#21from sylvestre/fuzz
Also fuzz fuzz_parse_datetime_from_str for a minute
sylvestre authoredJun 8, 2023
Commits on Jun 9, 2023
rename from humantime_to_duration to parse_datetime
sylvestre committedJun 9, 2023 Merge pull request#22from sylvestre/rename
rename from humantime_to_duration to parse_datetime
sylvestre authoredJun 9, 2023 - sylvestre committed
Jun 9, 2023 - sylvestre committed
Jun 9, 2023
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:git diff 70d3e53...bed2d16
Uh oh!
There was an error while loading.Please reload this page.