https://github.com/erabossid/fcc-timestamp-microservice

glitch-page- FCC Timestamp-Microservice Project
https://github.com/erabossid/fcc-timestamp-microservice

Last synced: about 1 month ago
JSON representation

glitch-page- FCC Timestamp-Microservice Project

• Host: GitHub
• URL: https://github.com/erabossid/fcc-timestamp-microservice
• Owner: erabossid
• Created: 2020-04-13T12:58:38.000Z (over 4 years ago)
• Default Branch: master
• Last Pushed: 2020-04-13T13:26:00.000Z (over 4 years ago)
• Last Synced: 2024-11-15T01:44:18.822Z (about 2 months ago)
• Language: HTML
• Homepage: https://fcc-timestamp-microservice-thetradecoder.glitch.me/api/timestamp/
• Size: 10.7 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
### solved-by: theTradeCoder

# 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" }