* 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: Estender um conjunto de estilos CSS para outro elemento
|
|
challengeType: 0
|
|
forumTopicId: 301456
|
|
dashedName: extend-one-set-of-css-styles-to-another-element
|
|
---
|
|
|
|
# --description--
|
|
|
|
Sass tem um recurso chamado `extend` que faz com que seja fácil pegar emprestado as regras CSS de um elemento e construr a partir delas em outro.
|
|
|
|
Por exemplo, o bloco abaixo de regras CSS estiliza uma classe `.panel`. Tem um `background-color`, um `height` e um `border`.
|
|
|
|
```scss
|
|
.panel{
|
|
background-color: red;
|
|
height: 70px;
|
|
border: 2px solid green;
|
|
}
|
|
```
|
|
|
|
Agora você quer outro painel chamado `.big-panel`. Ele tem as mesmas propriedades de base que `.panel`, mas também precisa de um `width` e `font-size`. É possível copiar e colar as regras iniciais de CSS do `.panel`, mas o código se torna repetitivo à medida que você adiciona mais tipos de painéis. A diretiva `extend` é uma maneira simples de reutilizar as regras escritas para um elemento, e então adicionar mais para outro:
|
|
|
|
```scss
|
|
.big-panel{
|
|
@extend .panel;
|
|
width: 150px;
|
|
font-size: 2em;
|
|
}
|
|
```
|
|
|
|
O `.big-panel` terá as mesmas propriedades que `.panel` além dos novos estilos.
|
|
|
|
# --instructions--
|
|
|
|
Faça uma classe `.info-important` que estenda `.info` e também tenha um `background-color` definido como magenta.
|
|
|
|
# --hints--
|
|
|
|
A classe `info-important` deve ter um `background-color` definido para `magenta`.
|
|
|
|
```js
|
|
assert(
|
|
code.match(
|
|
/\.info-important\s*?{[\s\S]*background-color\s*?:\s*?magenta\s*?;[\s\S]*}/gi
|
|
)
|
|
);
|
|
```
|
|
|
|
A classe `info-important` deve usar `@extend` para herdar o estilo da classe `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>
|
|
```
|