* 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>
2.7 KiB
id, title, challengeType, forumTopicId, dashedName
id | title | challengeType | forumTopicId | dashedName |
---|---|---|---|---|
587d7dbf367417b2b2512bba | Usar @each para mapear sobre itens em uma lista | 0 | 301461 | use-each-to-map-over-items-in-a-list |
--description--
O último desafio mostrou como a diretiva @for
usa valores de início e fim para iterar uma quantidade determinada de vezes. Sass também oferece a diretiva @each
a qual itera sobre cada item em uma lista ou mapa. Em cada iteração, a variável é atribuída ao valor atual da lista ou do mapa.
@each $color in blue, red, green {
.#{$color}-text {color: $color;}
}
Um mapa possui uma sintaxe ligeiramente diferente. Exemplo:
$colors: (color1: blue, color2: red, color3: green);
@each $key, $color in $colors {
.#{$color}-text {color: $color;}
}
Note que a variável $key
é necessária para referenciar as chaves no mapa. Caso contrário, o CSS compilado teria nele color1
, color2
e assim por diante. Os dois exemplos de código acima são convertidos para os CSS seguintes:
.blue-text {
color: blue;
}
.red-text {
color: red;
}
.green-text {
color: green;
}
--instructions--
Escreva uma diretiva @each
que passar por uma lista: blue, black, red
e atribui cada variável à classe .color-bg
, aonde a parte color
altera para cada item. Cada classe deve definir a propriedade background-color
para a respectiva cor.
--hints--
O código deve usar a diretiva @each
.
assert(code.match(/@each /g));
A classe .blue-bg
deve ter a propriedade background-color
definida com o valor blue.
assert($('.blue-bg').css('background-color') == 'rgb(0, 0, 255)');
A classe .black-bg
deve ter a propriedade background-color
com o valor black.
assert($('.black-bg').css('background-color') == 'rgb(0, 0, 0)');
A classe .red-bg
deve ter a propriedade background-color
com o valor red.
assert($('.red-bg').css('background-color') == 'rgb(255, 0, 0)');
--seed--
--seed-contents--
<style type='text/scss'>
div {
height: 200px;
width: 200px;
}
</style>
<div class="blue-bg"></div>
<div class="black-bg"></div>
<div class="red-bg"></div>
--solutions--
<style type='text/scss'>
@each $color in blue, black, red {
.#{$color}-bg {background-color: $color;}
}
div {
height: 200px;
width: 200px;
}
</style>
<div class="blue-bg"></div>
<div class="black-bg"></div>
<div class="red-bg"></div>
<style type='text/scss'>
$colors: (color1: blue, color2: black, color3: red);
@each $key, $color in $colors {
.#{$color}-bg {background-color: $color;}
}
div {
height: 200px;
width: 200px;
}
</style>
<div class="blue-bg"></div>
<div class="black-bg"></div>
<div class="red-bg"></div>