jiebi/CodeConvo huggingface dataset:
Change:
# --description-- <del> It's time to hook up the `playNextSong` function to an event listener. </del> <ins> Now it is time to test out the `playNextSong` function. </ins> Add a `click` event listener to the `nextButton` element, then pass in `playNextSong` as the second argument of your event listener. This is the function the event listener will run. <ins> Test out your app by first clicking on the play button followed by the next button. You should see that everything is working as expected. </ins> # --hints-- You should call the `addEventListener()` method on your `nextButton` variable.

Discussion:
This project is missing key times to encourage the camper to test out their code. This will help camper see the results of the code they just wrote. 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
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 Happy coding
Change:
**Examples** ```js <del> 2   < 5 '3' < 7 5   < 5 3   < 2 '8' < 4 </del> <ins> 2   < 5 // true '3' < 7 // true 5   < 5 // false 3   < 2 // false '8' < 4 // false </ins> ``` <del> In order, these expressions would evaluate to `true`, `true`, `false`, `false`, and `false`. </del> # --instructions-- Add the less than operator to the indicated lines so that the return statements make sense.

Discussion:
The student has to go all the way down up to the explanation "In order, these expressions would evaluate to true, false, true, and true." to realize what the result of the operations is. My suggestion is that the second section of the code should look like this: 1 == 1 // true 1 == 2 // false 1 == '1' // true "3" == 3 // true instead of the screenshot attached. <!-- Add a link to the coding challenge with the problem. -- <!-- If applicable, add screenshots to help explain your problem. you can drag and drop, png, jpg, gif, etc. in this box. --!
I would be fine with this change. Any interest in making a PR for it
, Can I? I don't know how to do it and I have never done it in my life, but besides that, I would like to do it by myself using some guide you could give me. I have never used GitHub in the past. And this will help me to contribute even more to this awesome project.
We have some . It may look a little intimidating, but if you follow the instructions it's not bad. The file where this needs to be fixed is Technically, you can edit the file on github and make a PR from there - which can work for some simple fixes, but you can't see and test your changes. I think we would accept those if you want to do that, but I would recommend setting the project up locally at some point if you want to contribute regularly. To be clear, we usually like to get second opinion before making changes like this - since we don't have that, I can't guarantee a PR would be merged - but I think others would be fine with the change so if you want to make a PR, go ahead.
This change seems good. For context, we got rid of a lot of comments since we'd need to translate them. However, these are keywords and don't need translation.
shall I take this up?
Could you clarify if this is actually what we wanted, because this is exactly what we removed 12 months ago in:
Yes, this is okay because these instances specifically are only keywords that don't get translated anyway.
Change:
"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>.');",

Discussion:
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.
Change:
```js let array = [1, 2, 3]; array[1] = 25; <ins> console.log(array); // prints [1, 25, 3] </ins> ``` Update the **third** element of your `rows` array to be the number `10`. Then print the `rows` array to your console.

Discussion:
We are getting a lot of confusion on the forum about step 18. The confusion stems from not know how to log the array to the console. So we should update the code example in the description to log the example array. That should help with what is expected to do. js let array = [1, 2, 3]; array[1] = 25; (array); // prints [1, 25, 3] ` 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
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 Happy coding
Change:
You should assign `arr.map()` to the `playerCards.innerHTML` using the `+=` operator. ```js <del> assert.match(code, /playerCards.innerHTMLs*+=s*arr.map(s*(s*)s*=>s*{s*}s*)/) </del> <ins> assert.match(code, /playerCards.innerHTMLs*+=s*arr.map(s*((s*)s*=>|functions*(s*))s*{s*}s*)/); </ins> ``` # --seed--

