https://github.com/flexyledger/apis-and-microservices-projects
https://github.com/flexyledger/apis-and-microservices-projects
Last synced: about 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/flexyledger/apis-and-microservices-projects
- Owner: flexyledger
- Created: 2018-10-27T08:45:30.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2018-10-27T08:49:59.000Z (over 6 years ago)
- Last Synced: 2024-02-01T21:26:39.507Z (over 1 year ago)
- Language: JavaScript
- Size: 10.7 KB
- Stars: 0
- Watchers: 0
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# API Project: Timestamp Microservice for FCC
### User stories :
1. The API endpoint is `GET [project_url]/api/timestamp/:date_string?`
2. A date string is valid if can be successfully parsed by `new Date(date_string)` (JS) . Note that the unix timestamp needs to be an **integer** (not a string) specifying **milliseconds**. In our test we will use date strings compliant with ISO-8601 (e.g. `"2016-11-20"`) because this will ensure an UTC timestamp.
3. If the date string is **empty** it should be equivalent to trigger `new Date()`, i.e. the service uses the current timestamp.
4. If the date string is **valid** the api returns a JSON having the structure
`{"unix": , "utc" : }`
e.g. `{"unix": 1479663089000 ,"utc": "Sun, 20 Nov 2016 17:31:29 GMT"}`.
5. If the date string is **invalid** the api returns a JSON having the structure `{"unix": null, "utc" : "Invalid Date" }`. It is what you get from the date manipulation functions used above.
#### Example usage:
* https://curse-arrow.hyperdev.space/api/timestamp/2015-12-15
* https://curse-arrow.hyperdev.space/api/timestamp/1450137600000
#### Example output:
* { "unix": 1450137600, "natural": "December 15, 2015" }