NatLabRockies / NatLabRockies/developer.nlr.gov
Returning dates/times as unix timestamps vs ISO strings
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 60
- Forks
- 57
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 3
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, endpoint, or failing test is identified. Start by reviewing the APIs' existing date and time response conventions and the linked API Usability Testing feedback. Done would require a decided, documented timestamp format and an agreed scope for affected API responses.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100