* chore: rename APIs and Microservices to include "Backend" (#42515) * fix typo * fix typo * undo change * Corrected grammar mistake Corrected a grammar mistake by removing a comma. * change APIs and Microservices cert title * update title * Change APIs and Microservices certi title * Update translations.json * update title * feat(curriculum): rename apis and microservices cert * rename folder structure * rename certificate * rename learn Markdown * apis-and-microservices -> back-end-development-and-apis * update backend meta * update i18n langs and cypress test Co-authored-by: Shaun Hamilton <shauhami020@gmail.com> * fix: add development to front-end libraries (#42512) * fix: added-the-word-Development-to-front-end-libraries * fix/added-the-word-Development-to-front-end-libraries * fix/added-word-development-to-front-end-libraries-in-other-related-files * fix/added-the-word-Development-to-front-end-and-all-related-files * fix/removed-typos-from-last-commit-in-index.md * fix/reverted-changes-that-i-made-to-dependecies * fix/removed xvfg * fix/reverted changes that i made to package.json * remove unwanted changes * front-end-development-libraries changes * rename backend certSlug and README * update i18n folder names and keys * test: add legacy path redirect tests This uses serve.json from the client-config repo, since we currently use that in production * fix: create public dir before moving serve.json * fix: add missing script * refactor: collect redirect tests * test: convert to cy.location for stricter tests * rename certificate folder to 00-certificates * change crowdin config to recognise new certificates location * allow translations to be used Co-authored-by: Nicholas Carrigan (he/him) <nhcarrigan@gmail.com> * add forwards slashes to path redirects * fix cypress path tests again * plese cypress * fix: test different challenge Okay so I literally have no idea why this one particular challenge fails in Cypress Firefox ONLY. Tom and I paired and spun a full build instance and confirmed in Firefox the page loads and redirects as expected. Changing to another bootstrap challenge passes Cypress firefox locally. Absolutely boggled by this. AAAAAAAAAAAAAAA * fix: separate the test Okay apparently the test does not work unless we separate it into a different `it` statement. >:( >:( >:( >:( Co-authored-by: Sujal Gupta <55016909+heysujal@users.noreply.github.com> Co-authored-by: Noor Fakhry <65724923+NoorFakhry@users.noreply.github.com> Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com> Co-authored-by: Nicholas Carrigan (he/him) <nhcarrigan@gmail.com>
		
			
				
	
	
		
			155 lines
		
	
	
		
			4.1 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
			
		
		
	
	
			155 lines
		
	
	
		
			4.1 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
| ---
 | |
| id: bd7158d8c443edefaeb5bdef
 | |
| title: Timestamp Microservice
 | |
| challengeType: 4
 | |
| forumTopicId: 301508
 | |
| dashedName: timestamp-microservice
 | |
| ---
 | |
| 
 | |
| # --description--
 | |
| 
 | |
| Build a full stack JavaScript app that is functionally similar to this: <https://timestamp-microservice.freecodecamp.rocks/>. Working on this project will involve you writing your code using one of the following methods:
 | |
| 
 | |
| -   Clone [this GitHub repo](https://github.com/freeCodeCamp/boilerplate-project-timestamp/) and complete your project locally.
 | |
| -   Use [our Replit starter project](https://replit.com/github/freeCodeCamp/boilerplate-project-timestamp) to complete your project.
 | |
| -   Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
 | |
| 
 | |
| When you are done, make sure a working demo of your project is hosted somewhere public. Then submit the URL to it in the `Solution Link` field. Optionally, also submit a link to your projects source code in the `GitHub Link` field.
 | |
| 
 | |
| # --hints--
 | |
| 
 | |
| You should provide your own project, not the example URL.
 | |
| 
 | |
| ```js
 | |
| (getUserInput) => {
 | |
|   assert(
 | |
|     !/.*\/timestamp-microservice\.freecodecamp\.rocks/.test(getUserInput('url'))
 | |
|   );
 | |
| };
 | |
| ```
 | |
| 
 | |
| A request to `/api/:date?` with a valid date should return a JSON object with a `unix` key that is a Unix timestamp of the input date in milliseconds
 | |
| 
 | |
| ```js
 | |
| (getUserInput) =>
 | |
|   $.get(getUserInput('url') + '/api/2016-12-25').then(
 | |
|     (data) => {
 | |
|       assert.equal(
 | |
|         data.unix,
 | |
|         1482624000000,
 | |
|         'Should be a valid unix timestamp'
 | |
|       );
 | |
|     },
 | |
|     (xhr) => {
 | |
|       throw new Error(xhr.responseText);
 | |
|     }
 | |
|   );
 | |
| ```
 | |
| 
 | |
| A request to `/api/:date?` with a valid date should return a JSON object with a `utc` key that is a string of the input date in the format: `Thu, 01 Jan 1970 00:00:00 GMT`
 | |
| 
 | |
| ```js
 | |
| (getUserInput) =>
 | |
|   $.get(getUserInput('url') + '/api/2016-12-25').then(
 | |
|     (data) => {
 | |
|       assert.equal(
 | |
|         data.utc,
 | |
|         'Sun, 25 Dec 2016 00:00:00 GMT',
 | |
|         'Should be a valid UTC date string'
 | |
|       );
 | |
|     },
 | |
|     (xhr) => {
 | |
|       throw new Error(xhr.responseText);
 | |
|     }
 | |
|   );
 | |
| ```
 | |
| 
 | |
| A request to `/api/1451001600000` should return `{ unix: 1451001600000, utc: "Fri, 25 Dec 2015 00:00:00 GMT" }`
 | |
| 
 | |
| ```js
 | |
| (getUserInput) =>
 | |
|   $.get(getUserInput('url') + '/api/1451001600000').then(
 | |
|     (data) => {
 | |
|       assert(
 | |
|         data.unix === 1451001600000 &&
 | |
|           data.utc === 'Fri, 25 Dec 2015 00:00:00 GMT'
 | |
|       );
 | |
|     },
 | |
|     (xhr) => {
 | |
|       throw new Error(xhr.responseText);
 | |
|     }
 | |
|   );
 | |
| ```
 | |
| 
 | |
| Your project can handle dates that can be successfully parsed by `new Date(date_string)`
 | |
| 
 | |
| ```js
 | |
| (getUserInput) =>
 | |
|   $.get(getUserInput('url') + '/api/05 October 2011').then(
 | |
|     (data) => {
 | |
|       assert(
 | |
|         data.unix === 1317772800000 &&
 | |
|           data.utc === 'Wed, 05 Oct 2011 00:00:00 GMT'
 | |
|       );
 | |
|     },
 | |
|     (xhr) => {
 | |
|       throw new Error(xhr.responseText);
 | |
|     }
 | |
|   );
 | |
| ```
 | |
| 
 | |
| If the input date string is invalid, the api returns an object having the structure `{ error : "Invalid Date" }`
 | |
| 
 | |
| ```js
 | |
| (getUserInput) =>
 | |
|   $.get(getUserInput('url') + '/api/this-is-not-a-date').then(
 | |
|     (data) => {
 | |
|       assert.equal(data.error.toLowerCase(), 'invalid date');
 | |
|     },
 | |
|     (xhr) => {
 | |
|       assert(xhr.responseJSON.error.toLowerCase() === 'invalid date');
 | |
|     }
 | |
|   );
 | |
| ```
 | |
| 
 | |
| An empty date parameter should return the current time in a JSON object with a `unix` key
 | |
| 
 | |
| ```js
 | |
| (getUserInput) =>
 | |
|   $.get(getUserInput('url') + '/api').then(
 | |
|     (data) => {
 | |
|       var now = Date.now();
 | |
|       assert.approximately(data.unix, now, 20000);
 | |
|     },
 | |
|     (xhr) => {
 | |
|       throw new Error(xhr.responseText);
 | |
|     }
 | |
|   );
 | |
| ```
 | |
| 
 | |
| An empty date parameter should return the current time in a JSON object with a `utc` key
 | |
| 
 | |
| ```js
 | |
| (getUserInput) =>
 | |
|   $.get(getUserInput('url') + '/api').then(
 | |
|     (data) => {
 | |
|       var now = Date.now();
 | |
|       var serverTime = new Date(data.utc).getTime();
 | |
|       assert.approximately(serverTime, now, 20000);
 | |
|     },
 | |
|     (xhr) => {
 | |
|       throw new Error(xhr.responseText);
 | |
|     }
 | |
|   );
 | |
| ```
 | |
| 
 | |
| # --solutions--
 | |
| 
 | |
| ```js
 | |
| /**
 | |
|   Backend challenges don't need solutions, 
 | |
|   because they would need to be tested against a full working project. 
 | |
|   Please check our contributing guidelines to learn more.
 | |
| */
 | |
| ```
 |