jiebi/CodeConvo huggingface dataset:
Code change:
"id": "bad87fee1348cd8acef08812", "title": "Create a Block Element Bootstrap Button", "description": [ <del> "Normally, your <code>button</code> elements are only as wide as the text that they contain. By making them block elements, your button will stretch to fill your page's entire horizontal space.", </del> <ins> "Normally, your <code>button</code> elements are only as wide as the text that they contain. By making them block elements, your button will stretch to fill your page's entire horizontal space and any elements following it will flow onto a "new line" below the block.", </ins> "This image illustrates the difference between <code>inline</code> elements and <code>block-level</code> elements:", "<a href="http://i.imgur.com/O32cDWE.png" data-lightbox="img-enlarge"><img class="img-responsive" src="http://i.imgur.com/O32cDWE.png" title="Click to enlarge" alt="An "inline" button is as small as the text it contains. In this image, it's centered. Below it is a "block-level" button, which stretches to fill the entire horizontal space.'></a>", "Note that these buttons still need the <code>btn</code> class.",

Related discussion:
text: I think "Each id should be unique to a specific element." would be less ambiguous (and more accurate) as "Each id must be unique on the page."
Code change:
"id": "bad87fee1348cd8acef08812", "title": "Create a Block Element Bootstrap Button", "description": [ <del> "Normally, your <code>button</code> elements are only as wide as the text that they contain. By making them block elements, your button will stretch to fill your page's entire horizontal space.", </del> <ins> "Normally, your <code>button</code> elements are only as wide as the text that they contain. By making them block elements, your button will stretch to fill your page's entire horizontal space and any elements following it will flow onto a "new line" below the block.", </ins> "This image illustrates the difference between <code>inline</code> elements and <code>block-level</code> elements:", "<a href="http://i.imgur.com/O32cDWE.png" data-lightbox="img-enlarge"><img class="img-responsive" src="http://i.imgur.com/O32cDWE.png" title="Click to enlarge" alt="An "inline" button is as small as the text it contains. In this image, it's centered. Below it is a "block-level" button, which stretches to fill the entire horizontal space.'></a>", "Note that these buttons still need the <code>btn</code> class.",

Related discussion:
text: I want to suggest that, at this point, in addition to the comment about the block element ' stretch to fill your page's entire horizontal space.', there is a comment that any element following it will flow to a "new line". You could argue that is [almost] "assumed". But I believe it should be stated.
Code change:
], "challengeSeed":[ "//var ourDog = {", <del> "//   "name": "Camper"", "//   "legs": 4", "//   "tails": 1", </del> <ins> "//   "name": "Camper",", "//   "legs": 4,", "//   "tails": 1,", </ins> "//   "friends": ["everything!"]", "//};", "",

Related discussion:
text: Challenge has an issue. The commented code sample at the top of the challenge is missing commas between properties. <img width="1158" alt="screen shot 2015-08-16 at 5 01 57 pm" src=""
And on this challenge, too.
Code change:
export function insertEditableRegions(challengeFiles = []) { if (challengeFiles?.some(file => file.editableRegionBoundaries?.length > 0)) { const editableRegionStrings = fileExtension => { <del> const startComment = fileExtension === 'html' ? '<!--' : '/*'; const endComment = fileExtension === 'html' ? '-->' : '*/'; return `n${startComment} User Editable Region ${endComment}n`; </del> <ins> switch (fileExtension) { case 'html': return 'n<!-- User Editable Region -->n'; case 'css': return 'n/* User Editable Region */n'; case 'py': return 'n# User Editable Regionn'; case 'js': return 'n// User Editable Regionn'; default: return 'nUser Editable Regionn'; } </ins> }; const filesWithEditableRegions = challengeFiles.map(file => {

Related discussion:
text: The creation of the help wanted forum post should be changed to use correct Python comments for files. Right now the posts are created with the wrong type of comment. !
I want to work on this issue
We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labelled with or are open for contributions. Please make sure you read . We prioritize contributors following the instructions in our guide. Join us in or if you need help contributing - our community will be happy to assist you.
Code change:
`bookList` should not change and still equal `["The Hound of the Baskervilles", "On The Electrodynamics of Moving Bodies", "Philosophiæ Naturalis Principia Mathematica", "Disquisitiones Arithmeticae"]`. ```js <ins> add(bookList, "Test"); </ins> assert( JSON.stringify(bookList) === JSON.stringify([

Related discussion:
text: <!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. -- This is the starter code: The starter code for this challenge is strange. 1) Why the space between the function name and the ()s for the arguments? 2) I get that the idea is to have the learners change the function signature, but it is a bit strange having a mismatch between the function signatures and the function calls in the starter code.
The linked PR in this issue. For , we could probably move away from having variables in the seed code and instead assert the function returns the expected value
Code change:
}; this._editor = null; <ins> this.focusOnEditor = this.focusOnEditor.bind(this); </ins> } editorWillMount = monaco => {

Related discussion:
text: Is your feature request related to a problem? Please describe. It currently can take a several key presses to navigate to the editor if it does not have focus. Describe the solution you'd like It should be possible to focus on the editor with a hotkey, for example 'e'. The issue where this was mostly discussed will be closed soon, but some thoughts about implementing this appeared there:
Code change:
import { createSelector } from 'reselect'; import { executeChallenge, updateFile } from '../redux'; <del> import { userSelector } from '../../../redux'; </del> <ins> import { userSelector, isDonationModalOpenSelector } from '../../../redux'; </ins> import { Loader } from '../../../components/helpers'; const MonacoEditor = React.lazy(() => import('react-monaco-editor')); const propTypes = { <ins> canFocus: PropTypes.bool, </ins> contents: PropTypes.string, dimensions: PropTypes.object, executeChallenge: PropTypes.func.isRequired,

Related discussion:
text: Describe the bug When you go to a challenge and the donation modal appears a stack overflow error occurs To Reproduce Steps to reproduce the behavior: Chrome go to on the dev console error Screenshots ! Desktop (please complete the following information): OS: Ubuntu Browser Chrome Version 76.0.3809.100 (Official Build) (64-bit) Additional context Removing removes it, so presumably it's a clash between that and the modal.
You are correct, I think there could be a race condition between the two.
Code change:
], "challengeSeed":[ "// var ourDog = {", <del> "//   "name": "Camper"", "//   "legs": 4", "//   "tails": 1", </del> <ins> "//   "name": "Camper",", "//   "legs": 4,", "//   "tails": 1,", </ins> "//   "friends": ["everything!"]", "// };", "",

Related discussion:
text: Challenge has an issue. The commented code sample at the top of the challenge is missing commas between properties. <img width="1158" alt="screen shot 2015-08-16 at 5 01 57 pm" src=""
And on this challenge, too.
Code change:
assert.exists(title); ``` <del> The `title` element should be within the `head` element. </del> <ins> Your `title` element should be within the `head` element. </ins> ```js assert.exists(document.querySelector('head > title')); ``` <del> Your project should have a title of `Registration Form`. </del> <ins> Your project should have a title of `Registration Form`. Remember, the casing and spelling matters for the title. </ins> ```js const title = document.querySelector('title'); <del> assert.equal(title.text.toLowerCase(), 'registration form') </del> <ins> assert.equal(title.text, 'Registration Form'); </ins> ``` <del> Remember, the casing and spelling matters for the title. </del> <ins> You should create a `meta` element within the `head` element. </ins> ```js <del> const title = document.querySelector('title'); assert.equal(title.text, 'Registration Form'); </del> <ins> assert.exists(document.querySelector('head > meta')); ``` You should give the `meta` element a `charset` attribute with the value of `utf-8`. ```js assert.equal(document.querySelector('head > meta')?.getAttribute('charset')?.toLowerCase(), 'utf-8'); ``` Your `meta` element should be a void element, it does not have an end tag `</meta>`. ```js assert.notMatch(code, /</metas*>?/i); </ins> ``` # --seed--

Related discussion:
text: I followed Step 4 instructions. As I finished typing out the element, by habit I press + , and noticed that it accepted it, even though it shouldn't have as I was still missing the element It should have failed, as it's still missing the that Step 4 asked for ! Device: PC OS: Window 11 Version 23H2 Browser: Firefox 127.0.2 (64-bit) No response
This seem to also happen in other parts of the same course, such as Step 7 ! As you can see, it is missing its closing tag As well as Step 11 ! It's missing its closing tag yet the Step still validate it
Can you please open a new issue for the form element. I'm guessing the browser is auto closing it, and we don't have a regex test for it. It should result in a valid form element, because the browser will close it. However, the element technically does not have any "Tag omission" so it should have an end tag in the HTML (even if it gets to the DOM by the browser).
Done
Code change:
id: 587d778d367417b2b2512aaa title: Make Elements Only Visible to a Screen Reader by Using Custom CSS challengeType: 0 <del> videoUrl: 'https://scrimba.com/c/c8azdfM' </del> <ins> videoUrl: 'https://scrimba.com/c/cJ8QGkhJ' </ins> --- ## Description

Related discussion:
text: The video for the lecture does not exist.
Two videos from that section are missing: "Add an Accessible Date Picker" and "Make Elements Only Visible to a Screen Reader by Using Custom CSS". It seems both videos are down on the Scrimba platform. In the , both videos seem to be missing. If this video has been uploaded elsewhere, we can replace the URL for now. Otherwise, those two videos may need to be re-uploaded. Side note: The playlists are also incorrectly named. It seems that the Applied Accessibility and Applied Visual Design titles have accidentally been switched.
Code change:
"Aside from using open source libraries such as jQuery and Bootstrap, and short snippets of code which are clearly attributed to their original author, 100% of the code in my projects was written by me, or <del> along with another camper with whom I was pair programming in real time." </del> <ins> along with another person going through the freeCodeCamp curriculum with whom I was pair programming in real time." </ins> </p> <p key={5}> "I pledge that I did not plagiarize any of my freeCodeCamp.org work. I

Related discussion:
text: <img width="1074" alt="Profile_freeCodeCamp_org" src="https://user-"
can I take this issue?
Thank you and for your interest. This issue might need a little more investigation before arriving at the final solution. I encourage you to find similar issues to tackle in the meantime. should I only audit the copy to replace profile with portfolio or you would rather changing the profile instances in the client and the api-server entirely?
I would like to get it assigned..
this should come as a cosmetic change to the copy only, do not change any endpoints or code (functions, objects, files) etc. It can be done to both API and the client where copy edit is needed.
Code change:
"Aside from using open source libraries such as jQuery and Bootstrap, and short snippets of code which are clearly attributed to their original author, 100% of the code in my projects was written by me, or <del> along with another camper with whom I was pair programming in real time." </del> <ins> along with another person going through the freeCodeCamp curriculum with whom I was pair programming in real time." </ins> </p> <p key={5}> "I pledge that I did not plagiarize any of my freeCodeCamp.org work. I

Related discussion:
text: <img width="927" alt="Settings_freeCodeCamp_org" src="https://user-"
Code change:
], "MDNlinks": [ "Comparison Operators", <del> "String.slice()", </del> <ins> "Array.slice()", </ins> "Array.filter()", "Array.indexOf()", <del> "String.concat()" </del> <ins> "Array.concat()" </ins> ], "type": "bonfire", "challengeType": 5,

Related discussion:
text: Challenge has an issue. It seems that it's more appropritae to show helpful links to: () () instead of: () () Am I right?
Code change:
The `<header>` tag is a container which is used for navigational links or introductory content. It may typically include heading elements, such as `<h1>`, `<h2>`, but may also include other elements such as a search form, logo, author information etc. <del> <h1> corresponds to the most important heading. As we move to other tags like <h2>, <h3>, etc the degree of importance decreases. </del> <ins> `<h1>` corresponds to the most important heading. As we move to other tags like `<h2>`, `<h3>`, etc the degree of importance decreases. </ins> Although not required, the `<header>` tag is intended to contain the surrounding sections heading. It may also be used more than once in an HTML document. It is important to note that the `<header>` tag does not introduce a new section, but is simply the head of a section. Here's an example using the `<header>` tag:

Related discussion:
text: <!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: The formatting of the header-tag page in the guide is wrong. I checked the codebase and there are missing back-ticks for some of the html tags in the markdown page. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: Version 70.0.3538.102 (Official Build) (64-bit) Operating System: MacOS 10.14.1 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !
Code change:
"<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",

Related discussion:
text: 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)
Code change:
const res = await fetch(url + '/api/users', { method: 'POST', headers: { 'Content-Type': 'application/x-www-form-urlencoded' }, <del> body: `username=fcc_test_${Date.now()}`.substingr(0, 29) </del> <ins> body: `username=fcc_test_${Date.now()}`.substring(0, 29) </ins> }); if (res.ok) { const { _id, username } = await res.json();

Related discussion:
text: I have pass all test case of "Exercise Tracker" challenge except the 7th test case("you can POST to /api/users/:id/exercises with ..."), I tried many way but still can't pass this test case. When i open the console of Chorm, i found the bug "(...).subtingr is not a function" when i click on the button "I've completed this challenge" to submit the `` the console of brower the link into Solution Link on "I've completed this challenge" error This error should be disappear ! Device: [Laptop] OS: [Windows 11] Browser: [Chrome] Version: [106.0.5249.103] No response
~Please provide the link to the project that you submitted~ EDIT: still half asleep sorry, ignore that
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: List of files: Line contains the typo, should be . 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.
Hello, I am interested in working on it
hey there, I suggest reading our contributing guidelines! as it says, all issues with and labels are up for grabs
I have fixed this issue and raised a PR.
Code change:
"In the game of <a href="https://en.wikipedia.org/wiki/Golf" target="_blank">golf</a> each hole has a <code>par</code> meaning the average number of <code>strokes</code> a golfer is expected to make in order to sink the ball in a hole to complete the play. Depending on how far above or below <code>par</code> your <code>strokes</code> are, there is a different nickname.", "Your function will be passed <code>par</code> and <code>strokes</code> arguments. Return the correct string according to this table which lists the strokes in order of priority; top (highest) to bottom (lowest):", "<table class="table table-striped"><thead><tr><th>Strokes</th><th>Return</th></tr></thead><tbody><tr><td>1</td><td>"Hole-in-one!"</td></tr><tr><td>&lt;= par - 2</td><td>"Eagle"</td></tr><tr><td>par - 1</td><td>"Birdie"</td></tr><tr><td>par</td><td>"Par"</td></tr><tr><td>par + 1</td><td>"Bogey"</td></tr><tr><td>par + 2</td><td>"Double Bogey"</td></tr><tr><td>&gt;= par + 3</td><td>"Go Home!"</td></tr></tbody></table>", <del> "<code>par</code> and <code>strokes</code> will always be numeric and positive." </del> <ins> "<code>par</code> and <code>strokes</code> will always be numeric and positive. We have added an array of all the names for your convenience." </ins> ], "releasedOn": "January 1, 2016", "challengeSeed": [ <ins> "var names = ["Hole-in-one!", "Eagle", "Birdie", "Par", "Bogey", "Double Bogey", "Go Home!"];", </ins> "function golfScore(par, strokes) {", "  // Only change code below this line", "  ",

Related discussion:
text: I agree with MiloATH's proposed changes. Would definitely reduce the potential for typos when working the problem. As a side note, feel free to let me know if I am breaking any GitHub etiquette at any point. Zero experience providing input on collaborative projects. Looking for to learning and have really enjoyed FreeCodeCamp thus far. You guys and gals are doing awesome work. :)
Sure - we will let you know in a polite way if you break GitHub etiquette. Thanks for being receptive to feedback :)
Code change:
--fcc-editable-region-- function pick(guess) { <del> let numbers = []; </del> <ins> const numbers = []; </ins> } --fcc-editable-region--

Related discussion:
text: No need to use here since the array is not re-assigned in later steps. We used for other arrays in this project that aren't reassigned. No response All No response
Hello, I fixed this by doing the following: 1) went to 2) found the ID of step-162 () 3) went to the repositories code and searched for the markdown file through ID. 4) the markdown file 5) Updated the markdown file to use 'const' instead of 'let' ! After this commit is approved, this should be able to be closed.
All of the seed code for subsequent challenges would also be changed.
I am not sure what you mean by this. Is there anything I can do to learn this? Are you referring to all references of 'let' initialization to be changed to 'const' in future steps?
Not quite - the answer to this step becomes part of the starting code for all future steps. If we change the instructions to use here, then then starting code on all future steps needs to be swapped to reflect that.
Hi, I raised a PR to fix this
Code change:
return ( <button className={classes} onClick={onClick} type='button'> <del> <span className='sr-only'>{label ?? 'Close'}</span> </del> <ins> <span className='sr-only'>{label || 'Close'}</span> </ins> <span aria-hidden>×</span> </button> );

Related discussion:
text: I got a mini heart attack as I randomly tested the Storybook page of the component and found that the component failed a11y checks. <img width="1680" alt="Screenshot 2024-03-06 at 00 49 32" src=""This is because: We pass as an empty string to the component in the Storybook demo: We use the operator in the computation of the button's label, which would only fall back to if is either or : Note that this issue is only in Storybook and not in /learn as we do pass a to there: In , replace the operator with the operator In , make an empty object instead of containing empty and
I do not care much about the implementation, BUT, surely if a label of is never valid, then it is best to make the optional, and not pass one to the component? That is, I can imagine passing to a component because I do not want one, but was forced to pass one because it is not optional.
For this particular component, I agree that can be optional or can even be removed as a configuration option, since I don't think we need any customization here (the button's label should just be "Close" rather than something else). In fact, is already an optional prop of . However, has a limitation, which is that the library is not localized, so we still want to pass strings from /learn in order to have them translated. Semi-related, there was a discussion a while back regarding whether or not we should expose for consumption outside of . We decided to export the component because: The component in doesn't have a close button, but its version in /learn (which is called ) has one, so was built. (I wasn't around during the development of most of the components so I don't have the full context of the technical design) The limitation mentioned above.
Code change:
Your `letters.forEach()` callback function should be nested inside the `range(1, 99).forEach(number => {}` callback function. ```js <del> assert.match(code, /ranges*(s*1s*,s*99s*)s*.forEachs*(s*((s*numbers*)|number)s*=>s*{s*[^}]*letters.forEach(s*((s*letters*)|letter)s*=>s*{s*}s*)s*}s*)/) </del> <ins> assert.match(code, /ranges*(s*1s*,s*99s*)s*.forEachs*(s*((s*numbers*)|number)s*=>s*{s*[^}]*letters.forEach(s*((s*letters*)|letter)s*=>s*{s*}s*)s*;?s*}s*)/) </ins> ``` # --seed--

Related discussion:
text: This step will fail with code and will pass removing the semicolon at the end of the third line. It doesn't look like this test allows for semicolon