Timestamp Microservice https://timestamp.radiidev.repl.co/
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Kristofer Koishigawa b2b2330cfc
Update views/index.html
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
4 years ago
public Initial commit from Gomix. 7 years ago
views Update views/index.html 4 years ago
.gitconfig Initial commit from Gomix. 7 years ago
.hyperdev-assets Initial commit from Gomix. 7 years ago
README.md fix: syncs index.html and README.md with the example project at https://curse-arrow.glitch.me/ 4 years ago
package.json Initial commit from Gomix. 7 years ago
server.js Initial commit from Gomix. 7 years ago

README.md

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