jiebi/CodeConvo huggingface dataset:
Change:
The Waypoint description says: It seems to me that the first paragraph should be the last, i.e., the assignment was given before the Waypoint's description.

Discussion:
"id": "bad87fee1248bd9aedf08824", "title": "Add Different Margins to Each Side of an Element", "description": [ <del> "Give the green box a <code>margin</code> of <code>40px</code> on its top and left side, but only <code>20px</code> on its bottom and right side.", </del> "Sometimes you will want to customize an element so that it has a different <code>margin</code> on each of its sides.", <del> "CSS allows you to control the <code>margin</code> of an element on all four sides with <code>margin-top</code>, <code>margin-right</code>, <code>margin-bottom</code>, and <code>margin-left</code> properties." </del> <ins> "CSS allows you to control the <code>margin</code> of an element on all four sides with <code>margin-top</code>, <code>margin-right</code>, <code>margin-bottom</code>, and <code>margin-left</code> properties.", "Give the green box a <code>margin</code> of <code>40px</code> on its top and left side, but only <code>20px</code> on its bottom and right side." </ins> ], "tests": [ "assert($(".green-box").css("margin-top") === "40px", 'Your <code>green-box</code> class should give the top of elements <code>40px</code> of <code>margin</code>.')",
Change:
Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.1; Win64; x64; rv:44.0) Gecko/ Firefox/44.0</code. Please describe how to reproduce this issue, and include links to screenshots if possible. In the instructions for this exercise the second example reads, "Likewise, where([20,3,5], 19) should return 2 because it is less than 20 (index 2) and greater than 5 (index 1)." Based on the example result given, the example array should be [3,5,20].
After completing this exercise I realized that the second example may not be a typo, as the exercise requires the use of the sort() method to sort the given arrays in a numerically ascending order. So, rather than a typo, this example may just be confusing to those who have not completed the exercise.
It might make sense to add a clarifying statement like:

Discussion:
"title": "Where do I belong", "description": [ "Return the lowest index at which a value (second argument) should be inserted into an array (first argument) once it has been sorted.", <del> "For example, where([1,2,3,4], 1.5) should return 1 because it is greater than 1 (index 0), but less than 2 (index 1).", "Likewise, where([20,3,5], 19) should return 2 because it is less than 20 (index 2) and greater than 5 (index 1).", </del> <ins> "For example, <code>where([1,2,3,4], 1.5)</code> should return <code>1</code> because it is greater than <code>1</code> (index 0), but less than <code>2</code> (index 1).", "Likewise, <code>where([20,3,5], 19)</code> should return <code>2</code> because once the array has been sorted it will look like <code>[3,5,20]</code> and <code>19</code> is less than <code>20</code> (index 2) and greater than <code>5</code> (index 1).", </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. Write your own code." ], "challengeSeed": [
Change:
Says: Replace your a element's href attribute with a #, also known as a hash symbol, to turn it into a dead link. I think it is kind of unclear - would potentially be better as "Replace the value of your a element's...." Tripped me up at first. Submitting a pull request for the change

Discussion:
"description": [ "Sometimes you want to add <code>a</code> elements to your website before you know where they will link.", "This is also handy when you're changing the behavior of a link using <code>jQuery</code>, which we'll learn about later.", <del> "Replace your <code>a</code> element's <code>href</code> attribute with a <code>#</code>, also known as a hash symbol, to turn it into a dead link." </del> <ins> "Replace the value of your <code>a</code> element's <code>href</code> attribute with a <code>#</code>, also known as a hash symbol, to turn it into a dead link." </ins> ], "tests": [ "assert($("a").attr("href") === "#", 'Your <code>a</code> element should be a dead link with a <code>href</code> attribute set to "#".')"
Change:
Challenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X 1075) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:
The editor is highlighting your code to let you know something doesn't look right, which in this case is that you open your with uppercase and close it with lowercase. ! However, despite this being bad practice it is valid markup and should pass. I am putting in a PR to make the regular expressions case insensitive now.
Okay, thank you for the response. Will make sure to get into the habit of being deliberate with casing. Thank you.

Discussion:
"tests": [ "assert($("ul").length > 0, 'Create a <code>ul</code> element.')", "assert($("ul li").length > 2, 'You should have three <code>li</code> elements within your <code>ul</code> element.')", <del> "assert(editor.match(/</ul>/g) && editor.match(/<ul/g) && editor.match(/</ul>/g).length === editor.match(/<ul/g).length, 'Make sure your <code>ul</code> element has a closing tag.')", "assert(editor.match(/</li>/g) && editor.match(/<li[s>]/g) && editor.match(/</li>/g).length === editor.match(/<li[s>]/g).length, 'Make sure your <code>li</code> elements have closing tags.')" </del> <ins> "assert(editor.match(/</ul>/gi) && editor.match(/<ul/gi) && editor.match(/</ul>/gi).length === editor.match(/<ul/gi).length, 'Make sure your <code>ul</code> element has a closing tag.')", "assert(editor.match(/</li>/gi) && editor.match(/<li[s>]/gi) && editor.match(/</li>/gi).length === editor.match(/<li[s>]/gi).length, 'Make sure your <code>li</code> elements have closing tags.')" </ins> ], "challengeSeed": [ "<link href="http://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">",
Change:
here "giving it a i element with the classes fa and fa-thumbs-up." shoud be "an i" and not "a i" Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:

Discussion:
"Font Awesome is a convenient library of icons. These icons are vector graphics, stored in the <code>.svg</code> file format. These icons are treated just like fonts. You can specify their size using pixels, and they will assume the font size of their parent HTML elements.", "The <code>i</code> element was originally used to make other elements italic, but is now commonly used for icons. You add the Font Awesome classes to the <code>i</code> element to turn it into an icon, for example:", "<code>&lt;i class="fa fa-info-circle"&gt;&lt;/i&gt;</code>", <del> "Use Font Awesome to add a <code>thumbs-up</code> icon to your like button by giving it a <code>i</code> element with the classes <code>fa</code> and <code>fa-thumbs-up</code>." </del> <ins> "Use Font Awesome to add a <code>thumbs-up</code> icon to your like button by giving it an <code>i</code> element with the classes <code>fa</code> and <code>fa-thumbs-up</code>." </ins> ], "tests": [ "assert($("i").hasClass("fa fa-thumbs-up"), 'Add an <code>i</code> element with the classes <code>fa</code> and <code>fa-thumbs-up</code>.')",
Change:
Challenge [Bonfire: Validate US Telephone Numbers] This actually returns false as the test says it should, but the test does not pass. The rest of the tests pass in my actual telephoneCheck() function.
Thanks for the report! It looks like that test was actually testing against the string rather than like the message said. I have submitted a PR to correct this.
ok good so i'm not insane. just mental. +1:

Discussion:
"assert(telephoneCheck("(555)555-5555") === true, 'message: <code>telephoneCheck("(555)555-5555")</code> should return true.');", "assert(telephoneCheck("1(555)555-5555") === true, 'message: <code>telephoneCheck("1(555)555-5555")</code> should return true.');", "assert(telephoneCheck("1 555 555 5555") === true, 'message: <code>telephoneCheck("1 555 555 5555")</code> should return true.');", <del> "assert(telephoneCheck("555-555-5555") === true, 'message: <code>telephoneCheck("555-555-5555")</code> should return true.');", </del> "assert(telephoneCheck("1 456 789 4444") === true, 'message: <code>telephoneCheck("1 456 789 4444")</code> should return true.');", "assert(telephoneCheck("123**&!!asdf#") === false, 'message: <code>telephoneCheck("123**&!!asdf#")</code> should return false.');", "assert(telephoneCheck("55555555") === false, 'message: <code>telephoneCheck("55555555")</code> should return false.');",

"assert(telephoneCheck("(275)76227382") === false, 'message: <code>telephoneCheck("(275)76227382")</code> should return false.');", "assert(telephoneCheck("2(757)6227382") === false, 'message: <code>telephoneCheck("2(757)6227382")</code> should return false.');", "assert(telephoneCheck("2(757)622-7382") === false, 'message: <code>telephoneCheck("2(757)622-7382")</code> should return false.');", <del> "assert(telephoneCheck("555)-555-5555") === false, 'message: <code>telephoneCheck("555)555-5555")</code> should return false.');", </del> <ins> "assert(telephoneCheck("555)-555-5555") === false, 'message: <code>telephoneCheck("555)-555-5555")</code> should return false.');", </ins> "assert(telephoneCheck("(555-555-5555") === false, 'message: <code>telephoneCheck("(555-555-5555")</code> should return false.');" ], "challengeSeed": [
Change:
Ever since we the last test case to , there have been questions about it. We either need to add several additional test cases which have a later number which does not meet the test criteria retained, or alter earlier test cases to have that same condition. Relevant Text (Emphasis ): < Drop the elements of an array (first argument), starting from the front, until the predicate (second argument) returns true. Existing Test Case: We do believe that this "early exit" solution is important and should be supported by test cases.
Ref: for an example of the sort of issue we see.
I'll do this. Note I've never actually made a PR before, anywhere.

Discussion:
"drop([1, 2, 3], function(n) {return n < 3; });" ], "tests": [ <del> "assert.deepEqual(drop([1, 2, 3, 4], function(n) {return n>= 3;}), [3, 4], 'message: <code>drop([1, 2, 3, 4], function(n) {return n >= 3;})</code> should return <code>[3, 4]</code>.');", </del> <ins> "assert.deepEqual(drop([1, 2, 3, 4], function(n) {return n >= 3;}), [3, 4], 'message: <code>drop([1, 2, 3, 4], function(n) {return n >= 3;})</code> should return <code>[3, 4]</code>.');", "assert.deepEqual(drop([0, 1, 0, 1], function(n) {return n === 1;}), [1, 0, 1], 'message: <code>drop([0, 1, 0, 1], function(n) {return n === 1;})</code> should return <code>[1, 0, 1]</code>.');", </ins> "assert.deepEqual(drop([1, 2, 3], function(n) {return n > 0;}), [1, 2, 3], 'message: <code>drop([1, 2, 3], function(n) {return n > 0;})</code> should return <code>[1, 2, 3]</code>.');", "assert.deepEqual(drop([1, 2, 3, 4], function(n) {return n > 5;}), [], 'message: <code>drop([1, 2, 3, 4], function(n) {return n > 5;})</code> should return <code>[]</code>.');", "assert.deepEqual(drop([1, 2, 3, 7, 4], function(n) {return n > 3;}), [7, 4], 'message: <code>drop([1, 2, 3, 7, 4], function(n) {return n > 3;})</code> should return <code>[7, 4]</code>.');",
Change:
I the "thumbs-up" icon to the "Info" button and I still passed the challenge. I don't know if this was intended to help. Cheers! :D Challenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/601.2.7 (KHTML, like Gecko) Version/9.0.1 Safari/601.2.7</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:
Thanks for the report. I've put in a PR that will check what the parent element of your icon is.
Thanks for taking the time to fix it! :D Cheers!

Discussion:
], "tests": [ "assert($("i").hasClass("fa fa-thumbs-up"), 'Add an <code>i</code> element with the classes <code>fa</code> and <code>fa-thumbs-up</code>.')", <ins> "assert($("i.fa-thumbs-up").parent().text().match(/Like/gi), 'Your <code>fa-thumbs-up</code> icon should be located within the Like button.')", </ins> "assert($("button").children("i").length > 0, 'Nest your <code>i</code> element within your <code>button</code> element.')", "assert(editor.match(/</i>/g), 'Make sure your <code>i</code> element has a closing tag.')" ],
Change:
Challenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36</code. The first sentence of the instructions, , is incomplete. At a guess, it should read
I could be wrong, but could we just remove this sentence from the challenge? It just seems to be hanging there (maybe from an old version of the challenge?) not actually contributing to the description.
I initially read it as a recap for the benefit of anyone taking a break after the previous waypoints, but perhaps it isn't necessary. Without it, the next paragraph would still prompt the reader to refer to the previous lessons if they had forgotten what led to the current state.
I agree, just nuke the sentence. The next one is a nice lead-in.

Discussion:
"id": "bb000000000000000000004", "title":  "Render Images from Data Sources", "description": [ <del> "In the JSON that we receive data from Free Code Camp's Cat Photo API.", </del> "We've seen from the last two lessons that each object in our JSON array contains an <code>imageLink</code> key with a value that is the url of a cat's image.", "When we're looping through these objects, let's use this <code>imageLink</code> property to display this image in an <code>img</code> element.", "Here's the code that does this:",
Change:
Anywhere from 1000px width to when the UI goes into responsive mode the numbers on the check list move into it's respective check box. Image posted bellow <img width="1109" alt="screen shot 2015-12-17 at 9 08 15 pm" src=""
Confirmed, although this is a pretty marginal corner case. There is maybe a 200px wide zone where there is overlap.
It happens quite a bit for me. Regardless I just want a softball for my first issue :) , Rex Schrader wrote: * |
This really isn't the issue with new UI (width < 760px). However, now checkboxes are awkwardly too far. !

Discussion:
ol for step, index in description .row.checklist-element(id="#{dashedName + index}") <del> .col-xs-3.col-sm-1.col-md-2.padded-ionic-icon.text-center </del> <ins> .col-xs-2.col-sm-1.col-md-2.padded-ionic-icon.text-right </ins> input(type='checkbox' class='challenge-list-checkbox') <del> .col-xs-9.col-sm-11.col-md-10 </del> <ins> .col-xs-10.col-sm-11.col-md-10 </ins> li.step-text.wrappable!= step .col-xs-12.col-sm-12.col-md-8 .embed-responsive.embed-responsive-16by9

extends ../layout-wide block content .row <del> .col-md-4.bonfire-top </del> <ins> .col-md-4 </ins> h4.text-center= name hr ol for step, index in description .row.checklist-element(id="#{dashedName + index}") <del> .col-xs-3.col-sm-1.col-md-2.padded-ionic-icon.text-center </del> <ins> .col-xs-2.col-sm-1.col-md-2.padded-ionic-icon.text-right </ins> input(type='checkbox' class='challenge-list-checkbox') <del> .col-xs-9.col-sm-11.col-md-10 </del> <ins> .col-xs-10.col-sm-11.col-md-10 </ins> li.step-text.wrappable!= step .col-xs-12.col-sm-12.col-md-8 .embed-responsive.embed-responsive-16by9
Change:
Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; WOW64) 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:
you need a closing brace after the quoted class.
thanx

Discussion:
h4.negative-10.text-nowrap Community Builder img.profile-image(src='https://s3.amazonaws.com/freecodecamp/branden-byers.jpg' alt="Branden Byers picture") h4.text-nowrap Madison, Wisconsin <del> p.negative-10 "I'm a massage therapist and Stay-at-home-dad. I learned Hypercard, then Rails, but now I feel at home with JavaScript." </del> <ins> p.negative-10 "Cookbook author and stay-at-home-dad. Started coding as a kid, got distracted, but now I'm back in full JavaScript force!" </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 Coordinator

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") h4.text-nowrap Seattle, Washington <del> p.negative-10 "My high school job was testing basketball shoes for Nike. I learned code to work smarter, not harder. I have no thyroid." </del>  No newline at end of file <ins> p.negative-10 "My high school job was testing basketball shoes for Nike. I learned code to work smarter, not harder. I have no thyroid." </ins>
Change:
Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; WOW64) 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:
you need a closing brace after the quoted class.
thanx

Discussion:
"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'." ], <del> "challengeEntryPoint": "titleCase("I'm a little tea pot")", </del> <ins> "challengeEntryPoint": "titleCase("I'm a little tea pot");", </ins> "challengeSeed": "function titleCase(str) {n  return str;rn}", "tests": [ "expect(titleCase("I'm a little tea pot")).to.be.a('String');",
Change:
Return statement Issue: JS Line 3: Return statement text should be "Greater than 10" instead of "10 or bigger" Challenge Link : Browser Version : v47.0.2526.106 (64-bit) Operating System Version : Mac OS X 10.11.2 Steps to reproduce: to the above challenge link and check the text. (Optional)Read/Run the below test case in the above waypoint challenge page myTest(10) should return "Between 5 and 10" Screenshot 1: ! Screenshot 2: !
:+1: yes "10 or bigger" means
This same waypoint has some more minor bugs associated with it (in the test cases). They are : To save PR Reviewer time, I am merging this very minor issues in one and creating one commit to fix this.

Discussion:
"challengeSeed": [ "function myTest(val) {", "  if(val > 10) {", <del> "    return "10 or Bigger";", </del> <ins> "    return "Greater than 10";", </ins> "  }", "  ", "  if(val < 5) {",

"" ], "solutions": [ <del> "function myTest(val) {n  if(val > 10) {n    return "10 or Bigger";n  } else if(val < 5) {n    return "Smaller than 5";n  } else {n    return "Between 5 and 10";n  }n}" </del> <ins> "function myTest(val) {n  if(val > 10) {n    return "Greater than 10";n  } else if(val < 5) {n    return "Smaller than 5";n  } else {n    return "Between 5 and 10";n  }n}" </ins> ], "tests": [ "assert(code.match(/else/g).length > 1, 'message: You should have at least two <code>else</code> statements');", "assert(code.match(/if/g).length > 1, 'message: You should have at least two <code>if</code> statements');", <del> "assert(myTest(0) === "Smaller than 5", 'message: <code>myTest(4)</code> should return "Smaller than 5"');", "assert(myTest(5) === "Between 5 and 10", 'message: <code>myTest(5)</code> should return "Smaller than 5"');", </del> <ins> "assert(myTest(0) === "Smaller than 5", 'message: <code>myTest(0)</code> should return "Smaller than 5"');", "assert(myTest(5) === "Between 5 and 10", 'message: <code>myTest(5)</code> should return "Between 5 and 10"');", </ins> "assert(myTest(7) === "Between 5 and 10", 'message: <code>myTest(7)</code> should return "Between 5 and 10"');", "assert(myTest(10) === "Between 5 and 10", 'message: <code>myTest(10)</code> should return "Between 5 and 10"');", <del> "assert(myTest(12) === "10 or Bigger", 'message: <code>myTest(12)</code> should return "10 or Bigger"');" </del> <ins> "assert(myTest(12) === "Greater than 10", 'message: <code>myTest(12)</code> should return "Greater than 10"');" </ins> ], "type": "waypoint", "challengeType": "1",
Change:
Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.1; WOW64) 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. conditions are not displayed ... not abele to continue. !
It does still pass if the correct code is provided. Your code uses the variable named when the instructions ask for a variable called . For testers: Able to reproduce on Attempting to run any code, except passing code, does not make the tests appear as it has with previous similar issues. After successful code is run the tests appear, but will disappear again with a hard refresh.
ou that's right, i passed, but i only see conditions after i passed... tanks sludge256

