* 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>
134 lines
4.0 KiB
Markdown
134 lines
4.0 KiB
Markdown
---
|
|
id: 5a24c314108439a4d4036158
|
|
title: Nunca mutes el estado
|
|
challengeType: 6
|
|
forumTopicId: 301445
|
|
dashedName: never-mutate-state
|
|
---
|
|
|
|
# --description--
|
|
|
|
Estos desafíos finales describen varios métodos para hacer cumplir el principio clave de la inmutabilidad del estado en Redux. Estado inmutable significa que nunca se modifica el estado directamente, sino que se devuelve una nueva copia del estado.
|
|
|
|
Si tomaras una captura del estado de una aplicación Redux a lo largo del tiempo, verías algo como `state 1`, `state 2`, `state 3`,`state 4`, `...` y así sucesivamente donde cada estado puede ser similar al anterior, pero cada uno es un dato distinto. Esta inmutabilidad, de hecho, es lo que proporciona características tales como la depuración de viajes en el tiempo de la que puedes haber oído hablar.
|
|
|
|
Redux no impone activamente la inmutabilidad del estado en su almacén o reductores, esa responsabilidad recae en el programador. Afortunadamente, JavaScript (especialmente ES6) proporciona varias herramientas útiles que puedes utilizar para reforzar la inmutabilidad de tu estado, ya sea un `string`, `number`, `array`, u `object`. Ten en cuenta que las cadenas y los números son valores primitivos y son inmutables por naturaleza. En otras palabras, 3 siempre es 3. No se puede cambiar el valor del número 3. Sin embargo, un `array` u `object` es mutable. En la práctica, tu estado probablemente consistirá en un `array` u `object`, ya que son estructuras de datos útiles para representar muchos tipos de información.
|
|
|
|
# --instructions--
|
|
|
|
Hay un `store` y un `reducer` en el editor de código para gestionar los elementos de las tareas pendientes. Termina de escribir el caso `ADD_TO_DO` en el reductor para añadir una nueva tarea al estado. Hay algunas maneras de lograr esto con JavaScript estándar o ES6. Ve si puedes encontrar la forma de devolver un nuevo arreglo con el elemento de `action.todo` añadido al final.
|
|
|
|
# --hints--
|
|
|
|
El almacén Redux debe existir e inicializarse con un estado igual al arreglo `todos` del editor de código.
|
|
|
|
```js
|
|
assert(
|
|
(function () {
|
|
const todos = [
|
|
'Go to the store',
|
|
'Clean the house',
|
|
'Cook dinner',
|
|
'Learn to code'
|
|
];
|
|
const initialState = store.getState();
|
|
return (
|
|
Array.isArray(initialState) && initialState.join(',') === todos.join(',')
|
|
);
|
|
})()
|
|
);
|
|
```
|
|
|
|
`addToDo` e `immutableReducer` deben ser funciones.
|
|
|
|
```js
|
|
assert(typeof addToDo === 'function' && typeof immutableReducer === 'function');
|
|
```
|
|
|
|
El envío de una acción de tipo `ADD_TO_DO` en el almacén Redux debe añadir un elemento `todo` y NO debe mutar el estado.
|
|
|
|
```js
|
|
assert(
|
|
(function () {
|
|
const initialState = store.getState();
|
|
const isFrozen = DeepFreeze(initialState);
|
|
store.dispatch(addToDo('__TEST__TO__DO__'));
|
|
const finalState = store.getState();
|
|
const expectedState = [
|
|
'Go to the store',
|
|
'Clean the house',
|
|
'Cook dinner',
|
|
'Learn to code',
|
|
'__TEST__TO__DO__'
|
|
];
|
|
return isFrozen && DeepEqual(finalState, expectedState);
|
|
})()
|
|
);
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```js
|
|
const ADD_TO_DO = 'ADD_TO_DO';
|
|
|
|
// A list of strings representing tasks to do:
|
|
const todos = [
|
|
'Go to the store',
|
|
'Clean the house',
|
|
'Cook dinner',
|
|
'Learn to code',
|
|
];
|
|
|
|
const immutableReducer = (state = todos, action) => {
|
|
switch(action.type) {
|
|
case ADD_TO_DO:
|
|
// Don't mutate state here or the tests will fail
|
|
return
|
|
default:
|
|
return state;
|
|
}
|
|
};
|
|
|
|
const addToDo = (todo) => {
|
|
return {
|
|
type: ADD_TO_DO,
|
|
todo
|
|
}
|
|
}
|
|
|
|
const store = Redux.createStore(immutableReducer);
|
|
```
|
|
|
|
# --solutions--
|
|
|
|
```js
|
|
const ADD_TO_DO = 'ADD_TO_DO';
|
|
|
|
const todos = [
|
|
'Go to the store',
|
|
'Clean the house',
|
|
'Cook dinner',
|
|
'Learn to code',
|
|
];
|
|
|
|
const immutableReducer = (state = todos, action) => {
|
|
switch(action.type) {
|
|
case ADD_TO_DO:
|
|
return state.concat(action.todo);
|
|
default:
|
|
return state;
|
|
}
|
|
};
|
|
|
|
const addToDo = (todo) => {
|
|
return {
|
|
type: ADD_TO_DO,
|
|
todo
|
|
}
|
|
}
|
|
|
|
const store = Redux.createStore(immutableReducer);
|
|
```
|