| {: , : , : [{: , : Add them as a new contact in Screen Hero, then click the monitor-looking button to attempt to share your screen with them.\Once the Screen Hero session starts, your screen's margins will glow orange. You are now sharing your screen.\", \"Your pair will have their own cursor, and will be able to type text on his or her and keyboard.\", <del> \"Now it's time to tackle our Bonfires.\Go to <a href='http://freecodecamp.com/bonfires' target='_blank'>http://freecodecamp.com/bonfires</a> and start working through our Bonfire challenges.\Now it's time to tackle our Bonfires. You can begin them by advancing to the next challenge.\", </ins> \"Once you you finish pair programming, end the session in Screen Hero session.\", \"Congratulations! You have completed your first pair programming session.\", \"Pair program as much as possible with different campers until you've completed all the Bonfire challenges. This is a big time investment, but the JavaScript practice you get will be well worth it!\, : }], : []} |
| {: , : , : [{: , : tests\assert($('ul').length > 0, 'You should have an <code>ul</code> element on your webpage.')\assert($('ol').length > 0, 'You should have an <code>ol</code> element on your webpage.')\assert($('li').length > 5, 'You should have three <code>li</code> elements on within your <code>ul</code> element.')\assert($('li').length > 5, 'You should have three <code>li</code> elements on within your <code>ol</code> element.')\assert($('li').length > 5, 'You should have three <code>li</code> elements within your <code>ul</code> element.')\assert($('li').length > 5, 'You should have three <code>li</code> elements within your <code>ol</code> element.')\challengeSeed\<link href='http://fonts.googleapis.com/css?family=Lobster' rel='stylesheet' type='text/css'>\, : }], : []} |
| {: , : , : [{: , : For example, if you wanted to make a text input field required, you can just add the word \ within your <code>input</code> element use: <code><input type='text' required></code>\tests\assert($('input').prop('required'), 'Your text field have the property of being required.')\assert($('[placeholder]').length > 0, 'Your text field should have the placeholder text of \"cat photo URL\".')\assert($('input').prop('required'), 'Your text field should have the property of being required.')\assert(new RegExp('cat photo URL').test($('input').prop('placeholder')), 'Your text field should have the placeholder text of \"cat photo URL\".')\challengeSeed\<link href='http://fonts.googleapis.com/css?family=Lobster' rel='stylesheet' type='text/css'>\, : }], : []} |
| {: , : , : [{: , : Put the \, \ and \ buttons side-by-side by wrapping all three of them within one <code><div class=\></code> element, then each of them within a <code><div class=\></code> element.\Bootstrap uses a responsive grid system, which makes it easy to put elements into rows and specify each element's relative width. Most of Bootstrap's classes can be applied to a <code>div</code> element.\Here's a diagram of how Bootstrap's 12-column grid layout works:\<img class='img-responsive' src='https://www.evernote.com/l/AHTwlE2XCLhGFYJzoye_QfsF3ho6y87via4B/image.png'>\<a href='http://getbootstrap.com/css/#grid-example-basic' target='_blank'><img class='img-responsive' src='https://www.evernote.com/l/AHTwlE2XCLhGFYJzoye_QfsF3ho6y87via4B/image.png'></a>\Note that in this illustration, we use the <code>col-md-*</code> class. Here, \ means \, and \ is a number specifying how many columns wide the element should be. In this case, we're specifying how many columns wide an element should be on a medium-sized screen, such as a laptop.\", \"In the Cat Photo App that we're building, we'll use <code>col-xs-*</code>, where \"*\" is the number of columns wide the element should be, and \"xs\" means \"extra small\", like an extra-small mobile phone screen.\", \"The <code>row</code> class is applied to a <code>div</code>, and the buttons themselves can be wrapped within it.\"", "commid": "freeCodeCamp_pr_647"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-510409e65afd23db2023e0d793687c58d2348302aae33e5af881a8e4545e91db", "query": "This isn't exactly a bug, but in the description for the challenge, there is an image that shows how bootstrap lays out elements on a page. This image is way too small to see or read any of the text in the image, and there doesn't seem to be a good way to get a larger version of the image.\nThanks, we've updated the copy to have the image link to the specific section of the bootstrap website!positive_passagesdociddoc-en-freeCodeCamp-4aa2a01a6b29ba591967452055dd2bce22967259ecaf09e557ea3f198cd01986text\: \, \ : 0.062, \: [ <del> \row\col-xs-7\col-xs-5\, </del> \row\col-xs-*\, <ins> \row\col-xs-7\col-xs-5\, </ins> \ ], \: [ <del> \row\, </del> <ins> \row\, </ins> \col-xs-5\, \col-xs-7\ ],commidfreeCodeCamp_pr_647negative_passages |
| query_idq-en-freeCodeCamp-e3b6da71b738431f56c5e153a472f27b4b15d25d0cfae7f878b6878428a75bd8queryChallenge has an issue. It seems that it's more appropritae to show helpful links to: () () instead of: () () Am I right?", "positive_passages": [{"docid": "doc-en-freeCodeCamp-d187dca0878bafa11219167399cafff29b361df7c344b4a84f56fdf2b13bc3b1", "text": "], \"MDNlinks\": [ \"Comparison Operators\", <del> \"String.slice()\", </del> <ins> \"Array.slice()\", </ins> \"Array.filter()\", \"Array.indexOf()\", <del> \"String.concat()\" </del> <ins> \"Array.concat()\" </ins> ], \"type\": \"bonfire\", \"challengeType\": 5,", "commid": "freeCodeCamp_pr_1818"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-1ae6eba9d43a90c468c54b0adf7460baadb9538d5674e7db65c52c459901ee0b", "query": "Challenge has an issue. Waypoint requires you to have a 10px border around the img element, but you can pass by with a 5px border. Steps to reproduce: 1) Paste into your code, inside your style tag. 2) Add to your img tag classes 3) Change your to and to inside your style tag. Then the Waypoint allows you to the next challenge even if you don't change your border-width to 10px; !\nLooking at the code, it seems that there's not a test for . Also, property is tested with a RegExp and it yields true if the word 'solid' is written in any place in the editor, it might be better to check it with JQuery's .css function, as in the test for which, by the way, looks forpositive_passagesdociddoc-en-freeCodeCamp-5259fb492a096d424a0e81894aa61e6734de06b4cbecf5a272c48a7b07f9a562text\: [ \img\smaller-image\, \img\thick-green-border\, <del> \img\thick-green-border\img\border-top-width\, \solid\gi\, </del> <ins> \img\thick-green-border\img\border-top-width\, \img\border-right-style\solid\, </ins> \img\border-left-color\rgb(0, 128, 0)\ ], \: [commidfreeCodeCamp_pr_1798negative_passages |
| query_idq-en-freeCodeCamp-b4d5dce4ea7dd180d4ee9c9a31de9f8c73118dc4aaafd01a59553dbfa63c905cqueryChallenge has an issue. December 1st to February 3rd is two months not one month. The test is pretty wordy regardless. !\nI believe it needs to be used in numbers not the name of the month. Sent from my iPhone\nThe numbers and everything in the test are right, it's just the message. The output for is .\nOh because nothing is one month apart look the number format for the year one is 2015 and one is 2016. Sent from my iPhone\nThis is not a problem with the logic of the test or based on my input \u2013 it's just a typo. Yes the years are different but the two dates are only two months apart, therefore the year of the second argument doesn't need to be outputted because it can be inferred. The test should say something along the lines of, \"two months apart can be inferred, even if it is the next year\".\nClosing as fixed in", "positive_passages": [{"docid": "doc-en-freeCodeCamp-8f9328c9fcb0df2400ac3b5492a1096acc7e948a2b9735f2d0d069391b7dccc9", "text": "], \"tests\": [ \"assert.deepEqual(friendly(['2015-07-01', '2015-07-04']), ['July 1st','4th'], 'ending month should be omitted since it is already mentioned');\", <del> \"assert.deepEqual(friendly(['2015-12-01', '2016-02-03']), ['December 1st','February 3rd'], 'one month apart can be inferred it is the next year');\", </del> <ins> \"assert.deepEqual(friendly(['2015-12-01', '2016-02-03']), ['December 1st','February 3rd'], 'two months apart can be inferred if it is the next year');\", </ins> \"assert.deepEqual(friendly(['2015-12-01', '2017-02-03']), ['December 1st, 2015','February 3rd, 2017']);\", \"assert.deepEqual(friendly(['2016-03-01', '2016-05-05']), ['March 1st','May 5th, 2016']);\", \"assert.deepEqual(friendly(['2017-01-01', '2017-01-01']), ['January 1st, 2017'], 'since we do not duplicate only return once');\",", "commid": "freeCodeCamp_pr_1197"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-62249d204327cfb40994e2a3d3b06a6465d28816182ffefbc2eb70afbb9ac9ea", "query": "Challenge has an issue. in JavaScript we can can work with decimal numbers <--- needs full stop.\nmerged to", "positive_passages": [{"docid": "doc-en-freeCodeCamp-1ea516fca574d774df08fd3cd7024d9c027506ad092d391f85eb90371c20ee43", "text": "\"dashedName\": \"waypoint-add-two-numbers-with-javascript\", \"difficulty\": \"9.98141\", \"description\": [ <del> \"In JavaScript whole numbers (called integers) can be easily used to preform mathematical functions\", \"Let's try a few of the most commonly used ones now\We use <code>+</code>for addition\In JavaScript whole numbers (called integers) can be easily used to perform mathematical functions.\Let's try a few of the most commonly used ones now.\", \"We use <code>+</code>for addition.\", </ins> \"Replace the <code>0</code>with correct number to achieve the result in the comment.\" ], \"tests\": [", "commid": "freeCodeCamp_pr_1692"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-62249d204327cfb40994e2a3d3b06a6465d28816182ffefbc2eb70afbb9ac9ea", "query": "Challenge has an issue. in JavaScript we can can work with decimal numbers <--- needs full stop.\nmerged to", "positive_passages": [{"docid": "doc-en-freeCodeCamp-ef4b8e9a1d15441c22eadd99cea17b0f35e773238e351c541d9fb713c850b58e", "text": "\"dashedName\": \"waypoint-subtract-one-number-from-another-with-javascript\", \"difficulty\": \"9.98142\", \"description\": [ <del> \"In JavaScript whole numbers (called integers) can be easily used to preform mathematical functions\", \"Let's try a few of the most commonly used ones now\We use <code>-</code>for subtraction\In JavaScript whole numbers (called integers) can be easily used to perform mathematical functions.\Let's try a few of the most commonly used ones now.\", \"We use <code>-</code>for subtraction.\", </ins> \"Replace the <code>0</code>with correct number to achieve the result in the comment.\" ], \"tests\": [", "commid": "freeCodeCamp_pr_1692"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-62249d204327cfb40994e2a3d3b06a6465d28816182ffefbc2eb70afbb9ac9ea", "query": "Challenge has an issue. in JavaScript we can can work with decimal numbers <--- needs full stop.\nmerged to", "positive_passages": [{"docid": "doc-en-freeCodeCamp-fd75e49209914046fcbd6a674bd770d934e627992d9a590dbd60aec4cac132e4", "text": "\"dashedName\": \"waypoint-multiply-two-numbers-with-javascript\", \"difficulty\": \"9.98143\", \"description\": [ <del> \"In JavaScript whole numbers (called integers) can be easily used to preform mathematical functions\", \"Let's try a few of the most commonly used ones now\We use <code>*</code>for multiplication\In JavaScript whole numbers (called integers) can be easily used to perform mathematical functions.\Let's try a few of the most commonly used ones now.\", \"We use <code>*</code>for multiplication.\", </ins> \"Replace the <code>0</code>with correct number to achieve the result in the comment.\" ], \"tests\": [", "commid": "freeCodeCamp_pr_1692"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-62249d204327cfb40994e2a3d3b06a6465d28816182ffefbc2eb70afbb9ac9ea", "query": "Challenge has an issue. in JavaScript we can can work with decimal numbers <--- needs full stop.\nmerged to", "positive_passages": [{"docid": "doc-en-freeCodeCamp-b702c408e953e929e4a5b77c89907495383bac6ed0e0e31b32309c2f847558cc", "text": "\"dashedName\": \"waypoint-divide-one-number-by-another-with-javascript\", \"difficulty\": \"9.9814\", \"description\": [ <del> \"In JavaScript whole numbers (called integers) can be easily used to preform mathematical functions\", \"Let's try a few of the most commonly used ones now\We use <code>/</code>for division\In JavaScript whole numbers (called integers) can be easily used to perform mathematical functions.\Let's try a few of the most commonly used ones now.\", \"We use <code>/</code>for division.\", </ins> \"Replace the <code>0</code>with correct number to achieve the result in the comment.\" ], \"tests\": [", "commid": "freeCodeCamp_pr_1692"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-62249d204327cfb40994e2a3d3b06a6465d28816182ffefbc2eb70afbb9ac9ea", "query": "Challenge has an issue. in JavaScript we can can work with decimal numbers <--- needs full stop.\nmerged to", "positive_passages": [{"docid": "doc-en-freeCodeCamp-e008cab8cabad8a9d7e355aae27b95fae55ce5ff3b30470c8570570f2c9225e8", "text": "\"dashedName\": \"waypoint-create-decimal-numbers-with-javascript\", \"difficulty\": \"9.9815\", \"description\": [ <del> \"in JavaScript we can can work with decimal numbers\", </del> <ins> \"In JavaScript we can can work with decimal numbers.\", </ins> \"Let's create a variable <code>myDecimal</code> and give it a decimal value.\tests\, : }], : []} |
| {: , : , : [{: , : <code>function functionName (a, b) {</code>\<code>  return(a + b);</code>\<code>}</code>\We can \ our function like this: <code>functionName();</code>, and it will run and return it's <code>return</code> value to us.\", \"Create and call a function called <code>myFunction</code>.\" </del> <ins> \"We can \"call\" our function like this: <code>functionName();</code>, and it will run and return its <code>return</code> value to us.\", \"Create and call a function called <code>myFunction</code> that returns the sum of a and b.\" </ins> ], \"tests\":[ \"assert((function(){if(typeof(f) !== \"undefined\" && typeof(f) === \"number\" && f === a + b && editor.getValue().match(/return/gi).length >= 1 && editor.getValue().match(/a/gi).length >= 1 && editor.getValue().match(/b/gi).length >= 1 && editor.getValue().match(/+/gi).length >= 1){return(true);}else{return(false);}})(), 'Your function should return the value of a + b');\"", "commid": "freeCodeCamp_pr_2568"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-6e04504e91ab6bac1ecb6baed214c6c157c5c9db7c147c10b8b50b0f9f97337a", "query": "Challenge has an issue. ! The last sentence should read Create and call a function called that returns the sum of and .", "positive_passages": [{"docid": "doc-en-freeCodeCamp-4dddf0d88dd771362f5a1f74d968671e6297b2b61cbe54a3f54e89e8824d3064", "text": "\" return a - b;\", \"};\", \"\", <del> \"//Don't modify above this line\//Create a function called myFunction that returns the value of a plus b.\ // Only change code below this line.\// Don't modify above this line\", \"// Create a function called myFunction that returns the value of a plus b.\", \"// Only change code below this line.\", </ins> \"\", \"\", \"\",", "commid": "freeCodeCamp_pr_2568"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-b20dedd4cb9cd40e4d105a46740fd96c62746e2ee6e6ea40b9e26fc220d11b39", "query": "Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. The last line in code is: but for output box to work should be: ( replaced by )\nCreated PR", "positive_passages": [{"docid": "doc-en-freeCodeCamp-8dd68b874a9bd5c36fe29d682013497115f9d58176c92caccc7e44eccc592d4d", "text": "\"// Only change code above this line.\", \"// We use this function to show you the value of your variable in your output box.\", \"// You'll learn about functions soon.\if(typeof(myArray) !== \ && typeof(data) !== \){(function(y,z){return('myArray = ' + JSON.stringify(y) + ', data = ' + JSON.stringify(z));})(myArray, data);}\if(typeof(myArray) !== \ && typeof(myData) !== \){(function(y,z){return('myArray = ' + JSON.stringify(y) + ', myData = ' + JSON.stringify(z));})(myArray, myData);}\type\waypoint\challengeType\, : }], : []} |
| {: , : assert(editor.getValue().match(/(//)...../g),\1440\screen shot 2015-08-18 at 8 50 03 pm\\, : [{: , : Try creating one of each.\tests\assert(editor.getValue().match(/(//)...../g), 'Create a <code>//</code> style comment that contains at least five letters');\assert(editor.getValue().match(/(/*)...../g), 'Create a <code>/* */</code> style comment that contains at least five letters.');\assert(editor.getValue().match(/(*/)/g), 'Make sure that you close the comment with a <code>*/</code>');\assert(editor.getValue().match(/(//)...../g), 'Create a <code>//</code> style comment that contains at least five letters');\assert(editor.getValue().match(/(/*)[wW]{5,}(?=*/)/gm), 'Create a <code>/* */</code> style comment that contains at least five letters.');\assert(editor.getValue().match(/(*/)/g), 'Make sure that you close the comment with a <code>*/</code>');\challengeSeed\, : }], : []} |
| {: , : use\, : [{: , : title\Use Spans for Inline Elements\difficulty\description\You can use use spans to create inline elements. Remember when we used the <code>btn-block</code> class to make the button fill the entire row?\You can use spans to create inline elements. Remember when we used the <code>btn-block</code> class to make the button fill the entire row?\This image illustrates the difference between <code>inline</code> elements and <code>block-level</code> elements:\<img class=\ src=\ alt=\inline\block-level\, \,commidfreeCodeCamp_pr_2637negative_passages |
| query_idq-en-freeCodeCamp-f4e6799b251988ed729ad8cb9b2b6cc8f66ea0d34237570ab0a66cfa7261d9d9queryChallenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.99 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nClosing. Please feel free to re-open with steps and a description on how to reproduce the issue. Happy Coding!positive_passagesdociddoc-en-freeCodeCamp-3542290f48251a30ad49fb30a80607eaa07f2f3fd942a7f0ac69245920ea84f5text\: [ \ ], <del> \: \, \: [ \, \, \, \, \, \ </del> <ins> \: \, \: [ \, \, \, \, \, \ </ins> ] } ]commidfreeCodeCamp_pr_106negative_passages |
| query_idq-en-freeCodeCamp-ad8378882f4452e4a5460fe1fab0ff1044406f3082f5153f99b7dece4ed3a74fqueryAssignment: Let's remove all the values greater than five Assert: You should have removed all the values from the array that are greater than 4. problem arises if user includes 5 in result set", "positive_passages": [{"docid": "doc-en-freeCodeCamp-0af7ed915b422e2bfb3c300b02e299fd023f4bc8c3990022b2cacc60476a5eee", "text": "\"<code>});</code>\" ], \"tests\":[ <del> \"assert.deepEqual(array, [1,2,3,4], 'message: You should have removed all the values from the array that are greater than 4.');\", </del> <ins> \"assert.deepEqual(array, [1,2,3,4,5], 'message: You should have removed all the values from the array that are greater than 5.');\", </ins> \"assert(editor.getValue().match(/array.filters*(/gi), 'message: You should be using the filter method to remove the values from the array.');\", \"assert(editor.getValue().match(/[1,2,3,4,5,6,7,8,9,10]/gi), 'message: You should only be using <code>.filter</code> to modify the contents of the array.');\" ],", "commid": "freeCodeCamp_pr_3678"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-773618e5fb751570c28093293404f80e165427bf30ea73312316ceeb518de5e1", "query": "I think \"Each id should be unique to a specific element.\" would be less ambiguous (and more accurate) as \"Each id must be unique on the page.\"", "positive_passages": [{"docid": "doc-en-freeCodeCamp-c0e051a3a87be394d29dd6e183c003520275b44ccea80ece196326579202820a", "text": "\"id\": \"bad87fee1348cd8acef08812\", \"title\": \"Create a Block Element Bootstrap Button\", \"description\": [ <del> \"Normally, your <code>button</code> elements are only as wide as the text that they contain. By making them block elements, your button will stretch to fill your page's entire horizontal space.\Normally, your <code>button</code> elements are only as wide as the text that they contain. By making them block elements, your button will stretch to fill your page's entire horizontal space and any elements following it will flow onto a \"new line\" below the block.\", </ins> \"This image illustrates the difference between <code>inline</code> elements and <code>block-level</code> elements:\", \"<a href=\"http://i.imgur.com/O32cDWE.png\" data-lightbox=\"img-enlarge\"><img class=\"img-responsive\" src=\"http://i.imgur.com/O32cDWE.png\" title=\"Click to enlarge\" alt=\"An \"inline\" button is as small as the text it contains. In this image, it's centered. Below it is a \ button, which stretches to fill the entire horizontal space.'></a>\", \"Note that these buttons still need the <code>btn</code> class.\",", "commid": "freeCodeCamp_pr_3946"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-773618e5fb751570c28093293404f80e165427bf30ea73312316ceeb518de5e1", "query": "I think \"Each id should be unique to a specific element.\" would be less ambiguous (and more accurate) as \"Each id must be unique on the page.\"", "positive_passages": [{"docid": "doc-en-freeCodeCamp-b776637ba9b70536e85baf365d896694f81ec78bee67b9f249365cc86bcf555e", "text": "\"title\": \"Add ID Attributes to Bootstrap Elements\", \"description\": [ \"Recall that in addition to class attributes, you can give each of your elements an <code>id</code> attribute.\", <del> \"Each id should be unique to a specific element.\", </del> <ins> \"Each id must be unique to a specific element and used only once per page.\", </ins> \"Let's give a unique id to each of our <code>div</code> elements of class <code>well</code>.\Remember that you can give an element an id like this: <code><div class=\ id=\></code>\Give the well on the left the id of <code>left-well</code>. Give the well on the right the <code>id</code> of <code>right-well</code>.\, : }], : []} |
| {: , : \\\\, : [{: , : //gitter.im/freecodecamp/HalfWayClub\_blank\https://gitter.im/freecodecamp/HalfWayClub\_blank\, : }], : []} |
| {: , : Q\, : [{: , : <span class='text-info'>Bonus User Story:</span> As a user, I navigate to different sections of the webpage by clicking buttons in the navigation.\Don't worry if you don't have anything to showcase on your portfolio yet - you will build several apps on the next few CodePen challenges, and can come back and update your portfolio later.\There are many great portfolio templates out there, but for this challenge, you'll need to build a portfolio page yourself. Using Bootstrap will make this much easier for you.\", <del> \"Note that CodePen.io overrides the Window.open() function, so if you want to open windows using jquery, you will need to target invisible anchor elements like this one: <code><a target='_blank'></a></code>.\", </del> <ins> \"Note that CodePen.io overrides the Window.open() function, so if you want to open windows using jQuery, you will need to target invisible anchor elements like this one: <code><a target='_blank'></a></code>.\", </ins> \"Remember to use <a href='//github.com/FreeCodeCamp/freecodecamp/wiki/How-to-get-help-when-you-get-stuck' target='_blank'>Read-Search-Ask</a> if you get stuck.\", \"When you are finished, click the \"I've completed this challenge\, \commidfreeCodeCamp_pr_4907negative_passages |
| query_idq-en-freeCodeCamp-a8618945d00a44421a2a382c538d6c7ea7139b86bc538678cf083517711aa3efqueryChallenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: The example code should have valid Javascript code but the semicolon at the end is missing. !\n(Sorry, used the wrong branch at first.)positive_passagesdociddoc-en-freeCodeCamp-6626c79c2218d94e1e54cc831109171ecfed093d9401793b92094788c60ecf9dtext\: [ \, \, <del> \body\animated fadeOut\, </del> <ins> \body\animated fadeOut\, </ins> \ ], \: [commidfreeCodeCamp_pr_5950negative_passages |
| query_idq-en-freeCodeCamp-a8618945d00a44421a2a382c538d6c7ea7139b86bc538678cf083517711aa3efqueryChallenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: The example code should have valid Javascript code but the semicolon at the end is missing. !\n(Sorry, used the wrong branch at first.)positive_passagesdociddoc-en-freeCodeCamp-305ad6a2c2cd1ea31d2580aba473cd12e738615748e2dc14c5bd082ad33c817ctext\: [ \, \, <del> \body\, </del> <ins> \body\, </ins> \ ] }commidfreeCodeCamp_pr_5950negative_passages |
| query_idq-en-freeCodeCamp-a208cbb024b54c3572fc19ec061d2e7f932cdae90d6cb6a2f8c6a7ac92b43caaqueryChallenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. The word refered should be written with 2 Rs: referred. !positive_passagesdociddoc-en-freeCodeCamp-87a9b9a5d46248ce90f704ff5331d30a07b737a6b2b0b8ce2689fcf287a40702text\: \, \: \, \: [ <del> \, </del> <ins> \, </ins> \https://en.wikipedia.org/wiki/Floating_point#Accuracy_problems\_blank\, \, \commidfreeCodeCamp_pr_6120negative_passages |
| query_idq-en-freeCodeCamp-a208cbb024b54c3572fc19ec061d2e7f932cdae90d6cb6a2f8c6a7ac92b43caaqueryChallenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. The word refered should be written with 2 Rs: referred. !positive_passagesdociddoc-en-freeCodeCamp-b08a0067a949e61f7fb5172c564a9cbb688d47a0c85e538c983c67a1bf60a443text\, \, \, <del> \modulus\, </del> <ins> \modulus\, </ins> \, \ ],commidfreeCodeCamp_pr_6120negative_passages |
| query_idq-en-freeCodeCamp-a208cbb024b54c3572fc19ec061d2e7f932cdae90d6cb6a2f8c6a7ac92b43caaqueryChallenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. The word refered should be written with 2 Rs: referred. !positive_passagesdociddoc-en-freeCodeCamp-f004f1038239e414479c3850fb3d8358188a9a70101474e5d59c5388edad2e6ctext\: \, \: [ \, <del> \, </del> <ins> \, </ins> \Charles\C\Charles\, \, \,commidfreeCodeCamp_pr_6120negative_passages |
| query_idq-en-freeCodeCamp-83eca547f0d3e69a54239f5587b79bf7d0e0b7d58021b5936a170fa0b324dc7equeryChallenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: Usually, paragraphs are separated with an empty line but here it is not. Currently, both paragraphs are in one string with a separating the two paragraphs. For this challenge in the file, the second paragraph should be on its own string so the spacing is consistent with all the other challenges. !\nSame goes for this challenge as well:\nHumm, don't know why I did that. Yes, these need a proper line break.\nIs this how you fork? This is my first time.\nI would consult the . It's got a lot of helpful information. The things I can see that need to be changed are: the branch name (it needs to be in the form of so like would be good) and also the issue number should not be in the commit title. It should be in the commit body and say something like . Here's more information about .", "positive_passages": [{"docid": "doc-en-freeCodeCamp-2f285a05a9fe1fdd4811c0ea4dedc05986a46ed3c8be716d3cab944e1f4127fa", "text": "\"id\": \"56533eb9ac21ba0edf2244d4\", \"title\": \"Comparison with the Greater Than Operator\", \"description\": [ <del> \"The greater than operator (<code>></code>) compares the values of two numbers. If the number to the left is greater than the number to the right, it returns <code>true</code>. Otherwise, it returns <code>false</code>.<br>Like the equality operator, greater than operator will convert data types of values while comparing.\", </del> <ins> \"The greater than operator (<code>></code>) compares the values of two numbers. If the number to the left is greater than the number to the right, it returns <code>true</code>. Otherwise, it returns <code>false</code>.\", \"Like the equality operator, greater than operator will convert data types of values while comparing.\", </ins> \"<strong>Examples</strong>\", \"<blockquote> 5 > 3 // true<br> 7 > '3' // true<br> 2 > 3 // false<br>'1' > 9 // false</blockquote>\", \"<h4>Instructions</h4>\",", "commid": "freeCodeCamp_pr_6466"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-83eca547f0d3e69a54239f5587b79bf7d0e0b7d58021b5936a170fa0b324dc7e", "query": "Challenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: Usually, paragraphs are separated with an empty line but here it is not. Currently, both paragraphs are in one string with a separating the two paragraphs. For this challenge in the file, the second paragraph should be on its own string so the spacing is consistent with all the other challenges. !\nSame goes for this challenge as well:\nHumm, don't know why I did that. Yes, these need a proper line break.\nIs this how you fork? This is my first time.\nI would consult the . It's got a lot of helpful information. The things I can see that need to be changed are: the branch name (it needs to be in the form of so like would be good) and also the issue number should not be in the commit title. It should be in the commit body and say something like . Here's more information about .positive_passagesdociddoc-en-freeCodeCamp-9f0da0991cc001c7be5f12e82895c75d027ff28a80302626cbbb49c209192ef1text\: \, \: \, \: [ <del> \, </del> <ins> \, \, </ins> \, \, \,commidfreeCodeCamp_pr_6466negative_passages |
| query_idq-en-freeCodeCamp-48273a10ef403be661ec72df8437346e7b295b44109d7be0ab5acf26dcec5044query[ ] Use Responsive Design with Bootstrap Fluid Containers [ ] Make Images Mobile Responsive [ ] Center Text with Bootstrap [ ] Create a Bootstrap Button [ ] Create a Block Element Bootstrap Button [ ] Taste the Bootstrap Button Color Rainbow [ ] Call out Optional Actions with Button Info [ ] Warn your Users of a Dangerous Action [ ] Use the Bootstrap Grid to Put Elements Side By Side [ ] Ditch Custom CSS for Bootstrap [ ] Use Spans for Inline Elements [ ] Create a Custom Heading [ ] Add Font Awesome Icons to our Buttons [ ] Add Font Awesome Icons to all of our Buttons [ ] Responsively Style Radio Buttons [ ] Responsively Style Checkboxes [ ] Style Text Inputs as Form Controls [ ] Line up Form Elements Responsively with Bootstrap [ ] Create a Bootstrap Headline [ ] House our page within a Bootstrap Container Fluid Div [ ] Create a Bootstrap Row [ ] Split your Bootstrap Row [ ] Create Bootstrap Wells [ ] Add Elements within your Bootstrap Wells [ ] Apply the Default Bootstrap Button Style [ ] Create a Class to Target with jQuery Selectors [ ] Add ID Attributes to Bootstrap Elements [ ] Label Bootstrap Wells [ ] Give Each Element a Unique ID [ ] Label Bootstrap Buttons [ ] Use Comments to Clarify Code\nWorking on this onepositive_passagesdociddoc-en-freeCodeCamp-c388caa38e4ce34a544b537011745761e1cb501457fbdef6723042de7f9be32atext\, \love\Things cats love\, \Top 3 things cats hate\, <del> \text-danger\ </del> <ins> \text-danger\ </ins> ] }, {commidfreeCodeCamp_pr_7217negative_passages |
| query_idq-en-freeCodeCamp-48273a10ef403be661ec72df8437346e7b295b44109d7be0ab5acf26dcec5044query[ ] Use Responsive Design with Bootstrap Fluid Containers [ ] Make Images Mobile Responsive [ ] Center Text with Bootstrap [ ] Create a Bootstrap Button [ ] Create a Block Element Bootstrap Button [ ] Taste the Bootstrap Button Color Rainbow [ ] Call out Optional Actions with Button Info [ ] Warn your Users of a Dangerous Action [ ] Use the Bootstrap Grid to Put Elements Side By Side [ ] Ditch Custom CSS for Bootstrap [ ] Use Spans for Inline Elements [ ] Create a Custom Heading [ ] Add Font Awesome Icons to our Buttons [ ] Add Font Awesome Icons to all of our Buttons [ ] Responsively Style Radio Buttons [ ] Responsively Style Checkboxes [ ] Style Text Inputs as Form Controls [ ] Line up Form Elements Responsively with Bootstrap [ ] Create a Bootstrap Headline [ ] House our page within a Bootstrap Container Fluid Div [ ] Create a Bootstrap Row [ ] Split your Bootstrap Row [ ] Create Bootstrap Wells [ ] Add Elements within your Bootstrap Wells [ ] Apply the Default Bootstrap Button Style [ ] Create a Class to Target with jQuery Selectors [ ] Add ID Attributes to Bootstrap Elements [ ] Label Bootstrap Wells [ ] Give Each Element a Unique ID [ ] Label Bootstrap Buttons [ ] Use Comments to Clarify Code\nWorking on this onepositive_passagesdociddoc-en-freeCodeCamp-5067602d791d4a264e335047351d5a837652d340b9c3c207d21edc245a99bcb6text\: 0, \: \, \: [ <del> \, </del> <ins> \, </ins> \, \, \http://i.imgur.com/FaYuui8.png\img-enlarge\img-responsive\http://i.imgur.com/FaYuui8.png\Pulsa para agrandar\una imagen que muestra el sistema de cuadr\u00edcula de Bootstrap\,commidfreeCodeCamp_pr_7217negative_passages |
| query_idq-en-freeCodeCamp-48273a10ef403be661ec72df8437346e7b295b44109d7be0ab5acf26dcec5044query[ ] Use Responsive Design with Bootstrap Fluid Containers [ ] Make Images Mobile Responsive [ ] Center Text with Bootstrap [ ] Create a Bootstrap Button [ ] Create a Block Element Bootstrap Button [ ] Taste the Bootstrap Button Color Rainbow [ ] Call out Optional Actions with Button Info [ ] Warn your Users of a Dangerous Action [ ] Use the Bootstrap Grid to Put Elements Side By Side [ ] Ditch Custom CSS for Bootstrap [ ] Use Spans for Inline Elements [ ] Create a Custom Heading [ ] Add Font Awesome Icons to our Buttons [ ] Add Font Awesome Icons to all of our Buttons [ ] Responsively Style Radio Buttons [ ] Responsively Style Checkboxes [ ] Style Text Inputs as Form Controls [ ] Line up Form Elements Responsively with Bootstrap [ ] Create a Bootstrap Headline [ ] House our page within a Bootstrap Container Fluid Div [ ] Create a Bootstrap Row [ ] Split your Bootstrap Row [ ] Create Bootstrap Wells [ ] Add Elements within your Bootstrap Wells [ ] Apply the Default Bootstrap Button Style [ ] Create a Class to Target with jQuery Selectors [ ] Add ID Attributes to Bootstrap Elements [ ] Label Bootstrap Wells [ ] Give Each Element a Unique ID [ ] Label Bootstrap Buttons [ ] Use Comments to Clarify Code\nWorking on this onepositive_passagesdociddoc-en-freeCodeCamp-d11683a63fae007da081662edc19a9468a12bc5e95bfb8ae3515f7b8096e8e40text\: \, \: [ \, <ins> \, \stylesheet\//maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css\, \, \, \fa fa-info-circle\, </ins> \pulgar arriba\ ] },commidfreeCodeCamp_pr_7217negative_passages |
| query_idq-en-freeCodeCamp-48273a10ef403be661ec72df8437346e7b295b44109d7be0ab5acf26dcec5044query[ ] Use Responsive Design with Bootstrap Fluid Containers [ ] Make Images Mobile Responsive [ ] Center Text with Bootstrap [ ] Create a Bootstrap Button [ ] Create a Block Element Bootstrap Button [ ] Taste the Bootstrap Button Color Rainbow [ ] Call out Optional Actions with Button Info [ ] Warn your Users of a Dangerous Action [ ] Use the Bootstrap Grid to Put Elements Side By Side [ ] Ditch Custom CSS for Bootstrap [ ] Use Spans for Inline Elements [ ] Create a Custom Heading [ ] Add Font Awesome Icons to our Buttons [ ] Add Font Awesome Icons to all of our Buttons [ ] Responsively Style Radio Buttons [ ] Responsively Style Checkboxes [ ] Style Text Inputs as Form Controls [ ] Line up Form Elements Responsively with Bootstrap [ ] Create a Bootstrap Headline [ ] House our page within a Bootstrap Container Fluid Div [ ] Create a Bootstrap Row [ ] Split your Bootstrap Row [ ] Create Bootstrap Wells [ ] Add Elements within your Bootstrap Wells [ ] Apply the Default Bootstrap Button Style [ ] Create a Class to Target with jQuery Selectors [ ] Add ID Attributes to Bootstrap Elements [ ] Label Bootstrap Wells [ ] Give Each Element a Unique ID [ ] Label Bootstrap Buttons [ ] Use Comments to Clarify Code\nWorking on this onepositive_passagesdociddoc-en-freeCodeCamp-fba143451c7a673ecceebee38b89cb50a50f066ba9c2a8dc1fca96a4954e56aftext\, \, \well\center-well\, <del> \ </del> <ins> \ </ins> ] }, {commidfreeCodeCamp_pr_7217negative_passages |
| query_idq-en-freeCodeCamp-48273a10ef403be661ec72df8437346e7b295b44109d7be0ab5acf26dcec5044query[ ] Use Responsive Design with Bootstrap Fluid Containers [ ] Make Images Mobile Responsive [ ] Center Text with Bootstrap [ ] Create a Bootstrap Button [ ] Create a Block Element Bootstrap Button [ ] Taste the Bootstrap Button Color Rainbow [ ] Call out Optional Actions with Button Info [ ] Warn your Users of a Dangerous Action [ ] Use the Bootstrap Grid to Put Elements Side By Side [ ] Ditch Custom CSS for Bootstrap [ ] Use Spans for Inline Elements [ ] Create a Custom Heading [ ] Add Font Awesome Icons to our Buttons [ ] Add Font Awesome Icons to all of our Buttons [ ] Responsively Style Radio Buttons [ ] Responsively Style Checkboxes [ ] Style Text Inputs as Form Controls [ ] Line up Form Elements Responsively with Bootstrap [ ] Create a Bootstrap Headline [ ] House our page within a Bootstrap Container Fluid Div [ ] Create a Bootstrap Row [ ] Split your Bootstrap Row [ ] Create Bootstrap Wells [ ] Add Elements within your Bootstrap Wells [ ] Apply the Default Bootstrap Button Style [ ] Create a Class to Target with jQuery Selectors [ ] Add ID Attributes to Bootstrap Elements [ ] Label Bootstrap Wells [ ] Give Each Element a Unique ID [ ] Label Bootstrap Buttons [ ] Use Comments to Clarify Code\nWorking on this onepositive_passagesdociddoc-en-freeCodeCamp-4ef94076ab29296e7d56e0c792df90d94c63e6534b62ccf74d1db1cca3d217f5text\: \, \: [ \, <del> \ </del> <ins> \, \ </ins> ] }, {commidfreeCodeCamp_pr_7217negative_passages |
| query_idq-en-freeCodeCamp-4f16cd9c5aa008e12fa44b408eadbada57fad3334b1067b52d0f19fe8d95897equeryChallenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: The challenge accepts only (single or double quotes) without any spaces between the end of the call and the dot. For example, neither of the following is accepted:\nRegex should probably be this (escaped for JS): instead of this:\nWe welcome a PR to fix this :smile:positive_passagesdociddoc-en-freeCodeCamp-d677594f060323c97c3600a24aa5f6339bf860ab8f88909e8ae3fc071ea96446text\: [ \#left-well\background-color\#left-well\background-color\#left-well\background-color\#left-well\background-color\, \, <del> \)s*?#target1s*?(?:'|\")s*?).parent/gi), 'message: The <code>.parent()</code> method should be called on the <code>#target1</code> element.');\", </del> <ins> \"assert(code.match(/$s*?(s*?(?:'|\)s*?)s*?.parent/gi), 'message: The <code>.parent()</code> method should be called on the <code>#target1</code> element.');\assert(code.match(/<div class=\ id=\>/g), 'message: Only use jQuery to add these classes to the element.');\type\waypoint\, : }], : []} |
| {: , : , : [{: , : type\hike\challengeType\challengeType\nameEs\Herramientas de desarrollo de Chrome: Elementos\descriptionEs\Esta es informaci\u00f3n b\u00e1sica y una mini-lecci\u00f3n sobre la pesta\u00f1a Elements en las herramientas de desarrollo de Chrome. Echa un vistazo a la documentaci\u00f3n m\u00e1s detallada aqu\u00ed: developers.google.com/web/tools/iterate/inspect-styles/basics \Vamos a utilizar la p\u00e1gina web mckellen.com/ por sugerencia del usuario de FreeCodeCamp kmiasko.\Si pulsas con el bot\u00f3n derecho y seleccionas 'Inspeccionar elemento', tendr\u00e1s acceso a la pesta\u00f1a elements. \u00a1Puedes cambiar el texto, el color de fondo, el color de texto y cualquier otra propiedad CSS o elemento HTML que desees!\Estos cambios no se establecen de forma autom\u00e1tica, por lo que no debes usar el inspector como un IDE o como un lugar para crear o editar cualquier cosa que desees guardar. Puedes configurar algo que se llama 'autor\u00eda persistente' para salvar.\Las reglas de CSS como cascada, herencia y otras se aplican, as\u00ed que tenlo en cuenta a medida que juegas. Adem\u00e1s, los estilos anulados se muestran con un tachado sobre ellos. \Tambi\u00e9n hay que se\u00f1alar que todo el c\u00f3digo que veas en ese '\u00e1rbol' es c\u00f3digo HTML actual, no el original que hab\u00eda cuando se carg\u00f3 la p\u00e1gina. Si utilizas jQuery o JavaScript para cambiar algo, est\u00e9 \u00e1rbol se actualizar\u00e1.\El relleno, los bordes y los m\u00e1rgenes se inspeccionan f\u00e1cilmente y puedes editarlos usando la caja con colores que encontrar\u00e1s al lado derecho o en la parte de abajo.\Por favor, echa un vistazo a la documentaci\u00f3n de las herramientas de desarrollo de Chrome en developers.google.com/web/tools/chrome-devtools/\id\56b15f15632298c12f315183\, : }], : []} |
| {: , : , : [{: , : type\hike\challengeType\challengeType\nameEs\Herramientas de desarrollo de Chrome: red\descriptionEs\La pesta\u00f1a network (red) ayuda a responder preguntas como '\u00bfQu\u00e9 elemento o parte de la p\u00e1gina fue el m\u00e1s demorado?' o '\u00bfQu\u00e9 inici\u00f3 una petici\u00f3n?'\El panel de red registra informaci\u00f3n detallada sobre cu\u00e1nto tarda en cargar cada elemento de su p\u00e1gina o aplicaci\u00f3n.\Cada solicitud se registra en la bit\u00e1cora, que se puede encontrar en la parte inferior del panel de red.\Si te fijas en la l\u00ednea al lado derecho, te dar\u00e1s cuenta de un patr\u00f3n de colores. Cada color representa un tipo diferente de contenido en la solicitud. \Cuanto m\u00e1s larga sea la l\u00ednea de un color determinado, tanto m\u00e1s tiempo tom\u00f3 ese tipo de contenido en la solicitud. En \u00faltimas quieres l\u00edneas cortas, y si cualquier solicitud tiene largas l\u00edneas, sabes que puede estar ralentizando la p\u00e1gina web.\Si pulsas sobre una solicitud en la bit\u00e1cora, podr\u00e1s obtener informaci\u00f3n m\u00e1s detallada.\Consulta m\u00e1s documentaci\u00f3n detallada aqu\u00ed: developers.google.com/web/tools/profile-performance/network-performance/resource-loading\id\56b15f15632298c12f315182\, : }], : []} |
| {: , : , : [{: , : type\hike\challengeType\challengeType\nameEs\Herramientas de desarrollo de Chrome: Fuentes\descriptionEs\La pesta\u00f1a 'fuentes' es m\u00e1s \u00fatil para la depuraci\u00f3n de JavaScript. Cuanto m\u00e1s grande sea tu proyecto, tanto m\u00e1s dif\u00edcil resulta encontrar exactamente d\u00f3nde se produce un problema. \Puedes seleccionar diferentes partes del c\u00f3digo para ser 'puntos de interrupci\u00f3n', puestos de control que detendr\u00e1n la ejecuci\u00f3n del c\u00f3digo en ese preciso momento. \Hay diferentes puntos de interrupci\u00f3n que puedes establecer, por ejemplo una l\u00ednea de c\u00f3digo espec\u00edfica, un evento del DOM, una petici\u00f3n del servidor llamada solicitud XMLHTTP, o un evento de JavaScript.\Cuando estableces un punto de interrupci\u00f3n, el navegador detiene todo cuando llega a interpretar esa l\u00ednea de c\u00f3digo o evento.\Al reducir la velocidad de todo y darte la oportunidad de examinar lo que est\u00e1 sucediendo en cada punto que hayas configurado, podr\u00e1s controlar exactamente lo que est\u00e1 sucediendo en la p\u00e1gina o aplicaci\u00f3n.\Una vez has establecido todos los puntos de interrupci\u00f3n, puedes recorrer el c\u00f3digo y examinar el estado de tu p\u00e1gina o aplicaci\u00f3n en cada punto de interrupci\u00f3n.\Al igual que con los elementos, puedes editar en vivo mediante las herramientas de desarrollo, pero recuerda que debes guardar esos cambios para que no pierdas tu progreso.\Revisa documentaci\u00f3n m\u00e1s detallada aqu\u00ed: developers.google.com/web/tools/javascript/breakpoints/\id\56b15f15632298c12f315181\, : }], : []} |
| {: , : , : [{: , : type\hike\challengeType\challengeType\nameEs\Herramientas de desarrollo de Chrome: L\u00ednea de tiempo\descriptionEs\El panel L\u00ednea de tiempo te permite grabar y analizar toda la actividad en tu aplicaci\u00f3n mientras se ejecuta. Es el mejor lugar para comenzar a investigar los problemas de rendimiento que percibas en tu aplicaci\u00f3n. \Al igual que usas el panel de red para averiguar cu\u00e1nto tiempo toman las partes de la p\u00e1gina para comunicarse con el Internet y utilizas fuentes para averiguar d\u00f3nde algo se da\u00f1a, puedes utilizar la l\u00ednea de tiempo para averiguar con m\u00e1s detalle lo que est\u00e1 pasando y el tiempo que tarda.\En el panel l\u00ednea de tiempo grabas acontecimientos con el peque\u00f1o bot\u00f3n circular. Puedes grabar (o capturar) pilas, perfiles js, la memoria y la presentaci\u00f3n (CSS). \Al grabarlos (capturalos), quedan en peque\u00f1os y detallados registros que puedes organizar de muchas maneras para que se adapten a tus necesidades.\Todo esto te ayudar\u00e1 a entender mejor lo que est\u00e1 pasando en el navegador, en particular cu\u00e1les eventos requieren m\u00e1s memoria del navegador.\Cuando uses la l\u00ednea de tiempo, recuerda que debes utilizar el bot\u00f3n 'limpiar' (clear) para iniciar la grabaci\u00f3n y antes de cargar la p\u00e1gina, dependiendo de lo que desees capturar.\Te dar\u00e1s cuenta de que cuando grabas eventos JS, al pulsar en el t\u00edtulo o en una 'llamada a una funci\u00f3n' al lado izquierdo, te llevar\u00e1 al documento y a la l\u00ednea de esa funci\u00f3n en el panel de recursos. \Revisa documentaci\u00f3n m\u00e1s detallada aqu\u00ed: developers.google.com/web/tools/profile-performance/evaluate-performance/timeline-tool\id\56b15f15632298c12f315180\, : }], : []} |
| {: , : , : [{: , : type\hike\challengeType\challengeType\nameEs\Herramientas de desarrollo de Chrome: Perfiles\descriptionEs\El panel Perfiles te permite perfilar el tiempo de ejecuci\u00f3n y el uso de memoria de una aplicaci\u00f3n web o de una p\u00e1gina. Esto se aplica principalmente a la ejecuci\u00f3n de JavaScript en su p\u00e1gina o aplicaci\u00f3n. \Hay tres tipos de perfiles que se pueden recolectar: el perfil de la CPU, instant\u00e1neas de la memoria con estructura mont\u00f3n (Heap), y el perfil de la memoria con estructura mont\u00f3n. Los perfiles de memoria en estructura mont\u00f3n tienen m\u00e1s que ver con el uso de memoria, mientras que un perfil de la CPU tiene m\u00e1s que ver con el rendimiento de JavaScript. \Un perfilador llamado V8 se usa mientras se ejecuta el c\u00f3digo para identificar lo que en el JavaScript toma mucho tiempo, facilit\u00e1ndote de esta forma optimizar tu c\u00f3digo.\Cada uno de estos perfiles se puede ver a la izquierda, y se puede tomar m\u00faltiples perfiles de cada uno. En general, la pesta\u00f1a de perfiles es muy \u00fatil cuando deseas optimizar tu c\u00f3digo. \Revisa documentaci\u00f3n m\u00e1s detallada aqu\u00ed: developers.google.com/web/tools/profile-performance/rendering-tools/js-execution\id\56b15f15632298c12f31517f\, : }], : []} |
| {: , : , : [{: , : type\hike\challengeType\challengeType\nameEs\Herramientas de desarrollo de Chrome: Recursos\descriptionEs\El panel de Recursos te permite inspeccionar los recursos que se cargan en la p\u00e1gina, incluyendo IndexedDB o bases de datos SQL Web, almacenamiento local y de sesi\u00f3n, las galletas (cookies), memoria cach\u00e9 de aplicaciones, im\u00e1genes, fuentes y hojas de estilo.\Puedes ver y editar toda esta informaci\u00f3n dentro del navegador.\A medida que vayas construyendo aplicaciones web m\u00e1s avanzadas, juega con el panel de recursos y ver\u00e1s c\u00f3mo te ayudar\u00e1 a entender los requisitos de tu aplicaci\u00f3n y de tu p\u00e1gina en tiempo real.\Revisa documentaci\u00f3n m\u00e1s detallada aqu\u00ed: developers.google.com/web/tools/iterate/manage-data/index\id\56b15f15632298c12f31517e\, : }], : []} |
| {: , : , : [{: , : type\hike\challengeType\challengeType\nameEs\Herramientas de desarrollo de Chrome: Las auditor\u00edas\descriptionEs\La herramienta de auditor\u00eda te gu\u00eda para mejorar tu p\u00e1gina paso a paso.\En este v\u00eddeo, se utiliza esta herramienta con un generador de citas aleatorias desarrollado como uno de los proyectos de desarrollo de interfaces.\Las sugerencias que se ven, se generan autom\u00e1ticamente con la funci\u00f3n de auditor\u00eda.\Es importante tenerlas en cuenta para contextualizarlos con el resto de conocimiento que tienes de tu sitio.\A veces, puede ser que sea lo acertado, pero en ocasiones, por tu situaci\u00f3n las sugerencias que da son equivocadas.\Usa esta herramienta cuando desees mejorar tu sitio o aplicaci\u00f3n, pero no sepas por d\u00f3nde empezar.\id\56b15f15632298c12f31517d\, : }], : []} |
| {: , : , : [{: , : type\hike\challengeType\challengeType\nameEs\Herramientas de desarrollo de Chrome: Consola\descriptionEs\El panel de la consola ofrece dos funciones principales: registro de datos de diagn\u00f3stico en el proceso de desarrollo y proporcionar un int\u00e9rprete de \u00f3rdenes que puedes utilizar para interactuar con el documento y las Herramientas de desarrollo\Al utilizar la consola, puedes ver los datos en bruto o estructurados mediante instrucciones est\u00e1ndar JS y \u00f3rdenes espec\u00edficas para la consola.\Un ejemplo de datos estructurados ser\u00eda la informaci\u00f3n JSON que devuelva una API. Muy \u00fatil cuando se construyen las primeras aplicaciones de desarrollo de interfaces para FreeCodeCamp.\Debes saber que los mensajes se apilan y que puedes limpiarlos escribiendo <code>clear()</code>. Tambi\u00e9n puedes guardar la bit\u00e1cora seleccionando 'Preserve Log'. \Hay diferentes \u00f3rdenes que registrar\u00e1n en bit\u00e1coras de manera diferente, como console.log() para registrar informaci\u00f3n b\u00e1sica, console.error() y console.warn() para registrar en bit\u00e1coras 'informaci\u00f3n llamativa'.\La consola puede realizar un seguimiento de excepciones, que b\u00e1sicamente registra cuando algo sale mal. Puede incluso hacer una pausa en el c\u00f3digo durante esas excepciones, funci\u00f3n que posiblemente recuerdes de la pesta\u00f1a 'Fuente'. \Revisa documentaci\u00f3n m\u00e1s detallada aqu\u00ed: developers.google.com/web/tools/javascript/console/\id\56b15f15632298c12f31517c\, : }], : []} |
| {: , : , : [{: , : type\hike\challengeType\challengeType\nameEs\Herramientas de desarrollo de Chrome: Resumen\descriptionEs\, Las herramientas de desarrollo de Chrome son impresionantes, y cuanto m\u00e1s te puedas sumergir y tratar de utilizarlas, m\u00e1s r\u00e1pido aumentar\u00e1 tu nivel. \, Utiliza la documentaci\u00f3n, incluso si nunca has le\u00eddo documentaci\u00f3n antes: developers.google.com/web/tools/chrome-devtools/ \, Una vez que comiences a sentirte c\u00f3modo en una pesta\u00f1a, r\u00e9tate aprendiendo a usar una diferente. Trabajar eficazmente con todas las pesta\u00f1as te servir\u00e1 exponencialmente m\u00e1s que pegarte en tu zona de confort.\, : }], : []} |
| {: , : , : [{: , : challengeType\nameEs\Crea una calculadora JavaScript\descriptionEs\<span class='text-info'>Objetivo:</span> Crea una aplicaci\u00f3n con <a href='http://codepen.io' target='_blank'>CodePen.io</a> que reproduzca efectivamente mediante ingenier\u00eda inversa este app: <a href='http://codepen.io/FreeCodeCamp/full/zrRzMR' target='_blank'>http://codepen.io/FreeCodeCamp/full/zrRzMR</a>.\<span class='text-info'>Objetivo:</span> Crea una aplicaci\u00f3n con <a href='http://codepen.io' target='_blank'>CodePen.io</a> cuya funcionalidad sea similar a esta: <a href='http://codepen.io/FreeCodeCamp/full/zrRzMR' target='_blank'>http://codepen.io/FreeCodeCamp/full/zrRzMR</a>.\<span class='text-info'>Regla #1:</span> No veas el c\u00f3digo del proyecto de ejemplo en CodePen. Encuentra la forma de hacerlo por tu cuenta.\<span class='text-info'>Regla #2:</span> Puedes usar cualquier librer\u00eda o APIs que necesites.\<span class='text-info'>Regla #3:</span> Usa ingenier\u00eda inversa para reproducir la funcionalidad del proyecto de ejemplo, pero tambi\u00e9n si\u00e9ntete en la libertad de personalizarlo.\Las siguientes son las <a href='http://en.wikipedia.org/wiki/User_story' target='_blank'>historias de usuario</a> que debes satisfacer, incluyendo las historias opcionales:\<span class='text-info'>Historia de usuario:</span> Como usuario, puedo sumar, restar, multiplicar y dividir dos n\u00fameros.\<span class='text-info'>Regla #2:</span> Satisface las siguientes <a href='http://en.wikipedia.org/wiki/User_story' target='_blank'>historias de usuario</a>. Usa cualquier librer\u00eda o API que necesites. Dale tu estilo personal.\<span class='text-info'>Historia de usuario:</span> Puedo sumar, restar, multiplicar y dividir dos n\u00fameros.\<span class='text-info'>Historia de usuario opcional:</span> Puedo limpiar la pantalla con un bot\u00f3n de borrar.\<span class='text-info'>Historia de usuario opcional:</span> Puedo concatenar continuamente varias operaciones hasta que pulse el bot\u00f3n de igual, y la calculadora me mostrar\u00e1 la respuesta correcta.\Recuerda utilizar <a href='//github.com/FreeCodeCamp/freecodecamp/wiki/How-to-get-help-when-you-get-stuck' target='_blank'>Read-Search-Ask</a> si te sientes atascado.\Cuando hayas terminado, pulsa el bot\u00f3n de \ e incluye un link a tu CodePen. Si programaste en pareja, debes incluir tambi\u00e9n el nombre de usuario de Free Code Camp de tu compa\u00f1ero.\Si quieres retroalimentaci\u00f3n inmediata de parte de tus compa\u00f1eros campistas, pulsa este bot\u00f3n y pega el link de tu proyecto en CodePen. <br><br><a class='btn btn-primary btn-block' href='https://twitter.com/intent/tweet?text=Check%20out%20the%20project%20I%20just%20built%20with%20%40FreeCodeCamp:%20PASTE_YOUR_CODEPEN_URL_HERE%20%0A%20%23LearnToCode%20%23JavaScript' target='_blank'>Pulsa aqu\u00ed y agrega tu link en el texto del tweet</a>\Recuerda utilizar <a href='//github.com/FreeCodeCamp/freecodecamp/wiki/How-to-get-help-when-you-get-stuck' target='_blank'>Leer-Buscar-Preguntar</a> si te sientes atascado.\Cuando hayas terminado, pulsa el bot\u00f3n de \ e incluye un enlace a tu CodePen. \Puedes obtener retroalimentaci\u00f3n sobre tu proyecto por parte de otros campistas, comparti\u00e9ndolo en nuestra <a href='//gitter.im/freecodecamp/codereview' target='_blank'>Sala de chat para revisi\u00f3n de c\u00f3digo</a>. Tambi\u00e9n puedes compartirlo en Twitter y en el campamento de tu ciudad (en Facebook).\isRequired\, : }], : []} |
| {: , : , : [{: , : nameEs\Crea un reloj pomodoro\descriptionEs\<span class='text-info'>Objetivo:</span> Crea una aplicaci\u00f3n con <a href='http://codepen.io' target='_blank'>CodePen.io</a> que reproduzca efectivamente mediante ingenier\u00eda inversa este app: <a href='http://codepen.io/FreeCodeCamp/full/VemPZX' target='_blank'>http://codepen.io/FreeCodeCamp/full/VemPZX</a>.\<span class='text-info'>Objetivo:</span> Crea una aplicaci\u00f3n con <a href='http://codepen.io' target='_blank'>CodePen.io</a> cuya funcionalidad sea similar a la de esta: <a href='http://codepen.io/FreeCodeCamp/full/VemPZX' target='_blank'>http://codepen.io/FreeCodeCamp/full/VemPZX</a>.\<span class='text-info'>Regla #1:</span> No veas el c\u00f3digo del proyecto de ejemplo en CodePen. Encuentra la forma de hacerlo por tu cuenta.\<span class='text-info'>Regla #2:</span> Puedes usar cualquier librer\u00eda o APIs que necesites.\<span class='text-info'>Regla #3:</span> Usa ingenier\u00eda inversa para reproducir la funcionalidad del proyecto de ejemplo, pero tambi\u00e9n si\u00e9ntete en la libertad de personalizarlo.\Las siguientes son las <a href='http://en.wikipedia.org/wiki/User_story' target='_blank'>historias de usuario</a> que debes satisfacer, incluyendo las historias opcionales:\<span class='text-info'>Historia de usuario:</span> Como usuario, puedo iniciar un pomodoro de 25 minutos, y el cron\u00f3metro terminar\u00e1 cuando pasen 25 minutos.\<span class='text-info'>Regla #2:</span> Satisface las siguientes <a href='http://en.wikipedia.org/wiki/User_story' target='_blank'>historias de usuario</a>. Usa cualquier librer\u00eda o APIs que necesites. Dale tu estilo personal.\<span class='text-info'>Historia de usuario:</span> Puedo iniciar un pomodoro de 25 minutos, y el cron\u00f3metro terminar\u00e1 cuando pasen 25 minutos.\<span class='text-info'>Historia de usuario:</span> Como usuario, puedo reiniciar el reloj para comenzar mi siguiente pomodoro.\<span class='text-info'>Historia de usuario opcional:</span> Como usuario, puedo personalizar la longitud de cada pomodoro.\Recuerda utilizar <a href='//github.com/FreeCodeCamp/freecodecamp/wiki/How-to-get-help-when-you-get-stuck' target='_blank'>Read-Search-Ask</a> si te sientes atascado.\Cuando hayas terminado, pulsa el bot\u00f3n de \ e incluye un link a tu CodePen. Si programaste en pareja, debes incluir tambi\u00e9n el nombre de usuario de Free Code Camp de tu compa\u00f1ero.\Si quieres retroalimentaci\u00f3n inmediata de parte de tus compa\u00f1eros campistas, pulsa este bot\u00f3n y pega el link de tu proyecto en CodePen. <br><br><a class='btn btn-primary btn-block' href='https://twitter.com/intent/tweet?text=Check%20out%20the%20project%20I%20just%20built%20with%20%40FreeCodeCamp:%20PASTE_YOUR_CODEPEN_URL_HERE%20%0A%20%23LearnToCode%20%23JavaScript' target='_blank'>Pulsa aqu\u00ed y agrega tu link en el texto del tweet</a>\<span class='text-info'>Historia de usuario:</span> Como usuario, puedo personalizar la longitud de cada pomodoro.\Recuerda utilizar <a href='//github.com/FreeCodeCamp/freecodecamp/wiki/How-to-get-help-when-you-get-stuck' target='_blank'>Leer-Buscar-Preguntar</a> si te sientes atascado.\Cuando hayas terminado, pulsa el bot\u00f3n de \ e incluye un enlace a tu CodePen.\Puedes obtener retroalimentaci\u00f3n sobre tu proyecto por parte de otros campistas, comparti\u00e9ndolo en nuestra <a href='//gitter.im/freecodecamp/codereview' target='_blank'>Sala de chat para revisi\u00f3n de c\u00f3digo</a>. Tambi\u00e9n puedes compartirlo en Twitter y en el campamento de tu ciudad (en Facebook).\isRequired\challengeType\, : }], : []} |
| {: , : , : [{: , : challengeType\nameEs\Crea un juego de Tic Tac Toe\descriptionEs\<span class='text-info'>Objetivo:</span> Crea una aplicaci\u00f3n con <a href='http://codepen.io' target='_blank'>CodePen.io</a> que reproduzca efectivamente mediante ingenier\u00eda inversa este app: <a href='http://codepen.io/FreeCodeCamp/full/adBpvw' target='_blank'>http://codepen.io/FreeCodeCamp/full/adBpvw</a>.\<span class='text-info'>Objetivo:</span> Construye una aplicaci\u00f3n en <a href='http://codepen.io' target='_blank'>CodePen.io</a> cuya funcionalidad sea similar a la de esta: <a href='http://codepen.io/FreeCodeCamp/full/adBpvw' target='_blank'>http://codepen.io/FreeCodeCamp/full/adBpvw</a>.\<span class='text-info'>Regla #1:</span> No veas el c\u00f3digo del proyecto de ejemplo en CodePen. Encuentra la forma de hacerlo por tu cuenta.\<span class='text-info'>Regla #2:</span> Puedes usar cualquier librer\u00eda o APIs que necesites.\<span class='text-info'>Regla #3:</span> Usa ingenier\u00eda inversa para reproducir la funcionalidad del proyecto de ejemplo, pero tambi\u00e9n si\u00e9ntete en la libertad de personalizarlo.\Las siguientes son las <a href='http://en.wikipedia.org/wiki/User_story' target='_blank'>historias de usuario</a> que debes satisfacer, incluyendo las historias opcionales:\<span class='text-info'>Historia de usuario:</span> Como usuario, puedo iniciar un juego de Tic Tac Toe con la computadora.\<span class='text-info'>Historia de usuario opcional:</span> Como usuario, nunca puedo ganar contra la computadora - en el mejor de los casos puedo empatar.\<span class='text-info'>Historia de usuario opcional:</span> Como usuario, mi juego se reiniciar\u00e1 tan pronto como se termine, de tal forma que pueda jugar de nuevo.\<span class='text-info'>Historia de usuario opcional:</span> Como usuario, puedo elegir si quiero jugar como X o como O.\Recuerda utilizar <a href='//github.com/FreeCodeCamp/freecodecamp/wiki/How-to-get-help-when-you-get-stuck' target='_blank'>Read-Search-Ask</a> si te sientes atascado.\Cuando hayas terminado, pulsa el bot\u00f3n de \ e incluye un link a tu CodePen. Si programaste en pareja, debes incluir tambi\u00e9n el nombre de usuario de Free Code Camp de tu compa\u00f1ero.\Si quieres retroalimentaci\u00f3n inmediata de parte de tus compa\u00f1eros campistas, pulsa este bot\u00f3n y pega el link de tu proyecto en CodePen. <br><br><a class='btn btn-primary btn-block' href='https://twitter.com/intent/tweet?text=Check%20out%20the%20project%20I%20just%20built%20with%20%40FreeCodeCamp:%20PASTE_YOUR_CODEPEN_URL_HERE%20%0A%20%23LearnToCode%20%23JavaScript' target='_blank'>Pulsa aqu\u00ed y agrega tu link en el texto del tweet</a>\<span class='text-info'>Regla #2:</span> Satisface las siguientes <a href='http://en.wikipedia.org/wiki/User_story' target='_blank'>historias de usuario</a>. Usa cualquier librer\u00eda o APIs que necesites. Dale tu estilo personal.\<span class='text-info'>Historia de usuario:</span> Puedo jugar un juego de Tic Tac Toe contra el computador.\<span class='text-info'>Historia de usuario:</span> Mi juego se reiniciar\u00e1 tan pronto como termine para poder jugar de nuevo.\<span class='text-info'>Historia de usuario:</span> Puedo elegir si quiero jugar como X o como O.\Recuerda utilizar <a href='//github.com/FreeCodeCamp/freecodecamp/wiki/How-to-get-help-when-you-get-stuck' target='_blank'>Leer-Buscar-Preguntar</a> si te sientes atascado.\Cuando hayas terminado, pulsa el bot\u00f3n de \ e incluye un enlace a tu CodePen.\Puedes obtener retroalimentaci\u00f3n sobre tu proyecto por parte de otros campistas, comparti\u00e9ndolo en nuestra <a href='//gitter.im/freecodecamp/codereview' target='_blank'>Sala de chat para revisi\u00f3n de c\u00f3digo</a>. Tambi\u00e9n puedes compartirlo en Twitter y en el campamento de tu ciudad (en Facebook).\isRequired\, : }], : []} |
| {: , : , : [{: , : challengeType\nameEs\Construye un juego de Simon\descriptionEs\<span class='text-info'>Objetivo:</span> Crea una aplicaci\u00f3n con <a href='http://codepen.io' target='_blank'>CodePen.io</a> que reproduzca efectivamente mediante ingenier\u00eda inversa este app: <a href='http://codepen.io/Em-Ant/full/QbRyqq/' target='_blank'>http://codepen.io/FreeCodeCamp/full/obYBjE</a>.\<span class='text-info'>Objetivo:</span> Construye una aplicaci\u00f3n en <a href='http://codepen.io' target='_blank'>CodePen.io</a> cuya funcionalidad sea similar a la de esta: <a href='http://codepen.io/Em-Ant/full/QbRyqq/' target='_blank'>http://codepen.io/Em-Ant/full/QbRyqq/</a>.\<span class='text-info'>Regla #1:</span> No veas el c\u00f3digo del proyecto de ejemplo en CodePen. Encuentra la forma de hacerlo por tu cuenta.\<span class='text-info'>Regla #2:</span> Puedes usar cualquier librer\u00eda o APIs que necesites.\<span class='text-info'>Regla #3:</span> Usa ingenier\u00eda inversa para reproducir la funcionalidad del proyecto de ejemplo, pero tambi\u00e9n si\u00e9ntete en la libertad de personalizarlo.\Las siguientes son las <a href='http://en.wikipedia.org/wiki/User_story' target='_blank'>historias de usuario</a> que debes satisfacer, incluyendo las historias opcionales:\<span class='text-info'>Historia de usuario:</span> Como usuario, se me presenta una serie de colores aleatoria.\<span class='text-info'>Historia de usuario:</span> Como usuario, cada vez que presiono una secuencia de colores correctamente, veo la misma serie de colores con un paso adicional.\<span class='text-info'>Historia de usuario:</span> Como usuario, escucho un sonido que corresponde a cada bot\u00f3n cuando una sequencia se me presenta, as\u00ed como cuando yo presiono un bot\u00f3n.\<span class='text-info'>Historia de usuario:</span> Como usuario, si presiono el bot\u00f3n equivocado, se me notifica sobre mi error, y la serie correcta de colores se muestra de nuevo para recordarme cu\u00e1l es la secuencia correcta, tras lo cual puedo probar de nuevo.\<span class='text-info'>Historia de usuario:</span> Como usuario, puedo ver cu\u00e1ntos pasos hay en la serie de botones actual.\<span class='text-info'>Historia de usuario opcional:</span> Como usuario, si deseo reiniciar, puedo pulsar un bot\u00f3n para hacerlo, y el juego comenzar\u00e1 desde una secuencia con un solo paso.\<span class='text-info'>Historia de usuario opcional:</span> Como usuario, puedo jugar en modo estricto donde si presiono el bot\u00f3n equivocado, se me notifica de mi error, y el juego vuelve a comenzar con una nueva serie aleatoria de colores.\<span class='text-info'>Historia de usuario opcional:</span> Como usuario, la velocidad del juego se incrementa en el quinto, noveno y decimotercer paso.\<span class='text-info'>Historia de usuario opcional:</span> Como usuario, puedo ganar el juego si completo 20 pasos correctos. Se me notifica sobre mi victoria, tras lo cual el juego se reinicia.\<span class='text-info'>Regla #2:</span> Satisface las siguientes <a href='http://en.wikipedia.org/wiki/User_story' target='_blank'>historias de usuario</a>. Usa cualquier librer\u00eda o APIs que necesites. Dale tu estilo personal.\<span class='text-info'>Historia de usuario:</span> Se me presenta una serie aleatoria de pulsaciones a botones.\<span class='text-info'>Historia de usuario:</span> Cada vez que presiono una secuencia de pulsaciones correctamente, veo que vuelve a ejecutarse la misma serie de pulsaciones con un paso adicional.\<span class='text-info'>Historia de usuario:</span> Escucho un sonido que corresponde a cada bot\u00f3n cuando se ejecuta una secuencia de pulsaciones, as\u00ed como cuando yo presiono un bot\u00f3n.\<span class='text-info'>Historia de usuario:</span> Si presiono el bot\u00f3n equivocado, se me notifica sobre mi error, y se ejecuta de nuevo la serie correcta de pulsaciones para recordarme cu\u00e1l es la secuencia correcta, tras lo cual puedo intentar de nuevo.\<span class='text-info'>Historia de usuario:</span> Puedo ver cu\u00e1ntos pasos hay en la serie de pulsaciones actual.\<span class='text-info'>Historia de usuario:</span> Si deseo reiniciar, puedo pulsar un bot\u00f3n para hacerlo, y el juego comenzar\u00e1 desde una secuencia con un solo paso.\<span class='text-info'>Historia de usuario:</span> Puedo jugar en modo estricto donde si presiono el bot\u00f3n equivocado, se me notifica de mi error, y el juego vuelve a comenzar con una nueva serie aleatoria de colores.\<span class='text-info'>Historia de usuario:</span> Puedo ganar el juego si completo 20 pasos correctos. Se me notifica sobre mi victoria, tras lo cual el juego se reinicia.\<span class='text-info'>Pista:</span> Aqu\u00ed hay algunos mp3s que puedes utilizar para tus botones: <code>https://s3.amazonaws.com/freecodecamp/simonSound1.mp3</code>, <code>https://s3.amazonaws.com/freecodecamp/simonSound2.mp3</code>, <code>https://s3.amazonaws.com/freecodecamp/simonSound3.mp3</code>, <code>https://s3.amazonaws.com/freecodecamp/simonSound4.mp3</code>.\Recuerda utilizar <a href='//github.com/FreeCodeCamp/freecodecamp/wiki/How-to-get-help-when-you-get-stuck' target='_blank'>Read-Search-Ask</a> si te sientes atascado.\Cuando hayas terminado, pulsa el bot\u00f3n de \ e incluye un link a tu CodePen. Si programaste en pareja, debes incluir tambi\u00e9n el nombre de usuario de Free Code Camp de tu compa\u00f1ero.\Si quieres retroalimentaci\u00f3n inmediata de parte de tus compa\u00f1eros campistas, pulsa este bot\u00f3n y pega el link de tu proyecto en CodePen. <br><br><a class='btn btn-primary btn-block' href='https://twitter.com/intent/tweet?text=Check%20out%20the%20project%20I%20just%20built%20with%20%40FreeCodeCamp:%20PASTE_YOUR_CODEPEN_URL_HERE%20%0A%20%23LearnToCode%20%23JavaScript' target='_blank'>Pulsa aqu\u00ed y agrega tu link en el texto del tweet</a>\Recuerda utilizar <a href='//github.com/FreeCodeCamp/freecodecamp/wiki/How-to-get-help-when-you-get-stuck' target='_blank'>Leer-Buscar-Preguntar</a> si te sientes atascado.\Cuando hayas terminado, pulsa el bot\u00f3n de \ e incluye un enlace a tu CodePen.\Puedes obtener retroalimentaci\u00f3n sobre tu proyecto por parte de otros campistas, comparti\u00e9ndolo en nuestra <a href='//gitter.im/freecodecamp/codereview' target='_blank'>Sala de chat para revisi\u00f3n de c\u00f3digo</a>. Tambi\u00e9n puedes compartirlo en Twitter y en el campamento de tu ciudad (en Facebook).\isRequired\, : }], : []} |
| {: , : , : [{: , : description\Compare and update inventory stored in a 2d array against a second 2d array of a fresh delivery. Update current inventory item quantity, and if an item cannot be found, add the new item and quantity into the inventory array in alphabetical order.\challengeSeed\function inventory(arr1, arr2) {n // All inventory must be accounted for or you're fired!rn return arr1;rn}nn// Example inventory listsrnvar curInv = [rn [21, 'Bowling Ball'],rn [2, 'Dirty Sock'],rn [1, 'Hair pin'],rn [5, 'Microphone']rn];rnrnvar newInv = [rn [2, 'Hair Pin'],rn [3, 'Half-Eaten Apple'],rn [67, 'Bowling Ball'],rn [7, 'Toothpaste']rn];rnrninventory(curInv, newInv);\", \"tests\": [ \"expect(inventory([[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair pin'], [5, 'Microphone']], [[2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [67, 'Bowling Ball'], [7, 'Toothpaste']])).to.be.a('array');\", \"assert.equal(inventory([[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair pin'], [5, 'Microphone']], [[2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [67, 'Bowling Ball'], [7, 'Toothpaste']]).length, 6);\", \"assert.deepEqual(inventory([[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair pin'], [5, 'Microphone']], [[2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [67, 'Bowling Ball'], [7, 'Toothpaste']]), [[88, 'Bowling Ball'], [2, 'Dirty Sock'], [3, 'Hair pin'], [3, 'Half-Eaten Apple'], [5, 'Microphone'], [7, 'Toothpaste']]);\", \"assert.deepEqual(inventory([[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair pin'], [5, 'Microphone']], []), [[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair pin'], [5, 'Microphone']]);\", \"assert.deepEqual(inventory([], [[2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [67, 'Bowling Ball'], [7, 'Toothpaste']]), [[2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [67, 'Bowling Ball'], [7, 'Toothpaste']]);\", \"assert.deepEqual(inventory([[0, 'Bowling Ball'], [0, 'Dirty Sock'], [0, 'Hair pin'], [0, 'Microphone']], [[1, 'Hair Pin'], [1, 'Half-Eaten Apple'], [1, 'Bowling Ball'], [1, 'Toothpaste']]), [[1, 'Bowling Ball'], [1, 'Dirty Sock'], [1, 'Hair pin'], [1, 'Half-Eaten Apple'], [1, 'Microphone'], [1, 'Toothpaste']]);\" </del> <ins> \"challengeSeed\": \"function inventory(arr1, arr2) {n // All inventory must be accounted for or you're fired!rn return arr1;rn}nn// Example inventory listsrnvar curInv = [rn [21, 'Bowling Ball'],rn [2, 'Dirty Sock'],rn [1, 'Hair Pin'],rn [5, 'Microphone']rn];rnrnvar newInv = [rn [2, 'Hair Pin'],rn [3, 'Half-Eaten Apple'],rn [67, 'Bowling Ball'],rn [7, 'Toothpaste']rn];rnrninventory(curInv, newInv);\tests\expect(inventory([[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair Pin'], [5, 'Microphone']], [[2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [67, 'Bowling Ball'], [7, 'Toothpaste']])).to.be.a('array');\assert.equal(inventory([[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair Pin'], [5, 'Microphone']], [[2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [67, 'Bowling Ball'], [7, 'Toothpaste']]).length, 6);\assert.deepEqual(inventory([[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair Pin'], [5, 'Microphone']], [[2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [67, 'Bowling Ball'], [7, 'Toothpaste']]), [[88, 'Bowling Ball'], [2, 'Dirty Sock'], [3, 'Hair Pin'], [3, 'Half-Eaten Apple'], [5, 'Microphone'], [7, 'Toothpaste']]);\assert.deepEqual(inventory([[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair Pin'], [5, 'Microphone']], []), [[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair Pin'], [5, 'Microphone']]);\assert.deepEqual(inventory([], [[2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [67, 'Bowling Ball'], [7, 'Toothpaste']]), [[67, 'Bowling Ball'], [2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [7, 'Toothpaste']]);\assert.deepEqual(inventory([[0, 'Bowling Ball'], [0, 'Dirty Sock'], [0, 'Hair Pin'], [0, 'Microphone']], [[1, 'Hair Pin'], [1, 'Half-Eaten Apple'], [1, 'Bowling Ball'], [1, 'Toothpaste']]), [[1, 'Bowling Ball'], [0, 'Dirty Sock'], [1, 'Hair Pin'], [1, 'Half-Eaten Apple'], [0, 'Microphone'], [1, 'Toothpaste']]);\, : }], : []} |
| {: , : Huge\, : [{: , : video\114591799\challengeNumber\steps\Now that we've built a foundation in jQuery, let's go back to Dash and do it's last challenge.\", </del> <ins> \"Now that we've built a foundation in jQuery, let's go back to Dash and do its last challenge.\", </ins> \"If you aren't familiar with Mad Libs, they basically involve inserting random nouns, adjectives and verbs in to stories. The stories that result are often hilarious.\Go to <a href='https://dash.generalassemb.ly/projects/mad-libs-1' target='_blank'>https://dash.generalassemb.ly/projects/mad-libs-1</a> and complete the fifth project.\, : }], : []} |
| {: , : Huge\, : [{: , : , : }], : []} |
| {: , : Huge\, : [{: , : , : }], : []} |
| {: , : Huge\, : [{: , : , : }], : []} |
| {: , : Huge\, : [{: , : /nonprofits\https://s3.amazonaws.com/freecodecamp/testimonial-jen.jpg\@jenthebest's testimonial image\") .testimonial-copy Getting back on track with Free Code Camp and committing to a new career in 2015! h3 - @jenthebest .col-xs-12.col-sm-12.col-md-4 img.img-responsive.testimonial-image.img-center(src=\"https://s3.amazonaws.com/freecodecamp/testimonial-tate.jpg\", alt=\"@TateThurston's testimonial image\https://s3.amazonaws.com/freecodecamp/testimonial-cynthia.jpg\@cynthialanel's testimonial image\") .testimonial-copy I'm currently working through Free Code Camp to improve my JavaScript. The community is very welcoming! h3 - @cynthialanel .big-break h2 Skills you'll learn: .text-center .col-xs-12.col-sm-12.col-md-3 .landing-skill-icon.ion-social-html5 .black-text HTML5 .col-xs-12.col-sm-12.col-md-3 .landing-skill-icon.ion-social-css3 .black-text CSS3 .col-xs-12.col-sm-12.col-md-3 .landing-skill-icon.ion-social-javascript .black-text JavaScript .col-xs-12.col-sm-12.col-md-3 .landing-skill-icon.fa.fa-database.font-awesome-padding .black-text Databases .col-xs-12.col-sm-12.col-md-3 .landing-skill-icon.ion-social-chrome .black-text DevTools .col-xs-12.col-sm-12.col-md-3 .landing-skill-icon.ion-social-nodejs .black-text Node.js .col-xs-12.col-sm-12.col-md-3 .landing-skill-icon.ion-social-angular .black-text Angular.js .col-xs-12.col-sm-12.col-md-3 .landing-skill-icon.ion-ios-loop-strong .black-text Agile .big-break h2 h2 Fast facts about our community: h3.col-xs-offset-0.col-sm-offset-1.col-md-offset-2 ul.text-left li.ion-code We're 100% free and open source li.ion-code We're thousands of professionals who are learning to code li.ion-code We're building projects for dozens of nonprofits li.ion-code We share one goal: to boost our careers with code .big-break a.btn.btn-cta.signup-btn(href=\) Start learning to code (it's free) </ins> No newline at end of file", "commid": "freeCodeCamp_pr_30"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-1900eb6c754a31f7f4a4737a49530c75b5d45ee9dc1abb6ba52245f2c91bd944", "query": "Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.87 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nthe instructions are correct. You'll need to return \ whenever . If you get stuck with a challenge, please ask questions to the . Happy coding!positive_passagesdociddoc-en-freeCodeCamp-eff1cbf87f49bdb86166089047268cc20edea8b355ab116cc7276b579f99a8fctext\: \, \: [ \, <del> \, </del> <ins> \, </ins> \ ] },commidfreeCodeCamp_pr_87negative_passages |
| query_idq-en-freeCodeCamp-aaf5753eb39e674e331b05fb15d8afe05fa9175903ea67c896f0988d99acdcdcquery<!-- FreeCodeCamp Issue Template --<!-- Please provide as much detail as possible for us to fix your issue --<!-- Remove any heading sections you did not fill out --<!-- Insert link to challenge below -- <!-- Describe below when the issue happens and how to reproduce it --This challenge would be a lot more informative if a description of what adding the form-control class to the input field actually does. Something along the lines of: All textual [input], [textarea], and [select] elements with class [.form-control] have a width of 100%.\nThis challenge is currently quite short and it's defiantly worth adding an explanation here. To First Timer: You will need to add the sentence under line. Please, check our and if you need any assistance reach out to the .\nThe code you'll need to add specifically is It should render as\nHey there. I'm a first-timer interested in getting started with contributing to Free Code Camp. I will submit a PR for this issue. Thanks!\nHey What about tests ?? Tests should be for each input.\nhaving issue in style-text-inputs-as-form-controls just give a class=\"form-control\" to before your checkbox's 1st div and finally add here 3)positive_passagesdociddoc-en-freeCodeCamp-e9ae86693e537085f6ea767608db9510676c29be39db7b885c9dcf2a3f3da7c2text], \: [ \fa fa-paper-plane\, <del> \ </del> <ins> \, \ </ins> ], \: [ \https://fonts.googleapis.com/css?family=Lobster\stylesheet\text/css\,commidfreeCodeCamp_pr_10330negative_passages |
| query_idq-en-freeCodeCamp-31db290060f7e3a11ef15434626b4d27b6b937dfc49268e2d510d0f0e4663af8queryChallenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: ! As you can see on the screenshot there are two instances of #target5 button in the result. I believe it's incorrect. Issue is also affecting at least next challenge - this one\nDuplicate of Thanks for reporting This a very old and known issue, we have fixed it in the react version of the website, which will be released again soon. Until then please ignore this issue and continue. Happy Coding!\nThanks, I wasn't able to find because I didn't look at closed ones.\nsure thing, no problem. It's quite an old one, lol took me a while to find out as well.\nAmazing! Was about to report the same :)positive_passagesdociddoc-en-freeCodeCamp-089373e27da324936089b8a63a9d6d8b73ad51a2eeec19c909d89ef8d2439e3ftextvar isCompletedDate = Math.round(+new Date() / 1000); var bonfireHash = req.body.bonfireInfo.bonfireHash; var isSolution = req.body.bonfireInfo.solution; <del> // TODO debug(isCompletedWith, 'Is completed with'); </del> if (isCompletedWith) { var paired = User.find({\: isCompletedWith}).limit(1);commidfreeCodeCamp_pr_55negative_passages |
| query_idq-en-freeCodeCamp-31db290060f7e3a11ef15434626b4d27b6b937dfc49268e2d510d0f0e4663af8queryChallenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: ! As you can see on the screenshot there are two instances of #target5 button in the result. I believe it's incorrect. Issue is also affecting at least next challenge - this one\nDuplicate of Thanks for reporting This a very old and known issue, we have fixed it in the react version of the website, which will be released again soon. Until then please ignore this issue and continue. Happy Coding!\nThanks, I wasn't able to find because I didn't look at closed ones.\nsure thing, no problem. It's quite an old one, lol took me a while to find out as well.\nAmazing! Was about to report the same :)positive_passagesdociddoc-en-freeCodeCamp-f7074bae61dcd81de65837566cf89d83674231ca217d856ad305b1a7d1cc69c7textthrow err; } if (user && paired) { <del> res.redirect('/bonfires'); </del> <ins> res.send(true); </ins> } }) }); } }) } else { req.user.completedBonfires.push({ _id: bonfireHash, completedWith: null,commidfreeCodeCamp_pr_55negative_passages |
| query_idq-en-freeCodeCamp-31db290060f7e3a11ef15434626b4d27b6b937dfc49268e2d510d0f0e4663af8queryChallenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: ! As you can see on the screenshot there are two instances of #target5 button in the result. I believe it's incorrect. Issue is also affecting at least next challenge - this one\nDuplicate of Thanks for reporting This a very old and known issue, we have fixed it in the react version of the website, which will be released again soon. Until then please ignore this issue and continue. Happy Coding!\nThanks, I wasn't able to find because I didn't look at closed ones.\nsure thing, no problem. It's quite an old one, lol took me a while to find out as well.\nAmazing! Was about to report the same :)positive_passagesdociddoc-en-freeCodeCamp-1aa605eb80df2e320f6bdcef16b66b99449cfa6f473136fc8c6ad4df6a5c13d1text}) var index = req.user.uncompletedBonfires.indexOf(bonfireHash); if (index > -1) { req.user.uncompletedBonfires.splice(index,1) } req.user.save(function(err, user) { if (err) { throw err; } if (user) { <del> res.redirect('/bonfires'); </del> <ins> debug('Saving user'); res.send(true) </ins> } }); } }); // Unique Check API routecommidfreeCodeCamp_pr_55negative_passages |
| query_idq-en-freeCodeCamp-31db290060f7e3a11ef15434626b4d27b6b937dfc49268e2d510d0f0e4663af8queryChallenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: ! As you can see on the screenshot there are two instances of #target5 button in the result. I believe it's incorrect. Issue is also affecting at least next challenge - this one\nDuplicate of Thanks for reporting This a very old and known issue, we have fixed it in the react version of the website, which will be released again soon. Until then please ignore this issue and continue. Happy Coding!\nThanks, I wasn't able to find because I didn't look at closed ones.\nsure thing, no problem. It's quite an old one, lol took me a while to find out as well.\nAmazing! Was about to report the same :)positive_passagesdociddoc-en-freeCodeCamp-f13680d0435cbf36b53065c1665d2b3993eb4fc29c4c9b491948f6b895a9b5b6textreturn res.redirect('bonfires/meet-bonfire'); } var currentTime = parseInt(+new Date() / 1000); <del> if (currentTime - req.user.lastContentSync > 86400) { </del> <ins> if (currentTime - req.user.lastContentSync > 10) { </ins> req.user.lastContentSync = currentTime; var completed = req.user.completedBonfires.map(function (elem) { return elem._id;commidfreeCodeCamp_pr_55negative_passages |
| query_idq-en-freeCodeCamp-31db290060f7e3a11ef15434626b4d27b6b937dfc49268e2d510d0f0e4663af8queryChallenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: ! As you can see on the screenshot there are two instances of #target5 button in the result. I believe it's incorrect. Issue is also affecting at least next challenge - this one\nDuplicate of Thanks for reporting This a very old and known issue, we have fixed it in the react version of the website, which will be released again soon. Until then please ignore this issue and continue. Happy Coding!\nThanks, I wasn't able to find because I didn't look at closed ones.\nsure thing, no problem. It's quite an old one, lol took me a while to find out as well.\nAmazing! Was about to report the same :)positive_passagesdociddoc-en-freeCodeCamp-d326d6e516d4f955644f304ed99477c67416e8e0bcf19d62678c0f75e9848582text} } }); <del> } if (allTestsPassed) { allTestsPassed = false; showCompletion(); </del> <ins> if (allTestsPassed) { allTestsPassed = false; showCompletion(); } </ins> } };commidfreeCodeCamp_pr_55negative_passages |
| query_idq-en-freeCodeCamp-31db290060f7e3a11ef15434626b4d27b6b937dfc49268e2d510d0f0e4663af8queryChallenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: ! As you can see on the screenshot there are two instances of #target5 button in the result. I believe it's incorrect. Issue is also affecting at least next challenge - this one\nDuplicate of Thanks for reporting This a very old and known issue, we have fixed it in the react version of the website, which will be released again soon. Until then please ignore this issue and continue. Happy Coding!\nThanks, I wasn't able to find because I didn't look at closed ones.\nsure thing, no problem. It's quite an old one, lol took me a while to find out as well.\nAmazing! Was about to report the same :)positive_passagesdociddoc-en-freeCodeCamp-34ba44f798213a4465db989b4db08a15c66d640af01449fe72559acadc768bd2text$('#complete-bonfire-dialog').modal('show'); // Only post to server if there is an authenticated user if ($('.signup-btn-nav').length < 1) { <del> $.ajax({ type: 'POST', data: { </del> <ins> $.post( '/completed-bonfire', { </ins> bonfireInfo: { completedWith : didCompleteWith, solution: bonfireSolution, bonfireHash: thisBonfireHash } }, <del> url: '/completed-bonfire/' }); </del> <ins> function(res) { if (res) { window.location.href = 'http://localhost:3001/bonfires' } }) </ins> } } <ins> $('.next-bonfire-button').on('click', function() { var bonfireSolution = myCodeMirror.getValue(); var thisBonfireHash = passedBonfireHash || null; var didCompleteWith = $('#completed-with').val() || null; completedBonfire(didCompleteWith, bonfireSolution, thisBonfireHash); }); </ins> $('.all-challenges').on('click', function() { $('#all-challenges-dialog').modal('show'); });commidfreeCodeCamp_pr_55negative_passages |
| query_idq-en-freeCodeCamp-31db290060f7e3a11ef15434626b4d27b6b937dfc49268e2d510d0f0e4663af8queryChallenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: ! As you can see on the screenshot there are two instances of #target5 button in the result. I believe it's incorrect. Issue is also affecting at least next challenge - this one\nDuplicate of Thanks for reporting This a very old and known issue, we have fixed it in the react version of the website, which will be released again soon. Until then please ignore this issue and continue. Happy Coding!\nThanks, I wasn't able to find because I didn't look at closed ones.\nsure thing, no problem. It's quite an old one, lol took me a while to find out as well.\nAmazing! Was about to report the same :)positive_passagesdociddoc-en-freeCodeCamp-b99abe611b9ae009172884f0e6499581d69957110f62eda1ff6d4511423202datext}); <del> $('.next-bonfire-button').on('click', function() { var bonfireSolution = myCodeMirror.getValue(); var thisBonfireHash = passedBonfireHash || null; var didCompleteWith = $('#completed-with').val() || null; completedBonfire(didCompleteWith, bonfireSolution, thisBonfireHash); window.setTimeout(function() { // TODO window.location = '/bonfires'; }, 100); }); </del> // Bonfire instructions functions $('#more-info').on('click', function() {commidfreeCodeCamp_pr_55negative_passages |
| query_idq-en-freeCodeCamp-309ecc532e64605ca7d06fb59f3e8436c4303d2dacfe8bb83c521dc04b552c54queryChallenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. content: \; // when you addany extra space outside the empty string will not pass this challenge. Can't you add any whitespace?\nI believe this is by intention, rather than being a bug. You can, but you would do so using a few different means such as margin, padding, or positioning depending on the situation and what you are trying to accomplish. The content attribute of the :before and :after attributes would not interpret arbitrary white space in the way I believe you are asking.\nI see what you mean, the tests are too strict. I could fix this if a moderator approves that the tests need to be changed.\nWe just launched the new curriculum and learning platform. Please take a look at it: Do you still think this challenge is confusing or overly hard? If so, we would welcome improvements to this challenge.\nI will look into the tests tomorrow.\nYou're the man. Thanks! Please keep us posted\nI will prepared this and a couple of others for first timers. If the issue is not taken in a couple of days, I will come back and fix them. Let me know if you want me to fix them immediately The location of the test that needs to be changed: the new line should be: \: \\\nFYI on the issues page it encourages fist timers to search for the \ label which does not exist. It should say \ !\nDoes the issue still exist if not then I would like to work on it?\nsorry for the late response. Yes it is open.\ncould you link me to the page where you're seeing this? Then I can update it.\nIt is on the issues page when I sign in with my moderator account.\nplease review my PR regarding this issue.\nOK - thanks for letting me know - I still can't see it for some reason so you would be a better person to QA this.positive_passagesdociddoc-en-freeCodeCamp-a7d53ab195efcf5132dcaed837cbc67e8577b76100a1482541e47c66bcca366dtext\, \ ], <del> \: \I'm a little tea pot\")\", </del> <ins> \"challengeEntryPoint\": \"titleCase(\"I'm a little tea pot\, </ins> \: \, \: [ \I'm a little tea pot\")).to.be.a('String');\",", "commid": "freeCodeCamp_pr_57"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-ec570f1ef6eb9531c36cac6d7fe7311d9712e96aa359827727d7620a4b499831", "query": "Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nHi Thanks for reporting this issue. Here are some next steps that you should follow before we can help you with your query: Check first. Please use the or try looking through our for help with a specific challenge and any coding assistance. IMPORTANT: Please NOTE that this tracker is for reporting bugs and enhancements to freeCodeCamp's code base only. Happy Coding!positive_passagesdociddoc-en-freeCodeCamp-1a5fe3b66265ae259e7197b946b59f0eb9b4a9f288d5511af1ab779e6676bc05text\: \, \: [ \, <del> \, </del> <ins> \, </ins> \ ], \: \,commidfreeCodeCamp_pr_92negative_passages |
| query_idq-en-freeCodeCamp-ec570f1ef6eb9531c36cac6d7fe7311d9712e96aa359827727d7620a4b499831queryChallenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nHi Thanks for reporting this issue. Here are some next steps that you should follow before we can help you with your query: Check first. Please use the or try looking through our for help with a specific challenge and any coding assistance. IMPORTANT: Please NOTE that this tracker is for reporting bugs and enhancements to freeCodeCamp's code base only. Happy Coding!", "positive_passages": [{"docid": "doc-en-freeCodeCamp-3663f39a0d0c30e4a73e5a1e20fc84648dc54c1d05138d3d5b62719233472d44", "text": "\"name\": \"Sum All Odd Fibonacci Numbers\", \"difficulty\": \"2.09\", \"description\": [ <del> \"Return the sum of all odd fibonacci numbers up to and including the passed number if it is a fibonacci number.\", </del> <ins> \"Return the sum of all odd Fibonacci numbers up to and including the passed number if it is a Fibonacci number.\", </ins> \"The first few numbers of the Fibonacci sequence are 1, 1, 2, 3, 5 and 8, and each subsequent number is the sum of the previous two numbers.\", <del> \"As an example, passing 4 to the function should return 5 because all the odd fibonacci numbers under 4 are 1, 1, and 3.\" </del> <ins> \"As an example, passing 4 to the function should return 5 because all the odd Fibonacci numbers under 4 are 1, 1, and 3.\" </ins> ], \"challengeEntryPoint\": \"sumFibs(4);\", \"challengeSeed\": \"function sumFibs(num) {n return num;rn}\",", "commid": "freeCodeCamp_pr_92"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-ec570f1ef6eb9531c36cac6d7fe7311d9712e96aa359827727d7620a4b499831", "query": "Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nHi Thanks for reporting this issue. Here are some next steps that you should follow before we can help you with your query: Check first. Please use the or try looking through our for help with a specific challenge and any coding assistance. IMPORTANT: Please NOTE that this tracker is for reporting bugs and enhancements to freeCodeCamp's code base only. Happy Coding!positive_passagesdociddoc-en-freeCodeCamp-1ccca0566b647002ae9cd7be0892bc3bbea0e7abbf4d32d9acb57d32a0baea1ctext\: \, \: [ \, <del> \, </del> <ins> \, </ins> \ ], \: \,commidfreeCodeCamp_pr_92negative_passages |
| query_idq-en-freeCodeCamp-ec570f1ef6eb9531c36cac6d7fe7311d9712e96aa359827727d7620a4b499831queryChallenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nHi Thanks for reporting this issue. Here are some next steps that you should follow before we can help you with your query: Check first. Please use the or try looking through our for help with a specific challenge and any coding assistance. IMPORTANT: Please NOTE that this tracker is for reporting bugs and enhancements to freeCodeCamp's code base only. Happy Coding!", "positive_passages": [{"docid": "doc-en-freeCodeCamp-b92f786cf47b089e688a9268fad561e27601a0ef2dc2b7d6ceadd9d337718b00", "text": "\"Fill in the object constructor with the methods specified in the tests.\", \"Those methods are getFirstName(), getLastName(), getFullName(), setFirstName(), setLastName(), and setFullName().\", \"These methods must be the only available means for interacting with the object.\", <del> \"There will be some linting errors on the tests, you may safely ignore them. You should see undefined in the console output.\" </del> <ins> \"There will be some linting errors on the tests. You may safely ignore them. You should see undefined in the console output.\" </ins> ], \"challengeEntryPoint\": \"var bob = new Person('Bob Ross');\", \"challengeSeed\": \"var Person = function(firstAndLast) {n return firstAndLast;rn};\",", "commid": "freeCodeCamp_pr_92"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-ec570f1ef6eb9531c36cac6d7fe7311d9712e96aa359827727d7620a4b499831", "query": "Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nHi Thanks for reporting this issue. Here are some next steps that you should follow before we can help you with your query: Check first. Please use the or try looking through our for help with a specific challenge and any coding assistance. IMPORTANT: Please NOTE that this tracker is for reporting bugs and enhancements to freeCodeCamp's code base only. Happy Coding!positive_passagesdociddoc-en-freeCodeCamp-4cf015d64b8096c83a3c991ba3970153e6ccad7983065f9b5e8fe7150ffbe36ftext\, \, \, <del> \800-692-7753\8oo-six427676;laskdjf\1\ </del> <ins> \800-692-7753\8oo-six427676;laskdjf\1\ </ins> ], \: [ \555-555-5555\boolean\,commidfreeCodeCamp_pr_92negative_passages |
| query_idq-en-freeCodeCamp-f1217f2a9876161e822f26088d2ca6cc9e89c477e03ca52a140f2ca9ea85417bqueryBuild a Pinterest Clone Following the link to the gives the following warning in Firefox: 'The owner of midnight- has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website.' Firefox 54.0.1 Mac OS El Capitan 10.11.6\nConfirmed on chrome too. Must have missed this when we changed all the hyperdev links to glitch.\nI would like to tackle this.positive_passagesdociddoc-en-freeCodeCamp-8d8ea5d8486b166e7c36f1a598e6a4fc2219493fc913103ecccb8e7ebb07648ftext\: \, \: \, \: [ <del> \, </del> <ins> \, </ins> \, \, \,commidfreeCodeCamp_pr_15694negative_passages |
| query_idq-en-freeCodeCamp-f1217f2a9876161e822f26088d2ca6cc9e89c477e03ca52a140f2ca9ea85417bqueryBuild a Pinterest Clone Following the link to the gives the following warning in Firefox: 'The owner of midnight- has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website.' Firefox 54.0.1 Mac OS El Capitan 10.11.6\nConfirmed on chrome too. Must have missed this when we changed all the hyperdev links to glitch.\nI would like to tackle this.positive_passagesdociddoc-en-freeCodeCamp-0cf5fbe98aeea9e72623bbc88b6dc1790085729d2a740eb147c3dd4fa5799696text\: \, \: 4, \: [ <del> \, </del> <ins> \, </ins> \, \, \,commidfreeCodeCamp_pr_15694negative_passages |
| query_idq-en-freeCodeCamp-ebb7c7f050f1d2de841d7580d10247f518cf78c0f481f64970791f556d8788c8queryThis problem does not work with the freeCodeCamp platform since the description says to use an external file. This is impossible with the platform. After consulting with & it was decided to delete this challenge completely. This needs to be done.\nDoes this involve just removing the problem from the project-euler- file? I can take this.\nYup! Pretty simple. Just delete the entire problem from project-euler- Thanks for claiming this one.positive_passagesdociddoc-en-freeCodeCamp-8779945521524215017beefc91423cbea868f29e441bb8a520242b7a8df7c370text] }, { <del> \: \, \: 5, \: \, \: \, \: [ \ ], \: [], \: {}, \: [ \, \, \, \, \, \ ], \: [ \, \, \ ] }, { </del> \: \, \: 5, \: \,commidfreeCodeCamp_pr_15837negative_passages |
| query_idq-en-freeCodeCamp-4da7a05c0ed6a1ccfcabf7b1bfab7d608f69b3d270b211626d118958b7b823c8query<!-- freeCodeCamp Issue Template --<!-- Please provide as much detail as possible for us to fix your issue --<!-- Remove any heading sections you did not fill out --<!-- NOTE: If your issue is CodePen Project / Test Suite related, please open it using the below URL instead --<!-- --Sass: Use to Map Over Items in a List The challenge always fails on the point 2-3-4, despite the code seems to be correct, the preview works fine and inspecting the html show me the three styles (blue-bg, black-bg, red-bg) properly expanded Browser Name, Version: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36. Operating System: Microsoft Windows 7 Enterprise SP1 Mobile, Desktop, or Tablet: Desktop !\ncheckout this issuepositive_passagesdociddoc-en-freeCodeCamp-eba52b2d7a662d7c25740758f4646602a8ebc093c175093e424d02cd05033645text], \: [ \, <del> \, \, \ </del> <ins> \, \, \ </ins> ], \: [], \: [],commidfreeCodeCamp_pr_17032negative_passages |
| query_idq-en-freeCodeCamp-e2e5f4740fe7a01f6808d6a26b475b7abad68b5290e5fdbb1bdb78237790e11equery<!-- freeCodeCamp Issue Template --<!-- Please provide as much detail as possible for us to fix your issue --<!-- Remove any heading sections you did not fill out --<!-- NOTE: If your issue is CodePen Project / Test Suite related, please open it using the below URL instead --<!-- --<!-- Insert link to challenge below -- <!-- Describe below when the issue happens and how to reproduce it --The following text seems to be a typo: Be sure to match both upper- and lowercase vowels. It should say: Be sure to match both upper- and lowercase letters.\nHey, I'm a first timer to open source. Is it alright if I take this issue?\nPR out", "positive_passages": [{"docid": "doc-en-freeCodeCamp-7b168b4ddc48fa04c0b6a4975f015edde19f07ffd3805097d2f97cc6e4039c75", "text": "\"<blockquote>let catStr = \"cat\";<br>let batStr = \"bat\";<br>let matStr = \"mat\";<br>let bgRegex = /[a-e]at/;<br>catStr.match(bgRegex); // Returns [\"cat\"]<br>batStr.match(bgRegex); // Returns [\"bat\"]<br>matStr.match(bgRegex); // Returns null</blockquote>\", \"<hr>\", \"Match all the letters in the string <code>quoteSample</code>.\", <del> \"<strong>Note</strong><br>Be sure to match both upper- and lowercase vowels.\" </del> <ins> \"<strong>Note</strong><br>Be sure to match both upper- and lowercase <strong>letters<strong>.\" </ins> ], \"challengeSeed\": [ \"let quoteSample = \"The quick brown fox jumps over the lazy dog.\";\",", "commid": "freeCodeCamp_pr_16991"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-ace15fd60933668207dd4c09e6ab6fb05b3247a90b328bb3aaea5de677f02a45", "query": "Once we've built the JSON we want to output, I believe we can just use Pug like this for the button to initiate the file download:positive_passagesdociddoc-en-freeCodeCamp-af843584383383ff83a01f78e6f887dd90abe59717609e44daa4a0ddcfc7ece6textimport { bindActionCreators } from 'redux'; import { connect } from 'react-redux'; import { createSelector } from 'reselect'; <ins> import { Button } from 'react-bootstrap'; </ins> import { updateMyProfileUI } from '../redux'; import { userSelector } from '../../../redux'; <del> import { FullWidthRow } from '../../../helperComponents'; </del> <ins> import { FullWidthRow, Spacer } from '../../../helperComponents'; </ins> import SectionHeader from './SectionHeader.jsx'; import ToggleSetting from './ToggleSetting.jsx'; const mapStateToProps = createSelector( userSelector, <del> ({ profileUI = {} }) => ({ ...profileUI </del> <ins> user => ({ ...user.profileUI, user </ins> }) );commidfreeCodeCamp_pr_17252negative_passages |
| query_idq-en-freeCodeCamp-ace15fd60933668207dd4c09e6ab6fb05b3247a90b328bb3aaea5de677f02a45queryOnce we've built the JSON we want to output, I believe we can just use Pug like this for the button to initiate the file download:", "positive_passages": [{"docid": "doc-en-freeCodeCamp-a98d4ce92aa208678842545710071db28a1765945833926fb21fc114ef3f3edc", "text": "showPoints: PropTypes.bool, showPortfolio: PropTypes.bool, showTimeLine: PropTypes.bool, <del> updateMyProfileUI: PropTypes.func.isRequired </del> <ins> updateMyProfileUI: PropTypes.func.isRequired, user: PropTypes.object </ins> }; function PrivacySettings(props) {", "commid": "freeCodeCamp_pr_17252"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-ace15fd60933668207dd4c09e6ab6fb05b3247a90b328bb3aaea5de677f02a45", "query": "Once we've built the JSON we want to output, I believe we can just use Pug like this for the button to initiate the file download:positive_passagesdociddoc-en-freeCodeCamp-de67d52633926756586f647f9a0a42ad269899031cdf9d819b25790dd28ec20ctextshowPoints, showPortfolio, showTimeLine, <del> updateMyProfileUI </del> <ins> updateMyProfileUI, user </ins> } = props; const toggleFlag = flag => () => updateMyProfileUI({ profileUI: { [flag]: !props[flag] } });commidfreeCodeCamp_pr_17252negative_passages |
| query_idq-en-freeCodeCamp-ace15fd60933668207dd4c09e6ab6fb05b3247a90b328bb3aaea5de677f02a45queryOnce we've built the JSON we want to output, I believe we can just use Pug like this for the button to initiate the file download:", "positive_passages": [{"docid": "doc-en-freeCodeCamp-64b7012bd8506020828304f29a2617be3d24a0fb9a4cff6e27fc9fc7e87f2895", "text": "<SectionHeader>Privacy Settings</SectionHeader> <FullWidthRow> <p> <del> The settings in this section enable you to control what is show on{' '} </del> <ins> The settings in this section enable you to control what is shown on{' '} </ins> your freeCodeCamp public portfolio. </p> <ins> <p>There is also a button to see what data we hold on your account</p> </ins> <ToggleSetting action='Make my profile completely private' explain={", "commid": "freeCodeCamp_pr_17252"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-ace15fd60933668207dd4c09e6ab6fb05b3247a90b328bb3aaea5de677f02a45", "query": "Once we've built the JSON we want to output, I believe we can just use Pug like this for the button to initiate the file download:positive_passagesdociddoc-en-freeCodeCamp-5e9a20965e9ca8ef262290f3f2627697617291f9d44223546020f8bd3d700722texttoggleFlag={ toggleFlag('showTimeLine') } /> </FullWidthRow> <ins> <FullWidthRow> <Spacer /> <Button block={true} bsSize='lg' bsStyle='primary' download={`${user.username}.json`} href={ `data:text/json;charset=utf-8,${ encodeURIComponent(JSON.stringify(user)) }` } > Download all your data </Button> </FullWidthRow> </ins> </div> ); }commidfreeCodeCamp_pr_17252negative_passages |
| query_idq-en-freeCodeCamp-3a4a3254065fd8d23357503d7ab6ca69428da36ebb43eb97153845865502deb5query<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --I didn't know where to put this, but in this exercise the example code on line 3 does not define the removedFromOurArray variable with the var keyword. This causes the test to fail if the user follows the exercise explicitly and only changes the code below the commented line. I imagine this would be frustrating to new users. Browser Name: Chrome Browser Version: Version 66.0.3359.181 (Official Build) (64-bit) Operating System: Windows 10 !\nWorking on it\nI think this would need to raised on the repo for learn: cc\nHi we may have created some confusion on where to create issues and PR Issues are welcome to opened on any repo you like learn or the main repo. We ( will take care of moving them around as needed. Just tag us (me, Stuart are actively checking these) when in doubt. But its fine to just report an not worry ! As for which repo to make a PR against: All of the challenge execution logic is now moved to the learn repo. That is to say, it has become our challenge platform. Its based on Gatsby, and is a simple static app.The challenge themselves (just the content, instructions, and the tests) are on the main repo. They are now published as a npm package. And used on learn as a dependency.The main repo, will just serve the welcome page, user settings and portfolio.\nThank you for the information. I am just a beginner student, so I\u2019m sure I\u2019ve done something stupid. I didn\u2019t know where to put this, but thought I\u2019d raise this as it confused me and I thought it would confuse others. Please move this to the correct place or delete if appropriate. Thank you.\nits perfectly alright. Thanks for reporting issues. Please keep it up (on any repo you prefer)", "positive_passages": [{"docid": "doc-en-freeCodeCamp-ad3067a4713dc44a5a35fe7a9f937bf3efb5e4de7dded4027d3ad37e470b7eec", "text": "\"contents\": [ \"// Example\", \"var ourArray = [\"Stimpson\", \"J\", [\"cat\"]];\", <del> \"removedFromOurArray = ourArray.shift();\", </del> <ins> \"var removedFromOurArray = ourArray.shift();\", </ins> \"// removedFromOurArray now equals \"Stimpson\" and ourArray now equals [\"J\", [\"cat\"]].\", \"\", \"// Setup\",", "commid": "freeCodeCamp_pr_17239"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-3a4a3254065fd8d23357503d7ab6ca69428da36ebb43eb97153845865502deb5", "query": "<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --I didn't know where to put this, but in this exercise the example code on line 3 does not define the removedFromOurArray variable with the var keyword. This causes the test to fail if the user follows the exercise explicitly and only changes the code below the commented line. I imagine this would be frustrating to new users. Browser Name: Chrome Browser Version: Version 66.0.3359.181 (Official Build) (64-bit) Operating System: Windows 10 !\nWorking on it\nI think this would need to raised on the repo for learn: cc\nHi we may have created some confusion on where to create issues and PR Issues are welcome to opened on any repo you like learn or the main repo. We ( will take care of moving them around as needed. Just tag us (me, Stuart are actively checking these) when in doubt. But its fine to just report an not worry ! As for which repo to make a PR against: All of the challenge execution logic is now moved to the learn repo. That is to say, it has become our challenge platform. Its based on Gatsby, and is a simple static app.The challenge themselves (just the content, instructions, and the tests) are on the main repo. They are now published as a npm package. And used on learn as a dependency.The main repo, will just serve the welcome page, user settings and portfolio.\nThank you for the information. I am just a beginner student, so I\u2019m sure I\u2019ve done something stupid. I didn\u2019t know where to put this, but thought I\u2019d raise this as it confused me and I thought it would confuse others. Please move this to the correct place or delete if appropriate. Thank you.\nits perfectly alright. Thanks for reporting issues. Please keep it up (on any repo you prefer)positive_passagesdociddoc-en-freeCodeCamp-3d349d81b0d23c2ef92ebc4d5c0e5f24c28859afd543470c5e5ee74fc43b2bb4text} } ] <del> } </del> No newline at end of file <ins> } </ins>commidfreeCodeCamp_pr_17239negative_passages |
| query_idq-en-freeCodeCamp-1945137840e61f58a5ea1103c01a779d1d177e9979443bb1462916e75c44ba00queryWhen viewing my Legacy Data Visualization Certificate, the Issued date in the top right corner always displays the current date, not the date the Certificate was completed. See: (appears to always have the current date there)\nI'll also add, although it may need a new thread or belong somewhere else, that the legacy certificates that were already earned should not be rebranded as \"legacy certificates\" because it devalues the work that went into getting them when they were not legacy. The date issued and the certificate should suffice. Universities don't send out new diplomas when they change their curriculum with new information saying your BS/MS/MA/MD degree is \.\nRebranding the certificates as \ could also cause problems for folks job hunting. Potential employers seeing a \ may conclude that the work accomplished is already out of date.\nI see seemingly correct dates for my legacy front-end and back-end certs, but the legacy data visualization is showing today's date. any thoughts on removing the \"legacy\" label - they do make a good point, although there would be two certs with the same name (data visualization) - which could be confusing or cause problems.\nI've been poking around the code a bit for this one. My guess is that in , line 427, completeDate is null, which would always give the current date for the ctor of the Date class when this happens. Which implies that somehow completeDate isn't getting set. I'm still working through lines 418-421 trying to guess what's going on there (my background is C / C++, so declaring const {} on the left hand side is throwing me for a loop).\nso the user object probly looks like this... obviously with a bunch of other properties in the user object as well I think pulls the completedChallenges array from the user object and sets it to the completedChallenges variable - and maybe gives and empty array as a default value if its not found - i think that's how it works this lesson and the ones following it might help...\nThanks . I also found this last night So completedChallenges is an array pulled from the user object using destructuring with a default assignment. completedDate is looking through the completedChallenges array (\) trying to match id with the certId. I'll guess completedChallenges is an array of objects, in which each object includes an id and completedDate field. This code is used for all certs, but only the Legacy Data Visualization has a problem here, so this code in and of itself is probably correct. Which implies that the data being fed into it is a problem, such that it can't find a completedDate for the Legacy Data Visualization cert only. So my thoughts are: Possible mismatch between id and certId. Did this id change inadvertently between the old site and the new site? Were completedDates saved for the old Data Visualization Certificate in the first place? I think the next step to debug this would be to just the values of id, certId, & completedChallenges[] on an instance with access to whatever backend storage FreeCodeCamp actually uses. Should be easy to find from that point on, since this is 100% reproducible. Unfortunately, I don't have that kind of access, so I don't think I'm going any farther with this bug. Hopefully this offers a jump start to whomever picks this bug up in the future.\nnice digging - I wonder if it's a naming conflict, it's the only legacy cert with the same name as a new one\nI cannot reproduce this on my local version - leads me to think that anyone who would claim the certification since the new site went live would not have this problem... I downloaded all my data from the settings page of the live site - I cannot find the string of the \"legacyDataVisId\" anywhere in my downloaded data (the string is from ). I can find the strings of all the other certs I have claimed - So the id got changed somewhere along the lines I'm guessing - the downloaded data is hard to decipher, but it looks like there may have been two sections for data vis that got created when you claimed the cert on the old site... I cut some code out but these are surrounded by projects required for the certpositive_passagesdociddoc-en-freeCodeCamp-57e9b0d81f3ce7c2dbd049e28318970fa19e2107a2672d7ef6d3dd0311d0806ftextif (user[certType]) { const { completedChallenges = [] } = user; <del> const { completedDate = new Date() } = _.find(completedChallenges, ({ id }) => certId === id) || {}; </del> <ins> const certChallenge = _.find( completedChallenges, ({ id }) => certId === id ); let { completedDate = new Date() } = certChallenge || {}; // the challange id has been rotated for isDataVisCert // so we need to check for id 561add10cb82ac38a17513b3 if (certType === 'isDataVisCert' && !certChallenge) { console.log('olderId'); let oldDataVisIdChall = _.find( completedChallenges, ({ id }) => '561add10cb82ac38a17513b3' === id ); if (oldDataVisIdChall) { completedDate = oldDataVisIdChall.completedDate || completedDate; } } </ins> const { username, name } = user; return res.json({commidfreeCodeCamp_pr_35728negative_passages |
| query_idq-en-freeCodeCamp-06a38f5d8a502f52b90138f7f34998c5882602c9d6b56b982fd597fc905ce9d1query<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --The test requires a multi-line comment of the form . However, the test fails if additional ` characters are present at the beginning or the end of the text contained within the comment. Some examples : The regular expression for the corresponding test needs to be updated. Browser Name: Google Chrome Browser Version: 60+ Operating System: Ubuntu 18.04 !\nHi, I would like to have a go to fix this problem\nThat's good, please read .\nTest fails if multiline style comment includes either / File: Line: 33 this regex is the problem", "positive_passages": [{"docid": "doc-en-freeCodeCamp-c6919301c55a22f2ac6b11f85218c80601acdef2632934106f5b479135f87fb8", "text": "} pairedWith = pairedWith.pop(); <del> //debug('This is paired with', Object.keys(pairedWith)); debug('This is paired with's uncompleted bonfires array', pairedWith.uncompletedBonfires); </del> index = pairedWith.uncompletedBonfires.indexOf(bonfireHash); if (index > -1) { pairedWith.uncompletedBonfires.splice(index,1)commidfreeCodeCamp_pr_52negative_passages |
| query_idq-en-freeCodeCamp-06a38f5d8a502f52b90138f7f34998c5882602c9d6b56b982fd597fc905ce9d1query<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --The test requires a multi-line comment of the form . However, the test fails if additional ` characters are present at the beginning or the end of the text contained within the comment. Some examples : The regular expression for the corresponding test needs to be updated. Browser Name: Google Chrome Browser Version: 60+ Operating System: Ubuntu 18.04 !\nHi, I would like to have a go to fix this problem\nThat's good, please read .\nTest fails if multiline style comment includes either / File: Line: 33 this regex is the problem", "positive_passages": [{"docid": "doc-en-freeCodeCamp-7b26248dd1198e946204c817fa907173486717eeb6950e10b3ec9cf683216438", "text": "}; exports.returnNextBonfire = function(req, res, next) { <del> // TODO //var tempUser = false; </del> if (!req.user) { <del> res.redirect('bonfires/meet-bonfire'); //tempUser = true; //req.user = new User(); </del> <ins> return res.redirect('bonfires/meet-bonfire'); </ins> } <del> var currentTime = parseInt(+new Date() / 1000) </del> <ins> var currentTime = parseInt(+new Date() / 1000); </ins> if (currentTime - req.user.lastContentSync > 86400) { req.user.lastContentSync = currentTime; <del> var completed = req.user.completedBonfires.map(function(elem) { </del> <ins> var completed = req.user.completedBonfires.map(function (elem) { </ins> return elem._id; }); <del> req.user.uncompletedBonfires = resources.allBonfireIds().filter(function(elem) { if (completed.indexOf(elem) === -1) { return elem; } </del> <ins> req.user.uncompletedBonfires = resources.allBonfireIds().filter(function (elem) { if (completed.indexOf(elem) === -1) { return elem; } </ins> }); req.user.save(); }", "commid": "freeCodeCamp_pr_52"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-06a38f5d8a502f52b90138f7f34998c5882602c9d6b56b982fd597fc905ce9d1", "query": "<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --The test requires a multi-line comment of the form . However, the test fails if additional ` characters are present at the beginning or the end of the text contained within the comment. Some examples : The regular expression for the corresponding test needs to be updated. Browser Name: Google Chrome Browser Version: 60+ Operating System: Ubuntu 18.04 !\nHi, I would like to have a go to fix this problem\nThat's good, please read .\nTest fails if multiline style comment includes either / File: Line: 33 this regex is the problempositive_passagesdociddoc-en-freeCodeCamp-920d206ec3793065050994c0d9022ccf42194b104bea904e073e9e0ef33cc0a2textcompletedWith: null, title: bonfire[bonfireNumber].name, name: bonfire[bonfireNumber].name, <del> difficulty: +bonfire[bonfireNumber].difficulty, </del> <ins> difficulty: Math.floor(+bonfire[bonfireNumber].difficulty), </ins> brief: bonfire[bonfireNumber].description[0], details: bonfire[bonfireNumber].description.slice(1), tests: bonfire[bonfireNumber].tests,commidfreeCodeCamp_pr_52negative_passages |
| query_idq-en-freeCodeCamp-06a38f5d8a502f52b90138f7f34998c5882602c9d6b56b982fd597fc905ce9d1query<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --The test requires a multi-line comment of the form . However, the test fails if additional ` characters are present at the beginning or the end of the text contained within the comment. Some examples : The regular expression for the corresponding test needs to be updated. Browser Name: Google Chrome Browser Version: 60+ Operating System: Ubuntu 18.04 !\nHi, I would like to have a go to fix this problem\nThat's good, please read .\nTest fails if multiline style comment includes either / File: Line: 33 this regex is the problem", "positive_passages": [{"docid": "doc-en-freeCodeCamp-ad4945d6d68cae6f023eca8d9727ccfa670235109b6a902706dfdffbf64e32c5", "text": "res.render('bonfire/show', { completedWith: null, title: bonfireName, <ins> name: bonfireName, </ins> difficulty: +bonfireDifficulty, brief: bonfireDescription[0], details: bonfireDescription.slice(1),", "commid": "freeCodeCamp_pr_52"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-06a38f5d8a502f52b90138f7f34998c5882602c9d6b56b982fd597fc905ce9d1", "query": "<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --The test requires a multi-line comment of the form . However, the test fails if additional ` characters are present at the beginning or the end of the text contained within the comment. Some examples : The regular expression for the corresponding test needs to be updated. Browser Name: Google Chrome Browser Version: 60+ Operating System: Ubuntu 18.04 !\nHi, I would like to have a go to fix this problem\nThat's good, please read .\nTest fails if multiline style comment includes either / File: Line: 33 this regex is the problempositive_passagesdociddoc-en-freeCodeCamp-885197a4a599a92b0f1b1be7974d89a22add22779d5aef65fc52ac154cff0c7etext\: \You can do this!\ }, { <ins> \: \, \: \, \: \, \: [ \, \, \, \ ], \: [ \, \, \ ], \: \, \: \ }, { \: \, \: \, \: [ \Number\, \, \, \ ], \: \, \: [ \, \, \, \ ], \: \, \: \ }, { </ins> \ : \, \: \, <del> \: \, </del> <ins> \: \, </ins> \: [ \, \,commidfreeCodeCamp_pr_52negative_passages |
| query_idq-en-freeCodeCamp-06a38f5d8a502f52b90138f7f34998c5882602c9d6b56b982fd597fc905ce9d1query<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --The test requires a multi-line comment of the form . However, the test fails if additional ` characters are present at the beginning or the end of the text contained within the comment. Some examples : The regular expression for the corresponding test needs to be updated. Browser Name: Google Chrome Browser Version: 60+ Operating System: Ubuntu 18.04 !\nHi, I would like to have a go to fix this problem\nThat's good, please read .\nTest fails if multiline style comment includes either / File: Line: 33 this regex is the problem", "positive_passages": [{"docid": "doc-en-freeCodeCamp-e0ff432154bc9a8a52669d5d2733f3c41686c27d3b7c1c5d7e29631ad8672c06", "text": "\"challengeEntryPoint\": \"palindrome(\"eye\");\" }, { <ins> \"_id\": \"a26cbbe9ad8655a977e1ceb5\", \"name\": \"Find the Longest Word in a String\", \"difficulty\": \"1.04\", \"description\": [ \"Return the length of the longest word in the provided sentence.\", \"Your response should be a number.\" ], \"challengeEntryPoint\": \"findLongestWord('The quick brown fox jumped over the lazy dog');\", \"challengeSeed\": \"function findLongestWord(str) {n return str.length;rn}\", \"tests\": [ \"expect(findLongestWord('The quick brown fox jumped over the lazy dog')).to.be.a('Number');\", \"expect(findLongestWord('The quick brown fox jumped over the lazy dog')).to.equal(6);\", \"expect(findLongestWord('May the force be with you')).to.equal(5);\", \"expect(findLongestWord('Google do a barrel roll')).to.equal(6);\", \"expect(findLongestWord('What is the average airspeed velocity of an unladen swallow')).to.equal(8);\" ] }, { \"_id\": \"ab6137d4e35944e21037b769\", \"name\": \"Title Case a Sentence\", \"difficulty\": \"1.05\", \"description\": [ \"Return the provided string with the first letter of each word capitalized.\", \"For the purpose of this exercise, you should also capitalize connecting words like 'the' and 'of'.\" ], \"challengeEntryPoint\": \"titleCase(\"I'm a little tea pot\, \: \, \: [ \I'm a little tea pot\")).to.be.a('String');\", \"expect(titleCase(\"I'm a little tea pot\I'm A Little Tea Pot\");\", \"expect(titleCase(\"sHoRt AnD sToUt\")).to.equal(\"Short And Stout\");\", \"expect(titleCase(\"HERE IS MY HANDLE HERE IS MY SPOUT\")).to.equal(\"Here Is My Handle Here Is My Spout\");\" ] }, { \"_id\": \"a789b3483989747d63b0e427\", \"name\": \"Return Largest Numbers in Arrays\", \"difficulty\": \"1.06\", \"description\": [ \"Return an array consisting of the largest numbers in the provided array. The array will contain 4 sub-arrays.\", \"Remember, you an iterate through an array with a simple for loop, and access each member with array syntax arr[i] .\", \"If you are writing your own Chai.js tests, be sure to use a deep equal statement instead of an equal statement when comparing arrays.\" ], \"challengeEntryPoint\": \"largestOfFour([[4, 5, 1, 3], [13, 27, 18, 26], [32, 35, 37, 39], [1000, 1001, 857, 1]]);\", \"challengeSeed\": \"function largestOfFour(arr) {n // You can do this!rn return arr;rn}\", \"tests\": [ \"expect(largestOfFour([[4, 5, 1, 3], [13, 27, 18, 26], [32, 35, 37, 39], [1000, 1001, 857, 1]])).to.be.a('array');\", \"(largestOfFour([[4, 5, 1, 3], [13, 27, 18, 26], [32, 35, 37, 39], [1000, 1001, 857, 1]])).should.equals([5,27,39,1001]);\", \"assert(largestOfFour([[4, 9, 1, 3], [13, 35, 18, 26], [32, 35, 97, 39], [1000000, 1001, 857, 1]]) === [9,35,97,1000000]);\" ] }, { \"_id\": \"a3566b1109230028080c9345\", \"name\": \"Sum All Numbers in a Range\", \"difficulty\": \"2.00\", \"description\": [ \"We'll pass you an array of two numbers. Return the sum those two numbers and all numbers between them.\The lowest number will not always come first.\challengeEntryPoint\sumAll([1, 4]);\challengeSeed\function sumAll(arr) {n return(1);rn}\tests\expect(sumAll([1, 4])).to.be.a('Number');\expect(sumAll([1, 4])).to.equal(10);\expect(sumAll([4, 1])).to.equal(10);\expect(sumAll([5, 10])).to.equal(45);\expect(sumAll([10, 5])).to.equal(45);\_id\a5229172f011153519423690\name\Sum All Odd Fibonacci Numbers\difficulty\2.01\description\Return the sum of all odd fibonacci numbers up to and including the passed number.\Starting from 1, the first few numbers of a Fibonacci sequence are 1, 2, 3, 5 and 8, and each subsequent number is the sum of the previous two numbers.\challengeEntryPoint\sumFibs(1000);\challengeSeed\function sumFibs(num) {n return num;rn}\tests\expect(sumFibs(1)).to.be.a('number');\expect(sumFibs(1000)).to.equal(3382);\expect(sumFibs(4000000)).to.equal(10316619);\expect(sumFibs(4)).to.equal(10);\_id\a3bfc1673c0526e06d3ac698\name\Sum All Primes\difficulty\2.10\description\Sum all the prime numbers up to and including the provided number.\A prime number is defined as having only two divisors, 1 and itself. For example, 2 is a prime number because it's only divisible by 1 and 2. 1 isn't a prime number, because it's only divisible by itself.\", \"The provided number may not be a prime.\" ], \"challengeEntryPoint\": \"sumPrimes(10);\", \"challengeSeed\": \"function sumPrimes(num) {n return num;rn}\", \"tests\": [ \"expect(sumPrimes(10)).to.be.a('number');\", \"expect(sumPrimes(10)).to.equal(27);\", \"expect(sumPrimes(977)).to.equal(73156);\" ] }, { \"_id\": \"ae9defd7acaf69703ab432ea\", \"name\": \"Smallest Common Multiple\", \"difficulty\": \"2.11\", \"description\": [ \"Find the smallest number that evenly divides all numbers in the provided range.\", \"The range will be an array of two numbers that will not necessarily be in numerical order.\" ], \"challengeEntryPoint\": \"smallestCommons([1,5]);\", \"challengeSeed\": \"function smallestCommons(arr) {n return arr;rn}rn\", \"tests\": [ \"expect(smallestCommons([1,5])).to.be.a('number');\", \"expect(smallestCommons([1,5])).to.equal(60);\", \"expect(smallestCommons([5,1])).to.equal(60);\", \"(smallestCommons([1,13])).should.equal(360360);\" ] }, { </ins> \"_id\" : \"aff0395860f5d3034dc0bfc9\", \"name\": \"Validate US Telephone Numbers\", <del> \"difficulty\": \"3\", </del> <ins> \"difficulty\": \"3.10\", </ins> \"description\": [ \"Return true if the passed string is a valid US phone number\", \"The user may fill out the form field any way they choose as long as it is a valid US number. The following are all valid formats for US numbers:\",", "commid": "freeCodeCamp_pr_52"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-06a38f5d8a502f52b90138f7f34998c5882602c9d6b56b982fd597fc905ce9d1", "query": "<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --The test requires a multi-line comment of the form . However, the test fails if additional ` characters are present at the beginning or the end of the text contained within the comment. Some examples : The regular expression for the corresponding test needs to be updated. Browser Name: Google Chrome Browser Version: 60+ Operating System: Ubuntu 18.04 !\nHi, I would like to have a go to fix this problem\nThat's good, please read .\nTest fails if multiline style comment includes either / File: Line: 33 this regex is the problempositive_passagesdociddoc-en-freeCodeCamp-ae3072ccaa80178b68afc6c13423cf513897f565d61909c41c0f3f8904177dc0text\: \555-555-5555\ }, { <del> \: \, \: \, \: \, \: [ \, \, \, \ ], </del> <ins> \: \, \: \, \: \, </ins> \: [ <del> \, \, \ </del> <ins> \ </ins> ], <del> \: \, \: \ }, { \: \, \: \, </del> <ins> \: \, \: \, </ins> \: [ <del> \Number\, \, \, \ ], \: \, \: [ \, \, \, \ ], \: \, \: \ }, { \: \, \: \, \: \, \: [ \, \ ], \: \, \: \, \: [ \, \, \, \, \ ] }, { \: \, \: \, \: \, \: [ \, \ ], \: \, \: \, \: [ \, \, \, \, \ ] }, { \: \, \: \, \: \, \: [ \, \ ], \: \I'm a little tea pot\")\", \"challengeSeed\": \"function titleCase(str) {n return str;rn}\", \"tests\": [ \"expect(titleCase(\"I'm a little tea pot\, \I'm a little tea pot\")).to.equal(\"I'm A Little Tea Pot\, \sHoRt AnD sToUt\Short And Stout\, \HERE IS MY HANDLE HERE IS MY SPOUT\Here Is My Handle Here Is My Spout\ </del> <ins> \, \, \, \, \, \ </ins> ] } ]commidfreeCodeCamp_pr_52negative_passages |
| query_idq-en-freeCodeCamp-06a38f5d8a502f52b90138f7f34998c5882602c9d6b56b982fd597fc905ce9d1query<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --The test requires a multi-line comment of the form . However, the test fails if additional ` characters are present at the beginning or the end of the text contained within the comment. Some examples : The regular expression for the corresponding test needs to be updated. Browser Name: Google Chrome Browser Version: 60+ Operating System: Ubuntu 18.04 !\nHi, I would like to have a go to fix this problem\nThat's good, please read .\nTest fails if multiline style comment includes either / File: Line: 33 this regex is the problem", "positive_passages": [{"docid": "doc-en-freeCodeCamp-209cd44829d3cfae62952ad5ec6ea7bb1b09ea1d7cc8d1847885f8d44f9001d8", "text": ".form-group label.col-sm-2.control-label.wrappable(for='description') description: .col-sm-10 <del> textarea#description.form-control(name=\"description\", placeholder=\"Separate sentences by exactly one space only. Do not add in line breaks.\") </del> <ins> textarea#description.form-control(name=\"description\", rows=5, placeholder=\"Separate sentences by exactly one space only. Do not add in line breaks.\") </ins> .form-group label.col-sm-2.control-label.wrappable(for='challengeSeed') challengeSeed: .col-sm-10", "commid": "freeCodeCamp_pr_52"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-45e73593e6e4bb35574ddd060e5e0bf451b355aabd7e4740f7c40182a647d4a8", "query": "This is a response to a user of the forum having issues with the Stand in Line challenge. To quote: This is dead simple, there here are code tags around the word in the description, and we've taught users that code tags, naturally refer to code. Browser Name: any Browser Version: any Operating System: any !positive_passagesdociddoc-en-freeCodeCamp-69c2dbf179a1f99bb11b443fd6260cad7423ebc7a4bb40f4fbe89d1f5adf7625text## Description <section id='description'> <del> In Computer Science a <dfn>queue</dfn> is an abstract <dfn>Data Structure</dfn> where items are kept in order. New items can be added at the back of the <code>queue</code> and old items are taken off from the front of the <code>queue</code>. </del> <ins> In Computer Science a <dfn>queue</dfn> is an abstract <dfn>Data Structure</dfn> where items are kept in order. New items can be added at the back of the queue and old items are taken off from the front of the queue. </ins> Write a function <code>nextInLine</code> which takes an array (<code>arr</code>) and a number (<code>item</code>) as arguments. Add the number to the end of the array, then remove the first element of the array. The <code>nextInLine</code> function should then return the element that was removed.commidfreeCodeCamp_pr_35393negative_passages |
| query_idq-en-freeCodeCamp-3e49644400f1a38b54d33e39cb589c60416fc6835be301d2dfe6e22d59b38b5bqueryThe Optional bonus User Story was removed from the testable suite because it is no longer relevant. The User Story should also be removed from the web page.\nFixed inpositive_passagesdociddoc-en-freeCodeCamp-8debe593129d8d102410e566082249b58f6918baac69ded84fe793118e904b96text<strong>User Story #4:</strong> When I enter GitHub flavored markdown into the <code>#editor</code> element, the text is rendered as HTML in the <code>#preview</code> element as I type (HINT: You don't need to parse Markdown yourself - you can import the Marked library for this: <a href='https://cdnjs.com/libraries/marked' target='_blank'>https://cdnjs.com/libraries/marked</a>). <strong>User Story #5:</strong> When my markdown previewer first loads, the default text in the <code>#editor</code> field should contain valid markdown that represents at least one of each of the following elements: a header (H1 size), a sub header (H2 size), a link, inline code, a code block, a list item, a blockquote, an image, and bolded text. <strong>User Story #6:</strong> When my markdown previewer first loads, the default markdown in the <code>#editor</code> field should be rendered as HTML in the <code>#preview</code> element. <del> <strong>Optional Bonus (you do not need to make this test pass):</strong> When I click a link rendered by my markdown previewer, the link is opened up in a new tab (HINT: read the Marked.js docs for this one!). </del> <strong>Optional Bonus (you do not need to make this test pass):</strong> My markdown previewer interprets carriage returns and renders them as <code>br</code> (line break) elements. You can build your project by forking <a href='http://codepen.io/freeCodeCamp/pen/MJjpwO' target='_blank'>this CodePen pen</a>. Or you can use this CDN link to run the tests in any environment you like: <code>https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js</code> Once you're done, submit the URL to your working project with all its tests passing.commidfreeCodeCamp_pr_18290negative_passages |
| query_idq-en-freeCodeCamp-a645685b48e5309fb800426194b42c5c4929980c90836e094ae098c4cf916ddequeryDescribe the bug PR builds for freeCodeCamp / freeCodeCamp are failing in Travis CI with the following: To Reproduce a minor PR change build in Travis CI (ie: https://travis-) Expected behavior PR should pass all the builds to allow QAs to merge PRs to repo. Screenshots ! Additional context ref:jsdom/jsdom\nCorrect me if I'm wrong but '' is asking for: If this file was missing would that not trip something?\nDid you mean this file: ? I believe all this is unused completely. And some of the files around that as well. If you are investigating, I recommend you look The challenge-markdown-parser is something worth looking at as well. It's in the tools.positive_passagesdociddoc-en-freeCodeCamp-5e319515b5e237da32789e4bed9ab54cfe9c4e78d26a0ed6e616e270f64aa34ctext</html> `, { runScripts: 'dangerously', <del> virtualConsole </del> <ins> virtualConsole, url: 'http://localhost' </ins> }); const { window } = dom;commidfreeCodeCamp_pr_32933negative_passages |
| query_idq-en-freeCodeCamp-82c810b4500ee0bbdf69e03a27492ccf234d8aa3100d01a16255b9b7731acbd0query<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: I commented out the code and then followed the new syntax for the challenge, but because the commented out code had normal function declaration it didn't pass. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Google Chrome Operating System: Mac OS High Sierra If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): // change code below this line const bicycle = { gear: 2, setGear(newGear) { \"use strict\" = newGear } } / const bicycle = { gear: 2, setGear: function(newGear) { \"use strict\"; = newGear; } }; // change code above this line bicycle.setGear(3); (); /\nHi, We used regex to match \"function\" keyword in the code but this instance can be fixed. I'll take a stab at it.\nI think this issue occurs with a lot of the challenges. For an example, and Can a statement just be left in the description saying to not use the keyword even as a comment?\nA better way is how we solved other such problems. We stripped all the comments out with a regular expression and then validated the user did not use what they were not supposed to. I just created PR to fixed this issue,positive_passagesdociddoc-en-freeCodeCamp-c459bd8b6c9b33bd444380b33f01600bb12e4d78e68bc9e129786cbd47b29cf2text```yml tests: - text: Traditional function expression should not be used. <del> testString: getUserInput => assert(!getUserInput('index').match(/function/)); </del> <ins> testString: getUserInput => assert(!removeJSComments(code).match(/function/)); </ins> - text: <code>setGear</code> should be a declarative function. <del> testString: getUserInput => assert(typeof bicycle.setGear === 'function' && getUserInput('index').match(/setGears*(.+)s*{/)); </del> <ins> testString: assert(typeof bicycle.setGear === 'function' && code.match(/setGears*(.+)s*{/)); </ins> - text: <code>bicycle.setGear(48)</code> should change the <code>gear</code> value to 48. testString: assert((new bicycle.setGear(48)).gear === 48);commidfreeCodeCamp_pr_35906negative_passages |
| query_idq-en-freeCodeCamp-82c810b4500ee0bbdf69e03a27492ccf234d8aa3100d01a16255b9b7731acbd0query<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: I commented out the code and then followed the new syntax for the challenge, but because the commented out code had normal function declaration it didn't pass. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Google Chrome Operating System: Mac OS High Sierra If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): // change code below this line const bicycle = { gear: 2, setGear(newGear) { \"use strict\" = newGear } } / const bicycle = { gear: 2, setGear: function(newGear) { \"use strict\"; = newGear; } }; // change code above this line bicycle.setGear(3); (); /\nHi, We used regex to match \"function\" keyword in the code but this instance can be fixed. I'll take a stab at it.\nI think this issue occurs with a lot of the challenges. For an example, and Can a statement just be left in the description saying to not use the keyword even as a comment?\nA better way is how we solved other such problems. We stripped all the comments out with a regular expression and then validated the user did not use what they were not supposed to. I just created PR to fixed this issue,positive_passagesdociddoc-en-freeCodeCamp-ecf821fc66b4489278b25ac24b5709cd332b504da29fab32f804a28521987b19text</div> <ins> ### After Test <div id='js-teardown'> ```js const removeJSComments = str => str.replace(//*[sS]*?*/|//.*$/gm, ''); ``` </div> </ins> </section> ## SolutioncommidfreeCodeCamp_pr_35906negative_passages |
| query_idq-en-freeCodeCamp-b0a89ea85ce5c1f9c5c88d50188036b01ae48772c6c0f28c162e134ce0a78ee1queryI created a solution for this exercise, and it failed. When I looked at the hint solution, my code was basically the same. When I plug the hint solution into the code and run the test, it fails, also. The output window displays 'rating is not defined' four times. When I copy everything to JS Fiddle and run the code, it works as expected.\nDid you ask this question on the forum and present the code you tried? That is the best place to ask. If you present your code to others on the forum and they conclude it is valid code which should pass the tests, then open an issue and present your code here also.\nThe problem is just that 'rating' has not been declared. The challenge code seems to be fine, but the guide should perhaps be a little stricter.positive_passagesdociddoc-en-freeCodeCamp-e4495ec20d4bce0625b5edfd3f6a66f3a42a5cd9b5ad4f77cc409d247a04e382text##  Intermediate Code Solution: ```javascript <del> rating = watchList.map( (item) => ({\:item[\], \:item[\]}) ); </del> <ins> const rating = watchList.map(item => ({title: item[\], rating: item[\]})); </ins> ``` ### Code Explanation: Using ES6 notation, each item in array is processed to extract title and rating.commidfreeCodeCamp_pr_34702negative_passages |
| query_idq-en-freeCodeCamp-ec5281fd9be05ac2c818b66647f2012c23ec1dee23e62dd1c8c2dd73e05cf9c0queryThe video for the lecture does not exist.\nTwo videos from that section are missing: \ and \. It seems both videos are down on the Scrimba platform. In the , both videos seem to be missing. If this video has been uploaded elsewhere, we can replace the URL for now. Otherwise, those two videos may need to be re-uploaded. Side note: The playlists are also incorrectly named. It seems that the Applied Accessibility and Applied Visual Design titles have accidentally been switched.positive_passagesdociddoc-en-freeCodeCamp-6ede35176b133bed5548bc2c54e5ba82c0fe01faad083ac5ab39f33c6f7eda33textid: 587d778b367417b2b2512aa8 title: Add an Accessible Date Picker challengeType: 0 <del> videoUrl: 'https://scrimba.com/c/cD9DJHr' </del> <ins> videoUrl: 'https://scrimba.com/c/cR3bRbCV' </ins> --- ## DescriptioncommidfreeCodeCamp_pr_35803negative_passages |
| query_idq-en-freeCodeCamp-ec5281fd9be05ac2c818b66647f2012c23ec1dee23e62dd1c8c2dd73e05cf9c0queryThe video for the lecture does not exist.\nTwo videos from that section are missing: \ and \. It seems both videos are down on the Scrimba platform. In the , both videos seem to be missing. If this video has been uploaded elsewhere, we can replace the URL for now. Otherwise, those two videos may need to be re-uploaded. Side note: The playlists are also incorrectly named. It seems that the Applied Accessibility and Applied Visual Design titles have accidentally been switched.positive_passagesdociddoc-en-freeCodeCamp-cff4b3531ea755cde5d7edd336795ed4235e9213ffa170cd165544641c22d97ctextid: 587d778d367417b2b2512aaa title: Make Elements Only Visible to a Screen Reader by Using Custom CSS challengeType: 0 <del> videoUrl: 'https://scrimba.com/c/c8azdfM' </del> <ins> videoUrl: 'https://scrimba.com/c/cJ8QGkhJ' </ins> --- ## DescriptioncommidfreeCodeCamp_pr_35803negative_passages |
| query_idq-en-freeCodeCamp-4ef68b7872a6418004b20f92f7629078a450b2fdecfc229c19da06d381b11a7equeryRelated to . Once that's done, the code blocks will be written in blocks of into ! while the same code on the guide looks like ! I think this change would make the code blocks easier to read, make the guide and challenges feel more like parts of a unified whole and fit better with the code editor aesthetic discussed in the . I'd be happy to work on this, if this is useful feature What do you think?\nYou should look into for this sort of thing. Goodluck. this is something we would probably be needing and using across Guide and Learn. So, I'll let you chime in and guide on this.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-ea6c1ef79edae71498aa3a7a3173126d12499973580ec22131d66c4dbe79a1fb", "text": "import DonateModal from '../Donation'; import 'prismjs/themes/prism.css'; <ins> import './prism.css'; import './prism-night.css'; </ins> import 'react-reflex/styles.css'; import './learn.css';", "commid": "freeCodeCamp_pr_36077"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-4ef68b7872a6418004b20f92f7629078a450b2fdecfc229c19da06d381b11a7e", "query": "Related to . Once that's done, the code blocks will be written in blocks of into ! while the same code on the guide looks like ! I think this change would make the code blocks easier to read, make the guide and challenges feel more like parts of a unified whole and fit better with the code editor aesthetic discussed in the . I'd be happy to work on this, if this is useful feature What do you think?\nYou should look into for this sort of thing. Goodluck. this is something we would probably be needing and using across Guide and Learn. So, I'll let you chime in and guide on this.positive_passagesdociddoc-en-freeCodeCamp-4e56bb6832d49069e15e5909a2fde69cdb8d140db7f58d157fb7660dee521b99text<ins> /** * Adapted from: * prism.js tomorrow night eighties for JavaScript, CoffeeScript, CSS and HTML * Based on https://github.com/chriskempson/tomorrow-theme * @author Rose Pritchard */ .night code[class*='language-'], .night pre[class*='language-'] { color: #ccc; font-family: Consolas, Monaco, 'Andale Mono', 'Ubuntu Mono', monospace; font-size: 1em; text-align: left; white-space: pre; word-spacing: normal; word-break: normal; word-wrap: normal; line-height: 1.5; -moz-tab-size: 4; -o-tab-size: 4; tab-size: 4; -webkit-hyphens: none; -moz-hyphens: none; -ms-hyphens: none; hyphens: none; text-shadow: none; } .night pre[class*='language-'] code[class*='language-'] { color: #d4d4d4; } /* Code blocks */ .night pre[class*='language-'] { padding: 1em; margin: 0.5em 0; overflow: auto; } .night :not(pre) > code[class*='language-'], .night pre[class*='language-'] { background: #242424; } /* Inline code */ .night :not(pre) > code[class*='language-'] { padding: 0.1em; border-radius: 0.3em; white-space: normal; } .night .token.comment, .night .token.block-comment, .night .token.prolog, .night .token.doctype, .night .token.cdata { color: #608b4e; } .night .token.punctuation { color: #ffff00; } .night .token.tag, .night .token.attr-name, .night .token.namespace, .night .token.deleted { color: #e2777a; } .night .token.function-name { color: #d4d4d4; } .night .token.boolean, .night .token.number, .night .token.function { color: #569cd6; } .night .token.property, .night .token.class-name, .night .token.constant, .night .token.symbol { color: #f8c555; } .night .token.selector, .night .token.important, .night .token.atrule, .night .token.keyword, .night .token.builtin { color: #569cd6; } .night .token.string, .night .token.char, .night .token.attr-value, .night .token.regex, .night .token.variable { color: #7ec699; } .night .token.operator, .night .token.entity, .night .token.url { color: #67cdcc; background: none; } .night .token.important, .night .token.bold { font-weight: bold; } .night .token.italic { font-style: italic; } .night .token.entity { cursor: help; } .night .token.inserted { color: green; } </ins>commidfreeCodeCamp_pr_36077negative_passages |
| query_idq-en-freeCodeCamp-4ef68b7872a6418004b20f92f7629078a450b2fdecfc229c19da06d381b11a7equeryRelated to . Once that's done, the code blocks will be written in blocks of into ! while the same code on the guide looks like ! I think this change would make the code blocks easier to read, make the guide and challenges feel more like parts of a unified whole and fit better with the code editor aesthetic discussed in the . I'd be happy to work on this, if this is useful feature What do you think?\nYou should look into for this sort of thing. Goodluck. this is something we would probably be needing and using across Guide and Learn. So, I'll let you chime in and guide on this.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-af1a927d1cb777360644472e238a0b9e13cee901b7fe92db853834b4b819eca4", "text": "<del> import React, { Fragment } from 'react'; </del> <ins> import React, { Fragment, Component } from 'react'; import Prism from 'prismjs'; </ins> import PropTypes from 'prop-types'; import './challenge-description.css';", "commid": "freeCodeCamp_pr_36077"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-4ef68b7872a6418004b20f92f7629078a450b2fdecfc229c19da06d381b11a7e", "query": "Related to . Once that's done, the code blocks will be written in blocks of into ! while the same code on the guide looks like ! I think this change would make the code blocks easier to read, make the guide and challenges feel more like parts of a unified whole and fit better with the code editor aesthetic discussed in the . I'd be happy to work on this, if this is useful feature What do you think?\nYou should look into for this sort of thing. Goodluck. this is something we would probably be needing and using across Guide and Learn. So, I'll let you chime in and guide on this.positive_passagesdociddoc-en-freeCodeCamp-0b8f3fc43f3286edd2ecdd6cacc386996971a3af6d9e93e2e26c17a42e96b134textsection: PropTypes.string }; <del> function ChallengeDescription({ description, instructions, section }) { return ( <div className={`challenge-instructions ${section}`}> <div dangerouslySetInnerHTML={{ __html: description }} /> {instructions && ( <Fragment> <hr /> <div dangerouslySetInnerHTML={{ __html: instructions }} /> </Fragment> )} <hr /> </div> ); </del> <ins> class ChallengeDescription extends Component { componentDidMount() { // Just in case 'current' has not been created, though it should have been. if (this.instructionsRef.current) { Prism.highlightAllUnder(this.instructionsRef.current); } } constructor(props) { super(props); this.instructionsRef = React.createRef(); } render() { const { description, instructions, section } = this.props; return ( <div className={`challenge-instructions ${section}`} ref={this.instructionsRef} > <div dangerouslySetInnerHTML={{ __html: description }} /> {instructions && ( <Fragment> <hr /> <div dangerouslySetInnerHTML={{ __html: instructions }} /> </Fragment> )} <hr /> </div> ); } </ins> } ChallengeDescription.displayName = 'ChallengeDescription';commidfreeCodeCamp_pr_36077negative_passages |
| query_idq-en-freeCodeCamp-72bb2682bd59e62633dd06b6811b4042dd43408796e6690030c5f58a63cd1459query<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: Challenge is missing a period in its description. ! Add a Link to the page with the problem: Here is the file that needs to be edited:\nBtw, I think there is a typo in the description as well: should be\nLooks like those could both changed.positive_passagesdociddoc-en-freeCodeCamp-83871e88d50541743c0cafe6ca44f791e342ffca0501a6217680e927b0286584text## Description <section id='description'> <del> To create a CSS Variable, you just need to give it a <code>name</code> with <code>two dashes</code> in front of it and assign it a <code>value</code> like this: </del> <ins> To create a CSS variable, you just need to give it a <code>name</code> with <code>two dashes</code> in front of it and assign it a <code>value</code> like this: </ins> ```css --penguin-skin: gray;commidfreeCodeCamp_pr_36041negative_passages |
| query_idq-en-freeCodeCamp-72bb2682bd59e62633dd06b6811b4042dd43408796e6690030c5f58a63cd1459query<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: Challenge is missing a period in its description. ! Add a Link to the page with the problem: Here is the file that needs to be edited:\nBtw, I think there is a typo in the description as well: should be\nLooks like those could both changed.positive_passagesdociddoc-en-freeCodeCamp-24578eceb7ec6bf18b1b975a44a02c75ab5879f66a4ae804a5ed4035e14457fatext## Instructions <section id='instructions'> <del> In the <code>penguin</code> class, create a variable name <code>--penguin-skin</code> and give it a value of <code>gray</code> </del> <ins> In the <code>penguin</code> class, create a variable name <code>--penguin-skin</code> and give it a value of <code>gray</code>. </ins> </section> ## TestscommidfreeCodeCamp_pr_36041negative_passages |
| query_idq-en-freeCodeCamp-e7fbcb23b866c25a5eeff5c091cd500b8b9b53f1c5deafea6ec8e1c2bee0228dqueryDescribe your problem and how to reproduce it: First Issue: The Basic solution uses call() function but doesn't include any reference to it. Second Issue: The Basic solution doesn't work when you use it as a solution for the challenge. You get the following error on the beta site: I guess setting to fixes this issue. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Mozilla Firefox Browser Version: 66.0.5 Operating System: Windows 10 One more thing. The error generated on the old site is helpful whereas the one on the new site isn't. Probably something to look at.\nThat is a valid point regarding the error message, but that is a different issue related to how the challenge tests are ran. I have gone ahead and created a PR () to address the solution in the Guide, but the last issue you mentioned will have to be discussed in a separate issue (feel free to create it if you have the time). I could not find any outstanding issues regarding why this does not show the error \"assignment to undeclared variable x\" which does show in the actual browser console. Are errors like this being suppressed on showing in the fake console for any reason?", "positive_passages": [{"docid": "doc-en-freeCodeCamp-e13dfe673314cd3b80e2e0af98050695c3ebe02141e98a7f026a4c14c5cb61b1", "text": "--- title: Caesars Cipher --- <del> ![:triangular_flag_on_post:](https://forum.freecodecamp.com/images/emoji/emoji_one/triangular_flag_on_post.png?v=3 \":triangular_flag_on_post:\") Remember to use <a>**`Read-Search-Ask`**</a> if you get stuck. Try to pair program ![:busts_in_silhouette:](https://forum.freecodecamp.com/images/emoji/emoji_one/busts_in_silhouette.png?v=3 \":busts_in_silhouette:\") and write your own code ![:pencil:](https://forum.freecodecamp.com/images/emoji/emoji_one/pencil.png?v=3 \":pencil:\") ### ![:checkered_flag:](https://forum.freecodecamp.com/images/emoji/emoji_one/checkered_flag.png?v=3 \":checkered_flag:\") Problem Explanation: * You need to write a function, which will take a string encoded with _Caesar cipher_ as a parameter and decode it. * The one used here is ROT13 where the value of the letter is shifted by 13 places. e.g. 'A' ![:left_right_arrow:](https://forum.freecodecamp.com/images/emoji/emoji_one/left_right_arrow.png?v=3 \":left_right_arrow:\") 'N', 'T' ![:left_right_arrow:](https://forum.freecodecamp.com/images/emoji/emoji_one/left_right_arrow.png?v=3 \":left_right_arrow:\") 'G'. * You have to shift it back 13 positions, such that 'N' ![:left_right_arrow:](https://forum.freecodecamp.com/images/emoji/emoji_one/left_right_arrow.png?v=3 \":left_right_arrow:\") 'A'. #### Relevant Links * <a href='http://forum.freecodecamp.com/t/javascript-string-prototype-charcodeat/15933' target='_blank' rel='nofollow'>String.prototype.charCodeAt</a> * <a href='https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/fromCharCode' target='_blank' rel='nofollow'>String.fromCharCode</a> </del> ## ![:speech_balloon:](https://forum.freecodecamp.com/images/emoji/emoji_one/speech_balloon.png?v=3 \":speech_balloon:\") Hint: 1", "commid": "freeCodeCamp_pr_36046"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-e7fbcb23b866c25a5eeff5c091cd500b8b9b53f1c5deafea6ec8e1c2bee0228d", "query": "Describe your problem and how to reproduce it: First Issue: The Basic solution uses call() function but doesn't include any reference to it. Second Issue: The Basic solution doesn't work when you use it as a solution for the challenge. You get the following error on the beta site: I guess setting to fixes this issue. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Mozilla Firefox Browser Version: 66.0.5 Operating System: Windows 10 One more thing. The error generated on the old site is helpful whereas the one on the new site isn't. Probably something to look at.\nThat is a valid point regarding the error message, but that is a different issue related to how the challenge tests are ran. I have gone ahead and created a PR () to address the solution in the Guide, but the last issue you mentioned will have to be discussed in a separate issue (feel free to create it if you have the time). I could not find any outstanding issues regarding why this does not show the error \ which does show in the actual browser console. Are errors like this being suppressed on showing in the fake console for any reason?positive_passagesdociddoc-en-freeCodeCamp-6794ef8d3965dadce84a6bd66ab65cc8ea2af6440d23816c0f7f0667bdf660eftext##  Basic Code Solution: ```javascript <del> function rot13(str) { // Split str into a character array return str.split('') // Iterate over each character in the array .map.call(str, function(char) { // Convert char to a character code x = char.charCodeAt(0); // Checks if character lies between A-Z if (x < 65 || x > 90) { return String.fromCharCode(x); // Return un-converted character } //N = ASCII 78, if the character code is less than 78, shift forward 13 places else if (x < 78) { return String.fromCharCode(x + 13); } // Otherwise shift the character 13 places backward return String.fromCharCode(x - 13); }).join(''); // Rejoin the array into a string } </del> <ins> function rot13(str) { // Split str into a character array return str.split('') // Iterate over each character in the array .map.call(str, function(char) { // Convert char to a character code var x = char.charCodeAt(0); // Checks if character lies between A-Z if (x < 65 || x > 90) { return String.fromCharCode(x); // Return un-converted character } //N = ASCII 78, if the character code is less than 78, shift forward 13 places else if (x < 78) { return String.fromCharCode(x + 13); } // Otherwise shift the character 13 places backward return String.fromCharCode(x - 13); }).join(''); // Rejoin the array into a string } </ins> ``` <del>  <a href='https://repl.it/CLjU/38' target='_blank' rel='nofollow'>Run Code</a> </del> ### Code Explanation:commidfreeCodeCamp_pr_36046negative_passages |
| query_idq-en-freeCodeCamp-e7fbcb23b866c25a5eeff5c091cd500b8b9b53f1c5deafea6ec8e1c2bee0228dqueryDescribe your problem and how to reproduce it: First Issue: The Basic solution uses call() function but doesn't include any reference to it. Second Issue: The Basic solution doesn't work when you use it as a solution for the challenge. You get the following error on the beta site: I guess setting to fixes this issue. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Mozilla Firefox Browser Version: 66.0.5 Operating System: Windows 10 One more thing. The error generated on the old site is helpful whereas the one on the new site isn't. Probably something to look at.\nThat is a valid point regarding the error message, but that is a different issue related to how the challenge tests are ran. I have gone ahead and created a PR () to address the solution in the Guide, but the last issue you mentioned will have to be discussed in a separate issue (feel free to create it if you have the time). I could not find any outstanding issues regarding why this does not show the error \"assignment to undeclared variable x\" which does show in the actual browser console. Are errors like this being suppressed on showing in the fake console for any reason?", "positive_passages": [{"docid": "doc-en-freeCodeCamp-7bc431c7f256392184273ca6921c12e2fd8572b3b8bb25c5dfaf10bd446b7c0e", "text": "#### Relevant Links <del> * <a href='http://forum.freecodecamp.com/t/javascript-array-prototype-map/14294' target='_blank' rel='nofollow'>Array.prototype.map</a> * <a href='http://forum.freecodecamp.com/t/javascript-string-prototype-split/15944' target='_blank' rel='nofollow'>String.prototype.split</a> * <a href='http://forum.freecodecamp.com/t/javascript-array-prototype-join/14292' target='_blank' rel='nofollow'>Array.prototype.join</a> </del> <ins> * <a href='https://forum.freecodecamp.com/t/javascript-array-prototype-map/14294' target='_blank' rel='nofollow'>Array.prototype.map</a> * <a href='https://forum.freecodecamp.com/t/javascript-string-prototype-split/15944' target='_blank' rel='nofollow'>String.prototype.split</a> * <a href='https://forum.freecodecamp.com/t/javascript-array-prototype-join/14292' target='_blank' rel='nofollow'>Array.prototype.join</a> </ins> ## ![:sunflower:](https://forum.freecodecamp.com/images/emoji/emoji_one/sunflower.png?v=3 \":sunflower:\") Intermediate Code Solution: ```javascript <del> // Solution with Regular expression and Array of ASCII character codes function rot13(str) { var rotCharArray = []; var regEx = /[A-Z]/ ; str = str.split(\"\"); for (var x in str) { if (regEx.test(str[x])) { // A more general approach // possible because of modular arithmetic // and cyclic nature of rot13 transform rotCharArray.push((str[x].charCodeAt() - 65 + 13) % 26 + 65); } else { rotCharArray.push(str[x].charCodeAt()); } } str = String.fromCharCode.apply(String, rotCharArray); return str; </del> <ins> // Solution with Regular expression and Array of ASCII character codes function rot13(str) { var rotCharArray = []; var regEx = /[A-Z]/; str = str.split(\"\"); for (var x in str) { if (regEx.test(str[x])) { // A more general approach // possible because of modular arithmetic // and cyclic nature of rot13 transform rotCharArray.push((str[x].charCodeAt() - 65 + 13) % 26 + 65); } else { rotCharArray.push(str[x].charCodeAt()); </ins> } <ins> } str = String.fromCharCode.apply(String, rotCharArray); return str; } </ins> <del> // Change the inputs below to test rot13(\"LBH QVQ VG!\"); </del> <ins> // Change the inputs below to test rot13(\"LBH QVQ VG!\"); </ins> ``` ### Code Explanation:", "commid": "freeCodeCamp_pr_36046"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-e7fbcb23b866c25a5eeff5c091cd500b8b9b53f1c5deafea6ec8e1c2bee0228d", "query": "Describe your problem and how to reproduce it: First Issue: The Basic solution uses call() function but doesn't include any reference to it. Second Issue: The Basic solution doesn't work when you use it as a solution for the challenge. You get the following error on the beta site: I guess setting to fixes this issue. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Mozilla Firefox Browser Version: 66.0.5 Operating System: Windows 10 One more thing. The error generated on the old site is helpful whereas the one on the new site isn't. Probably something to look at.\nThat is a valid point regarding the error message, but that is a different issue related to how the challenge tests are ran. I have gone ahead and created a PR () to address the solution in the Guide, but the last issue you mentioned will have to be discussed in a separate issue (feel free to create it if you have the time). I could not find any outstanding issues regarding why this does not show the error \ which does show in the actual browser console. Are errors like this being suppressed on showing in the fake console for any reason?positive_passagesdociddoc-en-freeCodeCamp-3cd93049a179b119cd457eeaf973f312b0d0963c6619d5658409acc4375e8ec4text* <a href='https://forum.freecodecamp.com/t/regular-expressions-resources/15931' target='_blank' rel='nofollow'>Regex</a> * <a href='https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp/test' target='_blank' rel='nofollow'>Regex.test</a> <del>  <a href='https://repl.it/CLjU/39' target='_blank' rel='nofollow'>Run Code</a> </del> ##  Advanced Code Solution: function rot13(str) { // LBH QVQ VG!commidfreeCodeCamp_pr_36046negative_passages |
| query_idq-en-freeCodeCamp-0b87ec43119e6650dd3089deb9a5c288ba75619239319c2be20179b9e309247dqueryThe new buttons hug the top of the panel. <img width=\ alt=\ src=\I can fix this one.positive_passagesdociddoc-en-freeCodeCamp-a1aae7853be3d912499590f1ebc0e7271c33402a3b90cbf4324b45fa1180585ctext} .challenge-title-wrap > a { <ins> margin-top: 10px; </ins> align-self: flex-start; }commidfreeCodeCamp_pr_36649negative_passages |
| query_idq-en-freeCodeCamp-e46de5b6a6364a2e085e6a7bafcb6dadbc916d06f6c18e125e1cb893fc0f08aequeryWhen you sign in, you get sent to the \ page where it shows the number of donators. The progress bar there is still green. I'm assuming we want to make it some shade of blue or something. <img width=\"652\" alt=\"Screen Shot 2019-08-21 at 9 17 21 AM\" src=\"https://user-\"", "positive_passages": [{"docid": "doc-en-freeCodeCamp-6ff5ab9e4111a57637f644701247257b0e25e33072c43520315cbd7b15955ee8", "text": "#supporter-progress-wrapper .progress { height: 38px; margin-bottom: 0px; <ins> background-color: var(--quaternary-background); </ins> } #supporter-progress-wrapper .progress-bar { padding-top: 8px; <ins> background-color: var(--secondary-color); </ins> }", "commid": "freeCodeCamp_pr_36661"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-76dec5e9803dfaf66c1065a535ee57ca6678297cd64f90a3de6acb2fff64963b", "query": "to replicate. go to incognito do not sign in go to learn choose a challenge !\nI can take a look at this\nthank you. There might to be other inconsistencies with the theme. If you try different scenarios like switching the theme, logging in logging out, and visiting the challenge page. That should expose any related issues that needs fixing. let me know if I could be of any help.\nin displaytheme is in charge of the code editor's theme. and in the theme colors get injected. we need night mode by default if not signed in\nI haven't tested, but it does look like the cause. Hope you don't mind raising a PR, since I don't want to take your credit\nI pointed it out for you. But yea, I have it ready.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-19e78c8e9a17ddf9a3868b39fe29d0a793f61ad5a0aeff57a4c3b6b215e97dee", "text": "const mapStateToProps = createSelector( userSelector, <del> ({ theme = 'default' }) => ({ theme }) </del> <ins> ({ theme = 'night' }) => ({ theme }) </ins> ); const mapDispatchToProps = dispatch =>", "commid": "freeCodeCamp_pr_36667"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-65f9bdaa48484b4ac7c481ee8109bc20ff65657b9daad57e218455276941eb88", "query": "Describe the bug Some challenge titles on the map wrap to a new line while the parent width is big enough for them to display on a single line. <img width=\"818\" alt=\"Screen Shot 2019-08-23 at 8 42 26 PM\" src=\"https://user-\"I think it's due to the rule applied to the tags.\nThe reason for this is because the element has a class which has !\nI think that can be removed. I don't see any reason to keep it.\nYeah we can remove the rule as long as we make sure that the removal doesn't affect anything else. Feel free to make a PR for this\nI think it might be nice if the effective left and right margins of the titles were the same. Currently, because they're (roughly) what happens is the left margin is larger, because each has its elements indented slightly by . Try and see what you think. Obviously it's a bit of a compromise (a few more titles will wrap), but I think that'll look better.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-4a855e3c07a70d7cce85969890307a5d8f51ed7f631de7ecc2b111e9215ea182", "text": ".map-challenge-title { margin-bottom: 0.25rem; <del> max-width: 28rem; </del> <ins> max-width: calc(100% - 80px); </ins> } .block a {", "commid": "freeCodeCamp_pr_36727"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-41c0f39122fff90b73fa76d291daebafb85da799a60a0961e5973b3d761a0745", "query": "Describe the bug If you complete a challenge, navigate back (taking you to the curriculum), then open a new challenge the success modal will still be open. To Reproduce Steps to reproduce the behavior: to the challenge -enter the success modal back to that the modal is still present Expected behavior The modal should be closed every time you leave a challenge. Screenshots !", "positive_passages": [{"docid": "doc-en-freeCodeCamp-77e8a4de2f47d574bf79c7adda3b49db443ed5b4778023a2a0585daa4ffd03b6", "text": "if (this.state.downloadURL) { URL.revokeObjectURL(this.state.downloadURL); } <ins> this.props.close(); </ins> } render() {", "commid": "freeCodeCamp_pr_36991"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-8e4542f91b669ae2b68b983782c1892864cd02b7f65829c964b78000553cf827", "query": "Is your feature request related to a problem? Please describe. It currently can take a several key presses to navigate to the editor if it does not have focus. Describe the solution you'd like It should be possible to focus on the editor with a hotkey, for example 'e'. The issue where this was mostly discussed will be closed soon, but some thoughts about implementing this appeared there:positive_passagesdociddoc-en-freeCodeCamp-c4b99870533c84a92af3ec991ce4d088f191d41b7c6cc50b77d64c2609afef11text}; this._editor = null; <ins> this.focusOnEditor = this.focusOnEditor.bind(this); </ins> } editorWillMount = monaco => {commidfreeCodeCamp_pr_37202negative_passages |
| query_idq-en-freeCodeCamp-8e4542f91b669ae2b68b983782c1892864cd02b7f65829c964b78000553cf827queryIs your feature request related to a problem? Please describe. It currently can take a several key presses to navigate to the editor if it does not have focus. Describe the solution you'd like It should be possible to focus on the editor with a hotkey, for example 'e'. The issue where this was mostly discussed will be closed soon, but some thoughts about implementing this appeared there:", "positive_passages": [{"docid": "doc-en-freeCodeCamp-6f8c9d014df3f93aa04d1d8c6f156a0cce36944ed5ca31b7f9d87998ab6fb899", "text": "} } <ins> focusOnEditor() { this._editor.focus(); } </ins> onChange = editorValue => { const { updateFile, fileKey } = this.props; updateFile({ key: fileKey, editorValue });", "commid": "freeCodeCamp_pr_37202"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-8e4542f91b669ae2b68b983782c1892864cd02b7f65829c964b78000553cf827", "query": "Is your feature request related to a problem? Please describe. It currently can take a several key presses to navigate to the editor if it does not have focus. Describe the solution you'd like It should be possible to focus on the editor with a hotkey, for example 'e'. The issue where this was mostly discussed will be closed soon, but some thoughts about implementing this appeared there:positive_passagesdociddoc-en-freeCodeCamp-9853f84866eb2ba8b031d87436f3a62045bf393730bdaea843ee94b4bbbb4a14textEditor.displayName = 'Editor'; Editor.propTypes = propTypes; <ins> // NOTE: withRef gets replaced by forwardRef in react-redux 6, // https://github.com/reduxjs/react-redux/releases/tag/v6.0.0 </ins> export default connect( mapStateToProps, <del> mapDispatchToProps </del> <ins> mapDispatchToProps, null, { withRef: true } </ins> )(Editor);commidfreeCodeCamp_pr_37202negative_passages |
| query_idq-en-freeCodeCamp-8e4542f91b669ae2b68b983782c1892864cd02b7f65829c964b78000553cf827queryIs your feature request related to a problem? Please describe. It currently can take a several key presses to navigate to the editor if it does not have focus. Describe the solution you'd like It should be possible to focus on the editor with a hotkey, for example 'e'. The issue where this was mostly discussed will be closed soon, but some thoughts about implementing this appeared there:", "positive_passages": [{"docid": "doc-en-freeCodeCamp-ae59debef22dc0e60df22045c2d8bcc6370e597aff2f2bca504a1539cb0b9a23", "text": "}; this.containerRef = React.createRef(); <ins> this.editorRef = React.createRef(); </ins> } onResize() { this.setState({ resizing: true });", "commid": "freeCodeCamp_pr_37202"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-8e4542f91b669ae2b68b983782c1892864cd02b7f65829c964b78000553cf827", "query": "Is your feature request related to a problem? Please describe. It currently can take a several key presses to navigate to the editor if it does not have focus. Describe the solution you'd like It should be possible to focus on the editor with a hotkey, for example 'e'. The issue where this was mostly discussed will be closed soon, but some thoughts about implementing this appeared there:positive_passagesdociddoc-en-freeCodeCamp-9a0b7a65d9f8ab83d19d1271c926c80adaf2b03d4c22d8cd163fd2e1d6311c3ftextchallengeFile && ( <Editor containerRef={this.containerRef} <ins> ref={this.editorRef} </ins> {...challengeFile} fileKey={challengeFile.key} />commidfreeCodeCamp_pr_37202negative_passages |
| query_idq-en-freeCodeCamp-8e4542f91b669ae2b68b983782c1892864cd02b7f65829c964b78000553cf827queryIs your feature request related to a problem? Please describe. It currently can take a several key presses to navigate to the editor if it does not have focus. Describe the solution you'd like It should be possible to focus on the editor with a hotkey, for example 'e'. The issue where this was mostly discussed will be closed soon, but some thoughts about implementing this appeared there:", "positive_passages": [{"docid": "doc-en-freeCodeCamp-3bcdb5aa93cc8dfb9654d4775a542f35d4bef606a83bbcaec69b48a400b1aa59", "text": "} = this.props; return ( <Hotkeys <ins> editorRef={this.editorRef} </ins> executeChallenge={executeChallenge} innerRef={this.containerRef} introPath={introPath}", "commid": "freeCodeCamp_pr_37202"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-8e4542f91b669ae2b68b983782c1892864cd02b7f65829c964b78000553cf827", "query": "Is your feature request related to a problem? Please describe. It currently can take a several key presses to navigate to the editor if it does not have focus. Describe the solution you'd like It should be possible to focus on the editor with a hotkey, for example 'e'. The issue where this was mostly discussed will be closed soon, but some thoughts about implementing this appeared there:positive_passagesdociddoc-en-freeCodeCamp-e6509666bf197d45f14e9e996007f43e72770e6da56fa12e682e4fde437c4b4etextconst keyMap = { NAVIGATION_MODE: 'escape', EXECUTE_CHALLENGE: ['ctrl+enter', 'command+enter'], <ins> FOCUS_EDITOR: 'e', </ins> NAVIGATE_PREV: ['p'], NAVIGATE_NEXT: ['n'] };commidfreeCodeCamp_pr_37202negative_passages |
| query_idq-en-freeCodeCamp-8e4542f91b669ae2b68b983782c1892864cd02b7f65829c964b78000553cf827queryIs your feature request related to a problem? Please describe. It currently can take a several key presses to navigate to the editor if it does not have focus. Describe the solution you'd like It should be possible to focus on the editor with a hotkey, for example 'e'. The issue where this was mostly discussed will be closed soon, but some thoughts about implementing this appeared there:", "positive_passages": [{"docid": "doc-en-freeCodeCamp-0d53c2b93b86e82ad6f8e058af05ae9dd2b24205ecf304b24fbc80c81667979e", "text": "const propTypes = { canFocusEditor: PropTypes.bool, children: PropTypes.any, <ins> editorRef: PropTypes.object, </ins> executeChallenge: PropTypes.func, innerRef: PropTypes.any, introPath: PropTypes.string,", "commid": "freeCodeCamp_pr_37202"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-8e4542f91b669ae2b68b983782c1892864cd02b7f65829c964b78000553cf827", "query": "Is your feature request related to a problem? Please describe. It currently can take a several key presses to navigate to the editor if it does not have focus. Describe the solution you'd like It should be possible to focus on the editor with a hotkey, for example 'e'. The issue where this was mostly discussed will be closed soon, but some thoughts about implementing this appeared there:positive_passagesdociddoc-en-freeCodeCamp-7fbe1712d4107e79c1ea2a3de494a4b91d8db96f471b9d2a37b54b5fbe50e37ftextfunction Hotkeys({ canFocusEditor, children, <ins> editorRef, </ins> executeChallenge, introPath, innerRef,commidfreeCodeCamp_pr_37202negative_passages |
| query_idq-en-freeCodeCamp-8e4542f91b669ae2b68b983782c1892864cd02b7f65829c964b78000553cf827queryIs your feature request related to a problem? Please describe. It currently can take a several key presses to navigate to the editor if it does not have focus. Describe the solution you'd like It should be possible to focus on the editor with a hotkey, for example 'e'. The issue where this was mostly discussed will be closed soon, but some thoughts about implementing this appeared there:", "positive_passages": [{"docid": "doc-en-freeCodeCamp-f099c8f2a1929360775ba86f7939f27b78086dfd0320ee6239d8d8bdf0750f13", "text": "e.preventDefault(); if (executeChallenge) executeChallenge(); }, <ins> FOCUS_EDITOR: e => { e.preventDefault(); if (editorRef && editorRef.current) { editorRef.current.getWrappedInstance().focusOnEditor(); } }, </ins> NAVIGATION_MODE: () => setEditorFocusability(false), NAVIGATE_PREV: () => { if (!canFocusEditor) navigate(prevChallengePath);", "commid": "freeCodeCamp_pr_37202"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-dd6374a03a6b38b5d2b05878e18706e6a348061aae73db34a6e34bd5f82824f6", "query": "Describe the bug Functionally, there is no problem with distinguishing between normal and focus state because there is blinking cursor when on focus state. Filled fields will also be selected and highlighted with blue color when navigating with keyboard tab. Aesthetically, there is suggestion from on issue to invert the input boxes with dark background and light text in night mode. Border color change between normal and focus state also need some visual improvements because currently it is hard to see. To Reproduce Steps to reproduce the behavior: to http://localhost:8000/settings to switch between normal and focus state on input boxes with mouse click or keyboard tab to Describe the bug Expected behavior Refer to suggestion in Describe the bug Desktop (please complete the following information): OS: Windows 10 1809 Build .832 Browser Latest Chrome Version 77.0.3865.120 (Official Build) (64-bit)\ni'll take this onepositive_passagesdociddoc-en-freeCodeCamp-61524963d9213b1ac39671c6491473321f23ef9c438aceae9eebc88ff2c4e764text} .form-control { <del> color: var(--theme-color); </del> <ins> color: var(--primary-color); </ins> outline: none; border-color: var(--quaternary-background); <ins> background-color: var(--primary-background); </ins> -webkit-box-shadow: none !important; -moz-box-shadow: none !important; box-shadow: none !important;commidfreeCodeCamp_pr_37470negative_passages |
| query_idq-en-freeCodeCamp-a70a29af2cc8e5511f0fa51a809372a087e4bd1eee35751386a3cf15a6f675fequery<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: Running on any JS challenge outputs on the console output instead of . Related forum topic: User reported seeing when it actually should be with the following code: Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Firefox Browser Version: 70.0 Operating System: Kubuntu 19.04 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): Screenshot of bug in a different challenge: !\nI don't know anything about this part of the code, but I do see JSON.stringify being used in test- and if you stringify you get back \"null\". Again, not sure if this is related or not just thought I would post it anyway.\nYeah, that's exactly the issue. My current plan is to use if it exists and stringify if not. I'm just not sure how to make sure this doesn't create any weirdness.\nWhat about using the parameter function? Would that be less likely to cause any weirdness?\nthat sounds way better. Do you think you'll have time to put that in a PR?", "positive_passages": [{"docid": "doc-en-freeCodeCamp-ebc2cefadeb3e2485ad013a8b45157de8e20317310ec01ba8eabbed94c5b83b1", "text": "} } <ins> function replacer(key, value) { if (Number.isNaN(value)) { return 'NaN'; } return value; } </ins> const oldLog = self.console.log.bind(self.console); self.console.log = function proxyConsole(...args) { <del> logs.push(args.map(arg => '' + JSON.stringify(arg)).join(' ')); </del> <ins> logs.push(args.map(arg => '' + JSON.stringify(arg, replacer)).join(' ')); </ins> if (logs.join('n').length > MAX_LOGS_SIZE) { flushLogs(); }", "commid": "freeCodeCamp_pr_37684"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-da99e2606395076974bf641d46ee0c1ffb370af7ecdb12be1ff9ddf117863bab", "query": "<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: I identified three challenges where the for loop validation does not work if newlines are used in the arguments. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Google Chrome Browser Version: 79.0.3945.88 Operating System: Ubuntu 18.04 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! ! !", "positive_passages": [{"docid": "doc-en-freeCodeCamp-016e6360b384f8e90f19bafca8726558fb093e239369c8c2c46a5ee99d7a7bfe", "text": "- text: Your code should use the <code>filter</code> method. testString: assert(code.match(/.filter/g)); - text: Your code should not use a <code>for</code> loop. <del> testString: assert(!code.match(/fors*?(.+?)/g)); </del> <ins> testString: assert(!code.match(/fors*?([sS]*?)/g)); </ins> - text: '<code>filteredList</code> should equal <code>[{\: \,\: \},{\: \,\: \},{\: \,\: \},{\: \,\: \}]</code>.' testString: 'assert.deepEqual(filteredList, [{\: \,\: \},{\: \,\: \},{\: \,\: \},{\: \,\: \}]);'", "commid": "freeCodeCamp_pr_38180"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-da99e2606395076974bf641d46ee0c1ffb370af7ecdb12be1ff9ddf117863bab", "query": "<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: I identified three challenges where the for loop validation does not work if newlines are used in the arguments. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Google Chrome Browser Version: 79.0.3945.88 Operating System: Ubuntu 18.04 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! ! !", "positive_passages": [{"docid": "doc-en-freeCodeCamp-34d04b4a19692bd73757c090f6854311e4f5fd801c93e43983b1e55c48131030", "text": "- text: The <code>watchList</code> variable should not change. testString: assert(watchList[0].Title === \"Inception\" && watchList[4].Director == \"James Cameron\"); - text: Your code should not use a <code>for</code> loop. <del> testString: assert(!removeJSComments(code).match(/fors*?(.*?)/)); </del> <ins> testString: assert(!removeJSComments(code).match(/fors*?([sS]*?)/)); </ins> - text: Your code should use the <code>map</code> method. testString: assert(code.match(/.map/g)); - text: <code>ratings</code> should equal <code>[{\"title\":\"Inception\",\"rating\":\"8.8\"},{\"title\":\"Interstellar\",\"rating\":\"8.6\"},{\"title\":\"The Dark Knight\",\"rating\":\"9.0\"},{\"title\":\"Batman Begins\",\"rating\":\"8.3\"},{\"title\":\"Avatar\",\"rating\":\"7.9\"}]</code>.", "commid": "freeCodeCamp_pr_38180"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-da99e2606395076974bf641d46ee0c1ffb370af7ecdb12be1ff9ddf117863bab", "query": "<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: I identified three challenges where the for loop validation does not work if newlines are used in the arguments. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Google Chrome Browser Version: 79.0.3945.88 Operating System: Ubuntu 18.04 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! ! !", "positive_passages": [{"docid": "doc-en-freeCodeCamp-8404d26cb669569e05aa3521e68262aa64146e7d7a5e56b5a3b0c2f6b054541f", "text": "- text: The <code>getRating(watchList)</code> should equal 8.675. testString: assert(getRating(watchList) === 8.675); - text: Your code should not use a <code>for</code> loop. <del> testString: assert(!code.match(/fors*?(.*)/g)); </del> <ins> testString: assert(!code.match(/fors*?([sS]*?)/g)); </ins> - text: Your code should return correct output after modifying the <code>watchList</code> object. testString: assert(getRating(watchList.filter((_, i) => i < 1 || i > 2)) === 8.55);", "commid": "freeCodeCamp_pr_38180"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-cd2e75022f114b0287b4b665a88ff8ba96c2988eaa299c1c9380abb53ad09526", "query": "Advanced Node and Express section needs package versions to the instructions, as discussed in: Example: \" Add <codepassport.socketio</codeversion <codeX.X.X</code, <codeconnect-mongo</codeversion <codeX.X.X</code, and <codecookie-parser</codeversion <codeX.X.X</codeas dependencies and require them as <codepassportSocketIo</code, <codeMongoStore</code, and <codecookieParser</coderespectfully. \" Before this is undertaken: [x] Wait for to be merged [ ] Discuss which versions to use and how to convey this ( or )\nI am leaning more toward the requirement, myself. With the carat prefix, will install the latest minor version. In theory, updates to the minor version are backwards compatible and shouldn't create any issues with the tests or challenges. However, minor versions can include depreciation notices like . The feature will still work, but this could be confusing to a camper. Using the tilde prefix means will install the latest patch version, which includes bug fixes but shouldn't lead to any depreciation notices. I think this will offer the best long-term compatibility with our tests and challenge instructions.\nWell, it has happened: Last versions which definitely work: I have tested this. Now, discussion: 1) Just ask for to be installed 2) Also change the lesson/code to work with this latest version?\nHey how is this show stopper coming along?\nAh yes... I have updated the label, because it should have been removed by . Can a PR automatically remove an issue's label? Otherwise, this issue is still open and help wanted , as there are many packages which need their versioning fixed. If no one else, I can slot in some time for this tomorrow.\nNo rush. Thanks for confirming, I have removed the assignment since this is no longer a showstopper.\nthank you so much for the Thank you for the suggestion. It helped me alotpositive_passagesdociddoc-en-freeCodeCamp-bf30abd3a92170db477751da2d4c21998d81833df5c7ee6b84c97558941a3b20textA strategy is a way of authenticating a user. You can use a strategy for allowing users to authenticate based on locally saved information (if you have them register first) or from a variety of providers such as Google or GitHub. For this project, we will set up a local strategy. To see a list of the hundreds of strategies, visit Passport's site [here](http://passportjs.org/). <del> Add `passport-local` as a dependency and add it to your server as follows: `const LocalStrategy = require('passport-local');` </del> <ins> Add `passport-local@~1.0.0` as a dependency and add it to your server as follows: `const LocalStrategy = require('passport-local');` </ins> Now you will have to tell passport to **use** an instantiated LocalStrategy object with a few settings defined. Make sure this (as well as everything from this point on) is encapsulated in the database connection since it relies on it!", "commid": "freeCodeCamp_pr_42297"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-cd2e75022f114b0287b4b665a88ff8ba96c2988eaa299c1c9380abb53ad09526", "query": "Advanced Node and Express section needs package versions to the instructions, as discussed in: Example: \" Add <codepassport.socketio</codeversion <codeX.X.X</code, <codeconnect-mongo</codeversion <codeX.X.X</code, and <codecookie-parser</codeversion <codeX.X.X</codeas dependencies and require them as <codepassportSocketIo</code, <codeMongoStore</code, and <codecookieParser</coderespectfully. \" Before this is undertaken: [x] Wait for to be merged [ ] Discuss which versions to use and how to convey this ( or )\nI am leaning more toward the requirement, myself. With the carat prefix, will install the latest minor version. In theory, updates to the minor version are backwards compatible and shouldn't create any issues with the tests or challenges. However, minor versions can include depreciation notices like . The feature will still work, but this could be confusing to a camper. Using the tilde prefix means will install the latest patch version, which includes bug fixes but shouldn't lead to any depreciation notices. I think this will offer the best long-term compatibility with our tests and challenge instructions.\nWell, it has happened: Last versions which definitely work: I have tested this. Now, discussion: 1) Just ask for to be installed 2) Also change the lesson/code to work with this latest version?\nHey how is this show stopper coming along?\nAh yes... I have updated the label, because it should have been removed by . Can a PR automatically remove an issue's label? Otherwise, this issue is still open and help wanted , as there are many packages which need their versioning fixed. If no one else, I can slot in some time for this tomorrow.\nNo rush. Thanks for confirming, I have removed the assignment since this is no longer a showstopper.\nthank you so much for the Thank you for the suggestion. It helped me alotpositive_passagesdociddoc-en-freeCodeCamp-3627faa088d1aa0b0772fb800ec89f0bbc55df7b9b4c058b6b6069f44df06c23textCurrently, you cannot determine who is connected to your web socket. While `req.user` contains the user object, that's only when your user interacts with the web server, and with web sockets you have no `req` (request) and therefore no user data. One way to solve the problem of knowing who is connected to your web socket is by parsing and decoding the cookie that contains the passport session then deserializing it to obtain the user object. Luckily, there is a package on NPM just for this that turns a once complex task into something simple! <del> Add `passport.socketio`, `connect-mongo@~3.2.0`, and `cookie-parser` as dependencies and require them as `passportSocketIo`, `MongoStore`, and `cookieParser` respectively. Also, we need to initialize a new memory store, from `express-session` which we previously required. It should look like this: </del> <ins> Add `passport.socketio@~3.7.0`, `connect-mongo@~3.2.0`, and `cookie-parser@~1.4.5` as dependencies and require them as `passportSocketIo`, `MongoStore`, and `cookieParser` respectively. Also, we need to initialize a new memory store, from `express-session` which we previously required. It should look like this: </ins> ```js const MongoStore = require('connect-mongo')(session);", "commid": "freeCodeCamp_pr_42297"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-cd2e75022f114b0287b4b665a88ff8ba96c2988eaa299c1c9380abb53ad09526", "query": "Advanced Node and Express section needs package versions to the instructions, as discussed in: Example: \" Add <codepassport.socketio</codeversion <codeX.X.X</code, <codeconnect-mongo</codeversion <codeX.X.X</code, and <codecookie-parser</codeversion <codeX.X.X</codeas dependencies and require them as <codepassportSocketIo</code, <codeMongoStore</code, and <codecookieParser</coderespectfully. \" Before this is undertaken: [x] Wait for to be merged [ ] Discuss which versions to use and how to convey this ( or )\nI am leaning more toward the requirement, myself. With the carat prefix, will install the latest minor version. In theory, updates to the minor version are backwards compatible and shouldn't create any issues with the tests or challenges. However, minor versions can include depreciation notices like . The feature will still work, but this could be confusing to a camper. Using the tilde prefix means will install the latest patch version, which includes bug fixes but shouldn't lead to any depreciation notices. I think this will offer the best long-term compatibility with our tests and challenge instructions.\nWell, it has happened: Last versions which definitely work: I have tested this. Now, discussion: 1) Just ask for to be installed 2) Also change the lesson/code to work with this latest version?\nHey how is this show stopper coming along?\nAh yes... I have updated the label, because it should have been removed by . Can a PR automatically remove an issue's label? Otherwise, this issue is still open and help wanted , as there are many packages which need their versioning fixed. If no one else, I can slot in some time for this tomorrow.\nNo rush. Thanks for confirming, I have removed the assignment since this is no longer a showstopper.\nthank you so much for the Thank you for the suggestion. It helped me alotpositive_passagesdociddoc-en-freeCodeCamp-b2bf78327ea8c47b1cca7a33b7d8de600c4fc2356ede5902ca4d5b2cd635be3etextGoing back to the information security section, you may remember that storing plaintext passwords is *never* okay. Now it is time to implement BCrypt to solve this issue. <del> Add BCrypt as a dependency, and require it in your server. You will need to handle hashing in 2 key areas: where you handle registering/saving a new account, and when you check to see that a password is correct on login. </del> <ins> Add `bcrypt@~5.0.0` as a dependency, and require it in your server. You will need to handle hashing in 2 key areas: where you handle registering/saving a new account, and when you check to see that a password is correct on login. </ins> Currently on our registration route, you insert a user's password into the database like so: `password: req.body.password`. An easy way to implement saving a hash instead is to add the following before your database logic `const hash = bcrypt.hashSync(req.body.password, 12);`, and replacing the `req.body.password` in the database saving with just `password: hash`.", "commid": "freeCodeCamp_pr_42297"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-cd2e75022f114b0287b4b665a88ff8ba96c2988eaa299c1c9380abb53ad09526", "query": "Advanced Node and Express section needs package versions to the instructions, as discussed in: Example: \" Add <codepassport.socketio</codeversion <codeX.X.X</code, <codeconnect-mongo</codeversion <codeX.X.X</code, and <codecookie-parser</codeversion <codeX.X.X</codeas dependencies and require them as <codepassportSocketIo</code, <codeMongoStore</code, and <codecookieParser</coderespectfully. \" Before this is undertaken: [x] Wait for to be merged [ ] Discuss which versions to use and how to convey this ( or )\nI am leaning more toward the requirement, myself. With the carat prefix, will install the latest minor version. In theory, updates to the minor version are backwards compatible and shouldn't create any issues with the tests or challenges. However, minor versions can include depreciation notices like . The feature will still work, but this could be confusing to a camper. Using the tilde prefix means will install the latest patch version, which includes bug fixes but shouldn't lead to any depreciation notices. I think this will offer the best long-term compatibility with our tests and challenge instructions.\nWell, it has happened: Last versions which definitely work: I have tested this. Now, discussion: 1) Just ask for to be installed 2) Also change the lesson/code to work with this latest version?\nHey how is this show stopper coming along?\nAh yes... I have updated the label, because it should have been removed by . Can a PR automatically remove an issue's label? Otherwise, this issue is still open and help wanted , as there are many packages which need their versioning fixed. If no one else, I can slot in some time for this tomorrow.\nNo rush. Thanks for confirming, I have removed the assignment since this is no longer a showstopper.\nthank you so much for the Thank you for the suggestion. It helped me alotpositive_passagesdociddoc-en-freeCodeCamp-b5bb85724beee3e46008853e2dc158c6ba7a85dcceb0530e9248e398d11a1bd7text# --description-- <del> The last part of setting up your GitHub authentication is to create the strategy itself. For this, you will need to add the dependency of 'passport-github' to your project and require it in your `auth.js` as `GithubStrategy` like this: `const GitHubStrategy = require('passport-github').Strategy;`. Do not forget to require and configure `dotenv` to use your environment variables. </del> <ins> The last part of setting up your GitHub authentication is to create the strategy itself. For this, you will need to add the dependency of `passport-github@~1.1.0` to your project and require it in your `auth.js` as `GithubStrategy` like this: `const GitHubStrategy = require('passport-github').Strategy;`. Do not forget to require and configure `dotenv` to use your environment variables. </ins> To set up the GitHub strategy, you have to tell Passport to use an instantiated `GitHubStrategy`, which accepts 2 arguments: an object (containing `clientID`, `clientSecret`, and `callbackURL`) and a function to be called when a user is successfully authenticated, which will determine if the user is new and what fields to save initially in the user's database object. This is common across many strategies, but some may require more information as outlined in that specific strategy's GitHub README. For example, Google requires a *scope* as well which determines what kind of information your request is asking to be returned and asks the user to approve such access. The current strategy we are implementing has its usage outlined [here](https://github.com/jaredhanson/passport-github/), but we're going through it all right here on freeCodeCamp!", "commid": "freeCodeCamp_pr_42297"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-cd2e75022f114b0287b4b665a88ff8ba96c2988eaa299c1c9380abb53ad09526", "query": "Advanced Node and Express section needs package versions to the instructions, as discussed in: Example: \" Add <codepassport.socketio</codeversion <codeX.X.X</code, <codeconnect-mongo</codeversion <codeX.X.X</code, and <codecookie-parser</codeversion <codeX.X.X</codeas dependencies and require them as <codepassportSocketIo</code, <codeMongoStore</code, and <codecookieParser</coderespectfully. \" Before this is undertaken: [x] Wait for to be merged [ ] Discuss which versions to use and how to convey this ( or )\nI am leaning more toward the requirement, myself. With the carat prefix, will install the latest minor version. In theory, updates to the minor version are backwards compatible and shouldn't create any issues with the tests or challenges. However, minor versions can include depreciation notices like . The feature will still work, but this could be confusing to a camper. Using the tilde prefix means will install the latest patch version, which includes bug fixes but shouldn't lead to any depreciation notices. I think this will offer the best long-term compatibility with our tests and challenge instructions.\nWell, it has happened: Last versions which definitely work: I have tested this. Now, discussion: 1) Just ask for to be installed 2) Also change the lesson/code to work with this latest version?\nHey how is this show stopper coming along?\nAh yes... I have updated the label, because it should have been removed by . Can a PR automatically remove an issue's label? Otherwise, this issue is still open and help wanted , as there are many packages which need their versioning fixed. If no one else, I can slot in some time for this tomorrow.\nNo rush. Thanks for confirming, I have removed the assignment since this is no longer a showstopper.\nthank you so much for the Thank you for the suggestion. It helped me alotpositive_passagesdociddoc-en-freeCodeCamp-7b4bdb86ca72fbdbd0df440aa99527ee15ad69fc0599ea439103c18f6f50690atextTo set this up properly, we need to have a serialize function and a deserialize function. In Passport, we create these with `passport.serializeUser( OURFUNCTION )` and `passport.deserializeUser( OURFUNCTION )` <del> The `serializeUser` is called with 2 arguments, the full user object and a callback used by passport. A unique key to identify that user should be returned in the callback, the easiest one to use being the user's `_id` in the object. It should be unique as it generated by MongoDB. Similarly, `deserializeUser` is called with that key and a callback function for passport as well, but, this time, we have to take that key and return the full user object to the callback. To make a query search for a Mongo `_id`, you will have to create `const ObjectID = require('mongodb').ObjectID;`, and then to use it you call `new ObjectID(THE_ID)`. Be sure to add MongoDB as a dependency. You can see this in the examples below: </del> <ins> The `serializeUser` is called with 2 arguments, the full user object and a callback used by passport. A unique key to identify that user should be returned in the callback, the easiest one to use being the user's `_id` in the object. It should be unique as it generated by MongoDB. Similarly, `deserializeUser` is called with that key and a callback function for passport as well, but, this time, we have to take that key and return the full user object to the callback. To make a query search for a Mongo `_id`, you will have to create `const ObjectID = require('mongodb').ObjectID;`, and then to use it you call `new ObjectID(THE_ID)`. Be sure to add `mongodb@~3.6.0` as a dependency. You can see this in the examples below: </ins> ```js passport.serializeUser((user, done) => {commidfreeCodeCamp_pr_42297negative_passages |
| query_idq-en-freeCodeCamp-cd2e75022f114b0287b4b665a88ff8ba96c2988eaa299c1c9380abb53ad09526queryAdvanced Node and Express section needs package versions to the instructions, as discussed in: Example: \ Before this is undertaken: [x] Wait for to be merged [ ] Discuss which versions to use and how to convey this ( or )\nI am leaning more toward the requirement, myself. With the carat prefix, will install the latest minor version. In theory, updates to the minor version are backwards compatible and shouldn't create any issues with the tests or challenges. However, minor versions can include depreciation notices like . The feature will still work, but this could be confusing to a camper. Using the tilde prefix means will install the latest patch version, which includes bug fixes but shouldn't lead to any depreciation notices. I think this will offer the best long-term compatibility with our tests and challenge instructions.\nWell, it has happened: Last versions which definitely work: I have tested this. Now, discussion: 1) Just ask for to be installed 2) Also change the lesson/code to work with this latest version?\nHey how is this show stopper coming along?\nAh yes... I have updated the label, because it should have been removed by . Can a PR automatically remove an issue's label? Otherwise, this issue is still open and help wanted , as there are many packages which need their versioning fixed. If no one else, I can slot in some time for this tomorrow.\nNo rush. Thanks for confirming, I have removed the assignment since this is no longer a showstopper.\nthank you so much for the Thank you for the suggestion. It helped me alot", "positive_passages": [{"docid": "doc-en-freeCodeCamp-eb4b12f25701162b8e08d49b6ba83e5af25a53d8103a1c235b997cbed55f6077", "text": "It's time to set up *Passport* so we can finally start allowing a user to register or login to an account! In addition to Passport, we will use Express-session to handle sessions. Using this middleware saves the session id as a cookie in the client and allows us to access the session data using that id on the server. This way we keep personal account information out of the cookie used by the client to verify to our server they are authenticated and just keep the *key* to access the data stored on the server. <del> To set up Passport for use in your project, you will need to add it as a dependency first in your package.json. `\: \` </del> <ins> To set up Passport for use in your project, you will need to add it as a dependency first in your package.json. `passport@~0.4.1` </ins> <del> In addition, add Express-session as a dependency now as well. Express-session has a ton of advanced features you can use but for now we're just going to use the basics! `\"express-session\": \"^1.15.0\"` </del> <ins> In addition, add Express-session as a dependency now as well. Express-session has a ton of advanced features you can use but for now we're just going to use the basics! `express-session@~1.17.1` </ins> You will need to set up the session settings now and initialize Passport. Be sure to first create the variables 'session' and 'passport' to require 'express-session' and 'passport' respectively.commidfreeCodeCamp_pr_42297negative_passages |
| query_idq-en-freeCodeCamp-cd2e75022f114b0287b4b665a88ff8ba96c2988eaa299c1c9380abb53ad09526queryAdvanced Node and Express section needs package versions to the instructions, as discussed in: Example: \ Before this is undertaken: [x] Wait for to be merged [ ] Discuss which versions to use and how to convey this ( or )\nI am leaning more toward the requirement, myself. With the carat prefix, will install the latest minor version. In theory, updates to the minor version are backwards compatible and shouldn't create any issues with the tests or challenges. However, minor versions can include depreciation notices like . The feature will still work, but this could be confusing to a camper. Using the tilde prefix means will install the latest patch version, which includes bug fixes but shouldn't lead to any depreciation notices. I think this will offer the best long-term compatibility with our tests and challenge instructions.\nWell, it has happened: Last versions which definitely work: I have tested this. Now, discussion: 1) Just ask for to be installed 2) Also change the lesson/code to work with this latest version?\nHey how is this show stopper coming along?\nAh yes... I have updated the label, because it should have been removed by . Can a PR automatically remove an issue's label? Otherwise, this issue is still open and help wanted , as there are many packages which need their versioning fixed. If no one else, I can slot in some time for this tomorrow.\nNo rush. Thanks for confirming, I have removed the assignment since this is no longer a showstopper.\nthank you so much for the Thank you for the suggestion. It helped me alot", "positive_passages": [{"docid": "doc-en-freeCodeCamp-1899a60af6fa80e6057f5d8ca3ead84867d3ba793888ea59918cb4d9de00396a", "text": "The following challenges will make use of the `chat.pug` file. So, in your `routes.js` file, add a GET route pointing to `/chat` which makes use of `ensureAuthenticated`, and renders `chat.pug`, with `{ user: req.user }` passed as an argument to the response. Now, alter your existing `/auth/github/callback` route to set the `req.session.user_id = req.user.id`, and redirect to `/chat`. <del> Add `http` and `socket.io` as a dependency and require/instantiate them in your server defined as follows: </del> <ins> Add `socket.io@~2.3.0` as a dependency and require/instantiate it in your server defined as follows, with `http` (comes built-in with Nodejs): </ins> ```javascript const http = require('http').createServer(app);", "commid": "freeCodeCamp_pr_42297"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-fa0dd1af7040c4eaa2f6709f8b8c3e59222b55d77275348444ab208fbbd776a1", "query": "<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: The usage of the word \"argument\" ist unclear to me. The title of this challenge uses the word \"parameter\". Then the instructions state: \"If an arrow function has a single argument, the parentheses enclosing the argument may be omitted.\" But the following snippet cited from the instructions shows the parameter \"item\" without parentheses: The functions are never invoked with an argument in the examples. As I understand it the sentence should say: \"If an arrow function has a single parameter, the parentheses enclosing the parameter may be omitted.\" Add a Link to the page with the problem: or, Tell us about your browser and operating system: Browser Name: Browser Version: Operating System: If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):\nHello~! I agree that the verbiage is wrong here. should probably be replaced with in the examples and text, with the exception of the top line (which, at a quick glance, is the only correct use of ):\nThese are the ones that should be changed, I think. In fact, we could use instead.\nI like that approach. Think this could be opened up to first timers?\nI would go for: Just like a regular function, you can pass arguments into an arrow function. If an arrow function has a single parameter, the parentheses enclosing the parameter may be omitted. It is possible to pass more than one argument into an arrow function.\nSure, that works.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-e4ed96661be3312397ffa1f201f117efccb84db7cd3cec1b5164ac2c861ac3d7", "text": "```js // doubles input value and returns it const doubler = (item) => item * 2; <ins> doubler(4); // returns 8 </ins> ``` <del> If an arrow function has a single argument, the parentheses enclosing the argument may be omitted. </del> <ins> If an arrow function has a single parameter, the parentheses enclosing the parameter may be omitted. </ins> ```js <del> // the same function, without the argument parentheses </del> <ins> // the same function, without the parameter parentheses </ins> const doubler = item => item * 2; ```", "commid": "freeCodeCamp_pr_40130"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-fa0dd1af7040c4eaa2f6709f8b8c3e59222b55d77275348444ab208fbbd776a1", "query": "<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: The usage of the word \"argument\" ist unclear to me. The title of this challenge uses the word \"parameter\". Then the instructions state: \"If an arrow function has a single argument, the parentheses enclosing the argument may be omitted.\" But the following snippet cited from the instructions shows the parameter \"item\" without parentheses: The functions are never invoked with an argument in the examples. As I understand it the sentence should say: \"If an arrow function has a single parameter, the parentheses enclosing the parameter may be omitted.\" Add a Link to the page with the problem: or, Tell us about your browser and operating system: Browser Name: Browser Version: Operating System: If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):\nHello~! I agree that the verbiage is wrong here. should probably be replaced with in the examples and text, with the exception of the top line (which, at a quick glance, is the only correct use of ):\nThese are the ones that should be changed, I think. In fact, we could use instead.\nI like that approach. Think this could be opened up to first timers?\nI would go for: Just like a regular function, you can pass arguments into an arrow function. If an arrow function has a single parameter, the parentheses enclosing the parameter may be omitted. It is possible to pass more than one argument into an arrow function.\nSure, that works.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-422b7b731c2be16583751f2552d7f005f207bf536410ecebf4d827b2faa2184c", "text": "```js // multiplies the first input value by the second and returns it const multiplier = (item, multi) => item * multi; <ins> multiplier(4, 2); // returns 8 </ins> ``` </section>", "commid": "freeCodeCamp_pr_40130"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-67a91c4a4d0c2db396218c3a0d28e36827f1d5ec23d8ee48c622ec11bd023197", "query": "GitHub yesterday (November 16) which our Cypress CI depended. So, currently all Cypress tests in CI are failing. Just using the latest version of the Cypress GitHub action should do the trick. (We are currently running the outdated action.) !", "positive_passages": [{"docid": "doc-en-freeCodeCamp-3886625a88dad0216fc207bebd5bb57f0a9d19bb826c72b5500b825aef05a2fe", "text": "run: npm run seed - name: Cypress run <del> uses: cypress-io/github-action@v1 </del> <ins> uses: cypress-io/github-action@v2 </ins> with: record: ${{ env.CYPRESS_RECORD_KEY != 0 }} build: npm run build", "commid": "freeCodeCamp_pr_40253"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-37a64e2288ca916ba2918ec4345c1a80dd829600e410bd4502fbd7309ca1f75d", "query": "Describe your problem and how to reproduce it: While working on the Sudoku solver project, one scenario came up that wasn't clear to me how to handle. The scenario is what do you do, if I ask to check a value of a cell with an existing value? For my project, I chose to return a conflict with the row, column, and region. However, I checked what the example app returns. The results it returns are logically inconsistent, which tells me this use case is undefined. For the example app: https://sudoku- coordinate enter C3, for value enter 2 (the existing value), click Check Placement returns value to 9, App returns value to 1, App returns These response are not logically consistent. For the first one, it appears to be checking against all of the existing values in the puzzle. For the second and third cases, it appears to be checking after replacing the value. I would expect this use case to be defined as either, it's a conflict, because there is an existing value at that cell or to replace the value in that cell and then check if it is valid or not and return the appropriate results. Add a Link to the page with the problem: ://sudoku- Tell us about your browser and operating system: Browser Name: Google Chrome Browser Version: 87.0.4280.67 (Official Build) (x86_64) Operating System: macOS Mojave 10.14.6\nYes, seems odd that you can place a value over an existing spot and it can return as valid Seems like this should be the response Or something along those lines\nI do agree that this should be handled as a valid placement (given that the number is already present in that cell). Unless there is objection/disagreement, I'd be willing to open this up for contribution.\nI also vote to make it behave as if it replaces the cell before checking validity. Or something along those lines. I have opened this up for contributions.positive_passagesdociddoc-en-freeCodeCamp-f2c237e5455fcc8b7c437b4594c3e7fc8060bd0478b00bddcf1191e6b233e6cftext}; ``` <ins> If `value` submitted to `/api/check` is already placed in `puzzle` on that `coordinate`, the returned value will be an object containing a `valid` property with `true` if `value` is not conflicting. ```js async (getUserInput) => { const input = '..9..5.1.85.4....2432......1...69.83.9.....6.62.71...9......1945....4.37.4.3..6..'; const coordinate = 'C3'; const value = '2'; const data = await fetch(getUserInput('url') + '/api/check', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ puzzle: input, coordinate, value }) }); const parsed = await data.json(); assert.property(parsed, 'valid'); assert.isTrue(parsed.valid); }; ``` </ins> If the puzzle submitted to `/api/check` contains values which are not numbers or periods, the returned value will be `{ error:\u00a0'Invalid characters in puzzle' }` ```jscommidfreeCodeCamp_pr_41225negative_passages |
| query_idq-en-freeCodeCamp-68eff5769d3b99738bb5922c6f38676c997029a8851d3ea4d0c7e4b2484a7b70queryDescribe your problem and how to reproduce it: Challenge description gives slightly different task, to what needs to be done to pass tests. Challenge is about , which looks at the beginning like (skipping zero at start): Challenge description asks to create function returning n-th member of the sequence. However expected values in tests, and sample solution don't match that. sternBrocot(2) should return 3. sternBrocot(3) should return 5. sternBrocot(5) should return 11. sternBrocot(7) should return 19. sternBrocot(10) should return 39. Function matching tests would be one returning at which position in sequence number is encountered for first time. Original challenge on Rosetta Code - have both these variations as a part of task, so that's most likely how it sneaked in. Add a Link to the page with the problem:\nI vote to have the function return the position in the sequence of the argument. We wouldn't need to change the tests, just the description.\nI'm in favour of that approach as well.positive_passagesdociddoc-en-freeCodeCamp-329bfee8602fd18c5d1cd9f489ba54001369915817f3a8a9c572d194a2bdb531text# --instructions-- <del> Create a function that returns the $ n^{th} $ member of the sequence using the method outlined above. </del> <ins> Create a function that returns the position in the Stern-Brocot sequence at which $ n $ is first encountered, where the sequence is generated with the method outlined above. Note that this sequence uses 1 based indexing. </ins> # --hints--commidfreeCodeCamp_pr_40686negative_passages |
| query_idq-en-freeCodeCamp-a6da83dc88ae80bff1a0527505aed14b2eb31f14bbb803088f4c4cc6ca1135f1queryDescribe the bug Last week, I saw multiple posts where people asking for help didn\u2019t write down what they needed help with. I think the help post template may be confusing some folks. Screenshots ! Additional context \u201cTell us what\u2019s happening\u201d looks a bit like an overall heading. I suggest the following changes to make it more obvious that people are supposed to write something down: Mockup !\nHello there, Thank you, for taking the time to open this. I believe it would help some Campers understand the need to add more information. However, I suspect the large majority just post without reading any further. The Discourse software does have a lot of cool features aiding the topic creating (e.g. Information about informative titles, showing similar topics). If others are in agreement, this would be an easy implementation, and could be put up for first timers? That being said, I find dedent to be pesky.\nI'm not big on the idea of adding an extra heading. Perhaps just the extra describe prompt: Tell us what's happening: Describe your issue in detail here Your code so far: Your browser information: blah blah blah Mildly related - I think we should add a colon after \ to match the other headings.\nIf it's a first-timer I'll let somebody do it but if not I can take care of making the changes. Your call!\nAny decision on if we're opening this for first timers?\nCan I work on this issue, being my first contribution to freeCodeCamp?\nplease go ahead.\nHi, I saw that this issue wanted to be done by someone a few days ago, but its still not been closed, I am also an newbie and am really eager to contribute so would be happy to help, and close it today. Was trying to find the template to change it, but couldn't find the file. Would it be possible for someone to point me to the right file? Thanks :)\nHey it's this one -\nThanks", "positive_passages": [{"docid": "doc-en-freeCodeCamp-4e192e57988ec297983d0a4f32ac6f7961c1e668bce8aa7ef56ba533bcc35427", "text": "let textMessage = dedent( `**Tell us what's happening:** <ins> Describe your issue in detail here. </ins> ${ projectFormValues.lengthcommidfreeCodeCamp_pr_41849negative_passages |
| query_idq-en-freeCodeCamp-7d1c5a414db938716f86d41ecf03950afa6b7a71864f7673ba551d048fed36faqueryMaybe this was done intentionally to give learning programmers more leeway. If that's not the case though, it's a bug. Describe your problem and how to reproduce it: In the -challenge, the request clearly is to add the new tag AFTER the previous p-tag. However, the following code also gets accepted as a correct solution. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Firefox Browser Version: 87.0 (64-bit) Operating System: Linux (Linux Mint) If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! !\nI think this can go either way, but I'm leaning towards changing the directions, and removing the to give the more leeway for newcomers, to somewhat like: This is ofcourse just my opinion, I would love for others to pitch in...\nI like the change. The less explicit version seems to better describe how the page is already behaving.\nI agree that this sounds like a good change :) Maybe is the way to go, to indicate it shouldn't be over the tag.\nAs we do not want any confusion about what the element should wrap. I suggest the following: I am opening this up to first timers An issue with the help wanted or first timers only label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the\nSure, I'll do my best!\nSee . I wrote this. I changed the second line to improve it with , while still keeping it similar to the previous description.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-f5da65b7b698c03cf08d7211028b40a1f8de435001943985940af7aad6fe28f2", "text": "# --instructions-- <del> Create a second `p` element after the existing `p` element with the following kitty ipsum text: `Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.` </del> <ins> Create a second `p` element with the following kitty ipsum text: `Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.` </ins> <del> Then, create a `main` element and nest the two `p` elements inside the `main` element. </del> <ins> Then, create a `main` element and nest only the two `p` elements inside the `main` element. </ins> # --hints--", "commid": "freeCodeCamp_pr_41859"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-af5d1eec538b00eb2549e47e866512b1949fb59e357e34e9b7b4b7033f3131b7", "query": "There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved. Error type: Cannot find preset's package (githubwhitesource/merge-confidence:beta)", "positive_passages": [{"docid": "doc-en-freeCodeCamp-49034a9ff648727d91e5e08ea785dedf41a63f5edce870de2b011e029d29ab1b", "text": "{ \"matchUpdateTypes\": [\"minor\", \"patch\", \"pin\", \"digest\"], \"matchCurrentVersion\": \"!/^0/\", <del> \"automerge\": true }, { </del> <ins> \"automerge\": true, </ins> \"rebaseWhen\": \"behind-base-branch\" } ],", "commid": "freeCodeCamp_pr_41982"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-ee90e34dd48c9238c86500826dfeee57088276c313289d40e50590bfa8448518", "query": "<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. -- <!-- Add a link to the coding challenge with the problem. --<!-- Copy and paste the code from the editor that you used in between the back-ticks below: -- Expected to see Clothing withdrawal transactions (-25.55) on output but only seeing the 'transfer from food $50'. Transfer method passes but the food transfer of 50 but it is 0. <!-- Add a clear and concise description of what you expected to happen. --<!-- If applicable, add screenshots to help explain your problem. you can drag and drop, png, jpg, gif, etc. in this box. --<!-- Please complete the following information. --- Device: PC Desktop OS: Windows 10 Browser: Firefox Version: 93.0 <!-- Add any other context about the problem here. --I've since updated my transfer method to use the withdrawal and deposit functions to accomplish the task correctly. It seems the Transfer method test case needs a bit of an upgrade to make sure withdrawals are working.\nThe test for transfer function is not checking if the amount is deducted or , But only checks for the ledger entries. Adding two additional tests for deduction and addition will fix this issue.\nI tossed up a PR for this: I two asserts to the existing test.positive_passagesdociddoc-en-freeCodeCamp-7ee11c540a42eb871ded4c747de9de1f559ebb6396c3adb2728731987c310f7dtexth4.negative-10.text-nowrap Community Builder img.profile-image(src='https://s3.amazonaws.com/freecodecamp/branden-byers.jpg' alt=\) h4.text-nowrap Madison, Wisconsin <del> p.negative-10 \ </del> <ins> p.negative-10 \ </ins> .col-xs-12.col-sm-4.col-md-3.team-member h3.negative-10.text-nowrap Michael Johnson h4.negative-10.text-nowrap Nonprofit CoordinatorcommidfreeCodeCamp_pr_10negative_passages |
| query_idq-en-freeCodeCamp-ee90e34dd48c9238c86500826dfeee57088276c313289d40e50590bfa8448518query<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. -- <!-- Add a link to the coding challenge with the problem. --<!-- Copy and paste the code from the editor that you used in between the back-ticks below: -- Expected to see Clothing withdrawal transactions (-25.55) on output but only seeing the 'transfer from food $50'. Transfer method passes but the food transfer of 50 but it is 0. <!-- Add a clear and concise description of what you expected to happen. --<!-- If applicable, add screenshots to help explain your problem. you can drag and drop, png, jpg, gif, etc. in this box. --<!-- Please complete the following information. --- Device: PC Desktop OS: Windows 10 Browser: Firefox Version: 93.0 <!-- Add any other context about the problem here. --I've since updated my transfer method to use the withdrawal and deposit functions to accomplish the task correctly. It seems the Transfer method test case needs a bit of an upgrade to make sure withdrawals are working.\nThe test for transfer function is not checking if the amount is deducted or , But only checks for the ledger entries. Adding two additional tests for deduction and addition will fix this issue.\nI tossed up a PR for this: I two asserts to the existing test.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-5cb615338fcb8302f75d5ce15a360adfc4a7c7902ec3e12247ce9db8c01e81b6", "text": "h4.negative-10.text-nowrap Live Content Manager img.profile-image(src='https://s3.amazonaws.com/freecodecamp/jason-rueckert.jpg' alt=\"Jason Rueckert's picture\My high school job was testing basketball shoes for Nike. I learned code to work smarter, not harder. I have no thyroid.\My high school job was testing basketball shoes for Nike. I learned code to work smarter, not harder. I have no thyroid.\, : }], : []} |
| {: , : , : [{: , : , : }], : []} |
| {: , : , : [{: , : , : }], : []} |
| {: , : , : [{: , : , : }], : []} |
| {: , : , : [{: , : , : }], : []} |
| {: , : , : [{: , : , : }], : []} |
| {: , : , : [{: , : , : }], : []} |
| {: , : , : [{: , : , : }], : []} |
| {: , : bracket notation\you should not have spacing\, : [{: , : , : }], : []} |
| {: , : Gender\Sex\Gender\, : [{: , : /forgot\, : }], : []} |
| {: , : Gender\Sex\Gender\, : [{: , : , : }], : []} |
| {: , : , : [{: , : , : }], : []} |
| {: , : , : [{: , : , : }], : []} |
| {: , : , : [{: , : , : }], : []} |
| {: , : , : [{: , : , : }], : []} |
| {: , : , : [{: , : , : }], : []} |
| {: , : , : [{: , : , : }], : []} |
| {: , : of\front of it\first-time\, : [{: , : , : }], : []} |
| {: , : reminder - the format of a media-query is (media-rule: value)\, : [{: , : , : }], : []} |
| {: , : , : [{: , : )en1s*>/i)); </del> <ins> assert(code.match(/<htmls+langs*=s*('|\")en1s*>/gi)); </ins> ``` You should have a closing `<html>` tag. Remember that closing tags have a `/` following the opening `<` bracket.", "commid": "freeCodeCamp_pr_46700"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-df6182c7220b486a368676ad8dc72bc41f4ae27ef9a251f7fc1331bd8fdd20bd", "query": "The challenge text mentions Ryan but there is no Ryan. We should only mention parts of the example that exist, ideally. No response All No response\nwow. Ryan was exist? that is interesting.\nThanks for opening this issue. This looks something that can be fixed by \"first time\" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-b6b7494f8d011f468fc8fb65931b033c3f5d220b6932563ebe680bedaf447b53", "text": "} ``` <del> This would log `Alan`, `Jeff`, `Sarah`, and `Ryan` - each value on its own line. </del> <ins> This would log `Alan`, `Jeff`, and `Sarah` - each value on its own line. </ins> In this statement, we defined a variable `user`, and as you can see, this variable was reset during each iteration to each of the object's keys as the statement looped through the object, resulting in each user's name being printed to the console.", "commid": "freeCodeCamp_pr_46832"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-dad59d4a629eb1617ab6ae4b2f4b788b4880b54d983318072c9d77768dce572a", "query": "There are three tests that test for non-empty labels: \"Your #name-label should not be empty.\" \"Your #email-label should not be empty.\" \"Your #number-label should not be empty.\" I think the word \"empty\" is slightly ambiguous here. These tests appear to be looking for actual text inside the label. But if the user nests an inside the label without text then the isn't exactly empty: The above will fail because there is no actual text in the but I can see how the user would not think the is empty. N/A Adjust the test descriptions so they clarify that text needs to be inside the . Perhaps something like: \. No response N/A No response\nPlease make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first. Happy contributing.positive_passagesdociddoc-en-freeCodeCamp-ded1f09381db90cf2b30ab44e4ed775ae2caeded0d4be98554f3957526e2577dtextassert(!!el && el.tagName === 'LABEL') ``` <del> Your `#name-label` should not be empty </del> <ins> Your `#name-label` should contain text that describes the input. </ins> ```js const el = document.getElementById('name-label') assert(!!el && el.innerText.length > 0) ``` <del> Your `#email-label` should not be empty </del> <ins> Your `#email-label` should contain text that describes the input. </ins> ```js const el = document.getElementById('email-label') assert(!!el && el.innerText.length > 0) ``` <del> Your `#number-label` should not be empty </del> <ins> Your `#number-label` should contain text that describes the input. </ins> ```js const el = document.getElementById('number-label')commidfreeCodeCamp_pr_46896negative_passages |
| query_idq-en-freeCodeCamp-dad59d4a629eb1617ab6ae4b2f4b788b4880b54d983318072c9d77768dce572aqueryThere are three tests that test for non-empty labels: \ \ \ I think the word \ is slightly ambiguous here. These tests appear to be looking for actual text inside the label. But if the user nests an inside the label without text then the isn't exactly empty: The above will fail because there is no actual text in the but I can see how the user would not think the is empty. N/A Adjust the test descriptions so they clarify that text needs to be inside the . Perhaps something like: \"Your #name-label should contain text that describes the input\". No response N/A No response\nPlease make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first. Happy contributing.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-66c8b120ddd73f3de61d0832acb4e6a9b8b87a2c8264744adb15ef38afdc9a44", "text": "assert(!!el && el.tagName === 'LABEL') ``` <del> Your `#name-label` should not be empty. </del> <ins> Your `#name-label` should contain text that describes the input. </ins> ```js const el = document.getElementById('name-label') assert(!!el && el.innerText.length > 0) ``` <del> Your `#email-label` should not be empty. </del> <ins> Your `#email-label` should contain text that describes the input. </ins> ```js const el = document.getElementById('email-label') assert(!!el && el.innerText.length > 0) ``` <del> Your `#number-label` should not be empty. </del> <ins> Your `#number-label` should contain text that describes the input. </ins> ```js const el = document.getElementById('number-label')", "commid": "freeCodeCamp_pr_46896"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-0fdff6d3d52e60383a90cdd02ea2790557efc98adc06de133ac93ff08ece83da", "query": "challenge-editor should be to the \"How to work on practice projects\" documentation here:\nI'll tackle this today.positive_passagesdociddoc-en-freeCodeCamp-ac8b61bbe5d203925705df15eb65f93c6787131e72ce40e385c9a9bd8897209atext# How to Work on Practice Projects <ins> Our practice projects use a step-based approach to teach concepts to campers. A project will consist of multiple files, which we refer to as **\**. These files are named by the challenge ID, to avoid issues with the translation flow. Unfortunately, this makes it difficult to find the file associated with a specific step. We've built a challenge editor tool that helps remedy this. This tool allows you to navigate the available projects, and the steps for each project (in order). There's also an embedded code editor you can use to work on the files directly. ## Using the Challenge Editor These instructions will tell you how to use our challenge editor tool to work on the practice projects. ### Starting the Editor To start the editor, make sure you are in the root freecodecamp directory. Then, run `npm run challenge-editor` to start both the client and the API that powers the editor. The client will run on port `3300`, so you can access it at `http://localhost:3300`. The API runs on port `3200`, to avoid conflicts with the learn client and server. This will allow you to run the freeCodeCamp application at the same time as the editor, so you can test your changes locally. ### Navigating the Editor The default view will list the available `superblocks` - these are the certifications. Click on the certification link you want to work on. This will take you to the list of blocks. These are the practice projects. Click on the project link you want to work on. This will take you to a list of steps for the project. If you are working on an existing step, you can click on the step link to open the editor. If you are adding or removing steps, click the `Use the step tools` link to switch to the step tools for that challenge. ### Editing Steps When you click on a step, you'll be taken to the editor. This is a basic text editor that offers syntax highlighting. After you have made your changes, click the `Save Changes` button to save your changes. You will get a browser alert letting you know that your changes are ready to commit. Note that you'll need to use `git` manually to stage and commit your files - this tool will not do that for you. ### Step Tools When you click the `Use the step tools` link, you'll be taken to the step tools page. This allows you to add or remove steps from the project. #### Create Next Step Clicking this button will add a new step at the end of the project. This step will use the previous step's code as the seed. #### Create Empty Steps Enter the number of steps you want to add in the input. Then, clicking the button will create that many empty steps at the end of the project. #### Insert Step Enter the step number that you want to add a step _after_. For example, if you want to add a step after `step-12`, enter `12`. Then, click the `Insert Step` button to add the step. The following steps will be re-ordered. #### Delete Step Enter the step number you want to delete. Then click the `Delete Step` button to remove that step. This will automatically update the step numbers for the remaining steps. #### Update Step Titles You should not have to use this tool unless you've manually deleted or added steps. This tool will reorder the step numbers. ## Using the Scripts Manually If you want to work on the steps manually, in your local IDE, you can run the step management scripts directly. </ins> The `tools/challenge-helper-scripts` folder contains tools to help facilitate the creation and maintenance of the freeCodeCamp project-based curriculum. <del> ## Create a new project </del> <ins> ### Create a new project </ins> <del> Run `npm run create-project`. This opens up a command line ui that guides you through the process. Once that has finished, there should be a new challenge in the English curriculum that you can use for the first step of the project. For example, if you created a project called `test-project` in the Responsive Web Design certification, it would be in `curriculum/challenges/english/01-responsive-web-design/test-project`. </del> <ins> Run `npm run create-project` from the root directory. This opens up a command line ui that guides you through the process. Once that has finished, there should be a new challenge in the English curriculum that you can use for the first step of the project. For example, if you created a project called `test-project` in the Responsive Web Design certification, it would be in `curriculum/challenges/english/01-responsive-web-design/test-project`. </ins> If you want to create new steps, the following tools simplify that process. <del> ## create-next-step </del> <ins> ### create-next-step </ins> A one-off script that will automatically add the next step based on the last step in the project. The challenge seed code will use the previous step's challenge seed code. <del> ### How to run script: </del> <ins> #### How to run script: </ins> 1. Change to the directory of the project. 2. Run the following npm command:commidfreeCodeCamp_pr_46993negative_passages |
| query_idq-en-freeCodeCamp-0fdff6d3d52e60383a90cdd02ea2790557efc98adc06de133ac93ff08ece83daquerychallenge-editor should be to the \ documentation here:\nI'll tackle this today.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-3eb0b0c5f00d78420d609b0f0047d471967781b6536881e648aa2e2a026446f0", "text": "npm run create-next-step ``` <del> ## create-empty-steps </del> <ins> ### create-empty-steps </ins> A one-off script that automatically adds a specified number of steps. The challenge seed code for all steps created will be empty. **Note:** This script also runs [update-step-titles](#update-step-titles). <del> ### How to run script: </del> <ins> #### How to run script: </ins> 1. Change to the directory of the project. 2. Run the following npm command:", "commid": "freeCodeCamp_pr_46993"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-0fdff6d3d52e60383a90cdd02ea2790557efc98adc06de133ac93ff08ece83da", "query": "challenge-editor should be to the \"How to work on practice projects\" documentation here:\nI'll tackle this today.positive_passagesdociddoc-en-freeCodeCamp-d615c8477c0ed8ad7031a91229de37c876d692f5e844206cab6b7b611c1c4276textnpm run create-empty-steps X # where X is the number of steps to create. ``` <del> ## insert-step </del> <ins> ### insert-step </ins> A one-off script that automatically adds a new step at a specified position, incrementing all subsequent steps (both their titles and in their meta.json). The challenge seed code will use the previous step's challenge seed code with the editable region markers (ERMs) removed. **Note:** This script also runs [update-step-titles](#update-step-titles). <del> ### How to run script: </del> <ins> #### How to run script: </ins> 1. Change to the directory of the project. 2. Run the following npm command:", "commid": "freeCodeCamp_pr_46993"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-0fdff6d3d52e60383a90cdd02ea2790557efc98adc06de133ac93ff08ece83da", "query": "challenge-editor should be to the \"How to work on practice projects\" documentation here:\nI'll tackle this today.positive_passagesdociddoc-en-freeCodeCamp-7b35e6681bfce7a1d7a5836fc2323f529a004132c9b6d2d71f3e6d941f7b46e5textnpm run insert-step X # where X is the position to insert the new step. ``` <del> ## delete-step </del> <ins> ### delete-step </ins> A one-off script that deletes an existing step, decrementing all subsequent steps (both their titles and in their meta.json) **Note:** This script also runs [update-step-titles](#update-step-titles). <del> ### How to run script </del> <ins> #### How to run script </ins> 1. Change to the directory of the project. 2. Run the following npm command:commidfreeCodeCamp_pr_46993negative_passages |
| query_idq-en-freeCodeCamp-0fdff6d3d52e60383a90cdd02ea2790557efc98adc06de133ac93ff08ece83daquerychallenge-editor should be to the \ documentation here:\nI'll tackle this today.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-783671bb6af22ae3bfc7f968ba37891e47bfec53aa541fb5154096a3cd50a065", "text": "npm run delete-step X # where X is the step number to be deleted. ``` <del> ## update-step-titles </del> <ins> ### update-step-titles </ins> A one-off script that automatically updates the frontmatter in a project's markdown files so that they are consistent with the project's meta.json. It ensures that each step's title (and dashedName) match the meta's challengeOrder. <del> ### How to run script </del> <ins> #### How to run script </ins> 1. Change to the directory of the project. 2. Run the following npm command:", "commid": "freeCodeCamp_pr_46993"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-30e6a8e64878128b0d314be65a6e4da78cc25444df2b62d946acfac9df330a24", "query": "in step 21 of building a piano project, the hint in line 30 is missing code blocks This should be changed to If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first. Happy contributing.\nI believe I did all this right. This is my first time contributing to open source. Very exciting :))", "positive_passages": [{"docid": "doc-en-freeCodeCamp-6bb37e7f626c77a612e1f2abbc161c3729f2de4dc1920e04a24d37ef1308937f", "text": "assert(img?.previousElementSibling === null); ``` <del> Your `img` element should have a `class` set to logo. </del> <ins> Your `img` element should have a `class` set to `logo`. </ins> ```js const img = document.querySelector('img');", "commid": "freeCodeCamp_pr_47016"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-a59d3501288551bf707f4b3b32ccb2d2a76baeb1dfa13adece3eb47180c04ad0", "query": "There is a typo in Understand BCrypt Hashes, is used instead of . Here is the typo If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first. Happy contributing.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-1481c6de585ef4590c47126c794824b41e28ee660333dd21fb666868d5433377", "text": "Add all your code for these lessons in the `server.js` file between the code we have started you off with. Do not change or delete the code we have added for you. <del> BCrypt has already been added as a dependency, so require it ad `bcrypt` in your server. </del> <ins> BCrypt has already been added as a dependency, so require it as `bcrypt` in your server. </ins> Submit your page when you think you've got it right.commidfreeCodeCamp_pr_47076negative_passages |
| query_idq-en-freeCodeCamp-82667795931f7b2612de039ff1d1d746a2bd03504b84276afe17aff1e6c29b21queryIt says that plot 1 should have an x label of Month, but it's the second plot that is monthly. It should say that plot 2 should have that xlabel. It should say that plot 2 should have an xlabel of Years It's testing correctly, so it should be an issue only with the assert message ! Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response\nsame thing for the ylabel in plot 2 actually, it says plot 1 there too\nHello, It seems that same thing is for the \.\nI am opening this for contribution. The PR has to be done on the boilerplate:positive_passagesdociddoc-en-freeCodeCamp-7ee11c540a42eb871ded4c747de9de1f559ebb6396c3adb2728731987c310f7dtexth4.negative-10.text-nowrap Community Builder img.profile-image(src='https://s3.amazonaws.com/freecodecamp/branden-byers.jpg' alt=\) h4.text-nowrap Madison, Wisconsin <del> p.negative-10 \ </del> <ins> p.negative-10 \ </ins> .col-xs-12.col-sm-4.col-md-3.team-member h3.negative-10.text-nowrap Michael Johnson h4.negative-10.text-nowrap Nonprofit CoordinatorcommidfreeCodeCamp_pr_10negative_passages |
| query_idq-en-freeCodeCamp-82667795931f7b2612de039ff1d1d746a2bd03504b84276afe17aff1e6c29b21queryIt says that plot 1 should have an x label of Month, but it's the second plot that is monthly. It should say that plot 2 should have that xlabel. It should say that plot 2 should have an xlabel of Years It's testing correctly, so it should be an issue only with the assert message ! Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response\nsame thing for the ylabel in plot 2 actually, it says plot 1 there too\nHello, It seems that same thing is for the \.\nI am opening this for contribution. The PR has to be done on the boilerplate:positive_passagesdociddoc-en-freeCodeCamp-5cb615338fcb8302f75d5ce15a360adfc4a7c7902ec3e12247ce9db8c01e81b6texth4.negative-10.text-nowrap Live Content Manager img.profile-image(src='https://s3.amazonaws.com/freecodecamp/jason-rueckert.jpg' alt=\) h4.text-nowrap Seattle, Washington <del> p.negative-10 \ </del> No newline at end of file <ins> p.negative-10 \ </ins>commidfreeCodeCamp_pr_10negative_passages |
| query_idq-en-freeCodeCamp-eeb507e0cc2f904517a215f8a786c9a69667cd3fc0f8e4675416fe0696b7ed77queryit should be --important <-- instead of import Learn Bash Scripting by Building Five Programs False. An important operator in that menu is =~. It allows for pattern matching. Using the same syntax but with this operator, check if hello contains the pattern el. ! Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response\nI'll fix this! Just for reference, I will be fixing this issue in repository.\nHey guys! I'm getting this error when typing in the terminal. Anyone know how to fix? I created a seperate branch that is up to date.\nFor generating file, the coderoad cli requires for the version branch to exist locally. Detailed guidelines how to contribute to these tutorials can be found on Please refer to the parts about making changes on the branch. Thank you and happy coding!\nPerfect. I have the typo fixed and ill make that branch work with coderoad. Thank you for your patiencepositive_passagesdociddoc-en-freeCodeCamp-dad0a4b262dc4235b2c1376f04c31ad3a83a220eb7453dd1060254954b83fdb8text} ]); <ins> profileValidation.controller('nonprofitFormController', ['$scope', function($scope) { } ]); </ins> profileValidation.directive('uniqueUsername', function($http) { return { restrict: 'A',commidfreeCodeCamp_pr_23negative_passages |
| query_idq-en-freeCodeCamp-eeb507e0cc2f904517a215f8a786c9a69667cd3fc0f8e4675416fe0696b7ed77queryit should be --important <-- instead of import Learn Bash Scripting by Building Five Programs False. An important operator in that menu is =~. It allows for pattern matching. Using the same syntax but with this operator, check if hello contains the pattern el. ! Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response\nI'll fix this! Just for reference, I will be fixing this issue in repository.\nHey guys! I'm getting this error when typing in the terminal. Anyone know how to fix? I created a seperate branch that is up to date.\nFor generating file, the coderoad cli requires for the version branch to exist locally. Detailed guidelines how to contribute to these tutorials can be found on Please refer to the parts about making changes on the branch. Thank you and happy coding!\nPerfect. I have the typo fixed and ill make that branch work with coderoad. Thank you for your patiencepositive_passagesdociddoc-en-freeCodeCamp-615a9817ca5b7872114006a926e51c51974eeb85c821f4a943a2a63e71828c46textli • Understand that they will build your project using JavaScript frameworks (as opposed to older or proprietary tools) li • Keep your expectations high. Our students' goal is to produce work that's up to your standards h3 If you're OK with these terms, great! We'd love to help you! Fill in this form and we'll get right back to you. <del> form.form-horizontal(role='form', action=\"/nonprofits/\", method='POST') </del> <ins> form.form-horizontal(role='form', action=\"/nonprofits/\", method='POST', novalidate='novalidate', name='nonprofitForm') </ins> input(type='hidden', name='_csrf', value=_csrf) .form-group <del> label(class='col-sm-2 control-label', for='name') Your name </del> <ins> label(class='col-sm-2 control-label', for='name') Your name * </ins> .col-sm-8 <del> input.form-control(type='text', name='name', id='name') </del> <ins> input.form-control(type='text', name='name', id='name', autocomplete=\"off\", ng-model='name', required='required') .col-sm-8.col-sm-offset-2(ng-show=\"nonprofitForm.name.$invalid && nonprofitForm.name.$error.required && !nonprofitForm.name.$pristine\") alert(type='danger') span.ion-close-circled(id='#name-error') | Your name is required. </ins> .form-group <del> label(class='col-sm-2 control-label', for='email') Your email </del> <ins> label(class='col-sm-2 control-label', for='email') Your email * </ins> .col-sm-8 <del> input.form-control(type='text', name='email', id='email') </del> <ins> input.form-control(type='text', name='email', id='email', autocomplete=\"off\", ng-model='email', required='required') .col-sm-8.col-sm-offset-2(ng-show=\"nonprofitForm.email.$invalid && nonprofitForm.email.$error.required && !nonprofitForm.email.$pristine\") alert(type='danger') span.ion-close-circled(id='#email-error'). Your email is required. </ins> .form-group <del> label(class='col-sm-2 control-label', for='message') Briefly describe what problem you need to solve, and for whom. </del> <ins> label(class='col-sm-2 control-label', for='message') Briefly describe what problem you need to solve, and for whom. * </ins> .col-sm-8 <del> textarea.form-control(type='text', name='message', id='message', rows='7') </del> <ins> textarea.form-control(type='text', name='message', id='message', rows='7', autocomplete=\"off\", ng-model='message', required='required') .col-sm-8.col-sm-offset-2(ng-show=\"nonprofitForm.message.$invalid && nonprofitForm.message.$error.required && !nonprofitForm.message.$pristine\") alert(type='danger') span.ion-close-circled(id='#message-error') | Your message is required. </ins> .form-group .col-sm-offset-2.col-sm-8 <del> button.btn.btn-primary(type='submit') </del> <ins> button.btn.btn-primary(type='submit', ng-disabled='nonprofitForm.$invalid') </ins> span.ion-paper-airplane <del> | Submit </del> <ins> | Submit </ins> No newline at end of file", "commid": "freeCodeCamp_pr_23"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-e02dce190a185a289d9417c2c17da4e0d4f1ba762360dd83a4bf7873d7075cdf", "query": "In this line, there is a missing code block around word false It should be like this here is the file: If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Happy contribution.\nI opened pull request", "positive_passages": [{"docid": "doc-en-freeCodeCamp-fea0de6a400f157168f6bd806ae49e7b5d2c4e41accc621ee978ab5c36dc6958", "text": "**Examples** <del> `3 == '3'` returns `true` because JavaScript performs type conversion from string to number. `3 === '3'` returns false because the types are different and type conversion is not performed. </del> <ins> `3 == '3'` returns `true` because JavaScript performs type conversion from string to number. `3 === '3'` returns `false` because the types are different and type conversion is not performed. </ins> **Note:** In JavaScript, you can determine the type of a variable or a value with the `typeof` operator, as follows:", "commid": "freeCodeCamp_pr_47506"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-31bb7435217889f2d07f7191ba41a186ed8ca1a9e7922fc8ba1e4e80e7e9aba9", "query": "A camper mentioned in his comment, that this icon below indicate to them that it's an external link not a popup. ! We can change it to clearer icon that show, that it's a popup. The original comment for context:\nI found it interesting, that say you should use ellipsis (\u2026) when there is some additional action required after the action (popup, dialog, confirmation) and it isn't clear by the action itself. This doesn't mean you should use an ellipsis whenever an action displays another window only when additional information is required to perform the action. Consequently, any command button whose implicit verb is to \"show another window\" doesn't take an ellipsis, such as with the commands About, Advanced, Help (or any other command linking to a Help topic), Options, Properties, or Settings. So maybe an ellipsis of some kind: in button's label or in the icon? More so, it's a part of too. If we were to stick with keeping an icon regardless, this regular feels like a better choice, with the arrow denoting there would be some kind of external interface but the enclosed square representing that it is not an external redirection, thus denoting some kind of popup or modal.\nI think these guides are saying that the ellipses should be when the button opens a window that requires the user to enter more information or perform another action. This isn't the case here, so I don't think they are warranted in this instance. If we want to use a new icon then I would suggest we use one that has . I'm not suggesting that we use this exact icon. This is just an example of what I'm suggesting.\nI second the use of some kind of variation of that icon. There's a small issue though, there's no such icon in the font awesome library for this so we'll have to find a different way to implement this.\nFont awesome has an icon that could have the same meaning: Alternatively Material Icons has a specific preview icon if these can be used?\ncan you assign me this task?\nissues with label, aren't open for contribution yet. You can however browse the label help wanted for open issues\nallright sir\nBoth and both are plausible.\nI'd suggest we should move forward to replace the icon with the icon. Should I move ahead and send over a PR? This is the output - !\nSure. Just make sure we don't need to add other dependencies to get that icon.positive_passagesdociddoc-en-freeCodeCamp-6fe5886ea225b25523730ccf288d056648d6a64afc2fcb50a218a0f6b23036f0textimport React from 'react'; <del> import { faExternalLinkAlt } from '@fortawesome/free-solid-svg-icons'; </del> <ins> import { faWindowRestore } from '@fortawesome/free-solid-svg-icons'; </ins> import { FontAwesomeIcon } from '@fortawesome/react-fontawesome'; import { useTranslation } from 'react-i18next'; import EditorTabs from './editor-tabs';commidfreeCodeCamp_pr_48169negative_passages |
| query_idq-en-freeCodeCamp-31bb7435217889f2d07f7191ba41a186ed8ca1a9e7922fc8ba1e4e80e7e9aba9queryA camper mentioned in his comment, that this icon below indicate to them that it's an external link not a popup. ! We can change it to clearer icon that show, that it's a popup. The original comment for context:\nI found it interesting, that say you should use ellipsis (\u2026) when there is some additional action required after the action (popup, dialog, confirmation) and it isn't clear by the action itself. This doesn't mean you should use an ellipsis whenever an action displays another window only when additional information is required to perform the action. Consequently, any command button whose implicit verb is to \ doesn't take an ellipsis, such as with the commands About, Advanced, Help (or any other command linking to a Help topic), Options, Properties, or Settings. So maybe an ellipsis of some kind: in button's label or in the icon? More so, it's a part of too. If we were to stick with keeping an icon regardless, this regular feels like a better choice, with the arrow denoting there would be some kind of external interface but the enclosed square representing that it is not an external redirection, thus denoting some kind of popup or modal.\nI think these guides are saying that the ellipses should be when the button opens a window that requires the user to enter more information or perform another action. This isn't the case here, so I don't think they are warranted in this instance. If we want to use a new icon then I would suggest we use one that has . I'm not suggesting that we use this exact icon. This is just an example of what I'm suggesting.\nI second the use of some kind of variation of that icon. There's a small issue though, there's no such icon in the font awesome library for this so we'll have to find a different way to implement this.\nFont awesome has an icon that could have the same meaning: Alternatively Material Icons has a specific preview icon if these can be used?\ncan you assign me this task?\nissues with label, aren't open for contribution yet. You can however browse the label help wanted for open issues\nallright sir\nBoth and both are plausible.\nI'd suggest we should move forward to replace the icon with the icon. Should I move ahead and send over a PR? This is the output - !\nSure. Just make sure we don't need to add other dependencies to get that icon.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-bc2f2fd3e2007aa685bb3ed37b2a3380f886aa109bd6c99dd0f38c7fccbafa92", "text": "onClick={() => togglePane('showPreviewPortal')} > <span className='sr-only'>{getPreviewBtnsSrText().portal}</span> <del> <FontAwesomeIcon icon={faExternalLinkAlt} /> </del> <ins> <FontAwesomeIcon icon={faWindowRestore} /> </ins> </button> </div> </div>", "commid": "freeCodeCamp_pr_48169"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-96104283f9a4fbf0245de80ba67e4fcab39ca33c00194478086c584d94e603fc", "query": "The declaration of arr doesn\u2019t need to be guarded by \u2018Do Not Change\u2019 comments. There exist many solutions (3 in the guide) that do not need that variable declaration. These comments should be removed or at least moved. All No response\n. I lean towards the second option of having only the comments within the function and no extra starter code.\nI was thinking something simplier We've ditched a lot of these comments in the rest of the intermediate algorithm challenges. Does the comment help us at all here?\nProbably not. I honestly would not even put the . At this point in the curriculum, users should know the function needs to have a statement and they can craft their own.\nSure, then the fix would be: This looks like a good first-timer issue.\nThanks for opening this issue. This looks like something that can be fixed by \ code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.positive_passagesdociddoc-en-freeCodeCamp-27e2990f887bf9234015676789fde56949759d858006da04a1716d9d21e7bafctext```js function whatIsInAName(collection, source) { <del> const arr = []; // Only change code below this line // Only change code above this line return arr; </del> } whatIsInAName([{ first: \, last: \ }, { first: \, last: null }, { first: \, last: \ }], { last: \ });commidfreeCodeCamp_pr_48531negative_passages |
| query_idq-en-freeCodeCamp-f2df56c6b5ccb3dd109432bad9073886bbbbffb4fcf93cdbfeddd369375d3375queryIn step 31 of the Learn HTML Forms by Building a Registration Form project, the step doesn't explicitly say that it wants the input element to be nested inside the label element. Instead it says: \"Add a label with the text Upload a profile picture: , and add an input accepting a file upload.\" This could be interpreted to mean that the input element should be on the right side of the label element. Only when we attempt this are we told by the Hint \"You should nest an input element inside the label element.\" To clarify the requirement, the step should use the word nest in the exercise as below for eg.: \"Add a label with the text Upload a profile picture: , and nest an input accepting a file upload within it.\", The step should explicitly state that the input element should be nested within the new label element. No response Not Applicable No response\nI think if all of the challenges will have specifications defined explicitly, it will serve no purpose of \"challenging\" the learners to really think and solve it. In the first place, the solution is already implied from the given code and then, if the learners will still have the hard time solving it, then the feature will definitely do its job.\nAgreed. The instructions should be clear to begin with. Making the users guess what the test requires isn't a \, it's just rude.\nFor what it is worth, the camper has nested an input in a label element a few times in this challenge prior to this step. I am not against adding this reminder to the instructions, but I don't want to lose sight of our goal to keep the instructions more lean and have the hints serve as the reminders.\nDefinitely. But I looked back at the instructions on the steps where they add the previous inputs and we do explicitly tell them to put the input within the label: step 17: Nest an input element within each label. step 25: within each of the first two label elements, add one input element with type=\. If we can add that information to those instructions then I think we can add it to this one. And let me just clarify that what I am really concerned about is this correct solution being rejected: I'm working under the assumption that correct code should always pass. So we need to tell the user that only a nested input will pass if that's all the test will accept.\nI understand that if someone is working on a series of steps they may not need to be told to nest the input again. However, if they stop and return to the project a few weeks later on, they may not remember that. The hint will remind them sure. I guess this is a minor issue given the hint is quite clear. Personally I like a more explicit instruction.positive_passagesdociddoc-en-freeCodeCamp-f678d913a9c384b61db3b7855ce4bdcebf5ce5ed24a956fee9e3cc649c8333aetextMoving on to the final `fieldset`. What if you wanted to allow a user to upload a profile picture? <del> Well, the `input` type `file` allows just that. Add a `label` with the text `Upload a profile picture: `, and add an `input` accepting a file upload. </del> <ins> Well, the `input` type `file` allows just that. Add a `label` with the text `Upload a profile picture: `, and nest an `input` accepting a file upload. </ins> # --hints--commidfreeCodeCamp_pr_48887negative_passages |
| query_idq-en-freeCodeCamp-4ae32381e7fdcedfea9d2c64ed8d264c8027509309386e343995d92b893daffequeryin step 53, the span elements are missing code elements. Here is the file We can add elements, to both of them. Like step 43: Or delete the first one and add code elements to the second one, but reading previous issues, I think campers may delete both elements wrapping the text and create one that wraps both the text. Note: that sentence is hard to work with in Arabic, and require adding nuances, because the structure of two code elements following each other which is weird in RTL layout.positive_passagesdociddoc-en-freeCodeCamp-ead547d4cbf04d1a800d229ecd6dbce9c452b89ba1bcf4e905ed0383f5e339f3text# --description-- <del> After your last `.divider`, create a new `p` element with the text `Cholesterol 0mg 0%`. Wrap the text `Cholesterol` in a `span` element, and give that `span` element the `class` attribute set to `bold`. Wrap the text `0%` in another `span` element, with the `class` set to `bold`. Finally, nest the `Cholesterol` and `0mg` span elements inside an additional span element for alignment. </del> <ins> After your last `.divider`, create a new `p` element with the text `Cholesterol 0mg 0%`. Wrap the text `Cholesterol` in a `span` element, and give that `span` element the `class` attribute set to `bold`. Wrap the text `0%` in another `span` element, with the `class` set to `bold`. Finally, nest the `Cholesterol` and `0mg` `span` elements inside an additional `span` element for alignment. </ins> # --hints--commidfreeCodeCamp_pr_49195negative_passages |
| query_idq-en-freeCodeCamp-a2da53959672c93226540a0c8a867da2453f772128c7d623321490260f6a9706queryThe following sentence in the Word Blanks lesson should have a code block (three backticks) surrounding the code section which is directly referring to the completed code block below it on the page. Instead of: Consider this sentence - It was really , and we ourselves . It should say: Consider this sentence - The sentence has been translated because of the missing code blocks (and will not make sense as it's a direct reference to the actual code shown below it) The sentence with the blanks should be in a code block that does not wrap. (three backticks above and below it) Instead of: Consider this sentence - It was really , and we ourselves . It becomes: Consider this sentence - No response n/a No response\nQuestion for those in the know. Do we have a way to keep content from being translated that doesn't involve using the triple back tick code block? I would be cool to use sr-only text \ (or something similar) for those underlines to represent missing text. But we can't do that using the code blocks since they are wrapped in a .\nDo they get wrapped in a if they're inline code?\nIt looks like they are just wrapped in strong tags in crowdin at least. I don't see a pre tag.\npre sounds like a plausible idea. We should go ahead with that.\nThe challenge require the sentence to not be translated, and element don't stop translation, it gives the choice to the translation to translate or not, which isn't ideal. Here is the file, to solve this issue, change the structure of the sentence to md It was really , and we ourselves . ` If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our prolific contributors will guide you through this.\nnope, but we can open an issue for this yes\nCan you assign me this issue\nOnly issues with the or label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the", "positive_passages": [{"docid": "doc-en-freeCodeCamp-fae528ec0aebda4209409ad5f2705729d72d74704455eae1761848b16d80a556", "text": "You are provided sentences with some missing words, like nouns, verbs, adjectives and adverbs. You then fill in the missing pieces with words of your choice in a way that the completed sentence makes sense. <del> Consider this sentence - It was really **____**, and we **____** ourselves **____**. This sentence has three missing pieces- an adjective, a verb and an adverb, and we can add words of our choice to complete it. We can then assign the completed sentence to a variable as follows: </del> <ins> Consider this sentence: ```md It was really ____, and we ____ ourselves ____. ``` This sentence has three missing pieces- an adjective, a verb and an adverb, and we can add words of our choice to complete it. We can then assign the completed sentence to a variable as follows: </ins> ```js const sentence = \"It was really \" + \"hot\" + \", and we \" + \"laughed\" + \" ourselves \" + \"silly\" + \".\";", "commid": "freeCodeCamp_pr_49779"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-ce818bd978147d43529b257bb183bb45ffc7191c6c2eb679f3224889a46baf7b", "query": "instead of the example command should be: docshow-to-add-cypress- project dependencies to run will see error: instead of the example command should be: No response", "positive_passages": [{"docid": "doc-en-freeCodeCamp-2749f69335b8746dbdc79c93d660cd8f3cb937c2d0ea27ba49b1e8cb6c906572", "text": "For example: ```console <del> pnpm run cypress -- run --spec=cypress/e2e/default/landing.js </del> <ins> pnpm run cypress -- run --spec=cypress/e2e/default/landing.ts </ins> ``` - To create a development build, start the development server, and run all existing cypress end-to-end tests:", "commid": "freeCodeCamp_pr_50027"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-f9cd58cb25280d2deb8301f0687764fd29dc1bec4c1fbfc7ba429a9d8e784782", "query": "This part is still tripping people up Usually one piece or another gets lost: Maybe this is clearer Side note - I still don't love the fact that we say like a variable instead of like a string literal. I think that's confusing here. (I know, I know, the style guide hates \"s) No response All No response\nAgreed, it has the potential to be confusing. Can we reword to say: \"If is the string and ...\"\nI'm still not clear on the reason why string literals in inline code blocks are forbidden by the style guide since it makes the instructions less clear in this case. do you have some context?\nI don't remember the full reason, only that it was a decision made as part of our i18n efforts. We reference a discussion in but I can't for the life of me find where that discussion is.positive_passagesdociddoc-en-freeCodeCamp-1ca92af9c7a9318709265cb74c7f2dd9e6afbdc2298cfc70b1f31d9bc73c6e15text- Your function must always return the entire `records` object. - If `value` is an empty string, delete the given `prop` property from the album. - If `prop` isn't `tracks` and `value` isn't an empty string, assign the `value` to that album's `prop`. <del> - If `prop` is `tracks` and value isn't an empty string, add the `value` to the end of the album's `tracks` array. You need to create this array first if the album does not have a `tracks` property. </del> <ins> - If `prop` is `tracks` and `value` isn't an empty string, you need to update the album's `tracks` array. First, if the album does not have a `tracks` property, assign it an empty array. Then add the `value` as the last item in the album's `tracks` array. </ins> **Note:** A copy of the `recordCollection` object is used for the tests. You should not directly modify the `recordCollection` object.commidfreeCodeCamp_pr_50203negative_passages |
| query_idq-en-freeCodeCamp-53592109330c779128e66264d8319434f8545026b44d41ad6e62a4e860f4d2a9queryIn the new JS curriculum I found a couple of example where comments have been inside code blocks in the challenge description. These comments are not translatable on Crowdin: We should avoid commenting code blocks or make those comments accessible from Crowdinpositive_passagesdociddoc-en-freeCodeCamp-f0f9a99e53b0b02ade166a47ad6dc6c65271f0f6e64333827b0de2284fe98072text```js switch (expression) { case 1: <del> /* this code will execute if the case matches the expression */ </del> <ins> console.log(\); </ins> break; default: <del> /* the default will execute if none of the other cases match the expression */ </del> <ins> console.log(\); </ins> } ``` <ins> In this example, the first `case` checks if `expression === 1`, and if so logs `1` to the console. If no cases are true, it will log `Not 1` to the console. The `break` statement stops execution of the `switch` when the `case` is true. </ins> Add a `switch` statement and use `e.target.value` for the expression. # --hints--commidfreeCodeCamp_pr_50254negative_passages |
| query_idq-en-freeCodeCamp-53592109330c779128e66264d8319434f8545026b44d41ad6e62a4e860f4d2a9queryIn the new JS curriculum I found a couple of example where comments have been inside code blocks in the challenge description. These comments are not translatable on Crowdin: We should avoid commenting code blocks or make those comments accessible from Crowdinpositive_passagesdociddoc-en-freeCodeCamp-7acb64986e1690e0ae409c489ae11b0b31fa2803d204c1c4a1a3632863aed9detext```js case \: <del> // code goes here </del> <ins> console.log(\); </ins> break; ```commidfreeCodeCamp_pr_50254negative_passages |
| query_idq-en-freeCodeCamp-53ecc40b1a9b775a4578f7b9b5384e2765ff7f1bf634da41daed7431857c7951queryThe setup instructions here suggest that I need MongoDB Community Server | 4.2.x. I've tried through docker and through macos homebrew instructions and can't get any 4.2 version. 4.4.x is available. Is that acceptable? If so, should I update this doc? Try to follow one of options for setting up MongoDB Community Server | 4.2.x Maybe 4.4.x is ok? No response\ni searched the tags on docker and no 4.2 is available. this article suggests other ways but the result is always\ni found this pr which suggests that 4.4 should work fine. so i guess i should update the docs? you agree?\nor there are other docker images available of 4.2.x. But people trying to follow directions won't get to them if we point them to starting from here: because mongo only points to their docker images.\ni also see that in there are docker instructions there. should i use that or is that for something different?\nHi thanks for the issue. We recommend asking around in our chat and forum when you are troubleshooting. The docs need to be updated to the version we are using right now. I have created a PR. It will be available soon at I hope this helps.\nI see that the docs have been updated to mongo 5.0. But maybe should the docs point to as the best way to set up mongo? That's what I used and it seems like the easiest option.\nThanks for pointing that out. The directory is a newer API in the works. It will have a full docker-based setup that is more convenient than the current workflow. We will release cleaner and easy-to-follow docs when that happens. Meanwhile we will stick to the docs you see at:positive_passagesdociddoc-en-freeCodeCamp-95f402ebd3099445318f9a80ef518ed55cb077b996320b6df5b516cbbe18143ftext| --------------------------------------------------------------------------------------------- | ------- | ------------------------------------------------------------------------------------------- | | [Node.js](http://nodejs.org) | `18.x` | We use the \ version, See [LTS Schedule](https://nodejs.org/en/about/releases/). | | [pnpm](https://pnpm.io/installation) | `8.x` | - | <del> | [MongoDB Community Server](https://docs.mongodb.com/manual/administration/install-community/) | `4.2.x` | - | </del> <ins> | [MongoDB Community Server](https://docs.mongodb.com/manual/administration/install-community/) | `5.0.x` | - | </ins> > [!ATTENTION] > If you have a different version, please install the recommended version. We can only support installation issues for recommended versions. See [troubleshooting](#troubleshooting) for details.commidfreeCodeCamp_pr_50492negative_passages |
| query_idq-en-freeCodeCamp-efc1044f1fe01397b30fe4eab8c0cbdfe3964f3cb62f3b6e15094fa9fdb020c8queryThe formula given for converting from C to F is given as a) But this can also be written as b) These two formulas are producing different results. Using for (which is used in the tests) we get: a) b) If formula is used then the tests for this challenge will fail due to the floating point rounding issue. The tests should pass regardless of where C is placed in the formula. Either we need to do a little rounding in the tests or replace with a different number in the tests that won't produce different results depending on the placement of C in the formula. No response Device: Desktop OS: Linux/Fedora 36 Browser: Firefox Version: 112 No response", "positive_passages": [{"docid": "doc-en-freeCodeCamp-22ef9c21fa3a3e2289de8986c8da7650c0a5b86e0c478fce071e5f24a4eadbf6", "text": "`Thermostat` should be a `class` with a defined `constructor` method. ```js <del> assert( typeof Thermostat === 'function' && typeof Thermostat.constructor === 'function' ); </del> <ins> assert.isFunction(Thermostat); assert.isFunction(Thermostat?.constructor); </ins> ``` <del> `class` keyword should be used. </del> <ins> The `class` keyword should be used. </ins> ```js <del> assert(code.match(/class/g)); </del> <ins> assert.match(code, /class/); </ins> ``` `Thermostat` should be able to be instantiated. ```js <del> assert( (() => { const t = new Thermostat(122); return typeof t === 'object'; })() ); </del> <ins> const _t = new Thermostat(122); assert.isObject(_t); </ins> ``` When instantiated with a Fahrenheit value, `Thermostat` should set the correct `temperature`. ```js <del> assert( (() => { const t = new Thermostat(122); return t.temperature === 50; })() ); </del> <ins> const _t = new Thermostat(122); assert.strictEqual(_t?.temperature, 50); </ins> ``` A `getter` should be defined. ```js <del> assert( (() => { const desc = Object.getOwnPropertyDescriptor( Thermostat.prototype, 'temperature' ); return !!desc && typeof desc.get === 'function'; })() ); </del> <ins> const _desc = Object.getOwnPropertyDescriptor(Thermostat.prototype, 'temperature'); assert.isFunction(_desc?.get); </ins> ``` A `setter` should be defined. ```js <del> assert( (() => { const desc = Object.getOwnPropertyDescriptor( Thermostat.prototype, 'temperature' ); return !!desc && typeof desc.set === 'function'; })() ); </del> <ins> const _desc = Object.getOwnPropertyDescriptor(Thermostat.prototype, 'temperature'); assert.isFunction(_desc?.set); </ins> ``` Calling the `setter` with a Celsius value should set the `temperature`. ```js <del> assert( (() => { const t = new Thermostat(32); t.temperature = 26; const u = new Thermostat(32); u.temperature = 50; return t.temperature === 26 && u.temperature === 50; })() ); </del> <ins> const _t = new Thermostat(32); _t.temperature = 26; const _u = new Thermostat(32); _u.temperature = 50; assert.approximately(_t.temperature, 26, 0.1); assert.approximately(_u.temperature, 50, 0.1); </ins> ``` # --seed--", "commid": "freeCodeCamp_pr_50560"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-e0493aef6c4dd2464d6a92c9352a4d33febc0843c2fba40a141a85b296196240", "query": "As i love free code ; I would like to inform the problem and stay as minimal as i can. staight on problem. in : Responsive Web Design Learn More About CSS Pseudo Selectors By Building A Balance SheetQUALITY CONTROL DEGRADING CODE ROBUSTNESS. 47: <tr class=\"data\"48: <thSavings <span class=\"description\"Funds set aside for emergencies.</span</th49: <td650</td51: <td 500</td<td728</td<---------- answered passed without this line of code. </tr! ! Device: [Asus f17 gaming] OS: [ Windows 11] Browser: [Chrome] thanks for such a go tutorial platform!\nHi thanks for the report. Could you share your full code here so that we can dig into what's going wrong?\nEdit: I backticks for clarity.\nThanks for sharing that but the code you shared passes the tests. That's expected, since it has in the correct place. If I remove then it fails, as it should. From your screenshot, it looked like you'd entered invalid code (i.e. without ) and managed to pass the tests. However, I've been unable to replicate this behaviour. If you have an example of invalid code that passes, could you share it here?\nfirst screen shot mentions step 15, the second one shows 16. Isn't the issue in the step 16?\nbut it is there in step 16 code\nyes in hurry i was not able to give accurate problem details. IT IS IN STEP 16 THANKS BRO\nSilly me newbie.\nOkay, that makes sense, thanks for clarifying. To fix this, there needs to be one more test that asserts that is set on the third element.\nsir did u get what i want to say? as if not possible is it allowed to express it on video call? if okay so? like on ms teams.\nHey we understand the issue and have a pull request open to address it. Thank you for reporting. We will get the fix in as soon as we canpositive_passagesdociddoc-en-freeCodeCamp-6412129831e23c5d265bf19174b860a59a76696ba5c60afabbbefc2daf7fc1d2textassert(document.querySelector('tbody')?.querySelectorAll('tr')?.[3]?.querySelectorAll('td')?.[2]?.textContent === '$809'); ``` <ins> Your third `td` element should have the `class` attribute set to `current`. ```js assert(document.querySelector('tbody')?.querySelectorAll('tr')?.[3]?.querySelectorAll('td')?.[2]?.classList?.contains('current')); ``` </ins> # --seed-- ## --seed-contents--commidfreeCodeCamp_pr_50799negative_passages |
| query_idq-en-freeCodeCamp-88d0a0e1c500b9f01bed1e6a43c440b3437d715f8a2f9cd432a6d1227434699fqueryThe test variable here should be prefaced with an or something like that to prevent colliding with a common user variable name. Valid code should pass No response All No response_\nFrom the individual tests: can be moved to the . This alone would be enough to make it not affected by such collision. Additionally using underscore after that, while not necessary also would be fine.\nThis is entirely user written code above. The user's choice of variable name conflicts with the variable name in the test suite, so we need to use a less common variable name in the test suite. A leading underscore is how I've seen that done in most challenges.\nWhoops - this one was my fault haha.\nTo confirm the fix: Within the , all instances of the variable in the tests should be changed to .\nI have this minor fix Please review Thankspositive_passagesdociddoc-en-freeCodeCamp-460b8c03dcf14196e327e5e7a4c3a0adb82adf9b7859c2feb6d57ff1e8f6eb52textNo properties should be added. `Object.keys(Person).length` should always return 6. ```js <del> const person = new Person('Bob', 'Ross'); person.setFirstName('Haskell'); person.setLastName('Curry'); person.setFullName('John', 'Smith'); assert.lengthOf(Object.keys(person), 6); </del> <ins> const _person = new Person('Bob', 'Ross'); _person.setFirstName('Haskell'); _person.setLastName('Curry'); _person.setFullName('John', 'Smith'); assert.lengthOf(Object.keys(_person), 6); </ins> ``` You should be able to instantiate your `Person` object. ```js <del> const person = new Person('Bob', 'Ross'); assert.instanceOf(person, Person); </del> <ins> const _person = new Person('Bob', 'Ross'); assert.instanceOf(_person, Person); </ins> ``` Your `Person` object should not have a `firstName` property. ```js <del> const person = new Person('Bob', 'Ross'); assert.notProperty(person, 'firstName'); </del> <ins> const _person = new Person('Bob', 'Ross'); assert.notProperty(_person, 'firstName'); </ins> ``` Your `Person` object should not have a `lastName` property. ```js <del> const person = new Person('Bob', 'Ross'); assert.notProperty(person, 'lastName'); </del> <ins> const _person = new Person('Bob', 'Ross'); assert.notProperty(_person, 'lastName'); </ins> ``` The `.getFirstName()` method should return the string `Bob`. ```js <del> const person = new Person('Bob', 'Ross'); assert.strictEqual(person.getFirstName(), 'Bob'); </del> <ins> const _person = new Person('Bob', 'Ross'); assert.strictEqual(_person.getFirstName(), 'Bob'); </ins> ``` The `.getLastName()` should return the string `Ross`. ```js <del> const person = new Person('Bob', 'Ross'); assert.strictEqual(person.getLastName(), 'Ross'); </del> <ins> const _person = new Person('Bob', 'Ross'); assert.strictEqual(_person.getLastName(), 'Ross'); </ins> ``` The `.getFullName()` method should return the string `Bob Ross`. ```js <del> const person = new Person('Bob', 'Ross'); assert.strictEqual(person.getFullName(), 'Bob Ross'); </del> <ins> const _person = new Person('Bob', 'Ross'); assert.strictEqual(_person.getFullName(), 'Bob Ross'); </ins> ``` The `.getFullName()` method should return the string `Haskell Ross` after calling `.setFirstName('Haskell')`. ```js <del> const person = new Person('Bob', 'Ross'); person.setFirstName('Haskell'); assert.strictEqual(person.getFullName(), 'Haskell Ross'); </del> <ins> const _person = new Person('Bob', 'Ross'); _person.setFirstName('Haskell'); assert.strictEqual(_person.getFullName(), 'Haskell Ross'); </ins> ``` The `.getFullName()` method should return the string `Bob Curry` after calling `.setLastName('Curry')`. ```js <del> const person = new Person('Bob', 'Ross'); person.setLastName('Curry'); assert.strictEqual(person.getFullName(), 'Bob Curry'); </del> <ins> const _person = new Person('Bob', 'Ross'); _person.setLastName('Curry'); assert.strictEqual(_person.getFullName(), 'Bob Curry'); </ins> ``` The `.getFullName()` method should return the string `Haskell Curry` after calling `.setFullName('Haskell', 'Curry')`. ```js <del> const person = new Person('Bob', 'Ross'); person.setFullName('Haskell', 'Curry'); assert.strictEqual(person.getFullName(), 'Haskell Curry'); </del> <ins> const _person = new Person('Bob', 'Ross'); _person.setFullName('Haskell', 'Curry'); assert.strictEqual(_person.getFullName(), 'Haskell Curry'); </ins> ``` The `.getFirstName()` method should return the string `Haskell` after calling `.setFullName('Haskell', 'Curry')`. ```js <del> const person = new Person('Bob', 'Ross'); person.setFullName('Haskell', 'Curry'); assert.strictEqual(person.getFirstName(), 'Haskell'); </del> <ins> const _person = new Person('Bob', 'Ross'); _person.setFullName('Haskell', 'Curry'); assert.strictEqual(_person.getFirstName(), 'Haskell'); </ins> ``` The `.getLastName()` method should return the string `Curry` after calling `.setFullName('Haskell', 'Curry')`. ```js <del> const person = new Person('Bob', 'Ross'); person.setFullName('Haskell', 'Curry'); assert.strictEqual(person.getLastName(), 'Curry'); </del> <ins> const _person = new Person('Bob', 'Ross'); _person.setFullName('Haskell', 'Curry'); assert.strictEqual(_person.getLastName(), 'Curry'); </ins> ``` The `.getFullName()` method should return the string `Emily Martinez de la Rosa` after calling `.setFullName('Emily Martinez', 'de la Rosa')`. ```js <del> const person = new Person('Bob', 'Ross'); person.setFullName('Emily Martinez', 'de la Rosa'); assert.strictEqual(person.getFullName(), 'Emily Martinez de la Rosa'); </del> <ins> const _person = new Person('Bob', 'Ross'); _person.setFullName('Emily Martinez', 'de la Rosa'); assert.strictEqual(_person.getFullName(), 'Emily Martinez de la Rosa'); </ins> ``` The `.getFirstName()` property should return the string `Emily Martinez` after calling `.setFullName('Emily Martinez', 'de la Rosa')`. ```js <del> const person = new Person('Bob', 'Ross'); person.setFullName('Emily Martinez', 'de la Rosa'); assert.strictEqual(person.getFirstName(), 'Emily Martinez'); </del> <ins> const _person = new Person('Bob', 'Ross'); _person.setFullName('Emily Martinez', 'de la Rosa'); assert.strictEqual(_person.getFirstName(), 'Emily Martinez'); </ins> ``` The `.getLastName()` property should return the string `de la Rosa` after calling `.setFullName('Emily Martinez', 'de la Rosa')`. ```js <del> const person = new Person('Bob', 'Ross'); person.setFullName('Emily Martinez', 'de la Rosa'); assert.strictEqual(person.getLastName(), 'de la Rosa'); </del> <ins> const _person = new Person('Bob', 'Ross'); _person.setFullName('Emily Martinez', 'de la Rosa'); assert.strictEqual(_person.getLastName(), 'de la Rosa'); </ins> ``` # --seed--commidfreeCodeCamp_pr_51355negative_passages |
| query_idq-en-freeCodeCamp-1868101fab42b0bcda017e628d7d2740abd2abf09983a6f8f1996d7be7354877queryThe English curriculum was as an upcoming change. A new \ style challenge was created for it. When you go to one of these challenges and try to type an , it doesn't show up (sometimes). If you type it really quickly after a different character, it does show up. I'm quite sure the hotkeys are interfering - if you turn them off, the problem goes away. The is the one that we noticed, but there could be other characters that have this issue as well. Fill in the blank style challenges the codebase with the upcoming changes shown to one of the fill in the blank challenges: http://localhost:8000/learn/a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/right to type an in the blank, it doesn't work of keyboard shortcuts in settings, it does work All keys to work all the time. Related discussion:", "positive_passages": [{"docid": "doc-en-freeCodeCamp-f92871f515bb61ac744596c49ef7f21f872b237e7702c0f9fb92c7354d871781", "text": "<Spacer size='medium' /> <h2>{t('learn.fill-in-the-blank')}</h2> <Spacer size='small' /> <del> <ObserveKeys> </del> <ins> {/* what we want to observe is ctrl/cmd + enter, but ObserveKeys is buggy and throws an error if it encounters a key combination, so we have to pass in the individual keys to observe */} <ObserveKeys only={['ctrl', 'cmd', 'enter']}> </ins> <div> <p> {splitSentence.map((s, i) => {", "commid": "freeCodeCamp_pr_52544"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-ee18ceb9bcccd91edf8c9ff247c3bd6380d5696be795f2f5564c3d5e35a7c882", "query": "The following valid code does not pass for of calorie counter project. The issue is with this line here If you remove the semicolon then the test will pass We will need to fix the test to make semicolons optional so the camper can pass with or without semicolons. here is the file you need to fix Please read through the docs first. And we don't assign issues. If you are interested in working on this, work on the fix and create a PR. Happy coding! This code does not pass even though it is valid Semicolons should be optional and the code above should pass No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No responsepositive_passagesdociddoc-en-freeCodeCamp-97dde888a7865cd221a867e9cb05a7bc727c0f57a9cf860e9f9ca518b9788b2ftextYour `for` loop should `push` `strArray[i]` to `cleanStrArray`. ```js <del> assert.match(code, /fors*(s*(let|var)s+is*=s*0s*;s*is*<s*strArray.lengths*;s*is*++s*)s*{s*ifs*(![(\|')-3s*,s*(\"|')s4s*].includes(s*strArray[i]s*))s*{s*cleanStrArray.push(s*strArray[i]s*)s*}/); </del> <ins> assert.match(code, /fors*(s*(let|var)s+is*=s*0s*;s*is*<s*strArray.lengths*;s*is*++s*)s*{s*ifs*(![(\|')-3s*,s*(\"|')s4s*].includes(s*strArray[i]s*))s*{s*cleanStrArray.push(s*strArray[i]s*)s*;?s*}/); </ins> ``` # --seed--commidfreeCodeCamp_pr_52690negative_passages |
| query_idq-en-freeCodeCamp-bf925e5510cd94fe8882e5a5fc8e56b560da73e3ab9030679837a119e65438cdqueryThe test is failing if there isn't a space between and . This fails: Test should pass without a space between and . No response N/A No response", "positive_passages": [{"docid": "doc-en-freeCodeCamp-9350ff34c81f33c584f6da6079b46f550f10a7e3d2abf5b18e0477dbfa5bb9a9", "text": "You should add an `else` block to the existing `if` block. ```js <del> assert.match(code, /ifs*(userData?.currentSongs*===s*nulls*||s*userData?.currentSong.ids*!==s*song.id)s*{s*audio.currentTimes*=s*0;?s*}s*elses{/) </del> <ins> assert.match(code, /ifs*(userData?.currentSongs*===s*nulls*||s*userData?.currentSong.ids*!==s*song.id)s*{s*audio.currentTimes*=s*0;?s*}s*elses*{/) </ins> ``` You should set `audio.currentTime` to `userData.songCurrentTime` inside the `else` block of your `if` statement. ```js <del> assert.match(code, /ifs*(userData?.currentSongs*===s*nulls*||s*userData?.currentSong.ids*!==s*song.id)s*{s*audio.currentTimes*=s*0;?s*}s*elses{s*audio.currentTimes*=s*userData.songCurrentTime;?s*}/) </del> <ins> assert.match(code, /ifs*(userData?.currentSongs*===s*nulls*||s*userData?.currentSong.ids*!==s*song.id)s*{s*audio.currentTimes*=s*0;?s*}s*elses*{s*audio.currentTimes*=s*userData.songCurrentTime;?s*}/) </ins> ``` # --seed--", "commid": "freeCodeCamp_pr_52817"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-f9bb0b76e1d1baecb3f89f97bb1398c552090346a8726cc608dc62daa37b8e2e", "query": "The fill-in-the-blank sentence doesn't match what the character says. The written sentence is: The character says: Note the \, instead of \. No response Device: all OS: all Browser: all Version: all No response\nThank you for reporting the issue. Note for maintainers: Step 54 () uses \ instead of \ in the quiz. I think it's fine as-is since there isn't associated audio/caption text, but I'd vote updating it, too, for consistency. This issue is open to first-time code contributors to this repository. Requirements: In Change the text in the tag from to In Change the text in the tag from to Change the fill-in-the-blank text from to Change the backtick placement in the description text from ` In Change the text of the answers from to Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.\nHi I've created a PR addressing these changes.positive_passagesdociddoc-en-freeCodeCamp-9dfc8d84e7346c3f5edc67819232eee98538b2c6d1e3b3e3387bf514809bfae3textdashedName: task-50 --- <del> <!-- (audio) Tom: Those are great traits for someone in her position, I think. What does she do as our team lead? --> </del> <ins> <!-- (audio) Tom: Those are great traits for someone in her position, I think. What does she do as the team lead? --> </ins> # --description--commidfreeCodeCamp_pr_53038negative_passages |
| query_idq-en-freeCodeCamp-f9bb0b76e1d1baecb3f89f97bb1398c552090346a8726cc608dc62daa37b8e2equeryThe fill-in-the-blank sentence doesn't match what the character says. The written sentence is: The character says: Note the \"the\", instead of \"our\". No response Device: all OS: all Browser: all Version: all No response\nThank you for reporting the issue. Note for maintainers: Step 54 () uses \"our\" instead of \"the\" in the quiz. I think it's fine as-is since there isn't associated audio/caption text, but I'd vote updating it, too, for consistency. This issue is open to first-time code contributors to this repository. Requirements: In Change the text in the tag from to In Change the text in the tag from to Change the fill-in-the-blank text from to Change the backtick placement in the description text from ` In Change the text of the answers from to Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.\nHi I've created a PR addressing these changes.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-50ae99ed20d62cf795810476927eec3e04c3b65164a195b45db67e5ad995a8b7", "text": "## --answers-- <del> `What do she does as our team lead?` </del> <ins> `What do she does as the team lead?` </ins> ### --feedback--", "commid": "freeCodeCamp_pr_53038"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-f9bb0b76e1d1baecb3f89f97bb1398c552090346a8726cc608dc62daa37b8e2e", "query": "The fill-in-the-blank sentence doesn't match what the character says. The written sentence is: The character says: Note the \, instead of \. No response Device: all OS: all Browser: all Version: all No response\nThank you for reporting the issue. Note for maintainers: Step 54 () uses \ instead of \ in the quiz. I think it's fine as-is since there isn't associated audio/caption text, but I'd vote updating it, too, for consistency. This issue is open to first-time code contributors to this repository. Requirements: In Change the text in the tag from to In Change the text in the tag from to Change the fill-in-the-blank text from to Change the backtick placement in the description text from ` In Change the text of the answers from to Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.\nHi I've created a PR addressing these changes.positive_passagesdociddoc-en-freeCodeCamp-288d7ce9223278f76d1ad0a638eb4c7131a78dac45ed6e799658a2acf9d3b3f3text--- <del> `What does he does as our team lead?` </del> <ins> `What does he does as the team lead?` </ins> ### --feedback--commidfreeCodeCamp_pr_53038negative_passages |
| query_idq-en-freeCodeCamp-f9bb0b76e1d1baecb3f89f97bb1398c552090346a8726cc608dc62daa37b8e2equeryThe fill-in-the-blank sentence doesn't match what the character says. The written sentence is: The character says: Note the \"the\", instead of \"our\". No response Device: all OS: all Browser: all Version: all No response\nThank you for reporting the issue. Note for maintainers: Step 54 () uses \"our\" instead of \"the\" in the quiz. I think it's fine as-is since there isn't associated audio/caption text, but I'd vote updating it, too, for consistency. This issue is open to first-time code contributors to this repository. Requirements: In Change the text in the tag from to In Change the text in the tag from to Change the fill-in-the-blank text from to Change the backtick placement in the description text from ` In Change the text of the answers from to Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.\nHi I've created a PR addressing these changes.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-a6dac553ef5bcf533bd5c3f450cfb08b4fb961697a6b671a06e2de70e3edda10", "text": "--- <del> `What do he does as our team lead?` </del> <ins> `What do he does as the team lead?` </ins> ### --feedback--", "commid": "freeCodeCamp_pr_53038"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-f9bb0b76e1d1baecb3f89f97bb1398c552090346a8726cc608dc62daa37b8e2e", "query": "The fill-in-the-blank sentence doesn't match what the character says. The written sentence is: The character says: Note the \, instead of \. No response Device: all OS: all Browser: all Version: all No response\nThank you for reporting the issue. Note for maintainers: Step 54 () uses \ instead of \ in the quiz. I think it's fine as-is since there isn't associated audio/caption text, but I'd vote updating it, too, for consistency. This issue is open to first-time code contributors to this repository. Requirements: In Change the text in the tag from to In Change the text in the tag from to Change the fill-in-the-blank text from to Change the backtick placement in the description text from ` In Change the text of the answers from to Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.\nHi I've created a PR addressing these changes.positive_passagesdociddoc-en-freeCodeCamp-20bdea9f47a6a2d85a10a31b827c31dca3c918732120380e653d93a03e324f0ctext--- <del> `What does she do as our team lead?` </del> <ins> `What does she do as the team lead?` </ins> ## --video-solution--commidfreeCodeCamp_pr_53038negative_passages |
| query_idq-en-freeCodeCamp-f9bb0b76e1d1baecb3f89f97bb1398c552090346a8726cc608dc62daa37b8e2equeryThe fill-in-the-blank sentence doesn't match what the character says. The written sentence is: The character says: Note the \"the\", instead of \"our\". No response Device: all OS: all Browser: all Version: all No response\nThank you for reporting the issue. Note for maintainers: Step 54 () uses \"our\" instead of \"the\" in the quiz. I think it's fine as-is since there isn't associated audio/caption text, but I'd vote updating it, too, for consistency. This issue is open to first-time code contributors to this repository. Requirements: In Change the text in the tag from to In Change the text in the tag from to Change the fill-in-the-blank text from to Change the backtick placement in the description text from ` In Change the text of the answers from to Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.\nHi I've created a PR addressing these changes.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-752b2e24371b4f06a812009bb711c540111623589eea5596f413c6a4922e125a", "text": "dashedName: task-55 --- <del> <!-- (audio) Tom: Those are great traits for someone in her position, I think. What does she do as our team lead? --> </del> <ins> <!-- (audio) Tom: Those are great traits for someone in her position, I think. What does she do as the team lead? --> </ins> # --description-- <del> Now you will practice listening for the correct form of `do.` Listen carefully to how Tom asks about Maria's job as a team lead. </del> <ins> Now you will practice listening for the correct form of `do`. Listen carefully to how Tom asks about Maria's job as a team lead. </ins> # --instructions--", "commid": "freeCodeCamp_pr_53038"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-f9bb0b76e1d1baecb3f89f97bb1398c552090346a8726cc608dc62daa37b8e2e", "query": "The fill-in-the-blank sentence doesn't match what the character says. The written sentence is: The character says: Note the \, instead of \. No response Device: all OS: all Browser: all Version: all No response\nThank you for reporting the issue. Note for maintainers: Step 54 () uses \ instead of \ in the quiz. I think it's fine as-is since there isn't associated audio/caption text, but I'd vote updating it, too, for consistency. This issue is open to first-time code contributors to this repository. Requirements: In Change the text in the tag from to In Change the text in the tag from to Change the fill-in-the-blank text from to Change the backtick placement in the description text from ` In Change the text of the answers from to Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.\nHi I've created a PR addressing these changes.positive_passagesdociddoc-en-freeCodeCamp-9c9ff29ae2c51e3cb29bd30b06fcf9adcc5fd130cfa771c979f1ad1586cc107atext## --sentence-- <del> `Those are great traits for someone in her position, I think. What _ she _ as our team lead?` </del> <ins> `Those are great traits for someone in her position, I think. What _ she _ as the team lead?` </ins> ## --blanks--commidfreeCodeCamp_pr_53038negative_passages |
| query_idq-en-freeCodeCamp-fa9d3d896a8feac20b08a2cd7a9fd968b1fe213b20a2af22d9ab18db419f1a62querySo the problem is that the \u201chint\u201d where it tells you what you should\u2019ve have coded it tells you that you should have \u201cdata\u201d as key, when you code that and it doesn\u2019t work it tells you you should have \u201cmyTaskArr\u201d as key, but that\u2019s wrong it should tell you \u201cmyTaskArr\u201d as \u201cvalue\u201d. So I was trying to have 2 keys, and obviously it was always wrong. The hint should tell you that \ is a value, not a key as it currently says. ! Device: Desktop PC OS: Windows 10 Browser: Edge Version: [e.g. 22] 120.0.2210.121\nNote: Due to PR adding one more step, earlier in this project, the relevant step in codebase is 49 now. Although that change did not yet reach the production at this time.positive_passagesdociddoc-en-freeCodeCamp-4f7a5b40d00ea67c7ef4336cc27bce1629ef21a559d8974da062deb3500c2b43textassert.match(code, /localStorage.setItem((\|')data1,s*myTaskArr);?/)", "commid": "freeCodeCamp_pr_53173"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-a9a20e6fb4828abe2d97db8f2a0dbd64d972923038d3879afd3152d7f904ea02", "query": "The description here is missing backticks for the number zero. Here is the new updated description. This has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the Here is the correct file that needs to be updated. Note: Even though the file says step 62 instead of step 63 that is on the site, this is still the correct file that needs updating. We recently made changes to the ordering and those changes haven't shown up yet on the live site. Happy coding see explanation above see explanation above No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response\nStep 145 has the same issue here Here is the file that needs to be updated here is the correct use of backticks for the number zero in the last sentence herepositive_passagesdociddoc-en-freeCodeCamp-e425bbdac185dd58ecf5fec4beae2ed8b5f276c9b15bbd62ae4c67cacb57f88btextPass in only the first element of the `locations` array by adding `[0]` at the end of the variable. For example: `myFunction(arg[0]);`. <del> This is called <dfn>bracket notation</dfn>. Values in an array are accessed by index. Indices are numerical values and start at 0 - this is called zero-based indexing. `arg[0]` would be the first element in the `arg` array. </del> <ins> This is called <dfn>bracket notation</dfn>. Values in an array are accessed by index. Indices are numerical values and start at `0` - this is called zero-based indexing. `arg[0]` would be the first element in the `arg` array. </ins> # --hints--commidfreeCodeCamp_pr_53243negative_passages |
| query_idq-en-freeCodeCamp-a9a20e6fb4828abe2d97db8f2a0dbd64d972923038d3879afd3152d7f904ea02queryThe description here is missing backticks for the number zero. Here is the new updated description. This has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the Here is the correct file that needs to be updated. Note: Even though the file says step 62 instead of step 63 that is on the site, this is still the correct file that needs updating. We recently made changes to the ordering and those changes haven't shown up yet on the live site. Happy coding see explanation above see explanation above No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response\nStep 145 has the same issue here Here is the file that needs to be updated here is the correct use of backticks for the number zero in the last sentence here", "positive_passages": [{"docid": "doc-en-freeCodeCamp-5ef7dedf806b7fdb07c5f693505e991a4526e3340503b2f25c1d37214bc2508f", "text": "The attack of the monster will be based on the monster's `level` and the player's `xp`. In the `getMonsterAttackValue` function, use `const` to create a variable called `hit`. Assign it the equation `(level * 5) - (Math.floor(Math.random() * xp));`. <del> This will set the monster's attack to five times their `level` minus a random number between 0 and the player's `xp`. </del> <ins> This will set the monster's attack to five times their `level` minus a random number between `0` and the player's `xp`. </ins> # --hints--", "commid": "freeCodeCamp_pr_53243"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-07d4a66ff07b253f027cbf2a27d3a6c0ff3f63bb8e279ef0254900dc17fa5e4a", "query": "Describe the bug Task 37 requires typing in one of the blanks. This can be problematic due to the letter, which might not be present in the used keyboard layout. Expected behavior I don't want to say to use completely different word for the fill the blank, as at some point there might be no other choice. There could be some kind way to ease up procuring of the letter in question, for example including it in the feedback, so it can be copied.\nHi I would love to work on this. If someone could point me in the right direction, that would be amazing!\nHi Thank you for being eager to contribute. This issue has not been triaged yet. Feel free to share your insights and ideas on the matter. However as far as the code contributing, take a look at the issues with label. Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Thank you and happy coding.\nYes, I think in both of those challenges we can update the \ in the feedback to: \\nI will open the issue to contribution with this as the solutionpositive_passagesdociddoc-en-freeCodeCamp-193ada1f903cb72746ea0ceaefdf6085db19a14c4ba4822b395ba0498f59178atext### --feedback-- <del> Places where you can buy and eat food. Don't forget the stress mark. </del> <ins> Places where you can buy and eat food. Don't forget the stress mark (`\u00e9`). </ins> # --scene--commidfreeCodeCamp_pr_53945negative_passages |
| query_idq-en-freeCodeCamp-07d4a66ff07b253f027cbf2a27d3a6c0ff3f63bb8e279ef0254900dc17fa5e4aqueryDescribe the bug Task 37 requires typing in one of the blanks. This can be problematic due to the letter, which might not be present in the used keyboard layout. Expected behavior I don't want to say to use completely different word for the fill the blank, as at some point there might be no other choice. There could be some kind way to ease up procuring of the letter in question, for example including it in the feedback, so it can be copied.\nHi I would love to work on this. If someone could point me in the right direction, that would be amazing!\nHi Thank you for being eager to contribute. This issue has not been triaged yet. Feel free to share your insights and ideas on the matter. However as far as the code contributing, take a look at the issues with label. Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Thank you and happy coding.\nYes, I think in both of those challenges we can update the \"Don't forget the stress mark.\Don't forget the stress mark ().\"\nI will open the issue to contribution with this as the solution", "positive_passages": [{"docid": "doc-en-freeCodeCamp-e9b4a6ac98179f12ce325c81c9b6ab14551c26d3b54f3288e080ac2444141ea0", "text": "### --feedback-- <del> Places to eat or drink. Don't forget the stress mark. </del> <ins> Places to eat or drink. Don't forget the stress mark (`\u00e9`). </ins> ---", "commid": "freeCodeCamp_pr_53945"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-aeb123045e55ed3ca93a0b150d76e7738cb3f868f6a3f9473295b5db406483ea", "query": "A camper on the forum had issues with passing step 37 of the pyramid project This was their code Their code is correct but the tests expect a certain order of The tests should be updated to expect either correct answer see explanation above see explanation above No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response\nconst character = \"#\"; const count = 8; const rows = []; for (let i = 0; i < count; i = i + 1) { (i); } let result = \"\" for (const row of rows) { result = + ; (result); } This worked for me, it took a while but realized I needed to swap the result with the row... This was helpful thank you\nThank you for this,I was really stuck", "positive_passages": [{"docid": "doc-en-freeCodeCamp-1f076b99e3c7c67284df98b6e95436e176ee4824ca5e50800ade88eb50ff25da", "text": "You should use the concatenation operator on your `result` variable. ```js <del> assert.match(code, /results*+/); </del> <ins> assert.match(code, /(?:results*+|+s*result)/); </ins> ``` You should concatenate `row` to your `result` variable. ```js <del> assert.match(code, /results*+s*row/); </del> <ins> assert.match(code, /results*+s*row|rows*+s*result/); </ins> ``` You should assign the result of your concatenation back to the `result` variable. ```js <del> assert.match(code, /results*=s*results*+s*row;?/) </del> <ins> assert.match(code, /results*=s*(results*+s*row|rows*+s*result);?/); </ins> ``` # --seed--", "commid": "freeCodeCamp_pr_54468"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-4be4c06a2e93db01cf60910074389899515ad47983d67a7d1e4df2d184a42091", "query": "When working through the , it's expected from the user to create a method that internally uses a to make a sum, like the following: But when presented the following solution, making the reduce's callback sum the other way around, it doesn't pass: Because of the , the previous presented solution should work. No response Device: Laptop OS: macOS 13.6.6 Browser: Chrome Version: 124 No response\nI agree that both versions should be accepted since they are valid solutions.positive_passagesdociddoc-en-freeCodeCamp-750747c0de366fdc61bd395347ae9d85b96e0c4117fe270d116ebb0235cb8f38text```js const afterCalculateTotal = code.split('calculateTotal')[1]; <del> assert.match(afterCalculateTotal, /(s*totals*,s*items*)s*=>s*totals*+s*item.price/); </del> <ins> assert.match(afterCalculateTotal, /(s*totals*,s*items*)s*=>s*(?:totals*+s*item.price|item.prices*+s*total)/); </ins> ``` Your `reduce` call should have an initial value of `0`. ```js const afterCalculateTotal = code.split('calculateTotal')[1]; <del> assert.match(afterCalculateTotal, /thiss*.s*itemss*.s*reduces*(s*(s*totals*,s*items*)s*=>s*totals*+s*item.prices*,s*0s*)/); </del> <ins> assert.match(afterCalculateTotal, /thiss*.s*itemss*.s*reduces*(s*(s*totals*,s*items*)s*=>s*(?:totals*+s*item.price|item.prices*+s*total)s*,s*0s*)/); </ins> ``` # --seed--commidfreeCodeCamp_pr_54631negative_passages |
| query_idq-en-freeCodeCamp-78f396ad66fdcf58e169a99f61c1bb00ed339fb81f724e2a5abb5503f8116fb9queryCurrently on step number 5 there's a note that reads Note that when reassigning a variable that has already been declared, you do not use the let keyword. As it stands this note is incorrect and unnecessary. No code, just instructions re-wording. The note could be changed to: Note: You can only re-assign a variables that has been declared with Or we can simply remove it altogether instead. <img width=\"1217\" alt=\"Screen Shot 2024-05-02 at 10 31 38\" src=\"\"- Device: [Laptop] OS: [MacOS 12.7.4] Browser: [Chrome] Version: [124.0.6367.91] No response\nThe note is correct. I think you are interpertering it wrong? It is saying does not need to be used when re-assinging the variable with a new value. edit: It is not saying that you can use any kind of keyword like or\nI understand what's it's trying to convey, but it's written in a confusing way. Here's the text directly copied into ChatGPT for some additional context: <img width=\"820\" alt=\"Screen Shot 2024-05-02 at 11 01 54\" src=\"\"\nText refers to potential situation when both assignments are using , ie: Depending on where exactly both are used, this can result in . - - x = 10; There's no on this line. It's one of the cases when chat doesn't know what it's talking about.\nHi thank you for creating the issue. As Sem pointed out, we don't think the note should be updated to because the new version communicates different information from the original. I think the confusion came from the word \. The word isn't needed since \"reassigning\" already implies that the variable has been declared, so I'd propose changing the sentence a little: cc'ing for input, since you're much more experienced with this kind of change than I am\nThanks for the input your proposal addresses the issue I presented\nThat change works for me. Let's open it up for first timers This has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the js let programmer = \"Naomi\"; programmer = \"CamperChan\"; ` Happy coding", "positive_passages": [{"docid": "doc-en-freeCodeCamp-1caaf0bb206d255294a1d5f8fa11a27db22eec215fb0de23e1bfbc9e312cde25", "text": "programmer = \"CamperChan\"; ``` <del> Note that when reassigning a variable that has already been declared, you do **not** use the `let` keyword. </del> <ins> Note that when reassigning a variable, you do **not** use the `let` keyword again. </ins> After your `console.log`, assign the value `\"World\"` to your `character` variable.", "commid": "freeCodeCamp_pr_54750"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-8e65f225c1a5cd51ab405d9298c02ec8e9590c3bfa58ebf801795d278c129122", "query": "There is a typo at the following step: It should present the text: Device: Laptop OS: Windows 11 Browser: Brave Version: 1.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-52c36d0cb49026c6e252e7b9df71672889ec5f8ae22712cf9d761764e3780348", "text": "transform: translateY(-50%); } <ins> .landing-skill-icon { color: #215f1e; font-size: 150px; } .black-text { color: #333; font-weight: 400; font-size: 40px; } .font-awesome-padding { margin-top: 45px; margin-bottom: 20px; } </ins> .background-svg { width: 220px; height: 220px;", "commid": "freeCodeCamp_pr_30"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-8e65f225c1a5cd51ab405d9298c02ec8e9590c3bfa58ebf801795d278c129122", "query": "There is a typo at the following step: It should present the text: Device: Laptop OS: Windows 11 Browser: Brave Version: 1.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-dcd93f573fe9b6449e6dead840938b11a7be5ab4fee6d9b25b12eccef7f9f2fa", "text": "background-position: center; } <ins> .testimonial-image { border-radius: 5px; height: 200px; width: 200px; } .testimonial-copy { font-size: 20px; text-align: center; @media (min-width: 991px) and (max-width: 1199px) { height: 120px; } @media (min-width: 1200px) { height: 90px; } } </ins> //uncomment this to see the dimensions of all elements outlined in red //* { // border-color: red;", "commid": "freeCodeCamp_pr_30"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-8e65f225c1a5cd51ab405d9298c02ec8e9590c3bfa58ebf801795d278c129122", "query": "There is a typo at the following step: It should present the text: Device: Laptop OS: Windows 11 Browser: Brave Version: 1.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-716ed0a99336d96c333a5894aad136a78559c688b8998eec06621cb6e6341f2d", "text": "extends layout block content <del> .hidden-xs a(href='https://github.com/freecodecamp/freecodecamp') img(style='position: absolute; top: 40; right: 0; border: 0; margin-top: -30px;', src='https://camo.githubusercontent.com/e7bbb0521b397edbd5fe43e7f760759336b5e05f/68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f6769746875622f726962626f6e732f666f726b6d655f72696768745f677265656e5f3030373230302e706e67', alt='Fork me on GitHub', data-canonical-src='https://s3.amazonaws.com/github/ribbons/forkme_right_green_007200.png') </del> .jumbotron .text-center h1.hug-top Code with Us", "commid": "freeCodeCamp_pr_30"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-8e65f225c1a5cd51ab405d9298c02ec8e9590c3bfa58ebf801795d278c129122", "query": "There is a typo at the following step: It should present the text: Device: Laptop OS: Windows 11 Browser: Brave Version: 1.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-7b96a1fd6254002bca9bd99a4d8e54ddadb4f6b9df0c4b588fb16916994c1057", "text": "br br a.btn.nonprofit-cta.btn-success(href=\"/nonprofits\") I'm with a nonprofit and want help coding something <del> include partials/about include partials/faq </del> No newline at end of file <ins> .big-break h2 Campers you'll hang out with: .row .col-xs-12.col-sm-12.col-md-4 img.img-responsive.testimonial-image.img-center(src=\"https://s3.amazonaws.com/freecodecamp/testimonial-jen.jpg\", alt=\"@jenthebest's testimonial image\https://s3.amazonaws.com/freecodecamp/testimonial-tate.jpg\@TateThurston's testimonial image\") .testimonial-copy Just built my company's website with skills I've learned from Free Code Camp! h3 - @TateThurston .col-xs-12.col-sm-12.col-md-4 img.img-responsive.testimonial-image.img-center(src=\"https://s3.amazonaws.com/freecodecamp/testimonial-cynthia.jpg\", alt=\"@cynthialanel's testimonial image\/login\, : }], : []} |
| {: , : first time\those\the\those\attribute value\paragraph elements\to select the element with that attribute value\(...) to select the paragraph element (...)\, : [{: , : , : }], : []} |
| {: , : first-time\, : [{: , : )#breakfast input[s*type=numbers*]s*1s*)/); ``` <del> You should assign the result of your `odocument.querySelectorAll()` call to `breakfastNumberInputs`. </del> <ins> You should assign the result of your `document.querySelectorAll()` call to `breakfastNumberInputs`. </ins> ```js assert.match(calculateCalories.toString(), /breakfastNumberInputss*=s*document.querySelectorAll(s*('|\")#breakfast input[s*type=numbers*]s*1s*)/);", "commid": "freeCodeCamp_pr_55282"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-493a68277a02a81ae39ea87707da3484b4270fecb5d444bcc424847a41a088d1", "query": "In step 10 of Luhn Algorithm, we teach campers how to create a substring using the operator. I think the explanation is a little short and could improved by: Adding comment next to each example, showing the result of each operation (we are currently communicating the value via the variable name, but I don't think it's clear enough) Mention that the starting index is inclusive, and the ending index is exclusive Additionally, I think we could: Change to to have the syntax more self-descriptive Mention that the default value of is 1 Perhaps the description should be changed to: python mystring = 'camperbot' mystring[0:6] == 'camper' # True my_string[0:6:3] == 'cp' # True `\nDifferent project but same kind of example: I remember we decided not to use because of translations, but using them in the code example and then explain what they mean is fine :+1:\nare we able to open this up for contribution?\nPersonally, I'd prefer to change the snippet into the following: I agree with all the rest.\nI've updated the issue description with Dario's code snippet. This issue is open for contributions. We typically do not assign issues. Instead, we accept the most quality contribution followed by the one that is made first. Please make sure you read our as well as our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Happy contributing.\nWhoops, sorry. I just noticed that Farhan is assigned to the issue. Are you working on this or could we mark this one up-for-grabs?\nYeah please mark this as up for grabpositive_passagesdociddoc-en-freeCodeCamp-1c0da98c60c51e0c05cbb34f240e41b8868766345e5c6bc3f7177c1b8a5de478text# --description-- <del> You have accessed elements (characters) of a string before, using the index operator `[]`. You can also use the index operator to access a range of characters in a string with `string[x:y:h]`: </del> <ins> You have accessed elements (characters) of a string before, using the index operator `[]`. You can also use the index operator to access a range of characters in a string with `string[start:stop:step]`: </ins> ```python my_string = 'camperbot' <del> camper = my_string[0:6] cp = my_string[0:6:3] </del> <ins> my_string[0:6] == 'camper' # True my_string[0:6:3] == 'cp' # True </ins> ``` <del> Where `x` is the starting index, `y` is the ending index, and `h` is the step (the amount of characters to skip over). </del> <ins> Where `start` is the starting index (inclusive), `stop` is the ending index (exclusive), and `step` is the amount of characters to skip over. If not specified, `step` is default to 1. </ins> Create a variable named `card_number_reversed` and assign it the value of the first 4 characters of `card_number`.commidfreeCodeCamp_pr_56133negative_passages |
| query_idq-en-freeCodeCamp-867030372fbd448a158e4df3e60290322f4827d743c61b6e1b8c4f4129d6d918queryStep 22 of build a Todo app can use a better a hint or a short reminder on destructuring if one can be into the instructions. If we forget to put the curly braces around the parameter names to destructure them, the hint only says: You should destructure id, title, date, description as the parameters of the callback of your forEach(). A better hint would be I think parameter destructuring was only covered once before this project. (though I may recall that incorrectly) here: Either a better hint or a reminder of parameter destructuring in the instructions would be helpful. No response N/A No response\nHello. I would like to work on this issue. Please assign this to me.\nLet's go with this text.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-c0efafa170a2d1265e52c7e95ef36c33011993b5e3c752485c9c6a946396bd6c", "text": "assert.match(code, /taskData.forEach(s*/) ``` <del> You should destructure `id`, `title`, `date`, `description` as the parameters of the callback of your `forEach()`. </del> <ins> You should use `{id, title, date, description}` as the destructured parameters of the `forEach()` callback function. </ins> ```js assert.match(code, /taskData.forEach(s*(s*{s*(?:ids*,s*titles*,s*dates*,s*description)|(?:titles*,s*ids*,s*dates*,s*description)|(?:dates*,s*ids*,s*titles*,s*description)|(?:ids*,s*dates*,s*titles*,s*description)|(?:titles*,s*dates*,s*ids*,s*description)|(?:dates*,s*titles*,s*ids*,s*description)|(?:dates*,s*titles*,s*descriptions*,s*id)|(?:titles*,s*dates*,s*descriptions*,s*id)|(?:descriptions*,s*dates*,s*titles*,s*id)|(?:dates*,s*descriptions*,s*titles*,s*id)|(?:titles*,s*descriptions*,s*dates*,s*id)|(?:descriptions*,s*titles*,s*dates*,s*id)|(?:descriptions*,s*ids*,s*dates*,s*title)|(?:ids*,s*descriptions*,s*dates*,s*title)|(?:dates*,s*descriptions*,s*ids*,s*title)|(?:descriptions*,s*dates*,s*ids*,s*title)|(?:ids*,s*dates*,s*descriptions*,s*title)|(?:dates*,s*ids*,s*descriptions*,s*title)|(?:titles*,s*ids*,s*descriptions*,s*date)|(?:ids*,s*titles*,s*descriptions*,s*date)|(?:descriptions*,s*titles*,s*ids*,s*date)|(?:titles*,s*descriptions*,s*ids*,s*date)|(?:ids*,s*descriptions*,s*titles*,s*date)|(?:descriptions*,s*ids*,s*titles*,s*date)s*}/)", "commid": "freeCodeCamp_pr_55643"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-51bcc5efa8857f0d5651211ee245bcb79bd0e8cc5266d4e068df8dd9e725a145", "query": "The instructions for step 103 of the spreadsheet project request that a range be created from an array. The say: My solution (listed below) tries to do that by passing in the first number found in nums and the last number found in nums as arguments to the range function. This solution is not accepted and the hint says: On reading this initially I have no clue what this hint is attempting to say. Does it want the range to span from the first number of the array to the second number only? Does it want the range property to define a function that takes two arguments? I'm really not sure what it wants. After some investigations though it seems that this step wanted the range to be between the first and second numbers of the array. I think this confusion could have been easily avoided if the instructions just said that. Change the instructions to say: numsnums No response N/A No response\nOne of the tests is checking , so it's clearly intended to use first and second number.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-4686fe8300776ca49a55dc4db0f9558dd72077f9f4c93a2fb5612abb9ab34fbf", "text": "# --description-- <del> Add a `range` property which generates a range from `nums`. Remember that you have a `range` function you can reuse here. </del> <ins> Add a `range` property which generates a range from the first number in `nums` to the second number in `nums`. Remember that you have a `range` function you can reuse here. </ins> # --hints--", "commid": "freeCodeCamp_pr_55747"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-d2ee317ccc60294a809a518b2e6dfb985d113573f551aaf8567199e471e68d35", "query": "The code should not be centered in the preview modal. or to on button for certification project with code ! ! Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response_", "positive_passages": [{"docid": "doc-en-freeCodeCamp-d86d0d308f5bf86c1441ce209a469926a29c64d6f1e17954153bfb629e0d09d2", "text": "</Table> )} {id && ( <del> <Modal onClose={closeSolution} open={solutionOpen}> </del> <ins> <Modal onClose={closeSolution} open={solutionOpen} size='large'> </ins> <Modal.Header showCloseButton={true} closeButtonClassNames='close'> {`${username}'s Solution to ${ idToNameMap.get(id)?.challengeTitle ?? '' }`} </Modal.Header> <del> <Modal.Body> </del> <ins> <Modal.Body alignment='left'> </ins> <SolutionViewer challengeFiles={challengeData.challengeFiles} solution={challengeData.solution ?? ''}commidfreeCodeCamp_pr_55759negative_passages |
| query_idq-en-freeCodeCamp-3c2973400fe61ed4bcdffcfb8de9b08b6abb6a04e4b848d21be3b6a586e7f28equerytypo error on the console warning: If a large straight is rolled, your checkForStraights function should enable the fifth radio button, set the value to 40, and update the displayed text to , score = 0. i recreated the last step to get to the warnings. it's supposed to say :If a large straight is rolled, your checkForStraights function should enable the fifth radio button, set the value to 40, and update the displayed text to , score = 40. ---- not 0. <img width=\"442\" alt=\"Screenshot 2024-08-25 at 8 08 39 PM\" src=\"\"- Device: Mac OS: Ventura 13.6.9 Browser: Brave, Safari Version: Brave - , Safari - Version 17.6 (.3.11.11.7, ) No response_\nThanks for opening this issue. This looks something that can be fixed by \"first time\" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-7d892ccec70900217d934d0193673f23b7b49f563585bd95677c4f2fc5b77cca", "text": "assert.strictEqual(scoreSpans[3].innerText, \", score = 30\"); ``` <del> If a large straight is rolled, your `checkForStraights` function should enable the fifth radio button, set the value to `40`, and update the displayed text to `, score = 0`. </del> <ins> If a large straight is rolled, your `checkForStraights` function should enable the fifth radio button, set the value to `40`, and update the displayed text to `, score = 40`. </ins> ```js resetRadioOptions();", "commid": "freeCodeCamp_pr_55947"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-55e02a4ddabdb0d3d11c965cc479e6e4748e9a816f8473cf78f8024180ac85db", "query": "The challenge or lesson asks the user to provide answer by looking at or by executing the sample code provided in front of him/her but the sample doesn't provide any output in console. When a user try that piece of code he/she should see an output in console. No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response\nCan I work on this and just add the myFunction(); at the end?\nhi Thanks for your interest in contributing. This issue has not been triaged yet, and a solution has not been agreed upon. Once the issue is open for contribution, you are welcome to create a pull request to reflect the issue consensus. Please also note that we typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue.\nOk, yes, it makes sense to add a function call in the code snippet. I'm opening this up for contributors to work on. This is the piece of code that needs to be changed: Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.\nHi I'd like to work on this issue and submit a pull request to address it. This will be my first issue. I just wanted to know if the video-solution is correct on that page. Just seems to say '2'. Is that intentional or is it missing a zero. Either way I'll add the function call in the code snippet and send a merge req right away. Thanks!\nHey We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labeled with or are open for contributions. Please make sure you read . We prioritize contributors following the instructions in our guide. Join us in or if you need help contributing - our community will be happy to assist you.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-f2098f4d39e68d814e59e66d3686a465111b33bd13afffd63c93d0c9c70082fe", "text": "let x = 20; console.log(x); } <ins> myFunction(); </ins> ``` ## --answers--", "commid": "freeCodeCamp_pr_56458"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-a0576a87f4cf2a28a4895412e10465c1a7b265fb291212aa477a546c7e500330", "query": "I suggest changing the phrase 'template interpolation' to 'template literals,' because are correctly referred to as template literals, which support string interpolation. ! Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response_\nit should be \"string interpolation\". Template literals are already mentioned a few words before, it would be extremely redundant. I'm opening this issue for first timers to make the change \ -\. This change needs to be done twice in this file: Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.\nSorry for the misunderstanding. I need to change the text from 'template interpolation' -'string interpolation'\nHi, I guess has raised his PR with the needed change. I haven't contributed before to any open source project. I thought this was an easy one to do to get started. Please tell any easy code or non-code contributions to be made. Happy to help.\nI am able to make the required change and happy to start open source contribution with hacktoberfest . Kindly assign this issue to me.\nWe typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labeled with or are open for contributions. Please make sure you read . We prioritize contributors following the instructions in our guide. Join us in or if you need help contributing - our community will be happy to assist you.\nThis pull request resolves the issue of incorrect terminology in the JavaScript curriculum where \"template interpolation\" was used. The correct term is \"string interpolation,\" as template literals support string interpolation. I have made the following changes: Replaced \"template interpolation\" with \"string interpolation\" in the two locations within the file. Fix :\nAfter reading the contributing guidelines, I now understand the mistake I made in my PR.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-be80b4c59c6c55b3b2d12ee697b115fecd0669761ac6b35d327e1a8864cece9b", "text": "# --description-- <del> Inside the template literal, create a `div` element with the `id` set to the `index` from the `.forEach()` array method. Remember to use template interpolation to do this. </del> <ins> Inside the template literal, create a `div` element with the `id` set to the `index` from the `.forEach()` array method. Remember to use string interpolation to do this. </ins> Also, add a `class` of `\"user-card\"` to the `div`.", "commid": "freeCodeCamp_pr_56440"}], "negative_passages": []} |
| {"query_id": "q-en-freeCodeCamp-a0576a87f4cf2a28a4895412e10465c1a7b265fb291212aa477a546c7e500330", "query": "I suggest changing the phrase 'template interpolation' to 'template literals,' because are correctly referred to as template literals, which support string interpolation. ! Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response_\nit should be \"string interpolation\". Template literals are already mentioned a few words before, it would be extremely redundant. I'm opening this issue for first timers to make the change \ -\. This change needs to be done twice in this file: Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.\nSorry for the misunderstanding. I need to change the text from 'template interpolation' -'string interpolation'\nHi, I guess has raised his PR with the needed change. I haven't contributed before to any open source project. I thought this was an easy one to do to get started. Please tell any easy code or non-code contributions to be made. Happy to help.\nI am able to make the required change and happy to start open source contribution with hacktoberfest . Kindly assign this issue to me.\nWe typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labeled with or are open for contributions. Please make sure you read . We prioritize contributors following the instructions in our guide. Join us in or if you need help contributing - our community will be happy to assist you.\nThis pull request resolves the issue of incorrect terminology in the JavaScript curriculum where \"template interpolation\" was used. The correct term is \"string interpolation,\" as template literals support string interpolation. I have made the following changes: Replaced \"template interpolation\" with \"string interpolation\" in the two locations within the file. Fix :\nAfter reading the contributing guidelines, I now understand the mistake I made in my PR.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-254df91b4dd83ed27e6822926cd7e9e3e298a5196828676e59bad120d391f5f7", "text": "assert.include(document.querySelector('#author-container > div')?.className, 'user-card'); ``` <del> Your `div` element should have the `id` of `index`. Remember to use template interpolation to set the `id`. </del> <ins> Your `div` element should have the `id` of `index`. Remember to use string interpolation to set the `id`. </ins> ```js displayAuthors([{author: \"Naomi\"}]);", "commid": "freeCodeCamp_pr_56440"}], "negative_passages": []} |
| |
