jiebi/CodeConvo huggingface dataset:
Code change:
In this lesson: In the second requirement the is included in the code tag markup which indicates it should be part of the href. It's minor but wrong and confusing for people new to html.

Related discussion:
text: ], "tests": [ "assert((/cat photos/gi).test($("a").text()), 'Your <code>a</code> element should have the <code>anchor text</code> of "cat photos"')", <del> "assert(/http://catphotoapp.com/gi.test($("a").attr("href")), 'You need an <code>a</code> element that links to <code>http&#58;//catphotoapp.com<code>.')", </del> <ins> "assert(/http://catphotoapp.com/gi.test($("a").attr("href")), 'You need an <code>a</code> element that links to <code>http&#58;//catphotoapp.com</code>.')", </ins> "assert(editor.match(/</a>/g) && editor.match(/</a>/g).length === editor.match(/<a/g).length, 'Make sure your <code>a</code> element has a closing tag.')" ], "challengeSeed": [
Code change:
One of the instructions has the following: start this tutorial by running npm install how-to-npm it says to run the npm tutorial by typing 'npm install how-to-npm but you are actually supposed to just type 'how-to-npm'

Related discussion:
text: "Wait for the workspace to finish processing and select it on the left sidebar, below the Create New Workspace button.", "Click the "Start Editing" button.", "In the lower right hand corner you should see a terminal window. In this window use the following commands. You don't need to know what these mean at this point.", <del> "Run this command: <code>npm install how-to-npm -g</code>", "Now start this tutorial by running <code>npm install how-to-npm@2.0.0</code>.", </del> <ins> "Install <code>how-to-npm</code> with this command: <code>npm install how-to-npm -g</code>", "Now start the tutorial by running <code>how-to-npm</code>.", </ins> "Note that you can resize the c9.io's windows by dragging their borders.", "Make sure that you are always in your project's "workspace" directory. You can always navigate back to this directory by running this command: <code>cd ~/workspace</code>.", "Note that you can only add dist tags to the specific version numbers published in steps 8 and 10. If you receive a 403 or 404 error, run <code>how-to-npm</code> and try again.",
Code change:
Challenge has an issue. 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 - for subtraction <---
merged to

Related discussion:
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", </del> <ins> "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": [
Code change:
Challenge has an issue. 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 - for subtraction <---
merged to

Related discussion:
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", </del> <ins> "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": [
Code change:
Challenge has an issue. 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 - for subtraction <---
merged to

Related discussion:
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", </del> <ins> "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": [
Code change:
Challenge has an issue. 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 - for subtraction <---
merged to

Related discussion:
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", </del> <ins> "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": [
Code change:
Challenge has an issue. 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 - for subtraction <---
merged to

Related discussion:
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 change:
! Same with the other waypoints that ask for a hex code that includes alpha chars.
Green worked fine.. blue has case issue.

Related discussion:
text: ], "tests": [ "assert($("body").css("background-color") === "rgb(255, 0, 0)", 'Give your <code>body</code> element the <code>background-color</code> of red.')", <del> "assert(editor.match(/#FF0000/g) && editor.match(/#FF0000/g).length > 0, 'Use the <code>hex code</code> for the color red instead of the word <code>red</code>. For example <code>body { color&#58; #FF0000; }</code>.')" </del> <ins> "assert(editor.match(/#FF0000/ig) && editor.match(/#FF0000/ig).length > 0, 'Use the <code>hex code</code> for the color red instead of the word <code>red</code>. For example <code>body { color&#58; #FF0000; }</code>.')" </ins> ], "challengeSeed": [ "<style>",
Code change:
! Same with the other waypoints that ask for a hex code that includes alpha chars.
Green worked fine.. blue has case issue.

Related discussion:
text: ], "tests": [ "assert($("body").css("background-color") === "rgb(0, 0, 255)", 'Give your <code>body</code> element the <code>background-color</code> of blue.')", <del> "assert(editor.match(/#0000FF/g) && editor.match(/#0000FF/g).length > 0, 'Use the <code>hex code</code> for the color blue instead of the word <code>blue</code>. For example <code>body { color&#58; #0000FF; }</code>.')" </del> <ins> "assert(editor.match(/#0000FF/ig) && editor.match(/#0000FF/ig).length > 0, 'Use the <code>hex code</code> for the color blue instead of the word <code>blue</code>. For example <code>body { color&#58; #0000FF; }</code>.')" </ins> ], "challengeSeed": [ "<style>",
Code change:
! Same with the other waypoints that ask for a hex code that includes alpha chars.
Green worked fine.. blue has case issue.

Related discussion:
text: ], "tests": [ "assert($("body").css("background-color") === "rgb(255, 165, 0)", 'Give your <code>body</code> element the <code>background-color</code> of orange.')", <del> "assert(editor.match(/#FFA500/g) && editor.match(/#FFA500/g).length > 0, 'Use the <code>hex code</code> for the color orange instead of the word <code>orange</code>. For example <code>body { color&#58; #FFA500; }</code>.')" </del> <ins> "assert(editor.match(/#FFA500/ig) && editor.match(/#FFA500/ig).length > 0, 'Use the <code>hex code</code> for the color orange instead of the word <code>orange</code>. For example <code>body { color&#58; #FFA500; }</code>.')" </ins> ], "challengeSeed": [ "<style>",
Code change:
Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. "Another type of JavaScript loop is called a "while loop" because it runs "while" something is true, and stops once that something is no longer true." Should probably read as: "Another type of JavaScript loop is called a "while loop", because it runs "while" something is true and stops once that something is no longer true." Commas separate complete sentences, or act as a pause.

Related discussion:
text: "difficulty":"9.9825", "description":[ "You can run the same code multiple times by using a loop.", <del> "Another type of JavaScript loop is called a "while loop" because it runs "while" something is true, and stops once that something is no longer true.", </del> <ins> "Another type of JavaScript loop is called a "while loop", because it runs "while" something is true and stops once that something is no longer true.", </ins> "<code>var ourArray = [];</code>", "<code>var i = 0;</code>", "<code>while(i < 5) {</code>",
Code change:
In waypoint description there is a word with missing letter "r" and wrong letter - "a" instead "e" . I don't know English well, therefore this typo a slightly confused me:) !

Related discussion:
text: "<code>g</code> means that we want to search the entire string for this pattern.", "<code>i</code> means that we want to ignore the case (uppercase or lowercase) when searching for the pattern.", "<code>Regular expressions</code> are usually surrounded by <code>/</code> symbols.", <del> "Let's try selecting all the occurances of the word <code>and</code> in the string <code>George Boole and Alan Turing went to the shop and got some milk</code>. We can do this by replacing the <code>.+</code> part of our regular expression with the current <code>regular expression</code> with the word <code>and</code>." </del> <ins> "Let's try selecting all the occurrences of the word <code>and</code> in the string <code>George Boole and Alan Turing went to the shop and got some milk</code>. We can do this by replacing the <code>.+</code> part of our regular expression with the current <code>regular expression</code> with the word <code>and</code>." </ins> ], "tests":[ "assert(test==2, 'Your <code>regular expression</code> should find two occurrences of the word <code>and</code>');",
Code change:
Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. There seems to be a conflict between the last paragraph above the "Go to Next Challenge" button, and the first test-item below the "Reset/Help/Bug" buttons (see screenshot, below). It is not clear if the <div class="well"'s should go inside the <div class="col-xs-6"'s, or vice versa. If I were to follow ALL the directions to the letter, I'd have two <div class="col-xs-6"'s nested inside each of two <div class="well"'s, each of which is inside an outer <div class="col-xs-6". I think this is just a text-editing problem, because my code passes when I did what I expected the waypoint to be looking for: an empty <div class="well"inside each of the previously-placed <div class="col-xs-6"'s; this is included in the screenshot, as well. Also, I am fairly the text is missing a "<", where I've sloppily drawn it in on my screenshot. !
I ran into this also. The challenge validates when you follow the instructions in the explanatory text. It does not validate when you only follow the instructions in the checkpoints.

Related discussion:
text: "Nest one <code>div</code> element with the class <code>well</code> within each of your <code>col-xs-6</code> <code>div</code> elements." ], "tests": [ <del> "assert($("div").length > 4, 'Add two <code>div</code> elements inside your <code>div class="well"></code> element both with the class <code>col-xs-6</code>')", </del> <ins> "assert($("div").length > 4, 'Add a <code>div</code> element with the class <code>well</code> inside each of your <code>div class="col-xs-6"> elements</code>')", </ins> "assert($("div.col-xs-6").children("div.well").length > 1, 'Nest both of your <code>div class="col-xs-6"</code> elements within your <code>div class="row"</code> element.')", "assert(editor.match(/</div>/g) && editor.match(/<div/g) && editor.match(/</div>/g).length === editor.match(/<div/g).length, 'Make sure all your <code>div</code> elements have closing tags.')" ],
Code change:
Challenge has an issue. This is backwards and should read: "Add two div elements inside your "col-xs-6" elements both with the class "well" - or something similar. !

Related discussion:
text: "Nest one <code>div</code> element with the class <code>well</code> within each of your <code>col-xs-6</code> <code>div</code> elements." ], "tests": [ <del> "assert($("div").length > 4, 'Add two <code>div</code> elements inside your <code>div class="well"></code> element both with the class <code>col-xs-6</code>')", </del> <ins> "assert($("div").length > 4, 'Add a <code>div</code> element with the class <code>well</code> inside each of your <code>div class="col-xs-6"> elements</code>')", </ins> "assert($("div.col-xs-6").children("div.well").length > 1, 'Nest both of your <code>div class="col-xs-6"</code> elements within your <code>div class="row"</code> element.')", "assert(editor.match(/</div>/g) && editor.match(/<div/g) && editor.match(/</div>/g).length === editor.match(/<div/g).length, 'Make sure all your <code>div</code> elements have closing tags.')" ],
Code change:
Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. step 9 says Install how-to-npm with this command: npm install -g git-it. it looks like we are installing something called git-it instead of how-to-npm. As before, if I am incorrect please disregard this issue and just close. Just trying to do what I can for you guys. Love this site!
Hey thanks for posting an issue! It looks like you are right! I believe the step should say
That's what it looked like to me to. It seems that the command was copied from the next page when you do actually have to install how-to-npm. Btw, now that I have done a lot of the free code camp challenges, how would I go about starting to contribute to the project? I would love to help out with the code or issues or anything really.
Awesome! Just jump right in :smile:! Maybe start with putting in a pull request for this issue? Feel free to ping me in gitter if you want to chat about this further (so as to not pollute this issue with conversation)
Dear camper, your issue is related to: Please see .
I checked when I was creating the pull request to fix this issue and it seems that the how-to-npm part of it is already fixed.

Related discussion:
text: "Choose Node.js in the selection area below the name field.", "Click the Create button. Then click into your new workspace.", "In the lower right hand corner you should see a terminal window. In this window use the following commands. You don't need to know what these mean at this point.", <del> "Install <code>how-to-npm</code> with this command: <code>npm install -g git-it</code>", </del> <ins> "Install <code>git-it</code> with this command: <code>npm install -g git-it</code>", </ins> "Now start the tutorial by running <code>git-it</code>.", "Note that you can resize the c9.io's windows by dragging their borders.", "Make sure that you are always in your project's "workspace" directory. You can always navigate back to this directory by running this command: <code>cd ~/workspace</code>.",
Code change:
Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. s - captures much more than spaces as the lesson implies, a better description that talks about what characters white space, as the title hints at, includes should be used.
Thanks for pointing this out. I agree, feel free to for this.

Related discussion:
text: }, { "id":"cf1111c1c12feddfaeb8bdef", <del> "title": "Find White Space with Regular Expressions", </del> <ins> "title": "Find Whitespace with Regular Expressions", </ins> "difficulty":"9.986", "description":[ <del> "We can also use selectors like <code>s</code> to find spaces in a string.", </del> <ins> "We can also use selectors like <code>s</code> to find whitespace in a string.", "The whitespace characters are <code>" "</code> (space), <code>r</code> (carriage return), <code>n</code> (newline), <code>t</code> (tab), and <code>f</code> (form feed).", </ins> "It is used like this:", "<code>/s+/g</code>", <del> "Select all the spaces in the sentence string." </del> <ins> "Select all the whitespace characters in the sentence string." </ins> ], "tests":[ "assert(test === 7, 'message: Your RegEx should have found seven spaces in the <code>testString</code>.');",
Code change:
On "Here's an example of how you would use the children() function to give the children of your left-well element the background color of blue : $("#left-well").children().css("color", "blue")" Shouldn't it just be color of blue instead of background color of blue?
thank you for pointing this out!!

Related discussion:
text: "Many HTML elements have <code>children</code> which <code>inherit</code> their properties from their parent HTML elements.", "For example, every HTML element is a child of your <code>body</code> element, and your "jQuery Playground" <code>h3</code> element is a child of your <code>&#60;div class="container-fluid"&#62</code> element.", "jQuery has a function called <code>children()</code> that allows you to access the children of whichever element you've selected.", <del> "Here's an example of how you would use the <code>children()</code> function to give the children of your <code>left-well</code> element the background color of blue: <code>$("#left-well").children().css("color", "blue")</code>", </del> <ins> "Here's an example of how you would use the <code>children()</code> function to give the children of your <code>left-well</code> element the color of blue: <code>$("#left-well").children().css("color", "blue")</code>", </ins> "Give all the children of your <code>#right-well</code> element a color of green." ], "tests": [
Code change:
! Challenge has an issue. User Agent is: <codeMozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:
This challenge is asking to you wrap the existing tag that is right below the , not create a new one at the bottom. The test expects to find your up there with the original , so adding it down at the bottom causes the test to fail. However, this is the third time in a week or so that I've seen this same issue reported, so I propose adding some clarifying language to the waypoint that lets the user know they should not be moving existing tag, only wrapping it.
It worked. Indeed the language should be more clarifying.
Great, just reading your your response. Unsure if you have clarifying language yet but I have run into the same of two days ago, 10/21...
The change has been pulled into the staging branch but hasn't been pushed into the production code yet. It shouldn't be too long before it is.

Related discussion:
text: "</style>", "", "<h2 class="red-text">CatPhotoApp</h2>", <ins> "<!--Do not alter code above this line-->", </ins> "", "<a href="http://www.freecatphotoapp.com">cat photos</a>", "", <ins> "<!--Do not alter code below this line-->", </ins> "<img class="smaller-image thick-green-border" src="https://bit.ly/fcc-relaxing-cat">", "", "<p class="red-text">Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</p>",
Code change:
Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; WOW64; rv:41.0) Gecko/ Firefox/41.0</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: Issue: Properties box says: "Let's delete the "tails" property from myDog." Test success statement: "Delete the property "bark" from myDog." Test succeeds on deleting bark property, not tails.
I noticed that too !

Related discussion:
text: "Let's delete the <code>"tails"</code> property from <code>myDog</code>." ], "tests": [ <del> "assert(myDog.bark === undefined, 'message: Delete the property <code>"bark"</code> from <code>myDog</code>.');" </del> <ins> "assert(myDog.tails === undefined, 'message: Delete the property <code>"tails"</code> from <code>myDog</code>.');" </ins> ], "challengeSeed": [ "var ourDog = {",
Code change:
Should be "become" I would fix it but I'm not sure where this file is located. !
closed. Fixed with

Related discussion:
text: [ "http://i.imgur.com/EoTfOyC.jpg", "An image of some of our campers coding together in Montreal.", <del> "Keep practicing coding every day and hanging out with other people who code, and you will becoming a job-ready coder.", </del> <ins> "Keep practicing coding every day and hanging out with other people who code, and you will become a job-ready coder.", </ins> "" ], [
Code change:
[x] Trigger Click Events with jQuery [x] Change Text with Click Events [x] Get JSON with the jQuery getJSON Method [x] Convert JSON Data to HTML [x] Render Images from Data Sources [x] Prefilter JSON [x] Get Geo-location Data
Trabajando en esta

Related discussion:
text: "challenges": [ { "id": "bb000000000000000000001", <del> "title":  "Trigger Click Events with jQuery", </del> <ins> "title": "Trigger Click Events with jQuery", </ins> "description": [ "In this section, we'll learn how to get data from APIs. APIs - or Application Programming Interfaces - are tools that computers use to communicate with one another.", "We'll also learn how to update HTML with the data we get from these APIs using a technology called Ajax.",