-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Support for Timex to replace Tzdata #31
Comments
I was just thinking about this again this morning. Many developers indeed stick to tzdata while it's slower and still has bugs, and I can only guess the main reason being Timex. I intend to address this soon enough and allow for a smooth transition from Timex/tzdata to tz. (Note that I did have a look into Timex a long time ago and found that creating a PR to support any time zone database would be too large of an effort. Therefore I'll come with an alternative solution.) |
@nallwhy Timex was created before the native calendar API had the full range of functions it offers today. An idea is to provide a library allowing to migrate to the native apis: https://github.com/mathieuprog/tz_timex It will generate a set of warnings guiding you on how to replace the Timex code. Could you tell me:
Note that I did not publish on hex right now, you may depend on the github repo. |
Thanks! I can check it in 3 days as I'm currently on holiday. |
I understand the concept of |
https://hex.pm/packages/datix Your app or TzTimex could use one of those libraries to provide |
Following TzTimex and your comments, I've succeeded to remove Timex from my project. (I used datix.) |
I’m considering replacing tzdata with the tz library, but it’s difficult to make the switch if the tz library doesn’t provide equivalent support for the functions used in timex, which many elixir applications depend on.
Providing support for the key functions that timex uses from tzdata would make the transition much smoother and help more developers adopt tz across a wider range of applications.
function list
The text was updated successfully, but these errors were encountered: