* 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>
		
			
				
	
	
		
			128 lines
		
	
	
		
			3.5 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
			
		
		
	
	
			128 lines
		
	
	
		
			3.5 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
| ---
 | |
| id: 5a24c314108439a4d403617d
 | |
| title: Usar o método do ciclo de vida componentDidMount
 | |
| challengeType: 6
 | |
| forumTopicId: 301422
 | |
| dashedName: use-the-lifecycle-method-componentdidmount
 | |
| ---
 | |
| 
 | |
| # --description--
 | |
| 
 | |
| A maioria dos desenvolvedores web, em algum momento, precisa chamar uma rota de uma API para recuperar dados. Se você está trabalhando com React, é importante saber onde executar esta ação.
 | |
| 
 | |
| A melhor prática com React é colocar chamadas de API ou qualquer chamada para seu servidor no método do ciclo de vida `componentDidMount()`. Este método é chamado depois que um componente é montado no DOM. Qualquer chamada para `setState()` aqui ativará uma nova renderização do componente. Quando você chamar uma API neste método, e definir seu estado com os dados que a API retorna, ele automaticamente acionará uma atualização quando receber os dados.
 | |
| 
 | |
| # --instructions--
 | |
| 
 | |
| Há uma chamada de API simulada em `componentDidMount()`. Ele define o estado após 2,5 segundos para simular a chamada de um servidor para recuperar dados. Este exemplo solicita o total de usuários ativos atuais para um site. No método de renderização, renderiza o valor de `activeUsers` no `h1` após o texto `Active Users:`. Observe o que acontece na pré-visualização e sinta-se livre para mudar o tempo limite para ver os diferentes efeitos.
 | |
| 
 | |
| # --hints--
 | |
| 
 | |
| `MyComponent` deve renderizar um elemento `div` o qual envolve a tag `h1`.
 | |
| 
 | |
| ```js
 | |
| assert(
 | |
|   (() => {
 | |
|     const mockedComponent = Enzyme.mount(React.createElement(MyComponent));
 | |
|     return (
 | |
|       mockedComponent.find('div').length === 1 &&
 | |
|       mockedComponent.find('h1').length === 1
 | |
|     );
 | |
|   })()
 | |
| );
 | |
| ```
 | |
| 
 | |
| State do componente deve ser atualizado com uma função de timeout em `componentDidMount`.
 | |
| 
 | |
| ```js
 | |
| assert(
 | |
|   (() => {
 | |
|     const mockedComponent = Enzyme.mount(React.createElement(MyComponent));
 | |
|     return new RegExp('setTimeout(.|\n)+setState(.|\n)+activeUsers').test(
 | |
|       String(mockedComponent.instance().componentDidMount)
 | |
|     );
 | |
|   })()
 | |
| );
 | |
| ```
 | |
| 
 | |
| A tag `h1` deve renderizar o valor `activeUsers` do state de `MyComponent`.
 | |
| 
 | |
| ```js
 | |
| (() => {
 | |
|   const mockedComponent = Enzyme.mount(React.createElement(MyComponent));
 | |
|   const first = () => {
 | |
|     mockedComponent.setState({ activeUsers: 1237 });
 | |
|     return mockedComponent.find('h1').text();
 | |
|   };
 | |
|   const second = () => {
 | |
|     mockedComponent.setState({ activeUsers: 1000 });
 | |
|     return mockedComponent.find('h1').text();
 | |
|   };
 | |
|   assert(new RegExp('1237').test(first()) && new RegExp('1000').test(second()));
 | |
| })();
 | |
| ```
 | |
| 
 | |
| # --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 = {
 | |
|       activeUsers: null
 | |
|     };
 | |
|   }
 | |
|   componentDidMount() {
 | |
|     setTimeout(() => {
 | |
|       this.setState({
 | |
|         activeUsers: 1273
 | |
|       });
 | |
|     }, 2500);
 | |
|   }
 | |
|   render() {
 | |
|     return (
 | |
|       <div>
 | |
|         {/* Change code below this line */}
 | |
|         <h1>Active Users: </h1>
 | |
|         {/* Change code above this line */}
 | |
|       </div>
 | |
|     );
 | |
|   }
 | |
| }
 | |
| ```
 | |
| 
 | |
| # --solutions--
 | |
| 
 | |
| ```jsx
 | |
| class MyComponent extends React.Component {
 | |
|   constructor(props) {
 | |
|     super(props);
 | |
|     this.state = {
 | |
|       activeUsers: null
 | |
|     };
 | |
|   }
 | |
|   componentDidMount() {
 | |
|     setTimeout(() => {
 | |
|       this.setState({
 | |
|         activeUsers: 1273
 | |
|       });
 | |
|     }, 2500);
 | |
|   }
 | |
|   render() {
 | |
|     return (
 | |
|       <div>
 | |
|         <h1>Active Users: {this.state.activeUsers}</h1>
 | |
|       </div>
 | |
|     );
 | |
|   }
 | |
| }
 | |
| ```
 |