* 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>
146 lines
3.9 KiB
Markdown
146 lines
3.9 KiB
Markdown
---
|
|
id: 5a24c314108439a4d403616f
|
|
title: Review Using Props with Stateless Functional Components
|
|
challengeType: 6
|
|
forumTopicId: 301411
|
|
dashedName: review-using-props-with-stateless-functional-components
|
|
---
|
|
|
|
# --description--
|
|
|
|
Except for the last challenge, you've been passing props to stateless functional components. These components act like pure functions. They accept props as input and return the same view every time they are passed the same props. You may be wondering what state is, and the next challenge will cover it in more detail. Before that, here's a review of the terminology for components.
|
|
|
|
A *stateless functional component* is any function you write which accepts props and returns JSX. A *stateless component*, on the other hand, is a class that extends `React.Component`, but does not use internal state (covered in the next challenge). Finally, a *stateful component* is a class component that does maintain its own internal state. You may see stateful components referred to simply as components or React components.
|
|
|
|
A common pattern is to try to minimize statefulness and to create stateless functional components wherever possible. This helps contain your state management to a specific area of your application. In turn, this improves development and maintenance of your app by making it easier to follow how changes to state affect its behavior.
|
|
|
|
# --instructions--
|
|
|
|
The code editor has a `CampSite` component that renders a `Camper` component as a child. Define the `Camper` component and assign it default props of `{ name: 'CamperBot' }`. Inside the `Camper` component, render any code that you want, but make sure to have one `p` element that includes only the `name` value that is passed in as a `prop`. Finally, define `propTypes` on the `Camper` component to require `name` to be provided as a prop and verify that it is of type `string`.
|
|
|
|
# --hints--
|
|
|
|
The `CampSite` component should render.
|
|
|
|
```js
|
|
assert(
|
|
(function () {
|
|
const mockedComponent = Enzyme.mount(React.createElement(CampSite));
|
|
return mockedComponent.find('CampSite').length === 1;
|
|
})()
|
|
);
|
|
```
|
|
|
|
The `Camper` component should render.
|
|
|
|
```js
|
|
assert(
|
|
(function () {
|
|
const mockedComponent = Enzyme.mount(React.createElement(CampSite));
|
|
return mockedComponent.find('Camper').length === 1;
|
|
})()
|
|
);
|
|
```
|
|
|
|
The `Camper` component should include default props which assign the string `CamperBot` to the key `name`.
|
|
|
|
```js
|
|
assert(
|
|
/Camper.defaultProps={name:(['"`])CamperBot\1,?}/.test(
|
|
__helpers.removeWhiteSpace(code)
|
|
)
|
|
);
|
|
```
|
|
|
|
The `Camper` component should include prop types which require the `name` prop to be of type `string`.
|
|
|
|
```js
|
|
assert(
|
|
/Camper.propTypes={name:PropTypes.string.isRequired,?}/.test(
|
|
__helpers.removeWhiteSpace(code)
|
|
)
|
|
);
|
|
```
|
|
|
|
The `Camper` component should contain a `p` element with only the text from the `name` prop.
|
|
|
|
```js
|
|
assert(
|
|
(function () {
|
|
const mockedComponent = Enzyme.mount(React.createElement(CampSite));
|
|
return (
|
|
mockedComponent.find('p').text() ===
|
|
mockedComponent.find('Camper').props().name
|
|
);
|
|
})()
|
|
);
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --before-user-code--
|
|
|
|
```jsx
|
|
var PropTypes = {
|
|
string: { isRequired: true }
|
|
};
|
|
```
|
|
|
|
## --after-user-code--
|
|
|
|
```jsx
|
|
ReactDOM.render(<CampSite />, document.getElementById('root'))
|
|
```
|
|
|
|
## --seed-contents--
|
|
|
|
```jsx
|
|
class CampSite extends React.Component {
|
|
constructor(props) {
|
|
super(props);
|
|
}
|
|
render() {
|
|
return (
|
|
<div>
|
|
<Camper/>
|
|
</div>
|
|
);
|
|
}
|
|
};
|
|
// Change code below this line
|
|
```
|
|
|
|
# --solutions--
|
|
|
|
```jsx
|
|
class CampSite extends React.Component {
|
|
constructor(props) {
|
|
super(props);
|
|
}
|
|
render() {
|
|
return (
|
|
<div>
|
|
<Camper/>
|
|
</div>
|
|
);
|
|
}
|
|
};
|
|
// Change code below this line
|
|
|
|
const Camper = (props) => {
|
|
return (
|
|
<div>
|
|
<p>{props.name}</p>
|
|
</div>
|
|
);
|
|
};
|
|
|
|
Camper.propTypes = {
|
|
name: PropTypes.string.isRequired
|
|
};
|
|
|
|
Camper.defaultProps = {
|
|
name: 'CamperBot'
|
|
};
|
|
```
|