* 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>
		
			
				
	
	
		
			135 lines
		
	
	
		
			3.3 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
			
		
		
	
	
			135 lines
		
	
	
		
			3.3 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
---
 | 
						|
id: 5a24c314108439a4d4036164
 | 
						|
title: Create a Component with Composition
 | 
						|
challengeType: 6
 | 
						|
forumTopicId: 301383
 | 
						|
dashedName: create-a-component-with-composition
 | 
						|
---
 | 
						|
 | 
						|
# --description--
 | 
						|
 | 
						|
Now we will look at how we can compose multiple React components together. Imagine you are building an app and have created three components: a `Navbar`, `Dashboard`, and `Footer`.
 | 
						|
 | 
						|
To compose these components together, you could create an `App` *parent* component which renders each of these three components as *children*. To render a component as a child in a React component, you include the component name written as a custom HTML tag in the JSX. For example, in the `render` method you could write:
 | 
						|
 | 
						|
```jsx
 | 
						|
return (
 | 
						|
 <App>
 | 
						|
  <Navbar />
 | 
						|
  <Dashboard />
 | 
						|
  <Footer />
 | 
						|
 </App>
 | 
						|
)
 | 
						|
```
 | 
						|
 | 
						|
When React encounters a custom HTML tag that references another component (a component name wrapped in `< />` like in this example), it renders the markup for that component in the location of the tag. This should illustrate the parent/child relationship between the `App` component and the `Navbar`, `Dashboard`, and `Footer`.
 | 
						|
 | 
						|
# --instructions--
 | 
						|
 | 
						|
In the code editor, there is a simple functional component called `ChildComponent` and a class component called `ParentComponent`. Compose the two together by rendering the `ChildComponent` within the `ParentComponent`. Make sure to close the `ChildComponent` tag with a forward slash.
 | 
						|
 | 
						|
**Note:** `ChildComponent` is defined with an ES6 arrow function because this is a very common practice when using React. However, know that this is just a function. If you aren't familiar with the arrow function syntax, please refer to the JavaScript section.
 | 
						|
 | 
						|
# --hints--
 | 
						|
 | 
						|
The React component should return a single `div` element.
 | 
						|
 | 
						|
```js
 | 
						|
assert(
 | 
						|
  (function () {
 | 
						|
    var shallowRender = Enzyme.shallow(React.createElement(ParentComponent));
 | 
						|
    return shallowRender.type() === 'div';
 | 
						|
  })()
 | 
						|
);
 | 
						|
```
 | 
						|
 | 
						|
The component should return two nested elements.
 | 
						|
 | 
						|
```js
 | 
						|
assert(
 | 
						|
  (function () {
 | 
						|
    var shallowRender = Enzyme.shallow(React.createElement(ParentComponent));
 | 
						|
    return shallowRender.children().length === 2;
 | 
						|
  })()
 | 
						|
);
 | 
						|
```
 | 
						|
 | 
						|
The component should return the `ChildComponent` as its second child.
 | 
						|
 | 
						|
```js
 | 
						|
assert(
 | 
						|
  (function () {
 | 
						|
    const mockedComponent = Enzyme.mount(React.createElement(ParentComponent));
 | 
						|
    return (
 | 
						|
      mockedComponent.find('ParentComponent').find('ChildComponent').length ===
 | 
						|
      1
 | 
						|
    );
 | 
						|
  })()
 | 
						|
);
 | 
						|
```
 | 
						|
 | 
						|
# --seed--
 | 
						|
 | 
						|
## --after-user-code--
 | 
						|
 | 
						|
```jsx
 | 
						|
ReactDOM.render(<ParentComponent />, document.getElementById('root'))
 | 
						|
```
 | 
						|
 | 
						|
## --seed-contents--
 | 
						|
 | 
						|
```jsx
 | 
						|
const ChildComponent = () => {
 | 
						|
  return (
 | 
						|
    <div>
 | 
						|
      <p>I am the child</p>
 | 
						|
    </div>
 | 
						|
  );
 | 
						|
};
 | 
						|
 | 
						|
class ParentComponent extends React.Component {
 | 
						|
  constructor(props) {
 | 
						|
    super(props);
 | 
						|
  }
 | 
						|
  render() {
 | 
						|
    return (
 | 
						|
      <div>
 | 
						|
        <h1>I am the parent</h1>
 | 
						|
        { /* Change code below this line */ }
 | 
						|
 | 
						|
 | 
						|
        { /* Change code above this line */ }
 | 
						|
      </div>
 | 
						|
    );
 | 
						|
  }
 | 
						|
};
 | 
						|
```
 | 
						|
 | 
						|
# --solutions--
 | 
						|
 | 
						|
```jsx
 | 
						|
const ChildComponent = () => {
 | 
						|
  return (
 | 
						|
    <div>
 | 
						|
      <p>I am the child</p>
 | 
						|
    </div>
 | 
						|
  );
 | 
						|
};
 | 
						|
 | 
						|
class ParentComponent extends React.Component {
 | 
						|
  constructor(props) {
 | 
						|
    super(props);
 | 
						|
  }
 | 
						|
  render() {
 | 
						|
    return (
 | 
						|
      <div>
 | 
						|
        <h1>I am the parent</h1>
 | 
						|
        { /* Change code below this line */ }
 | 
						|
        <ChildComponent />
 | 
						|
        { /* Change code above this line */ }
 | 
						|
      </div>
 | 
						|
    );
 | 
						|
  }
 | 
						|
};
 | 
						|
```
 |