This commit applies changes from 78e86f514f.
It introduces Help dialog which guides the user to review Read-Search-Ask
methodology, ask the question on the forums or in gitter chatroom.
This dialog replaces existing Help button which was leading to Gitter Chatroom.
* fix(challenges): Add function scope of use strict
Refactored first 13 challenges with function scope `"use strict";`
syntax
Closes#16254
fix(challenges): Refactor ES6 challenges
Refactored ES6 challenges up to 22 to use function scope `"use strict";`
test(challenges): QA ES6 Challenges
Refactored es6 challenges getting tested and QA'd
fix(challenges): QA remaining ES6 challenges
* refactor(challenges): Quick edit for ES6 challenges
More changes to come. This commit solves issues addressed by Quincy
* refactor(challenges): ES6 Textual refactor
Textual refactor. Improved challenge test messages to be more
explanatory
* fix(challenges): Add function scope of use strict
Refactored first 13 challenges with function scope `"use strict";`
syntax
Closes#16254
fix(challenges): Refactor ES6 challenges
Refactored ES6 challenges up to 22 to use function scope `"use strict";`
test(challenges): QA ES6 Challenges
Refactored es6 challenges getting tested and QA'd
fix(challenges): QA remaining ES6 challenges
* refactor(challenges): Quick edit for ES6 challenges
More changes to come. This commit solves issues addressed by Quincy
* refactor(challenges): ES6 Textual refactor
Textual refactor. Improved challenge test messages to be more
explanatory
Edited the description and tests so that freeCodeCamp users learn to
write functions that return a similar data structure type each time.
BREAKING CHANGE: None.
Closes#16083
Edited the description and tests so that freeCodeCamp users learn to
write functions that return a similar data structure type each time.
BREAKING CHANGE: None.
Closes#16083
Edited the file so that the loopProtect code, which is in the head of
the iframe on www.freecodecamp.org, is in the same script tag as the
base challenge content that get's rendered to the page. While the
loopProtect code is not rendered to the page like the rest of the
challenge code, it's within the same scope and seems to function
normally.
BREAKING CHANGE: None that I know of, but will keep checking.
Closes#16260