* 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>
* 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: 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>
* 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
In the challenge seed renderOnline variable has been used and referenced but in the solution seed the variable has been changed to renderOnlineUser so, changed renderOnlineUsers back to renderOnline variable.
* make test more robust
* fix: changed test to ignore extra spaces in html
* Revert "make test more robust"
This reverts commit 89718eb5e5ceab90b78238af644e2ee77d854d69.
* Fix solution
* Update description
* Add test for this.setState function syntax
* Update toggle element instructions
* Fix simple-counter solutions
* Fix bind-this challenge seed and solution
* Fix && challenge seed and solution
* Fix ternary challenge seed and solution
* Use the function form -> Pass a function
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* Mention "passing a function" instead of "alternative form"
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* Rephrase explanation
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* clarify why functions should be used
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* Improve tests
* Fix \s escaping in []
* Improve regex
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* Add test for `this`
* Use block code
* Update bind-this challenge
* Fix last part of instructions
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* componentWillReceiveProps is deprecated
Consider removing this lesson from the React tutorial, once this lifecycle method is now deprecated.
In case it isn't, a warning in the beginning should be displayed
* Removed also `componentWillReceiveProps`
* fix(challenge): check for li and specify elements accepting text
* fix(challenge): revert text
* fix(challenge): remove word added by mistake
* fix(challenge): update test, cleanup assertion text
* fix: Allow trailing commas to be used in challenge
* fix: use regex to simplify challenge tests
* Update curriculum/challenges/english/03-front-end-libraries/react/review-using-props-with-stateless-functional-components.english.md
Co-Authored-By: ojeytonwilliams <ojeytonwilliams@gmail.com>
A stateful component is always a class component because functional components can't maintain state by definition. Changed a line to better reflect that.
Hi,
I noticed that in the instructions it is written that in the code editor there is a functional component and a React component. I do believe this is a typo as both are React components, just defined differently. Therefore, the sentence should be "...there is a simple functional component called ChildComponent and a class component called ParentComponent...".
Theo
* Edit Description
Making some editing to make the description more understandable. I am a beginner but I think me edits makes more sense. If you think so, please merge them for helping others.
* Update curriculum/challenges/english/03-front-end-libraries/react/pass-props-to-a-stateless-functional-component.english.md
Co-Authored-By: Ahmed-Elbessfy <ahmedelbessfy@gmail.com>
