* 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>
190 lines
5.0 KiB
Markdown
190 lines
5.0 KiB
Markdown
---
|
|
id: 5a24c314108439a4d4036176
|
|
title: Use State to Toggle an Element
|
|
challengeType: 6
|
|
forumTopicId: 301421
|
|
dashedName: use-state-to-toggle-an-element
|
|
---
|
|
|
|
# --description--
|
|
|
|
Sometimes you might need to know the previous state when updating the state. However, state updates may be asynchronous - this means React may batch multiple `setState()` calls into a single update. This means you can't rely on the previous value of `this.state` or `this.props` when calculating the next value. So, you should not use code like this:
|
|
|
|
```jsx
|
|
this.setState({
|
|
counter: this.state.counter + this.props.increment
|
|
});
|
|
```
|
|
|
|
Instead, you should pass `setState` a function that allows you to access state and props. Using a function with `setState` guarantees you are working with the most current values of state and props. This means that the above should be rewritten as:
|
|
|
|
```jsx
|
|
this.setState((state, props) => ({
|
|
counter: state.counter + props.increment
|
|
}));
|
|
```
|
|
|
|
You can also use a form without `props` if you need only the `state`:
|
|
|
|
```jsx
|
|
this.setState(state => ({
|
|
counter: state.counter + 1
|
|
}));
|
|
```
|
|
|
|
Note that you have to wrap the object literal in parentheses, otherwise JavaScript thinks it's a block of code.
|
|
|
|
# --instructions--
|
|
|
|
`MyComponent` has a `visibility` property which is initialized to `false`. The render method returns one view if the value of `visibility` is true, and a different view if it is false.
|
|
|
|
Currently, there is no way of updating the `visibility` property in the component's `state`. The value should toggle back and forth between true and false. There is a click handler on the button which triggers a class method called `toggleVisibility()`. Pass a function to `setState` to define this method so that the `state` of `visibility` toggles to the opposite value when the method is called. If `visibility` is `false`, the method sets it to `true`, and vice versa.
|
|
|
|
Finally, click the button to see the conditional rendering of the component based on its `state`.
|
|
|
|
**Hint:** Don't forget to bind the `this` keyword to the method in the `constructor`!
|
|
|
|
# --hints--
|
|
|
|
`MyComponent` should return a `div` element which contains a `button`.
|
|
|
|
```js
|
|
assert.strictEqual(
|
|
Enzyme.mount(React.createElement(MyComponent)).find('div').find('button')
|
|
.length,
|
|
1
|
|
);
|
|
```
|
|
|
|
The state of `MyComponent` should initialize with a `visibility` property set to `false`.
|
|
|
|
```js
|
|
assert.strictEqual(
|
|
Enzyme.mount(React.createElement(MyComponent)).state('visibility'),
|
|
false
|
|
);
|
|
```
|
|
|
|
Clicking the button element should toggle the `visibility` property in state between `true` and `false`.
|
|
|
|
```js
|
|
(() => {
|
|
const mockedComponent = Enzyme.mount(React.createElement(MyComponent));
|
|
const first = () => {
|
|
mockedComponent.setState({ visibility: false });
|
|
return mockedComponent.state('visibility');
|
|
};
|
|
const second = () => {
|
|
mockedComponent.find('button').simulate('click');
|
|
return mockedComponent.state('visibility');
|
|
};
|
|
const third = () => {
|
|
mockedComponent.find('button').simulate('click');
|
|
return mockedComponent.state('visibility');
|
|
};
|
|
const firstValue = first();
|
|
const secondValue = second();
|
|
const thirdValue = third();
|
|
assert(!firstValue && secondValue && !thirdValue);
|
|
})();
|
|
```
|
|
|
|
An anonymous function should be passed to `setState`.
|
|
|
|
```js
|
|
const paramRegex = '[a-zA-Z$_]\\w*(,[a-zA-Z$_]\\w*)?';
|
|
assert(
|
|
new RegExp(
|
|
'this\\.setState\\((function\\(' +
|
|
paramRegex +
|
|
'\\){|([a-zA-Z$_]\\w*|\\(' +
|
|
paramRegex +
|
|
'\\))=>)'
|
|
).test(__helpers.removeWhiteSpace(code))
|
|
);
|
|
```
|
|
|
|
`this` should not be used inside `setState`
|
|
|
|
```js
|
|
assert(!/this\.setState\([^}]*this/.test(code));
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --after-user-code--
|
|
|
|
```jsx
|
|
ReactDOM.render(<MyComponent />, document.getElementById('root'));
|
|
```
|
|
|
|
## --seed-contents--
|
|
|
|
```jsx
|
|
class MyComponent extends React.Component {
|
|
constructor(props) {
|
|
super(props);
|
|
this.state = {
|
|
visibility: false
|
|
};
|
|
// Change code below this line
|
|
|
|
// Change code above this line
|
|
}
|
|
// Change code below this line
|
|
|
|
// Change code above this line
|
|
render() {
|
|
if (this.state.visibility) {
|
|
return (
|
|
<div>
|
|
<button onClick={this.toggleVisibility}>Click Me</button>
|
|
<h1>Now you see me!</h1>
|
|
</div>
|
|
);
|
|
} else {
|
|
return (
|
|
<div>
|
|
<button onClick={this.toggleVisibility}>Click Me</button>
|
|
</div>
|
|
);
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
# --solutions--
|
|
|
|
```jsx
|
|
class MyComponent extends React.Component {
|
|
constructor(props) {
|
|
super(props);
|
|
this.state = {
|
|
visibility: false
|
|
};
|
|
this.toggleVisibility = this.toggleVisibility.bind(this);
|
|
}
|
|
toggleVisibility() {
|
|
this.setState(state => ({
|
|
visibility: !state.visibility
|
|
}));
|
|
}
|
|
render() {
|
|
if (this.state.visibility) {
|
|
return (
|
|
<div>
|
|
<button onClick={this.toggleVisibility}>Click Me</button>
|
|
<h1>Now you see me!</h1>
|
|
</div>
|
|
);
|
|
} else {
|
|
return (
|
|
<div>
|
|
<button onClick={this.toggleVisibility}>Click Me</button>
|
|
</div>
|
|
);
|
|
}
|
|
}
|
|
}
|
|
```
|