Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Idea: optionally support Timex in last_modified and related callbacks (depending on the return type?) #12

Closed
yrashk opened this issue Jan 27, 2015 · 5 comments
Assignees

Comments

@yrashk
Copy link
Contributor

yrashk commented Jan 27, 2015

Timex is a great datetime library: https://hex.pm/packages/timex

@awetzel
Copy link
Collaborator

awetzel commented Jan 28, 2015

Yes pretty good idea, add a dependency is against the initial goal of this webmachine rewriting, but actually make it optional seems doable and useful. I will do it when I find time next week.

@tomekowal
Copy link

There is also calendar library: https://github.com/lau/calendar It might be a good idea to wait until Elixir 1.3 which will provide date and time types http://tuvistavie.com/2016/elixir-1-3/#calendar-datatypes Then the libraries will have to adjust to those types :)

@Shakadak
Copy link
Member

Hi, is this still of interest ? I'd like to understand the need and the context.

@Shakadak Shakadak self-assigned this Sep 15, 2021
@tomekowal
Copy link

tomekowal commented Sep 15, 2021

I commented in 2016 but I am not interested anymore and I don't really remember what was my use case back then. Thanks for asking, though!

@Shakadak
Copy link
Member

Alright, the need didn't come up in our projects either, so I'm closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants