jiebi/CodeConvo huggingface dataset:
Change:
"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": [

Discussion:
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:

Challenge [Bonfire: Validate US Telephone Numbers] Apparently the test case "telephoneCheck("555-555-5555") should return true." runs twice.
Change:
"description": [ "We're done playing with our jQuery playground. Let's tear it down!", "jQuery can target the <code>body</code> element as well.", <del> "Here's how we would make the entire body fade out: <code> $("body").addClass("animated fadeOut")</code>", </del> <ins> "Here's how we would make the entire body fade out: <code> $("body").addClass("animated fadeOut");</code>", </ins> "But let's do something more dramatic. Add the classes <code>animated</code> and <code>hinge</code> to your <code>body</code> element." ], "tests": [

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: The example code should have valid Javascript code but the semicolon at the end is missing. !
(Sorry, used the wrong branch at first.)
Change:
description, instructions, translationPending, <del> superBlock </del> <ins> superBlock, block </ins> } }, isChallengeCompleted,

Discussion:
Describe your problem and how to reproduce it: In the challenges/projects that don't use editor, link text at the top in the contain some additional text, for example Challenges that have editor on page don't seem to have this problem. Add a Link to the page with the problem: If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! !
Change:
Within `tests/2_functional-tests.js`, immediately after the `Browser` declaration, add your project URL to the `site` property of the variable: ```js <del> Browser.site = 'http://localhost:3000'; // Your URL here </del> <ins> Browser.site = 'http://0.0.0.0:3000'; // Your URL here </ins> ``` Then at the root level of the `'Functional Tests with Zombie.js'` suite, instantiate a new instance of the `Browser` object with the following code:

Discussion:
Setting causes the error Using Or forcing the DNS result order () fixes it. The best I can tell, in newer versions of Node the DNS result order has changed (might have been in v17). We had to fix a different challenge at one point to allow IPv6 IPs. I think this issue is related. Not sure what the best solution is but we might have to update the boilerplate or the challenge text. We can force the result order in the boilerplate if needed. Edit: My best guess why we haven't seen this issue more is because we (at least at one point) forced the engine in and possibly Replit running older versions of Node for a long time. I believe most people will see it locally with new versions of Node and I see it on Gitpod running Node 20. Not to get an error with the code the challenge tells you to use. 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] Forum:
:sparkles: Thanks to the community, there's an estimated bounty value of $6.81 USD for a successful merge request of this issue via contributions such as 9.750 STORJ tokens. Happy coding :grinning: Details and T&Cs at
I think updating the challenge text to expect is good.
Change:
Add a `style` attribute to the `div` in the code editor to give the text a color of red and font size of `72px`. <del> Note that you can optionally set the font size to be a number, omitting the units `px`, or write it as `72px`. </del> <ins> Note that you can optionally set the font size to be a number, omitting the units `px`, or write it as `"72px"`. </ins> # --hints-- The component should render a `div` element.

Discussion:
Currently, the instructions in module happens to be as follows: The instructions tell the users that instead of setting the font size property to a number ( i.e. 72 ), they can optionally set the font size property to but don't inform the user that needs to be enclosed within quotes i.e. needs to be a string value. Furthermore, the word units in the second sentence should be changed to unit because in this particular case, we are just referring to a single unit i.e. . Considering this, I think the instructions of module should be reworded as follows: The instructions in module should be as follows: <img width="517" alt="image" src=""- Device: Laptop OS: macOS 13.0.1 Browser: Chrome Version: 107.0.5304.110
Hello there, I would like to contribute by fixing this issue,I wanted to ask whether I have to be assigned to this issue to contribute of I can start right away? Also, can you please guide me on where can i find that component to contribute? Thanks :)
Oh~ I see. I was so confused why 72px doesn't work. Good thing I found this issue. Thanks for posting
I'm not sure about this. The instructions explicitly mention that this is a JavaScript Object, which at this point in the curriculum is something that campers should be familiar with. I would be okay with something like:
Or maybe just update the literal value shown. Considering the part "or write it as" it should show the actual value to write.
Thanks for the feedback , ! I think having it as looks like a good solution to this issue. Thanks guys for the input. I'll go ahead and create a PR. Cheers!
Change:
assert.match(sellWeapon.toString(), /golds*+=s*15/); ``` <del> You should set `goldText.innerText` to gold. </del> <ins> You should set `goldText.innerText` to `gold`. </ins> ```js assert.match(sellWeapon.toString(), /goldText.innerTexts*=s*gold/);

Discussion:
There is a typo in Step 108, the word is single while it should be . Here is the typo in step 102, there is a missing code block in this line it should be this in step 81, there are three missing code blocks in these line they should be 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.
I would like to work on this.
feel free to open a pull request, after you have read .
I have opened a PR please let me know if there are any changes or improvements that needs to be done.
Change:
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')

Discussion:
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: "Your #name-label should contain text that describes the input". No response N/A No response
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.
Change:
} ${ projectFormValues <del> ?.map(([key, val]) => `${key}: ${val}n`) </del> <ins> ?.map(([key, val]) => `${key}: ${transformEditorLink(val)}n`) </ins> ?.join('') || filesToMarkdown(files) }

Discussion:
In , if a user has submitted a project link, it will display the project's working view instead of the source code. I am not so sure adding the solution links as is currently functioning is helping much. See . Instead of showing the final project link, it would be more useful to show the source code link. In the linked forum post, going to the project results in the "Hmmm.... We Couldn't Reach Your Repl" page. For at least , we should restructure the link (if needed) to show the editable version of the project. For example, if the user submits , then we show . For Codepen projects, this is not an issue, but for Backend projects where the source code is not readily available, we either need to make my above suggested changes or remove this feature for backend challenges/projects. If a user is hosting their own project, then the same issue arises. Unless they submit a GitHub link to their project source code, a final project view does not help us identify problems for the user.
I was recently thinking about this, and just wondered how stable it would be to transform the Camper's URL into the project code URL. If you think this is a decent feature to have, and worth it, then I am willing to throw something together. I will put out a POC, now. Side Note: I have been looking into the fiasco, as some lessons still cause the dents.
Change:
"We can use if statements in JavaScript to only execute code if a certain condition is met.", "if statements require some sort of boolean condition evaluate.", "Example:", <del> "<code> if (1 == 2) {", </del> <ins> "<code> if (1 == 2) {</code>", </ins> "<code>&thinsp;&thinsp;return(true);</code>", "<code>}</code>", "<code>else {</code>",

Discussion:
Challenge has an issue: ! It looks to me as if this code is missing a closing code bracket:
Change:
</Button> ); const ShowMultifileProjectSolution = ( <del> <div className='solutions-dropdown'> </del> <ins> <div> </ins> <Dropdown id={`dropdown-for-${id}-${randomIdSuffix}`}> <Dropdown.Toggle className='btn-invert'> {viewText}{' '}

Discussion:
contains a single CSS rule: This rule is not needed as the underline of the is already turned off by the component library. Remove Remove the class from
This issue is open for contribution. 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. 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.
Change:
`bob instanceof Person` should return `true`. ```js <del> assert.deepEqual(bob instanceof Person, true); </del> <ins> assert.deepEqual(_test_bob instanceof Person, true); </ins> ``` `bob.firstName` should return `undefined`. ```js <del> assert.deepEqual(bob.firstName, undefined); </del> <ins> assert.deepEqual(_test_bob.firstName, undefined); </ins> ``` `bob.lastName` should return `undefined`. ```js <del> assert.deepEqual(bob.lastName, undefined); </del> <ins> assert.deepEqual(_test_bob.lastName, undefined); </ins> ``` `bob.getFirstName()` should return the string `Bob`. ```js <del> assert.deepEqual(bob.getFirstName(), 'Bob'); </del> <ins> assert.deepEqual(_test_bob.getFirstName(), 'Bob'); </ins> ``` `bob.getLastName()` should return the string `Ross`. ```js <del> assert.deepEqual(bob.getLastName(), 'Ross'); </del> <ins> assert.deepEqual(_test_bob.getLastName(), 'Ross'); </ins> ``` `bob.getFullName()` should return the string `Bob Ross`. ```js <del> assert.deepEqual(bob.getFullName(), 'Bob Ross'); </del> <ins> assert.deepEqual(_test_bob.getFullName(), 'Bob Ross'); </ins> ``` `bob.getFullName()` should return the string `Haskell Ross` after `bob.setFirstName("Haskell")`.

Discussion:
A user can fail with correct code because the tests secretly rely upon global variables accessible to the user. This code fails because the user has the correct solution but deleted the instantiation of the object. Tests should instantiate any data they need. We should update the seed code to We should then add and modify the test suite to use instead of . No response All No response
Hello, Just to clarify, did you want to add in the user code block? Because I noticed when I attempted to reproduce the bug you encountered that two test cases still passed, despite not being initialized in the user's code. I checked the lesson's markdown file and found out that those two test cases did have their own initialized. I was thinking of adding to all the test cases instead. For reference, here's the code for one of the test cases that still passed, despite the bug.
Those tests initiate their own values so they are fine. I'm talking about the tests that fail if users modify their seed code to not have the object initialization. The new variable would go into a new --after-user-code-- part; that's not currently present. Just adding this new variable inside of the seed creates the exact same problem. Note - this issue isn't marked as ready for contributions yet. Maybe we should review if the tests logic too to see if they are independent
Opening this up for contribution.
Hi assign this issue for branch bugfix/. I have resolved it, need to create PR for same
We don't assign issues. The first PR that fully covers the issue will be accepted.
Hi ok !! I have raised PR . thanks for reply.
Change:
### --feedback-- <del> `There are` is used for plural nouns, and `bank` is singular. You’ll learn about there are in the next few lessons. </del> <ins> `There are` is used for plural nouns, and `bank` is singular. You’ll learn about `there are` in the next few lessons. </ins> ---

Discussion:
needs to be wrapped in backticks ( ``) in the first sentence needs to be wrapped in backticks. Here also needs to be wrapped in backticks. This looks like something that can be fixed by "first-time" code contributors to this repository. The files you should look at to work on a fix are the 3 linked above. 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.
Change:
## ![:beginner:](https://forum.freecodecamp.com/images/emoji/emoji_one/beginner.png?v=3 ":beginner:") 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> ![:rocket:](https://forum.freecodecamp.com/images/emoji/emoji_one/rocket.png?v=3 ":rocket:") <a href='https://repl.it/CLjU/38' target='_blank' rel='nofollow'>Run Code</a> </del> ### Code Explanation:

Discussion:
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.
That 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?
Change:
"assert($("p").length > 1, 'message: You need 2 <code>p</code> elements with Kitty Ipsum text.');", "assert(code.match(/</p>/g) && code.match(/</p>/g).length === code.match(/<p/g).length, 'message: Make sure each of your <code>p</code> elements has a closing tag.');", "assert.isTrue((/Purrs+jumps+eat/gi).test($("p").text()), 'message: Your <code>p</code> element should contain the first few words of the provided additional <code>kitty ipsum text</code>.');", <del> "assert(Number.parseInt($("p:eq(0)").css("font-size"), 10) > 15 && Number.parseInt($("p:eq(1)").css("font-size"), 10) > 15, 'message: Give elements with the <code>p</code> tag a <code>font-size</code> of <code>16px</code>.')" </del> <ins> "assert(Number.parseInt($("p:eq(0)").css("font-size"), 10) > 15 && Number.parseInt($("p:eq(1)").css("font-size"), 10) > 15, 'message: Give elements with the <code>p</code> tag a <code>font-size</code> of <code>16px</code>. Browser and Text zoom should be at 100%.');" </ins> ], "challengeType": 0, "nameEs": "Cambia el tamaño de fuente de un elemento.",

Discussion:
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.111 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:
Hmm, I can't repro this. Do you have your browser zoomed in at all? Have you tried any other browsers?
Hey Itegman, Thanks for the response, yes my browser was size at 75%. After setting zoom to 100% the challenged passed.
Closing as a duplicate of . We've got a PR up now that will add a warning about needing to be 100% zoom for this particular challenge.
Change:
editableRegionBoundaries?: number[]; }) => void; usesMultifileEditor: boolean; <ins> isChallengeCompleted: boolean; </ins> } // TODO: this is grab bag of unrelated properties.  There's no need for them to

Discussion:
I am learning from the RWD course, and I wanted to revise what I had done previously. I went to previous steps, but I found that the steps are shown incomplete when I open them. It tells you to do the step again. This doesn't make sense because you have a button at the top if you do want to do the step again. Completed code should be shown in completed challenge's code editor along with an indicator like ! !
It would be relatively easy to show the solution to a step, and the "Step completed" text, (rather than storing the user's code) if a user has already submitted that step. If other maintainers are in favour of this change, I'd be happy to open this up for PRs.
My concern with that approach would be it completely destroys the UX if someone wants to go through a practise project again.
I propose to add a button under the summary of each project for this issue.
I'm not keen on adding a button to do that, given the potential for frustration if someone triggers that accidentally.
I think I'd be in favour of the existing flow, presonally.
At a minimum, we could probably add the checkmark next to "Step 22" like we do for all the other challenges after it has been completed. That seems to be missing here. !
That's a good idea, IMO.
I think just adding that check mark is probably the way to go then. It keeps it consistent with everything else. I'm going to open it up for contributions. If anyone still has reservations, be sure to bring them up.
May I suggest in addition to indicating completed challenges in the challenge itself, to do that in the list of steps. Here is a crude representation of what I have in mind: <p align="center"<img src="https://user-" width=500 align="centre"/</p
I believe it already does that. Here's a screenshot of what the challenge looks like for me, after I've completed it (the steps are highlighted in blue instead of white). !
Also, I would like to work on this issue, and I agree that adding a checkmark next to the step would be a good fix, but I noticed that the RWD courses don't have a step number or title at the top like the other courses do.

For other courses, the checkmark for completion is displayed next to the name of the challenge, like you can see in the first screenshot (of the JS Algorithms & Data Structures courses). However, for the RWD course, there is nothing in this location, as you can see in the second screenshot. ! ! How should we go about adding a checkmark to the RWD course? Should we just put it next to where it says on the screenshot (inside the instructions block)? Or should we move the step number to the same place as where the challenge names are for the other courses and put the checkmark there, in order to be consistent with the other courses?
Thanks I could not log in since yesterday and this is probably the reason I don't see indication for completed challenges in the list of steps.