Added new React component and added redux states for invalid challenge
Fixed problems for requested changes with eslint long string and used
the existing NotFound component + use Link component
Used react-bootstrap for Not-Found component and changed the "Map" link into
"current-challenge" link. Deleted 'invalid' state in Challenges.jsx
BREAKING CHANGE: N/A
Closes#16257
Edited the description so the exponents are displayed properly, and
added more tests and a solution.
Amend: Edited the seed so that the challenge function in the seed is called only once.
BREAKING CHANGE: None
Edited the description so the exponents are displayed properly, and
added more tests and a solution.
Amend: Edited the seed so that the challenge function in the seed is called only once.
BREAKING CHANGE: None
Added more tests, a solution, and an image to make the description more
clear. The image is from Project Euler but is rehosted on imgur.
Amend: Edited the seed so that the challenge function in the seed is called only once.
BREAKING CHANGE: None
Added more tests, a solution, and an image to make the description more
clear. The image is from Project Euler but is rehosted on imgur.
Amend: Edited the seed so that the challenge function in the seed is called only once.
BREAKING CHANGE: None
* fix(tests): Improve test output
Switches test-challengse from tap-spec to tap-difflet in
pessimistic mode for a more concise test output.
Also removes unused gulp tasks.
Closes#16406
* build(npm-script): Update scripts to have developer mode test run
the test fails if there is no space between @media and the parenthesis, even though it is possible to not have a space. Also it doesn't tell you that that is the problem, so it can make the person get stuck trying to figure out what they did wrong, when in fact they were right, like I was for half an hour until I came here to check the test =)
the test fails if there is no space between @media and the parenthesis, even though it is possible to not have a space. Also it doesn't tell you that that is the problem, so it can make the person get stuck trying to figure out what they did wrong, when in fact they were right, like I was for half an hour until I came here to check the test =)
Added a head property to the challenge object and moved the large fiftyDigitNums array to it, preventing the browser from having to re-render it with every keystroke and causing lag. Also fixed a problem where the testNums and fiftyDigitNums arrays were not declared with const properly in my original PR.
BREAKING CHANGE: None
Added a head property to the challenge object and moved the large fiftyDigitNums array to it, preventing the browser from having to re-render it with every keystroke and causing lag. Also fixed a problem where the testNums and fiftyDigitNums arrays were not declared with const properly in my original PR.
BREAKING CHANGE: None
