Skip to content

Commit 089d1f3

Browse files
translated _loops.md into danish
1 parent 05ddb45 commit 089d1f3

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

da/_loops.md

+14-14
Original file line numberDiff line numberDiff line change
@@ -1,38 +1,38 @@
11

2-
# Loops
2+
# Løkker
33

4-
Because Sass provides complex data structures such as [lists](#lists) and [maps](#maps), it is no surprise that it also gives a way for authors to iterate over those entities.
4+
Fordi Sass giver os komplekse datastrukturer såsom [lister](#lists) og [maps](#maps), så er det ikke nogen overraskelse at det også giver en måde for forfattere at iterere over disse enheder.
55

6-
However, the presence of loops usually implies moderately complex logic that probably does not belong to Sass. Before using a loop, make sure it makes sense and that it actually solves an issue.
6+
Dog, så indebærer tilstedeværelsen af løkker ofte en moderat, kompleks logik der sandsynligvis ikke hører til Sass. Før en løkke anvendes bør man sikre sig at den giver mening, og faktisk løser et problem.
77

88
## Each
99

10-
The `@each` loop is definitely the most-used out of the three loops provided by Sass. It provides a clean API to iterate over a list or a map.
10+
`@each` løkken er klart et af de mest-anvendte af de tre løkker, som Sass tilbyder. Den tilbyder en ren API til at iterere over en liste eller et map.
1111

1212
{% include snippets/loops/01/index.html %}
1313

14-
When iterating on a map, always use `$key` and `$value` as variable names to enforce consistency.
14+
Når der itereres over et map, så anvend altid `$key` og `$value` som variabelnavne for at fastholde konsistens.
1515

1616
{% include snippets/loops/02/index.html %}
1717

18-
Also be sure to respect those guidelines to preserve readability:
18+
Sikr dig også, at respektere disse guidelines for at bevare læsbarhed:
1919

20-
* Always an empty new line before `@each`;
21-
* Always an empty new line after the closing brace (`}`) unless the next line is a closing brace (`}`).
20+
* Hav altid en tom, ny linje før `@each`;
21+
* Hav altid en tom, ny linje efter den afsluttende klamme (`}`), medmindre den næste linje er en afsluttende klamme (`}`).
2222

2323
## For
2424

25-
The `@for` loop might be useful when combined with CSS `:nth-*` pseudo-classes. Except for these scenarios, prefer an `@each` loop if you *have to* iterate over something.
25+
`@for` løkken er brugbar når den kombineres med CSS' `:nth-*` pseudo-klasser. Bortset fra disse scenarier, så foretræk en `@each` løkke hvis du *er nødt til* at iterere over noget.
2626

2727
{% include snippets/loops/03/index.html %}
2828

29-
Always use `$i` as a variable name to stick to the usual convention and unless you have a really good reason to, never use the `to` keyword: always use `through`. Many developers do not even know Sass offers this variation; using it might lead to confusion.
29+
Anvend altid `$i` som en variabelnavn for at holde dig til den almene konvention, og medmindre du har en virkelig god grund til det, så brug aldrig `to` nøgleordet: brug altid `through`. Mange udviklere ved slet ikke at Sass tilbyder denne variation; at anvende den kan lede til forvirring.
3030

31-
Also be sure to respect those guidelines to preserve readability:
31+
Vær også sikker på, at respektere disse guidelines for at bevare læsbarhed:
3232

33-
* Always an empty new line before `@for`;
34-
* Always an empty new line after the closing brace (`}`) unless the next line is a closing brace (`}`).
33+
* Hav altid en tom, ny linje før `@for`;
34+
* Hav altid en tom, ny linje efter den afsluttende klamme (`}`), medmindre den næste linje er en afsluttende klamme (`}`).
3535

3636
## While
3737

38-
The `@while` loop has absolutely no use case in a real Sass project, especially since there is no way to break a loop from the inside. **Do not use it**.
38+
`@while` løkken har absolut ingen brugssituation i et virkeligt Sass-projekt, især siden der ikke er nogen måde at bryde løkken indefra. **Brug det ikke**.

0 commit comments

Comments
 (0)