Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems like great work so far! Thanks so much for putting in the work!
This commit puts `chrono` behind a feature flag and adds `time` as an alternative to it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking great so far! Thanks for all your work!
Ok...this should again be ready for a review. Hopefully the final one 😅🙃. Sorry for missing all the little things. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need to be sorry at all, thanks for your hard work! We'll merge this in for now, and I'll work on doing some things on my end and cutting a release!
You are welcome. And happy to hear that. |
Good work on this PR! I am a happy user of the lib and hope a new version can be released. Would that be an option? |
Hey @frederikbosch , Yep I'm getting to it, unfortunately have had some other things pop up first. But I'll schedule for some time for it, at the latest I'd expect this weekend. |
This commit puts
chrono
behind a feature flag and addstime
as an alternative to it.One thing to note is, that i had to exclude https://github.com/Weasy666/paseto/blob/1b97dcb99565807e43057e96470a03472ed9ac46/src/tokens/mod.rs#L51 from being build, when both features
easy_token_chrono
andeasy_token_time
are activated, as there is no way to guess which time crate should be used to parse the json time.