* 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>
* fix(curriculum): regex to target html elements using jQuery to capture white spaces
* replace whitespace before test
* fix linting issue with single quotes
Co-authored-by: Shaun Hamilton <51722130+Sky020@users.noreply.github.com>
* Proposed change to remove whitespace for issue #39370
Issue #39370: whitespace fails the 3rd test with test comparing to a no whitespace example.
Proposed: remove all whitespace in between tags(or literally all whitespaces) before comparing it with the no whitespace example
* Update render-state-in-the-user-interface.english.md
* Updated proposed change to remove whitespace
An update to previously proposed change due to failed test of 'unexpected token \'<\'' was thrown'
* Update curriculum/challenges/english/03-front-end-libraries/react/render-state-in-the-user-interface.english.md
Co-authored-by: Shaun Hamilton <51722130+Sky020@users.noreply.github.com>
* fix: linting issue
Co-authored-by: Tom <20648924+moT01@users.noreply.github.com>
Co-authored-by: Shaun Hamilton <51722130+Sky020@users.noreply.github.com>
* fix(Curriculum): make sure the nested input element in the form is the existing element given in the editor
* Update curriculum/challenges/english/01-responsive-web-design/basic-html-and-html5/create-a-form-element.english.md
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* Update curriculum/challenges/english/01-responsive-web-design/basic-html-and-html5/create-a-form-element.english.md
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* Update curriculum/challenges/english/01-responsive-web-design/basic-html-and-html5/create-a-form-element.english.md
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* Update curriculum/challenges/english/01-responsive-web-design/basic-html-and-html5/create-a-form-element.english.md
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* Update curriculum/challenges/english/01-responsive-web-design/basic-html-and-html5/create-a-form-element.english.md
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* fix: use backticks to avoid linting error
Co-authored-by: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
Co-authored-by: Randell Dawson <rdawson@onepathtech.com>
* fix: resolve#39301
Add a test to check the "MyComponent" constructor's parameters (params) and to check that the super function exists in the constructor.
* docs: describe the test better
* Update curriculum/challenges/english/03-front-end-libraries/react/write-a-react-component-from-scratch.english.md
Co-authored-by: Nicholas Carrigan <nhcarrigan@gmail.com>
Co-authored-by: Parth Parth <34807532+thecodingaviator@users.noreply.github.com>
Co-authored-by: Nicholas Carrigan <nhcarrigan@gmail.com>
* Update greatest-subsequential-sum.english.md
Added missing closing bracket in test description in the tests section.
Removed variable declared twice in the solution section.
* Update euler-method.english.md
* Update euler-method.english.md
* Update euler-method.english.md
Added parameter description fixing the suggested changes.
* Update euler-method.english.md
Removed some formatting from the added text.
* Update euler-method.english.md
Moved seed function parameter description to instructions section.
* feat: update backend project links
Replace solution and remix Glitch links with equivalent Repl.it links in backend projects/challenges and intro pages.
* fix: link and Repl.it casing
* fix: update mention of glitch in testing challenge
* Apply suggestions from code review
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
Co-authored-by: Mrugesh Mohapatra <1884376+raisedadead@users.noreply.github.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix:Incorrect Usaage of setState in React Challenge
* apply suggestion
* also set stage usage in other challenges
* fix setState usage in challenges
* correct syntax
* correct usage of useState in other files
* add current message to state
* remove current message from state
* change connect redux to the message app
* remove extra space
* fix: Replace Array.prototype.sort and update old isSorted method.
* fix: Change name of function from 'checkInBuiltSort' to 'checkBuilitInSort'.
* fix: Change name of function from 'checkBuilitInSort' to 'isBuiltInSortUsed'.
* 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.
