* 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>
122 lines
2.7 KiB
Markdown
122 lines
2.7 KiB
Markdown
---
|
|
id: 587d7dbd367417b2b2512bb4
|
|
title: Memorizzare dati con le variabili Sass
|
|
challengeType: 0
|
|
forumTopicId: 301460
|
|
dashedName: store-data-with-sass-variables
|
|
---
|
|
|
|
# --description--
|
|
|
|
Una caratteristica di Sass che è diversa da CSS è che utilizza le variabili. Esse sono dichiarate e impostate per memorizzare i dati, come in JavaScript.
|
|
|
|
In JavaScript, le variabili sono definite utilizzando le parole chiave `let` e `const`. In Sass, le variabili iniziano con un `$` seguito dal nome della variabile.
|
|
|
|
Ecco alcuni esempi:
|
|
|
|
```scss
|
|
$main-fonts: Arial, sans-serif;
|
|
$headings-color: green;
|
|
```
|
|
|
|
E per usare le variabili:
|
|
|
|
```scss
|
|
h1 {
|
|
font-family: $main-fonts;
|
|
color: $headings-color;
|
|
}
|
|
```
|
|
|
|
Un esempio in cui le variabili sono utili è quando un certo numero di elementi deve avere lo stesso colore. Se quel colore viene cambiato, l'unico punto da modificare nel codice è il valore della variabile.
|
|
|
|
# --instructions--
|
|
|
|
Crea una variabile `$text-color` e impostala su `red`. Quindi cambiare il valore della proprietà `color` per il `.blog-post` e per `h2` impostandoli alla variabile `$text-color`.
|
|
|
|
# --hints--
|
|
|
|
Il tuo codice dovrebbe avere una variabile Sass dichiarata per `$text-color` con un valore di `red`.
|
|
|
|
```js
|
|
assert(code.match(/\$text-color\s*:\s*?red\s*;/g));
|
|
```
|
|
|
|
Il tuo codice dovrebbe utilizzare la variabile `$text-color` per cambiare il `color` per gli elementi `.blog-post` e `h2`.
|
|
|
|
```js
|
|
assert(code.match(/color\s*:\s*\$text-color\s*;?/g));
|
|
```
|
|
|
|
Il tuo elemento `.blog-post` dovrebbe avere un `color` rosso.
|
|
|
|
```js
|
|
assert($('.blog-post').css('color') == 'rgb(255, 0, 0)');
|
|
```
|
|
|
|
I tuoi elementi `h2` dovrebbero avere un `color` rosso.
|
|
|
|
```js
|
|
assert($('h2').css('color') == 'rgb(255, 0, 0)');
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<style type='text/scss'>
|
|
|
|
|
|
.header{
|
|
text-align: center;
|
|
}
|
|
.blog-post, h2 {
|
|
color: red;
|
|
}
|
|
</style>
|
|
|
|
<h1 class="header">Learn Sass</h1>
|
|
<div class="blog-post">
|
|
<h2>Some random title</h2>
|
|
<p>This is a paragraph with some random text in it</p>
|
|
</div>
|
|
<div class="blog-post">
|
|
<h2>Header #2</h2>
|
|
<p>Here is some more random text.</p>
|
|
</div>
|
|
<div class="blog-post">
|
|
<h2>Here is another header</h2>
|
|
<p>Even more random text within a paragraph</p>
|
|
</div>
|
|
```
|
|
|
|
# --solutions--
|
|
|
|
```html
|
|
<style type='text/scss'>
|
|
$text-color: red;
|
|
|
|
.header{
|
|
text-align: center;
|
|
}
|
|
.blog-post, h2 {
|
|
color: $text-color;
|
|
}
|
|
</style>
|
|
|
|
<h1 class="header">Learn Sass</h1>
|
|
<div class="blog-post">
|
|
<h2>Some random title</h2>
|
|
<p>This is a paragraph with some random text in it</p>
|
|
</div>
|
|
<div class="blog-post">
|
|
<h2>Header #2</h2>
|
|
<p>Here is some more random text.</p>
|
|
</div>
|
|
<div class="blog-post">
|
|
<h2>Here is another header</h2>
|
|
<p>Even more random text within a paragraph</p>
|
|
</div>
|
|
```
|