36363f277d
* fix: handle missing solutions correctly Rather than creating an [[]] the parser now creates [] which isEmpty(). This makes the test suite check the next challenge for a solution. In addition, the logic for testing solutions was fixed. * chore: update snapshots * test: build new superblock in node.js-tests CI * test: allow forward slash in superblock slug * fix: borked tests oops * test: ignore duplicated projects * fix: i did not break these shaun did :) * fix: idIndex is index of id not id Co-authored-by: Nicholas Carrigan <nhcarrigan@gmail.com>
1.0 KiB
1.0 KiB
id, title, challengeType, dashedName
| id | title | challengeType | dashedName |
|---|---|---|---|
| 61a8fe15a6a31306e60d1e89 | Step 4 | 0 | step-4 |
--description--
Normalise your page, by setting the width to 100%, and height to 100vh.
--hints--
You should give body a width of --fcc-expected--, but found --fcc-actual--.
assert.equal(new __helpers.CSSHelp(document).getStyle('body')?.width, '100%');
You should give body a height of --fcc-expected--, but found --fcc-actual--.
assert.equal(new __helpers.CSSHelp(document).getStyle('body')?.height, '100vh');
--seed--
--seed-contents--
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8" />
<link rel="stylesheet" type="text/css" href="./styles.css" />
<title>CSS Penguin</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
</head>
<body>
</body>
</html>
--fcc-editable-region--
body {
background: linear-gradient(45deg, rgb(118, 201, 255), rgb(247, 255, 222));
margin: 0;
padding: 0;
}
--fcc-editable-region--