Discussion:
A camper on the forum ran into an issue here They wanted to know why they couldn't pass with a regular function for the callback. the directions don't specify it should be an arrow function instead. but both answers should pass. So the tests should be updated. 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
Hi, Can I work on fixing this issue ? I would need some help in locally setting up so that I can test my code changes.
Change:
"var b = 2;", "", "// Only change code below this line", <del> " " </del> <ins> "" </ins> ], "tail": [ "(function(a,b){return "a = " + a + ", b = " + b;})(a,b);"

Discussion:
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: This is a very minor issue, almost trivial, but this Waypoint initializes the editor with an unnecessary space right under . The space can be found if you look back at the code It should be instead of .
Easy enough. I'll grab this one.
So maybe I'm doing something wrong but I just fetched the latest from "staging" and there is no space between the quotation marks in the latest version. This appears to have already been corrected.
Hmmm, I'm not sure why you're not seeing it on your end. I still see it on github and in the most recent staging I just pulled down.
My mistake, I hadn't pushed to my forked repo and I guess that was keeping the latest fetched files from showing. Should be fixed with
Change:
--fcc-editable-region-- let done = 0; <del> while (rows.length <= count) { </del> <ins> while (rows.length < count) { </ins> done++; rows.push(padRow(done, count)); }

Discussion:
On step 89 and 90 of the Pyramid generator there is this misterious error that appear, it can be confusing for campers. !
Error is coming from the function, specifically one of the string repeats. Depending on the and , when or will be , calling method of string will show that error. Edit: When condition is there's no such issue.
Yep. I think reworking the lessons so we never leave the learner with broken code (or at least never unexplained broken code) is the way to go.
I'm not sure if it was even intended to have broken code, description is suggesting everything should work fine. Step 91 asks for two changes, one of which specifically makes this error appear (second change fixes the issue).
Yeah, it's a bit confusing. Probably not intentional, though. On 91 there's this: the only time I don't see the error is when I've followed all the instructions on step 91.
Is this not enough to clear up any doubts? Cuz after following the instructions in step 91, there's nothing mysterious about the error anymore.
I don't think so. Step 89, where error is introduced, doesn't mention it. Neither does 90. It's only when you reach 91 that the error is mentioned and the text is which is incorrect. Changing to has no effect on the error. It's only the combination of that and adjusting the conditional that finally removes the error. The main issue with this is that it breaks the feedback loop between learner's actions and the code's behaviour. Speaking for myself, everything gets harder when the results of my actions are essentially invisible. I know we run tests to check you re doing it right, but that's not really a substitute for them seeing how your actions impact the program.
Okay. We need to at least note the possibility of an unexpected error to the camper. I'm thinking on step 89 now.
Just for posterity, the steps got shifted. Error is introduced by completing step 95 Error is resolved by completing step 96 What should be changed here: Step 95 should: Introduce and explain the error Ask the campers to change the comparison to Step 96 should: No longer ask campers to change the to Not mention that creates a
Change:
The content of this repository is bound by the following licenses: - The computer software is licensed under the [BSD-3-Clause](LICENSE.md) license. <del> - The learning resources in the [`/curriculum`](/curriculum) and [`/guide`](/guide) directories including their subdirectories thereon are licensed under the [CC-BY-SA-4.0](/curriculum/LICENSE.md) license. </del> <ins> - The learning resources in the [`/curriculum`](/curriculum) directory including their subdirectories thereon are licensed under the [CC-BY-SA-4.0](/curriculum/LICENSE.md) license. </ins>

Discussion:
<!-- 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 am trying to find the guide folder, but it that I cannot locate it. Was it remove temporarily or relocated to a different section? <details<summaryPrevious report </summaryAdd a Link to the page with the problem: Just take a look on the freeCodeCamp repository main section and and the guide folder is missing. Tell us about your browser and operating system: Browser Name: Chrome Browser Version: Version 74.0.3729.169 (Official Build) (64-bit) Operating System: Windows 10 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! <details
Yes, the guide has been removed from this repo completely. See: We will not have the general guide articles anymore. Instead we intend to publish these as tutorials that are curated by the editorial team. These would then be published by them on the Developer News. The challenge hints and articles will still be available on the forum which we have already migrated. I am closing this thread, but pinning this for visibility. <details<summaryPrevious comment </summaryThe current production guide at , will soon be moved over to our forum as a wiki. The changes that were made over the past months will also be to the forum wiki post migration. We are no longer accepting any pull-requests for the guide on this repository. Contribution Guidelines for the same will be made available soon. We request your patience. <details
Change:
)} {!isMobile && ( <DesktopLayout <del> challengeFiles={reduxChallengeFiles} </del> <ins> challengeFiles={challengeFiles} </ins> challengeType={challengeType} editor={renderEditor({ isMobileLayout: false,

Discussion:
During development adding or modifying the head or tail code ( and ) don't seem to be updated in the challenge. Tested locally and on gitpod. Steps to reproduce the behavior: /modify the or in challenge. For example one of the steps in the JS curriculum. I was adding function and variables to it, and then was attempting to use them in tests. and wait for challenge to be updated. () the challenge page, or visit it for the first time. running tests, referencing the function/variables from head/tail code, there will be reference errors. Changing head or tail code, should update the challenge to use it. Login status don't seem to affect issue. During changing the code, thinking I might do something incorrectly, there were handful times when challenge was updated with the head/tail code. Not sure what was the exact reason. What makes it stranger is stopping client develop and starting again, is not necessarily solving the problem. At some point I thought that's working to get challenge fully updated, but right now that doesn't seem to work.
I might have seen this as well. I remember trying to save a regex in to use in multiple tests, and it didn't seem to work. Kind of just thought I was using it incorrectly, but maybe this was the issue.
Thanks for the detailed investigation of another tricky bug. It was another example where saved code messes things up. They're always a pain to debug because everyone sees something different, depending on whether or not they have something saved. Hopefully this is the last of them!
What's the most throwing off, that wasn't even code saved manually!
Weird. Is there nothing in your local storage?
Hmm, well there is after running tests. That must have been the point when saving mishap happened.
Oh, that's right. No mystery beyond "how did I forget this?" :face_exhaling:
Change:
"<code>});</code>" ], "tests":[ <del> "assert(singleVal == 30, 'message: <code>singleVal</code> should have been set to the result of you reduce operation.');", </del> <ins> "assert(singleVal == 30, 'message: <code>singleVal</code> should have been set to the result of your reduce operation.');", </ins> "assert(editor.getValue().match(/.reduce(/gi), 'message: You should have made use of the reduce method.');" ], "challengeSeed":[

Discussion:
Challenge Waypoint: Condense arrays with reduce has an issue. User Agent is: codeMozilla/5.0 Windows NT 6.1; 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: javascript var array 4,5,6,7,8 ; var singleVal 0; // Only change code below this line. // Only change code above this line. FUNCTION {return singleVal;} ; singleVal should have been set to the result of you reduce operation : change "you" to "your"
thanks for pointing this out!
Change:
"descriptionEs": [ "Ahora quitemos un elemento HTML de tu página usando jQuery.", "jQuery tiene una función llamada <code>.remove()</code> que eliminará un elemento HTML por completo", <del> "Elimina el elemento <code>target4</code> de la página utilizando la función <code>.remove()</code>." </del> <ins> "Elimina el elemento con identificación <code>target4</code> de la página utilizando la función <code>.remove()</code>." </ins> ] }, {

Discussion:
[x] Learn how Script Tags and Document Ready Work [x] Target HTML Elements with Selectors Using jQuery [x] Target Elements by Class Using jQuery [x] Target Elements by ID Using jQuery [x] Delete your jQuery Functions [x] Target the same element with multiple jQuery Selectors [x] Remove Classes from an element with jQuery [x] Change the CSS of an Element Using jQuery [x] Disable an Element Using jQuery [x] Change Text Inside an Element Using jQuery [x] Remove an Element Using jQuery [x] Use appendTo to Move Elements with jQuery [x] Clone an Element Using jQuery [x] Target the Parent of an Element Using jQuery [x] Target the Children of an Element Using jQuery [x] Target a Specific Child of an Element Using jQuery [x] Target Even Numbered Elements Using jQuery [x] Use jQuery to Modify the Entire Page
Checking
Change:
You should assign `arr.map()` to the `playerCards.innerHTML` using the `+=` operator. ```js <del> assert.match(code, /playerCards.innerHTMLs++=s*arr.map(s*(s*)s*=>s*{s*}s*)/) </del> <ins> assert.match(code, /playerCards.innerHTMLs*+=s*arr.map(s*(s*)s*=>s*{s*}s*)/) </ins> ``` # --seed--

Discussion:
The tests of this step have an issue with spacing, this code fails: This code passes:
Thanks 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: Regex in 4th test should be changed to optionally allow spaces before , from: to: 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.
/attempt
Change:
React.createElement(StatefulComponent) ); const initialState = mockedComponent.state(); <del> return mockedComponent.find('h1').text() === initialState.name; </del> <ins> return mockedComponent.find('h1').text() === initialState.firstName; </ins> })() ); ```

Discussion:
A user wondering why his solution passed. I then realized the 2nd test test is not working as intended. The user is supposed to assign a string to a property of . The user's solution assigns an uninitialized variable as a property. The purpose of the test is to make sure the user assigns a string value to a prop named , but the test still allows the user to pass as the prop's value and the test passes. Not sure why, but assigning an uninitialized property to ends up assigned an empty string to it. This of course passes the test requirement but defeats the purpose of the learning here. I suggest changed the required property name to something like , so if a user does something like this, all of the tests will fail. Test in question: The second test should fail because the property of should be undefinedbecause it was not initialized by the user's code. 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
After a bit of research, it appears that assigning as a property that is uninitialized is the same as writing: = { } Since the window has no name, it is just an empty string.
Change:
**Examples** ```js <del> 6   >=  6 7   >= '3' 2   >=  3 '7' >=  9 </del> <ins> 6   >=  6  // true 7   >= '3' // true 2   >=  3  // false '7' >=  9  // false </ins> ``` <del> In order, these expressions would evaluate to `true`, `true`, `false`, and `false`. </del> # --instructions-- Add the greater than or equal to operator to the indicated lines so that the return statements make sense.

Discussion:
The student has to go all the way down up to the explanation "In order, these expressions would evaluate to true, false, true, and true." to realize what the result of the operations is. My suggestion is that the second section of the code should look like this: 1 == 1 // true 1 == 2 // false 1 == '1' // true "3" == 3 // true instead of the screenshot attached. <!-- Add a link to the coding challenge with the problem. -- <!-- If applicable, add screenshots to help explain your problem. you can drag and drop, png, jpg, gif, etc. in this box. --!
I would be fine with this change. Any interest in making a PR for it
, Can I? I don't know how to do it and I have never done it in my life, but besides that, I would like to do it by myself using some guide you could give me. I have never used GitHub in the past. And this will help me to contribute even more to this awesome project.
We have some . It may look a little intimidating, but if you follow the instructions it's not bad. The file where this needs to be fixed is Technically, you can edit the file on github and make a PR from there - which can work for some simple fixes, but you can't see and test your changes. I think we would accept those if you want to do that, but I would recommend setting the project up locally at some point if you want to contribute regularly. To be clear, we usually like to get second opinion before making changes like this - since we don't have that, I can't guarantee a PR would be merged - but I think others would be fine with the change so if you want to make a PR, go ahead.
This change seems good. For context, we got rid of a lot of comments since we'd need to translate them. However, these are keywords and don't need translation.
shall I take this up?
Could you clarify if this is actually what we wanted, because this is exactly what we removed 12 months ago in:
Yes, this is okay because these instances specifically are only keywords that don't get translated anyway.
Change:
<del> npx lint-staged </del> <ins> NODE_OPTIONS="--max-old-space-size=7168" npx lint-staged </ins>

Discussion:
Linting fails on local environment in some cases. Issue did not reproduce on GitPod. update-email to the root directory Execution fails with the message under Linting should be successful No response Device: Macbook Air M2 OS: MacOSThis issue was originally raised in Discord: Thread created with the full error log: A contributor also ran into this issue in the past: Note that the lint operation in this one ran against the entire project () rather than a single file.
Thanks for opening this issue. I'm not able to reproduce the issue locally, so I'll need your help with this: Add: after this line: Commit this change using the flag Make a change to and check if you can commit the change without the flag This is to check if those rules are the culprit as I did run into some performance issues with them in the past. Here is our eslint current performance, in case anyone is interested: <img width="521" alt="Screenshot 2023-12-18 at 13 58 26" src=""
Thanks for your help I am still facing the issue. I the two lines after line 89, committed with --no-verify. I a space to and tried to commit without the flag. Attached the stack trace.
It seems like the memory allocation on your machine is capped at 2 GB. I tried reducing the limit to 512 MB using the following command, but could not reproduce the issue still: I'm wondering if it works if you increase the value on your end to . So please try this: In the root, add the following line to the "scripts" block: Then run in the terminal
Fixed it! I tried running but that did not seem to update the memory allocation when I ran Instead, I ran something similar to your command in the terminal - This fixed it. Thanks a lot! Should we add this in the documentation?