* fix(Curriculum): update examples on how to set key-value pairs
* Update curriculum/challenges/english/02-javascript-algorithms-and-data-structures/basic-data-structures/add-key-value-pairs-to-javascript-objects.english.md
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* Update curriculum/challenges/english/02-javascript-algorithms-and-data-structures/basic-data-structures/add-key-value-pairs-to-javascript-objects.english.md
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* Update add-key-value-pairs-to-javascript-objects.english.md
* Update add-key-value-pairs-to-javascript-objects.english.md
Co-authored-by: Tom <20648924+moT01@users.noreply.github.com>
* changed lesson to match behaviour
* Update wording for debugging
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* Update wording from suggestion
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* all suggestions with note
* fix: replaced code tags with backticks for markdown
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
Co-authored-by: Ashraf Nazar <ashraf.caspian@gmail.com>
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* Fix pig latin challenge description
Added statement for beginning with consonants and if a vowel does not begin with a vowel.
* fix: update description/instructions
* fix: removed extra line break
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: removed extra line break
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
Co-authored-by: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* newlines in Authentication with Socket.IO, test 3
Both my original formatting and glitch's "format this file" button add a newline between "io.use(" and "passport.authorize"
".+" catches one or more of anything that isn't a newline.
"[^]+" catches one or more of anything including newlines.
This change updates the test accordingly so people who use glitch's formatting don't get left searching for assistance
* less permissive match to prevent shenanigans
Won't work with comments still.
* fix my own silliness
* fix: remove example code from challenge seed
* fix: remove declaration from solution
* fix: added sum variable back in
* fix: reverted description back to original version
* fix: added examples to description section
* fix: added complete sentence
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: corrected typo
Co-Authored-By: Manish Giri <manish.giri.me@gmail.com>
* fix: reverted to original desc with formatted code
* fix: removed unnecessary code example from description section
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: failiing test on iterate through array with for loop
* fix: changed to Only change this line
Co-Authored-By: Manish Giri <manish.giri.me@gmail.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
Co-authored-by: Manish Giri <manish.giri.me@gmail.com>
Co-authored-by: moT01 <tmondloch01@gmail.com>
* Stronger test cases for testing objects for properties
Change function signature to take in a custom object to be tested
* YML formatting mistake
* Yaml no space in string
* Small one more fix - most likely final
* REmove double space in return
* Update instruction Section
* add: solution to project euler 22 md file
* Copied the array instead of using it directly
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: strip-comments-from-css
* fix: added challenge referenced in issue
* fix: added call to function removeCssComments
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
Como o inglês não posse gêneros em objetos (it), é necessário colocá-los em algumas traduções para que se mantenha a mesma claridade. Aqui era necessário pois o usuário pode não entender que o texto está se referindo a função em si.
Outras palavras foram mudadas para se condizer com as normas do português, assim como algumas pontuações.
* fix: consolidate/remove comments
* fix: remove => from comment
* fix: reverted changes to add same changes to another PR
* fix: removed 'the' from sentence
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: removed 'the' from the sentence
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: Chinese test suite
Add localeTiltes, descriptions, and adjust test text and testStrings to get the automated test suite working.
* fix: ran script, updated testStrings and solutions
* fix: improve Project Euler descriptions and test case
Improve formatting of Project Euler test descriptions. Also add poker hands array and new test case for problem 54
* feat: add typeof tests and gave functions proper names for first 100 challenges
* fix: continue fixing test descriptions and adding "before test" sections
* fix: address review comments
* fix: adjust grids in 18 and 67 and fix some text that reference files rather than the given arrays
* fix: implement bug fixes and improvements from review
* fix: remove console.log statements from seed and solution
Related to PR #38040
This PR is an attempt to consolidate/remove as many comments in the challenge seed code in the Responsive Web Design certification challenges, to be able to create a small translation lookup object for translating the English comments to other languages.
* Added meaning of ones in the matrix
* Apply suggestions from code review
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: add slash to avoid markdown lint error
Co-authored-by: mrugesh <1884376+raisedadead@users.noreply.github.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* add: solution to project euler problem 20
* Update curriculum/challenges/english/08-coding-interview-prep/project-euler/problem-20-factorial-digit-sum.english.md
Accidentally added last line. Calling function is unnecessary in solution.
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* right place for starting braces
Co-Authored-By: Manish Giri <manish.giri.me@gmail.com>
* moved starting brace to previous line.
Co-Authored-By: Manish Giri <manish.giri.me@gmail.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
Co-authored-by: Manish Giri <manish.giri.me@gmail.com>
* fix: added test to validate new array is returned
* fix: changed text to reflect changed test
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: correct test and add solution
I also changed the seed to report the results of an easier example to
the user, since just evaluating the function mostly wastes time.
* fix: use a better solution
* fix: credit original author
* Correct ProjectEuler:002 definition and tests
From projecteuler.net:
By considering the terms in the Fibonacci sequence whose values do not exceed four million, find the sum of the even-valued terms.
Correct: take all f(n) where f(n) <= 4,000,000 and f(n) is even
Incorrect: take all f(n) where n <= 4,000,000 and f(n) is even
* Incorporate PR review suggestios to ProjectEuler 002
Reword the problem statement
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
Co-authored-by: Tom <20648924+moT01@users.noreply.github.com>
* fix: update to clarify new boilerplates used
Updating challenge text to make it more clear that learners need to switch to new boilerplate
* fix: improved wording to clarify new boilerplates used
Updating challenge text to be consistent and make it clear where learners are to switch to new boilerplate
Incorporating suggestions from PR #38124
* fix: Correct paths in English exercises by prefixing "/" before "learn"
* fix(lang): Correct paths to exercises by prefixing "/" before "learn" in remaining languages
* Move the comment on line 71 to its own line
The comment "use function argument destructuring" was on the same line as some code, and when displayed as a challenge it returned to a new line and was not commented out.
* Update line 71 comment per @manish-giri suggestion
Move the comment "use function argument destructuring" to above the "change code below this line" comment for clarity. Based on conversation in this pull request https://github.com/freeCodeCamp/freeCodeCamp/pull/38036
Either improved the algorithm or reduced the difficulty for the slowest
tests. All these pass with testProtectTimeout = 500, so should be safe
on most machines with the current timeout of 2500.
* Added href to empty <a> tag in social auth implementation II
* corrected typos in authentication with socketIO challenge
* corrected typo as suggested
Co-Authored-By: Eric Leung <eric@erictleung.com>
Co-authored-by: Eric Leung <eric@erictleung.com>
* Translation fix
Changed the term "portas de visualização" back to "viewport", because it is a technical term, and when translated it loses its meaning
* Changes in the blockquote tag
The code inside the blockquote tag was translated to portuguese, but code shouldn't be translated because then it doesn't work, so I changed it to the same code of the English version of the challenge.
Also, I changed "A Camper Cat" to "O Camper Cat" in the line 13 because on other pages Camper Cat is referred as male, so it makes more sense to use the article "O" in portuguese.
* Update escape-sequences-in-strings.english.md
Fixed minor grammar issue in list item 1 of the description section.
* Update curriculum/challenges/english/02-javascript-algorithms-and-data-structures/basic-javascript/escape-sequences-in-strings.english.md
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.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
* fix: corrected test and added solution
* fix: redefine hash
* fix: use defined hash
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: sum all primes description
* Update curriculum/challenges/english/02-javascript-algorithms-and-data-structures/intermediate-algorithm-scripting/sum-all-primes.english.md
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* Update curriculum/challenges/english/02-javascript-algorithms-and-data-structures/intermediate-algorithm-scripting/sum-all-primes.english.md
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: simplify challenge without using reduce
* fix: prevent user from adding new elements to sum to 10
* fix: add from
Co-Authored-By: Manish Giri <manish.giri.me@gmail.com>
* 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
This challenge requests setting the justify-content attribute to one of the possible values shown in the previous challenge. One of these values - space-evenly - doesn't actually work (at least for the English version).
In this commit I fix the space-evenly issues to some extent.
I cannot tick the box saying that all files changed are in the same world language. However, the changes made should be understandable in all languages.
There still is more to be done for languages other than English, like adding to the test text for Arabic, Portuguese, and Spanish, and adding descriptions for space-evenly in the previous challenge.
* fix: changed test text to use should
* fix: corrected typo
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: removed extra period
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: removed extra period
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: removed extra period
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: removed extra period
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: corrected typo
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: changed test text to use should
* fix: corrected typo
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: corrected typo
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: remove unnecessary backslash
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: simplified text
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: added period
Co-Authored-By: Manish Giri <manish.giri.me@gmail.com>
* fix: changed challenge test text to use should
* fix: changed have to be used in
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: reworded test verbiage
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: improved test verbiage
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: improved test verbiage
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: corrected typo
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: corrected typo
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: changed have the to be used in
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: corrected verbiage
Co-Authored-By: Parth Parth <34807532+thecodingaviator@users.noreply.github.com>
* fix: changed test text to use should
* fix: corrected typo
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: corrected typo
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: corrected typo
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: use singular of verb
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: changed punctuation
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: reworded test text
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
The thumbs up from the previous challenge was removed from the seed in an earlier merge -- seems like it should be there since the instructions only say to add the icons to the remaining buttons.
* fix: broken Read-search-ask link now point to correct url
* fix: changed link to original forum link with more views
* fix: changed http links to correct version
* fix: link in help modal
* fix: added new test to test href attribute
* fix: changed You to Your
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* fix: changed a to an
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
* Switch statement example updated
* Update switch-statements.english.md example
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* Update switch-statements.english.md example
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: allow-leading-zero-to-be-optional-before-decimal-point-for-opacity
* fix: use getComputedStyle intead of regex
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
challenge requires two files to be created whose names are given with first letter in uppercase but further down in the description those files are imported with lowercase name.
it is little confusing and requires renaming of files
* Improve viewport unit readability
Ran into a readability issue when trying to complete challenge. Instead of using `width: 80vw` was attempting `vw: 80vw` based on the initial layout. I believe either this change or the example that was added but doesn't seem to be pushed yet will help.
* edited description to be a little more clear on how to access elements in an array through indeces
* Update curriculum/challenges/english/02-javascript-algorithms-and-data-structures/basic-javascript/access-array-data-with-indexes.english.md
Co-Authored-By: Tom <20648924+moT01@users.noreply.github.com>
This section is now after Basic Javascript, but the challenge indicates that "function" and "return" are unknown at this point. Simply a product of an (apparent?) move.
* feat: rewrite Iterate with JavaScript While Loops challenge
Previous example in the challenge description was the exact code
that challenge instructions say to implement. Change the challenge to
differentiate from the example.
resolvefreeCodeCamp/freeCodeCamp#37694
* fix: update iterate with javascript while loops solution
* refactor: improve iterate with js while loops challenge wording
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
The Spanish description became difficult to understand due to unnecessary translations of code words (inline, button, etc.).
The final statement for the challenge was also half translated, when it should remain in English to match the tests.
changed the phrase ¨Rellene el código del <code>incrementer</code> función...¨to Rellene el código de la función <code>incrementer...</code> as it was grammatically incorrect
* Fixed a typo in Specify How Fonts Degrade.
'-->!' inside the code is misleading and prompts a learner
to put the exclamation mark when it is not needed as '-->!' is
also followed by a period.
Instead of "'-->!'.", it should be "'-->'."
* Made text wording consistent for the test instructions.
* Changed "To begin with," to "To begin," and fixed a minor typo.
If we are going to use "To begin with," the sentence should be
"To begin with the lesson/challenge", otherwise, "To begin" will
be more than enough.
Also added a space between "font(using HTML..." and changed it to
"font (using HTML...".
* Added hyphen to "coopted" on Line 17
Added a hyphen to the word"coopted" to correct it to "co-opted" on Line 17.
* Update curriculum/challenges/english/03-front-end-libraries/jquery/change-text-inside-an-element-using-jquery.english.md
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* add solution to a challenge
add solution to the challenge: add-a-description-to-your-package-json
* add comment to all backend challenges
The comment expllains that these challenges don't need a solution.
* update test wording for undefined fn returns, bring code out of after test section and check that the function does what it says it does (rather than just checking the result), update seed, example, and solution
* 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>
* add testing for setter, getter and setting a temperature according to some of feedbacks into the issues 17403
* bugfix: temperature is not a function
* Add link to boilerplate Glitch file
The boilerplate link is hard to see in the previous "introduction" page. I was using the old Glitch project link, and was confused.
When I googled for a solution, it was clear than others had also been quite confused. I believe this additional instruction will help many people.
* Direct people back to introduction page
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* Remove unnecessary indentation
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* Remove spaces on empty line
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* Remove spaces on empty line
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* Add empty line to fix markdown link
Markdown link needs a blank line to render correctly
* fix: add extra line to prevent linting error
* fix/remove-bullet-points
Co-authored-by: Randell Dawson <rdawson@onepathtech.com>
Co-authored-by: Tom <tmondloch01@gmail.com>
* Squashed the removal of the before test section
* fix: changed blockquote triple backtick syntax
* fix: removed recursion explanation
* fix: changed meta title and thru to through
* fix: capitalize "after" in several strings
* 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(guide) add stubs and correct file path misspellings and pr… (#36528)
* fix: corrected file path to match curriculum
* fix: renamed to newer challenge name
* fix: added solutions to articles from challenge files
* fix: added missing .english to file name
* fix: added missing title to guide article
* fix: correct solution for guide article
* fix: replaced stub with hint
* fix: added space in Hint headers
* fix: added solution to guide article
* fix: added solution to guide article
* test: replaced stub with hint and solution
* fix: add Problem number: to title
* fix: changed generatorexponential to correct name
* fix: renamed knight's tour to knights-tour
* fix: updated guide article
* fix: added a recursion challenge
* fix: changed blockquote to triple backtick syntax
* fix: added an extra line to separate code section
* fix: renamed challenge and improved verbiage
* fix: added full path to challenge
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: improved wording
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: added closing )
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: added missing comma and the word at
Co-Authored-By: Manish Giri <manish.giri.me@gmail.com>
* fix: added missing text for test case
Co-Authored-By: Manish Giri <manish.giri.me@gmail.com>
* fix: added note regarding startNum and endNum being same
* fix: wrapped parameter names with code tags
* fix(challenge): rename challenge, change fields to properties, fix test
* fix(challenge): update challenge name in meta.json
* fix(challenge): update test and assertion message
* fix(challenge): update second assert message
* fix(challenge): remove the word Person from text
* fix: Improved grammar
Replaced 'middlewares' to 'middleware functions'. Middleware is an uncountable noun, just like 'software'. No such word as 'softwares'
* Update curriculum/challenges/english/05-apis-and-microservices/basic-node-and-express/serve-static-assets.english.md
Co-Authored-By: Parth Parth <34807532+thecodingaviator@users.noreply.github.com>
* fix: add test for input closing tag
* fix: add condintion to final syntax test
This wil test if there's any character after the input tag that isn't a white space
* fix/tests+remove-not-needed-text
* fixed testString to disallow any extra characters from passing. Also changed markup in testString and text
* Update curriculum/challenges/english/01-responsive-web-design/applied-accessibility/standardize-times-with-the-html5-datetime-attribute.english.md
Co-Authored-By: Stevo99 <Sfailla1983@gmail.com>
* fixed test so it won't pass if datetime attr is left blank
* fixed test so it will not pass if datetime attribute is left empty
* fixed error in testString where test would pass if user runs test right away
* added tear-down div to make test code look cleaner
* fixed merge conflict. added tear-down div to make code look cleaner
* fixed testString to disallow any extra characters from passing. Also changed markup in testString and text
* Update curriculum/challenges/english/01-responsive-web-design/applied-accessibility/standardize-times-with-the-html5-datetime-attribute.english.md
improvement to test case where element should have closing tag.
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fixed conflict in git
* Update curriculum/challenges/english/01-responsive-web-design/applied-accessibility/standardize-times-with-the-html5-datetime-attribute.english.md
removed unnecessary test
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* Update curriculum/challenges/english/01-responsive-web-design/applied-accessibility/standardize-times-with-the-html5-datetime-attribute.english.md
removed unnecessary test
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>