Timestamp Microservice https://timestamp.radiidev.repl.co/
Go to file
Obaida Albaroudi a9b12d4bb9 Added .replit
Lockfile
Readme
2020-07-08 15:54:27 +09:00
public Initial commit from Gomix. 2017-02-18 18:54:04 +00:00
views Update views/index.html 2020-04-23 15:42:35 +09:00
.gitconfig Initial commit from Gomix. 2017-02-18 18:54:04 +00:00
.gitignore Create .gitignore 2018-12-14 12:37:09 +01:00
.hyperdev-assets Initial commit from Gomix. 2017-02-18 18:54:04 +00:00
.replit Added .replit 2020-07-08 15:54:27 +09:00
package-lock.json Added .replit 2020-07-08 15:54:27 +09:00
package.json Added .replit 2020-07-08 15:54:27 +09:00
README.md Added .replit 2020-07-08 15:54:27 +09:00
server.js Initial commit from Gomix. 2017-02-18 18:54:04 +00:00

API Project: Timestamp Microservice for FCC

User stories:

Run on Repl.it

  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": <date.getTime()>, "utc" : <date.toUTCString()> } 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 {"error" : "Invalid Date" }.

Example usage:

Example output:

  • {"unix":1451001600000, "utc":"Fri, 25 Dec 2015 00:00:00 GMT"}