Discussion:
"" ], "tail": [ <del> "(function(t) { if(typeof t !== 'undefined') { return "Total = " + t; } else { return "Total is undefined";}})(total);" </del> <ins> "(function(){if(typeof total !== 'undefined') { return "total = " + total; } else { return "total is undefined";}})()" </ins> ], "solutions": [ "var myArr = [ 2, 3, 4, 5, 6];nvar total = 0;nnfor (var i = 0; i < myArr.length; i++) {n  total += myArr[i];n}"
Change:
Challenge has an issue. User Agent is: <codeMozilla/5.0 (X11; Linux x8664) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: I was asked to use "the first few words of this kitty ipsum text". I copied the first two words, but it failed validation. I tried copying the first three words instead, and that worked. Google defines 'a few' as "a small number of". synonyms: a small number, a handful, one or two, a couple, two or three_. Edit: it appears that copying 3 or more words works, but copying just 2 of them doesn't.
This isn't bike-shedding. It is rejecting valid solutions very early on in the first lesson, when it is important not to discourage people. Are reports like this not wanted?
Just discovered this. Yeah, "first few" should be "first three". Why have the ambiguity?
Having worked through most of the rest of the programming exercises I wonder if the aim is to get programmers used to working from low-quality specifications. Even if that is the case, I think having a poorly specified problem this early on runs too high a risk of putting people off forever.
That's certainly an interesting idea. I could imagine some sort of course where you must sort through (intentionally) ambiguous and unintelligible requirements to potentially satisfy an irate product manager or customer with unrealistic deadlines. Call it "Worse-case scenario" training :D
Call it: Situation Normal training.
Yes. FreeCodeCamp(now with Situation Normal Training)

Discussion:
"<p>Hello Paragraph</p>" ], "tests": [ <del> "assert.isTrue((/Kitty(s)+ipsum(s)+dolor/gi).test($("p").text()), 'message: Your <code>p</code> element should contain the first few words of the provided <code>kitty ipsum text</code>.');" </del> <ins> "assert.isTrue((/Kitty(s)+ipsum/gi).test($("p").text()), 'message: Your <code>p</code> element should contain the first few words of the provided <code>kitty ipsum text</code>.');" </ins> ], "challengeType": 0, "nameEs": "Llena espacios con texto de relleno",