* 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>
		
			
				
	
	
		
			114 lines
		
	
	
		
			3.7 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
			
		
		
	
	
			114 lines
		
	
	
		
			3.7 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
---
 | 
						|
id: 5a24c314108439a4d4036171
 | 
						|
title: Render State in the User Interface
 | 
						|
challengeType: 6
 | 
						|
forumTopicId: 301409
 | 
						|
dashedName: render-state-in-the-user-interface
 | 
						|
---
 | 
						|
 | 
						|
# --description--
 | 
						|
 | 
						|
Once you define a component's initial state, you can display any part of it in the UI that is rendered. If a component is stateful, it will always have access to the data in `state` in its `render()` method. You can access the data with `this.state`.
 | 
						|
 | 
						|
If you want to access a state value within the `return` of the render method, you have to enclose the value in curly braces.
 | 
						|
 | 
						|
`state` is one of the most powerful features of components in React. It allows you to track important data in your app and render a UI in response to changes in this data. If your data changes, your UI will change. React uses what is called a virtual DOM, to keep track of changes behind the scenes. When state data updates, it triggers a re-render of the components using that data - including child components that received the data as a prop. React updates the actual DOM, but only where necessary. This means you don't have to worry about changing the DOM. You simply declare what the UI should look like.
 | 
						|
 | 
						|
Note that if you make a component stateful, no other components are aware of its `state`. Its `state` is completely encapsulated, or local to that component, unless you pass state data to a child component as `props`. This notion of encapsulated `state` is very important because it allows you to write certain logic, then have that logic contained and isolated in one place in your code.
 | 
						|
 | 
						|
# --instructions--
 | 
						|
 | 
						|
In the code editor, `MyComponent` is already stateful. Define an `h1` tag in the component's render method which renders the value of `name` from the component's state.
 | 
						|
 | 
						|
**Note:** The `h1` should only render the value from `state` and nothing else. In JSX, any code you write with curly braces `{ }` will be treated as JavaScript. So to access the value from `state` just enclose the reference in curly braces.
 | 
						|
 | 
						|
# --hints--
 | 
						|
 | 
						|
`MyComponent` should have a key `name` with value `freeCodeCamp` stored in its state.
 | 
						|
 | 
						|
```js
 | 
						|
assert(
 | 
						|
  Enzyme.mount(React.createElement(MyComponent)).state('name') ===
 | 
						|
    'freeCodeCamp'
 | 
						|
);
 | 
						|
```
 | 
						|
 | 
						|
`MyComponent` should render an `h1` header enclosed in a single `div`.
 | 
						|
 | 
						|
```js
 | 
						|
assert(
 | 
						|
  /<div><h1>.*<\/h1><\/div>/.test(
 | 
						|
    Enzyme.mount(React.createElement(MyComponent)).html()
 | 
						|
  )
 | 
						|
);
 | 
						|
```
 | 
						|
 | 
						|
The rendered `h1` header should only contain text rendered from the component's state.
 | 
						|
 | 
						|
```js
 | 
						|
async () => {
 | 
						|
  const waitForIt = (fn) =>
 | 
						|
    new Promise((resolve, reject) => setTimeout(() => resolve(fn()), 250));
 | 
						|
  const mockedComponent = Enzyme.mount(React.createElement(MyComponent));
 | 
						|
  const first = () => {
 | 
						|
    mockedComponent.setState({ name: 'TestName' });
 | 
						|
    return waitForIt(() => mockedComponent.html());
 | 
						|
  };
 | 
						|
  const firstValue = await first();
 | 
						|
  const getValue = firstValue.replace(/\s/g, '');
 | 
						|
  assert(getValue === '<div><h1>TestName</h1></div>');
 | 
						|
};
 | 
						|
```
 | 
						|
 | 
						|
# --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 = {
 | 
						|
      name: 'freeCodeCamp'
 | 
						|
    }
 | 
						|
  }
 | 
						|
  render() {
 | 
						|
    return (
 | 
						|
      <div>
 | 
						|
        { /* Change code below this line */ }
 | 
						|
 | 
						|
        { /* Change code above this line */ }
 | 
						|
      </div>
 | 
						|
    );
 | 
						|
  }
 | 
						|
};
 | 
						|
```
 | 
						|
 | 
						|
# --solutions--
 | 
						|
 | 
						|
```jsx
 | 
						|
class MyComponent extends React.Component {
 | 
						|
  constructor(props) {
 | 
						|
    super(props);
 | 
						|
    this.state = {
 | 
						|
      name: 'freeCodeCamp'
 | 
						|
    }
 | 
						|
  }
 | 
						|
  render() {
 | 
						|
    return (
 | 
						|
      <div>
 | 
						|
        { /* Change code below this line */ }
 | 
						|
        <h1>{this.state.name}</h1>
 | 
						|
        { /* Change code above this line */ }
 | 
						|
      </div>
 | 
						|
    );
 | 
						|
  }
 | 
						|
};
 | 
						|
```
 |