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

Returning dates/times as unix timestamps vs ISO strings #8

Open
GUI opened this issue Nov 13, 2014 · 1 comment
Open

Returning dates/times as unix timestamps vs ISO strings #8

GUI opened this issue Nov 13, 2014 · 1 comment

Comments

@GUI
Copy link
Member

GUI commented Nov 13, 2014

Feedback from our API Usability Testing: One of the participants preferred if all times being returned from our APIs would be returned as unix timestamp integers. I think most of our APIs typically return things times as ISO 8601 strings. The preference for unix timestamps is that they can be added and subtracted directly without having to first parse and create date objects in your language based on the ISO 8601 string.

@GUI
Copy link
Member Author

GUI commented Nov 13, 2014

And I guess for my own personal preference here, I prefer the readability of ISO 8601 strings instead of unix timestamps. The string approach does mean you have to parse it into a date object in whatever language you're dealing with, but I think the same usually goes for unix timestamps as well (it seems rare that I'm just needing to add or subtract dates as integers, but this obviously depends a lot of the use case). But I'd certainly like to hear anyone else's feedback or preferences on how they prefer to receive dates and times in an API.

GUI pushed a commit that referenced this issue May 14, 2015
Split WindExchange docs into schools and education
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

1 participant