* 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>
111 lines
2.4 KiB
Markdown
111 lines
2.4 KiB
Markdown
---
|
|
id: 5a24bbe0dba28a8d3cbd4c5d
|
|
title: Crea un elemento JSX complejo
|
|
challengeType: 6
|
|
forumTopicId: 301382
|
|
dashedName: create-a-complex-jsx-element
|
|
---
|
|
|
|
# --description--
|
|
|
|
El último desafío fue un ejemplo sencillo de JSX, pero JSX también puede representar HTML más complejo.
|
|
|
|
Una cosa importante que debes saber sobre JSX anidado es que debe devolver un solo elemento.
|
|
|
|
Este elemento principal contendría a todos los demás niveles de elementos anidados.
|
|
|
|
Por ejemplo, varios elementos JSX escritos al mismo nivel sin elemento contenedor principal no se transpilarán.
|
|
|
|
Aquí va un ejemplo:
|
|
|
|
**JSX válido:**
|
|
|
|
```jsx
|
|
<div>
|
|
<p>Paragraph One</p>
|
|
<p>Paragraph Two</p>
|
|
<p>Paragraph Three</p>
|
|
</div>
|
|
```
|
|
|
|
**JSX inválido:**
|
|
|
|
```jsx
|
|
<p>Paragraph One</p>
|
|
<p>Paragraph Two</p>
|
|
<p>Paragraph Three</p>
|
|
```
|
|
|
|
# --instructions--
|
|
|
|
Define una nueva constante `JSX` que renderice un `div` que contenga los siguientes elementos en orden:
|
|
|
|
Un `h1`, un `p` y una lista desordenada que contiene tres elementos `li`. Puedes incluir cualquier texto que desees dentro de cada elemento.
|
|
|
|
**Nota: **Al renderizar varios elementos de esta forma, puedes envolverlos todos entre paréntesis, pero no es estrictamente necesario. Observa también que este desafío usa una etiqueta `div` para envolver a todos los elementos hijos dentro de un solo elemento principal. Si eliminas el `div`, JSX ya no se podrá transpilar. Ten esto en cuenta, ya que también será así cuando devuelvas elementos JSX en los componentes de React.
|
|
|
|
# --hints--
|
|
|
|
La constante `JSX` debe devolver un elemento `div`.
|
|
|
|
```js
|
|
assert(JSX.type === 'div');
|
|
```
|
|
|
|
El `div` debe contener una etiqueta `h1` como primer elemento.
|
|
|
|
```js
|
|
assert(JSX.props.children[0].type === 'h1');
|
|
```
|
|
|
|
El `div` debe contener una etiqueta `p` como segundo elemento.
|
|
|
|
```js
|
|
assert(JSX.props.children[1].type === 'p');
|
|
```
|
|
|
|
El `div` debe contener una etiqueta `ul` como tercer elemento.
|
|
|
|
```js
|
|
assert(JSX.props.children[2].type === 'ul');
|
|
```
|
|
|
|
El `ul` debe contener tres elementos `li`.
|
|
|
|
```js
|
|
assert(
|
|
JSX.props.children
|
|
.filter((ele) => ele.type === 'ul')[0]
|
|
.props.children.filter((ele) => ele.type === 'li').length === 3
|
|
);
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --after-user-code--
|
|
|
|
```jsx
|
|
ReactDOM.render(JSX, document.getElementById('root'))
|
|
```
|
|
|
|
## --seed-contents--
|
|
|
|
```jsx
|
|
|
|
```
|
|
|
|
# --solutions--
|
|
|
|
```jsx
|
|
const JSX = (
|
|
<div>
|
|
<h1>Hello JSX!</h1>
|
|
<p>Some info</p>
|
|
<ul>
|
|
<li>An item</li>
|
|
<li>Another item</li>
|
|
<li>A third item</li>
|
|
</ul>
|
|
</div>);
|
|
```
|