* fix some code tags, capitalization and punctuation
Note: The reserved word in JavaScript is "boolean", so I think it is appropriate to use it like this inside the code tags.
* Remove code tags and capitalize first letter
Co-authored-by: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* capitalize letter and replace slash
Co-authored-by: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
Co-authored-by: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* Improve the clarity on a challenge sentence
* add string type and remove double quotes
Co-authored-by: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
Co-authored-by: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* fix: fix the regex of the test of the challenge
* fix: fix data structure challenge
* fix: fix data structure challenge
* fix:fix the test regex of the challenge
* fix: fix the test regex
* Grammatically updated the instructions for the challenge
* Update curriculum/challenges/english/02-javascript-algorithms-and-data-structures/regular-expressions/reuse-patterns-using-capture-groups.md
Co-authored-by: Eric Leung <eric@erictleung.com>
Co-authored-by: Eric Leung <eric@erictleung.com>
* fix(learn): address escaped backticks
Addresses the instances of escaped backticks - where a backtick is
preceded by a backslash. In most cases, this was left over from the
old parser. In some cases, a backtick was intended to be wrapped in
code tags and has been adjusted accordingly.
This issue came to light due to a bug in the translation flow on
Crowdin.
Signed-off-by: nhcarrigan <nhcarrigan@gmail.com>
* fix: EVEN MORE :( :( :(
Signed-off-by: nhcarrigan <nhcarrigan@gmail.com>
* fix: backslash nightmares
Signed-off-by: nhcarrigan <nhcarrigan@gmail.com>
* fix: When you wish upon a *******
Signed-off-by: nhcarrigan <nhcarrigan@gmail.com>
* fix(curriculum): md error introduced by formatter
* fix(curriculum): remove extra `s
* fix: restore quote symbol
Signed-off-by: nhcarrigan <nhcarrigan@gmail.com>
* fix: Typo
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: apply review changes
Applying review feedback from call with @RandellDawson.
Signed-off-by: nhcarrigan <nhcarrigan@gmail.com>
* fix: markdown does weird stuff sometimes
Can't stick backticks together - use code.
Signed-off-by: nhcarrigan <nhcarrigan@gmail.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* Put value into quotes
It can be missunderstanding that "value" is a string!
* fix: remove quotes from inside code tags
Co-authored-by: Nicholas Carrigan (he/him) <nhcarrigan@gmail.com>
Co-authored-by: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
Co-authored-by: Nicholas Carrigan (he/him) <nhcarrigan@gmail.com>
* Possible semantic error
"identical" generally means that both variables are linked to exact same array which is not the case:
``` thisArray !== thatArray ```
Maybe "similar" or other word could be used instead
* Update curriculum/challenges/english/02-javascript-algorithms-and-data-structures/basic-data-structures/copy-an-array-with-the-spread-operator.md
Made the comment more accurate
Co-authored-by: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
Co-authored-by: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* Updated the regex in test
* Changed regex
Co-authored-by: Shaun Hamilton <51722130+Sky020@users.noreply.github.com>
* Updated changes in regex
Co-authored-by: Shaun Hamilton <51722130+Sky020@users.noreply.github.com>
Co-authored-by: Shaun Hamilton <51722130+Sky020@users.noreply.github.com>
* fix(learn): in ES6 spread operator challenge test for arr2 length > 0 too
Fixes#39662
* Accept correction
Co-authored-by: Nicholas Carrigan <nhcarrigan@gmail.com>
Co-authored-by: Nicholas Carrigan <nhcarrigan@gmail.com>
* Add meta.json for spreadsheet
* Add spreadsheet files
* Close code tags for tests in 2 files
* Add solution section
* Add index file
* Add javascript-spreadsheet to stringifier
* Move index to step
* Rename steps in meta.json
* Rename step numbers in files
* Add index file to proper location
* Remove inappropriate files from spreadsheet dir
* Fix typo in first step
* Fix test sections
* Rename files to correct step
* Fix broken tests
* Add newline between sections
* Change challengeType from 1 to 0
* Add missng ) in step-079.md
* test -> tests in step-079
* Simplify test in step-103
* Fix step-137 test
* Remove last step
* Added solutions and adjusted some tests
* Fix some challenges
* Remove wrong spaces
* Fix more tests
* Add missing semicolon
* Fix more tests
* Fix type: lastttwo
* Fix all remaining tests
The existing terminology carries negative sentiment that can be
interpreted in a racial or sense. Updating the name to have no
potential for such a connection.
Co-authored-by: Justin Rogers <justrog@gmail.com>
* fix: remove isHidden flag from frontmatter
* fix: add isUpcomingChange
Co-authored-by: Ahmad Abdolsaheb <ahmad.abdolsaheb@gmail.com>
* feat: hide blocks not challenges
Co-authored-by: Ahmad Abdolsaheb <ahmad.abdolsaheb@gmail.com>
Co-authored-by: Ahmad Abdolsaheb <ahmad.abdolsaheb@gmail.com>
* Update use-getters-and-setters-to-control-access-to-an-object.english.md
* fix: revert changes, keep example
Co-authored-by: Daniel Sing <danielsingsong@gmail.com>
* Update Regex to test if it's an IIFE instead of checking for a parenthases at the end.
* Second Test will now pass the test
* Escape One Parenthese
* Update Regex to be more structured
Co-authored-by: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* Missing regex ending literal
Co-authored-by: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* myReplace("I think we should look up there", "up", "Down")
* Checks for previously unchecked scanarios of the 'after' input being capitalized and 'before' word being uncapitalized.
* remove MDN links from English challenges
* add push challenge reference to record-collection
* refactor truthy falsy verbiage
* replace MDN link with news link
* remove unnecessary whitespace
* fix(learn): Added test for edge case
* Test checks edge cases for incorrect spelling in middle characters.
* fix: removed 'pen' sageTest
* the 'pen' points out that it is not the end of the first word to be tested for, but the end of the string.
However, this is explained clearly in the 'mountain' test below just as well.
* Fix text inconsistency
To match the eight ECMAScript Language Types on the previous paragraph.
Co-authored-by: moT01 <20648924+moT01@users.noreply.github.com>
* fix(learn): update instructions
edited text - change "returns a random number" to "returns a random whole number" to be more clear on the problem statement.
Address review comments : add the keyword "whole" to description, to make it consistent with challenge title and Instructions.
* Moved code tag to include new keyword
The new keyword hasn't been explained in the curriculum yet, so have moved the <code> tag to include the new keyword to give a prompt that it needs to be used in the solution.
* Update curriculum/challenges/english/02-javascript-algorithms-and-data-structures/es6/use-arrow-functions-to-write-concise-anonymous-functions.english.md
Added comma.
Co-authored-by: Lasse Jørgensen <28780271+lasjorg@users.noreply.github.com>