* fix(curriculum) prevent users from submitting an array instead of string
* use strict equality instead of new test
* Add suggestions from Tom
Co-authored-by: Tom <20648924+moT01@users.noreply.github.com>
Co-authored-by: Tom <20648924+moT01@users.noreply.github.com>
* 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>
* 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>
* allow use of g flag
added functionality of tests to allow for the use of g flag by resetting the lastIndex as per example in https://github.com/freeCodeCamp/freeCodeCamp/pull/37941.
* Update curriculum/challenges/english/02-javascript-algorithms-and-data-structures/regular-expressions/check-for-all-or-none.english.md
Co-Authored-By: Shaun Hamilton <51722130+Sky020@users.noreply.github.com>
* Update curriculum/challenges/english/02-javascript-algorithms-and-data-structures/regular-expressions/check-for-all-or-none.english.md
Co-Authored-By: Shaun Hamilton <51722130+Sky020@users.noreply.github.com>
* Update curriculum/challenges/english/02-javascript-algorithms-and-data-structures/regular-expressions/check-for-all-or-none.english.md
Co-Authored-By: Shaun Hamilton <51722130+Sky020@users.noreply.github.com>
* Update curriculum/challenges/english/02-javascript-algorithms-and-data-structures/regular-expressions/check-for-all-or-none.english.md
Co-Authored-By: Shaun Hamilton <51722130+Sky020@users.noreply.github.com>
Co-authored-by: Shaun Hamilton <51722130+Sky020@users.noreply.github.com>
* Differentiate between test & match
I noticed that nowhere was there a mention that .match() and .test() pass in and are applied to opposite objects. This would've saved me a few minutes of searching during later challenges that assume this is understood.
* Add in .match & .test difference after example
* fix: add spaces to stop lint errors
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* refactor: replace trivial regex capture group challenge
Previous challenge could be completed without any capture groups. New
challenge requires 3 capture groups and 3 uses of the submatches in the
replacement.
resolves#17645
* test: validate at least 3 capture groups were used
Use solution from SO
(https://stackoverflow.com/questions/16046620/regex-to-count-the-number-of-capturing-groups-in-a-regex)
as suggested by @RandellDawson to count the number of capturing
groups, regardless of whether or not the regex in question solves the
broader problem.
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* refactor: more meaningful variable name
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* test: add parenthesized substring test
* test: ensure 3 uses of substring replacement
* refactor: reword instructions
* fix: minor grammar fix
Co-Authored-By: Manish Giri <manish.giri.me@gmail.com>
* refactor: elaborate wording in test
* Added new test case '8pass99' for positive and negative lookahead
* Changed the pwRegex to reflect the new solution
* Updated the pwRegex to reflect the latest solution as on forum
* Added another test case to catch "/^(?=\w{6,})(?=\D*\d{2})/" solution
* fix: convert js algorithms and data structures
* fix: revert some blocks back to blockquote
* fix: reverted comparison code block to blockquotes
* fix: change js to json
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: convert various section to triple backticks
* fix: Make the formatting consistent for comparisons
awu43
Sem Bauke
Nicholas Carrigan (he/him)
Randell Dawson
Joshua Pelealu
Tom
Shaun Hamilton
Alex Soto
Martin Milani
Oliver Eyton-Williams
Marc Antoni
Yasmin Yazdi
Renato Melo
Damjan Ostrelič
Kimon
Hassaan Pasha
Vincent Shury
Igor Snitkin
Hassaan Pasha
Ashraf Nazar
Shubham Shah
Arthur
Divyanshu
SomeDer
Chayanon Tonsai
Randell Dawson
Siddhant Shekhar
Kristofer Koishigawa
lucassorenson