* 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>
117 lines
2.6 KiB
Markdown
117 lines
2.6 KiB
Markdown
---
|
|
id: 587d7fa5367417b2b2512bbd
|
|
title: Hereda un conjunto de estilos CSS a otro elemento
|
|
challengeType: 0
|
|
forumTopicId: 301456
|
|
dashedName: extend-one-set-of-css-styles-to-another-element
|
|
---
|
|
|
|
# --description--
|
|
|
|
Sass tiene una función llamada `extend` que facilita tomar prestadas las reglas CSS de un elemento y construir sobre ellas en otro.
|
|
|
|
Por ejemplo, el siguiente bloque de reglas CSS da estilo a la clase `.panel`. Este tiene un `background-color`, `height` y `border`.
|
|
|
|
```scss
|
|
.panel{
|
|
background-color: red;
|
|
height: 70px;
|
|
border: 2px solid green;
|
|
}
|
|
```
|
|
|
|
Ahora tienes otro panel llamado `.big-panel`. Tiene las mismas propiedades base que `.panel`, pero también necesita `width` y `font-size`. Es posible copiar y pegar las reglas de CSS iniciales de `.panel`, pero el código se vuelve repetitivo a medida que agregas más tipos de paneles. La directiva `extend` es una forma simple de reutilizar las reglas escritas para un elemento y luego añadir más para otro:
|
|
|
|
```scss
|
|
.big-panel{
|
|
@extend .panel;
|
|
width: 150px;
|
|
font-size: 2em;
|
|
}
|
|
```
|
|
|
|
El `.big-panel` tendrá las mismas propiedades que `.panel` además de los nuevos estilos.
|
|
|
|
# --instructions--
|
|
|
|
Crea una clase `.info-important` que hereda `.info` y también tiene un `background-color` establecido en magenta.
|
|
|
|
# --hints--
|
|
|
|
Tu clase `info-important` debe tener un `background-color` establecido a `magenta`.
|
|
|
|
```js
|
|
assert(
|
|
code.match(
|
|
/\.info-important\s*?{[\s\S]*background-color\s*?:\s*?magenta\s*?;[\s\S]*}/gi
|
|
)
|
|
);
|
|
```
|
|
|
|
Tu clase `info-important` debe usar `@extend` para heredar el estilo de la clase `info`.
|
|
|
|
```js
|
|
assert(
|
|
code.match(/\.info-important\s*?{[\s\S]*@extend\s*?.info\s*?;[\s\S]*/gi)
|
|
);
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<style type='text/scss'>
|
|
h3{
|
|
text-align: center;
|
|
}
|
|
.info{
|
|
width: 200px;
|
|
border: 1px solid black;
|
|
margin: 0 auto;
|
|
}
|
|
|
|
|
|
|
|
|
|
</style>
|
|
<h3>Posts</h3>
|
|
<div class="info-important">
|
|
<p>This is an important post. It should extend the class ".info" and have its own CSS styles.</p>
|
|
</div>
|
|
|
|
<div class="info">
|
|
<p>This is a simple post. It has basic styling and can be extended for other uses.</p>
|
|
</div>
|
|
```
|
|
|
|
# --solutions--
|
|
|
|
```html
|
|
<style type='text/scss'>
|
|
h3{
|
|
text-align: center;
|
|
}
|
|
.info{
|
|
width: 200px;
|
|
border: 1px solid black;
|
|
margin: 0 auto;
|
|
}
|
|
.info-important{
|
|
@extend .info;
|
|
background-color: magenta;
|
|
}
|
|
|
|
|
|
|
|
</style>
|
|
<h3>Posts</h3>
|
|
<div class="info-important">
|
|
<p>This is an important post. It should extend the class ".info" and have its own CSS styles.</p>
|
|
</div>
|
|
|
|
<div class="info">
|
|
<p>This is a simple post. It has basic styling and can be extended for other uses.</p>
|
|
</div>
|
|
```
|