Skip to content

Commit bbb7865

Browse files
authored
Update Docusaurus to latest (#290)
Co-authored-by: kazk <kazk@users.noreply.github.com>
1 parent 5a47124 commit bbb7865

File tree

3 files changed

+173
-192
lines changed

3 files changed

+173
-192
lines changed

content/training/troubleshooting.mdx

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
---
22
title: Troubleshooting Your Solution
3-
description: ""
43
kind: recipe
54
---
65

@@ -65,7 +64,7 @@ Most, if not all, languages on Codewars support writing to standard output (stdo
6564
<!--- For false positive "built in" -->
6665
<!--- textlint-disable terminology -->
6766

68-
**Important note:** remember that when tests are run, your solution is executed *first* (potentially with all the print statements inside), then assertions are performed on the returned value, and finally, green/red assertion messages are printed. This leads to the fact that whatever you print in your solution will appear **above** the assertion message it applies to. It's somewhat difficult to spot it visually in the Codewars test output panel. If you think that your output totally does not match the test case or its assertion message, be sure to look at the green/red message located **below** whatever you printed, and not above it. Additionally, some test suites are built in a way that the printed output and related assertion messages are separated visually from one from another, but such kata are rather exceptions and not that common.
67+
**Important note:** remember that when tests are run, your solution is executed _first_ (potentially with all the print statements inside), then assertions are performed on the returned value, and finally, green/red assertion messages are printed. This leads to the fact that whatever you print in your solution will appear **above** the assertion message it applies to. It's somewhat difficult to spot it visually in the Codewars test output panel. If you think that your output totally does not match the test case or its assertion message, be sure to look at the green/red message located **below** whatever you printed, and not above it. Additionally, some test suites are built in a way that the printed output and related assertion messages are separated visually from one from another, but such kata are rather exceptions and not that common.
6968

7069
<!--- textlint-enable terminology -->
7170

package.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,8 @@
1616
"write-heading-ids": "docusaurus write-heading-ids"
1717
},
1818
"dependencies": {
19-
"@docusaurus/core": "2.0.0-alpha.72",
20-
"@docusaurus/preset-classic": "2.0.0-alpha.72",
19+
"@docusaurus/core": "2.0.0-alpha.73",
20+
"@docusaurus/preset-classic": "2.0.0-alpha.73",
2121
"@mdx-js/react": "^1.6.21",
2222
"clsx": "^1.1.1",
2323
"react": "^17.0.1",

0 commit comments

Comments
 (0)