jiebi/CodeConvo huggingface dataset:
Change:
[stubTrue, identity] ]); <del> export function concatHtml({ required = [], template, files = [], theme = 'night' } = {}) { theme = theme === '' ? 'night' : theme; </del> <ins> export function concatHtml({ required = [], template, files = [] } = {}) { </ins> const createBody = template ? _template(template) : defaultTemplate; <del> const displayTheme = theme === 'night' ? nightThemeStyle : ` `; </del> const head = required .map(({ link, src }) => { if (link && src) {

Discussion:
I did not see anyone raising this issue, but I don't think the background of the preview in default or night mode should be anything other than white unless the coding exercise specifically changes the background to something else. The preview should be exactly what you would see in a browser. In almost all the challenges, the background would be white. !
I share your concerns The reason we changed the color of the display is that a white display is discomforting to the eye on night mode when everything else is dark. so we injected some styles to harmonize the view in general. That convention was carried over to light mode.
It might be better to default to white in light mode, same as the editor. As for night mode, some of the css challenges might need some changes to look reasonable in both modes. For instance, in night mode, looks like this: ! If we change the seed code to it would become ! It would have to be case-by-case, though.
That is a very good point. I will defer this to
Logically, I have to agree with - displaying anything other than what the code in the editor would produce might confuse campers. But it is a little rough on the eyes to have the white background on night mode. And the current theme looks a lot better - so it's a tough call. I scrolled through a number of challenges, and there's quite a few that don't look right with the blue background. So there might be a decent amount of work to go through and fix all of them.
I really like the new theme, but a preview should be a true preview. We want to make this like the real world. Developers working in some kind of night mode on their favorite local editors, still expect to check the "real" result of the code they have written on a browser or in a preview mode in their local editors. The night mode should only apply to the editor or the non-preview part of the FCC site. Anything else is just not realistic.
The preview should be white.
I agree with everyone here on this thread. The preview should remain white. Note that soon the preview won't always be there on the right side "brightening up" the user interface and ruining people's night mode experience.

Soon we will have a single column layout where you the preview only shows up when you click a button to show it, or it loads in a separate tab. - could you update the styling on this so that the preview area is unaffected by our styling?
Definitely.
Change:
"challengeSeed": [ "function myTest(val) {", "  if(val > 10) {", <del> "    return "10 or Bigger";", </del> <ins> "    return "Greater than 10";", </ins> "  }", "  ", "  if(val < 5) {",

Discussion:
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.
Change:
--focus-outline-color: var(--blue-mid); --font-family-sans-serif: 'Lato', sans-serif; --font-family-monospace: 'Hack-ZeroSlash', monospace; <del> --header-element-size: 30px; </del> <ins> --header-element-size: 28px; </ins> --header-sub-element-size: 45px; <del> --header-height: 56px; </del> <ins> --header-height: 38px; </ins> --breadcrumbs-height: 44px; --z-index-site-header: 200; }

Discussion:
The current header height of the learn platform is over 50. Please set it to 38px. Instructions: find the --header-height variable and set it 38px similar to the following: --header-height: 38px;
Change:
assert.match(code, /consts+collisionDetectionRuless*=s*[s*(?:[^]]*s*)*s*]s*;?/); ``` <del> You should have a boolean expression that checks if the player's `y` position plus the player's height is less than or equal to the platform's `y` position. </del> <ins> You should have a boolean expression that checks whether the player's `y` position plus the player's height is less than or equal to the platform's `y` position. </ins> ```js assert.match(code, /consts+collisionDetectionRuless*=s*[s*player.position.ys*+s*player.heights*<=s*platform.position.ys*,?s*]s*;?/);

Discussion:
following task ask for : reading this line suggests/ indicates to me writing an "if" statement inside of the array although that could be my understanding of the sentence my suggestion would be to update the sentence to the following No response Device: [macBook pro] OS: [Ventura 13.4.1 ] Browser: [chrome ] Version: [121.0] No response
Hi ! Thank you for creating this issue. I think the re wording makes sense. The only thing, I would change would be the first part of that sentence. We should mention explicitly that they are adding to the array. I will go ahead and open this up for contribution for
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
I updated the instructions of step 78 and committed the changes. Please have a look at that Thank you
I am sorry but since I am new to open-source contributions, I accidentally closed the previous PR. I am making a new Pull Request please have a look at that.
Change:
getContext } from 'redux-saga/effects'; import { channel } from 'redux-saga'; <ins> import escape from 'lodash/escape'; </ins> import { challengeDataSelector,

Discussion:
I stumbled upon this issue when playing around with the challenge. If a user wanted to see what the output of the final variable (the converted version of the string) to the FCC console, it does not get rendered showing the converted entities. You can see in the screenshot below that the browser console has the correct values but the FCC console does not show the same thing. ! I am guessing there are several other challenges where the user would not see the HTML code and would instead send the rendered version in the FCC console.
Change:
border-color: var(--secondary-color); background-color: var(--secondary-color); color: var(--secondary-background); <ins> cursor: pointer; </ins> } .btn:active,

Discussion:
When you mouse over the signin buttons on the buttons do not show the pointer cursor. They just show the default cursor. These buttons should show the cursor pointer like all the other buttons on freeCodeCamp.
Should I work on this? if allows
go ahead please.
Change:
"title": "Use Spans for Inline Elements", "difficulty": 2.105, "description": [ <del> "You can use use spans to create inline elements. Remember when we used the <code>btn-block</code> class to make the button fill the entire row?", </del> <ins> "You can use spans to create inline elements. Remember when we used the <code>btn-block</code> class to make the button fill the entire row?", </ins> "This image illustrates the difference between <code>inline</code> elements and <code>block-level</code> elements:", "<img class="img-responsive" src="https://www.evernote.com/l/AHTFU358y71AV6mokPeuTEgrZVdUJ4A8v3AB/image.png" 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.'>", "By using the <code>span</code> element, you can put several elements together, and even style different parts of the same element differently.",

Discussion:
Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. First line of the challenge has a typo where the word "use" comes twice: You can use use spans to create inline elements.
I have created a pull request that should close this issue. I can't merge it in myself though so we will have to wait until someone with write access to this repository can approve the pull request. Then this issue will be fixed in staging.
Change:
Create a `taskObj` object with an `id` property as the first property. For the value of the `id` property, retrieve the value of the `titleInput` field, convert it to lowercase, and then use the `split()` and `join()` methods to hyphenate it. <del> Make sure all of those are in template literals because you need the `id` property value as a string. </del> <ins> Make sure that the value of the `id` property is enclosed within template literals, as you will be appending more to the string later on. </ins> # --hints--

Discussion:
The instructions say, in part: A literal (heh) reading of these instructions resulted in a learner producing this code: I read the instructions and could not figure out what the template string was supposed to do. I had to check the next step. I'm still confused, because a join produces a string output, so it seems completely superfluous. See above. I don't know exactly how to reword this, but the "all of those" is probably too ambiguous. No response N/A No response
Yeah, I agree. it is not clear what it is pointing to. It could be reworded as, Or something along those lines. The next steps is adding a hyphen followed by So the final result will be this
May I proceed to create a pull request to address this issue? I require a merged pull request contribution for my university assignment in open source.
This wording looks good to me. If you want to create a PR you're welcome to do so.
I am currently addressing this issue and have submitted a pull request.I would greatly appreciate it if you could review my pull request at your earliest convenience. If the changes meet the project's standards and requirements, I kindly ask for your assistance in merging them.This contribution is essential for my university assignment.
Change:
``` <del> You should assign `letter + number` to `input.ariaLabel`. </del> <ins> You should give `input.ariaLabel` the same value as `input.id`. </ins> ```js <del> assert.match(code, /input.ariaLabels*=s*letters*+s*number/); </del> <ins> assert.match(code, /input.ariaLabels*=s*((letters*+s*number)|(input.id))/); </ins> ``` # --seed--

Discussion:
Step 18 of the spreadsheet project (js beta) asks us to: Set the aria-label attribute for the input element to the same value as the id attribute. This should be doable just by saying: ; But this code is not accepted and the hint shown is: You should assign letter + number to input.ariaLabel. I think the step should accept assigning into input.ariaLabel No response N/A No response
Yeah, I agree. should pass the test. Since the instruction is vague, I think the test should allow both answers: - Note that the hint text needs to be updated as well. I guess it could be something like:
Change:
const store = null; // Define the Redux store here, passing in your reducers ``` <ins> ## --after-user-code-- ```js const _store = Redux.createStore(counterReducer) ``` </ins> # --solutions-- ```js

Discussion:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --<!-- Add a link to the coding challenge with the problem. -- <!-- Copy and paste the code from the editor that you used in between the back-ticks below: --<!-- Add a clear and concise description of what you expected to happen. --This should be accepted as a correct answer, as it solves the challenge. <!-- Please complete the following information. --- Device: PC OS: Windows 10 Browser: Firefox Version: 97.0.1 <!-- Add any other context about the problem here. --The problem arises if the user tries to test their Redux store functionality After checking the source code of the challenge, the problem seems to be the method used to check if user initiated state correctly or not found in This is resulting in a false assert because the user has modified their state (with Tests) I don't know of a way to assert that the user initialized state other than the way mentioned above Maybe add a note that the user should remove their tests before checking their answer? Sorry if this was mentioned before, but I didn't find it so decided to open the issue.
Rather than adding note, more convenient might be creating new store during the test, off the , and checking initial state of that one.
I agree with gikf's suggestion here. We could create an section under and declare a which we could pass to the tests.
Change:
# --solutions-- ```js <del> // solution required </del> <ins> function numberRotations(minDigits, maxDigits) { const DIGITS_TO_KEEP = 100000n; const powersOfTen = Array(maxDigits).fill(0); powersOfTen[0] = 1n; for (let i = 1; i < maxDigits; i++) { powersOfTen[i] = powersOfTen[i - 1] * 10n; } // We want numbers of the form xd * m = dx // Or more precisely: //   (x * 10 + d) * m = d*10^(n-1) + x // Solving for x: //   x = d (10^(n-1) - m) / (10 * m - 1) let total = 0n; for (let numDigits = minDigits; numDigits <= maxDigits; numDigits++) { // Check all multiplier - digit pairs to see if a candidate can be built //  with the correct number of digits for (let multiplier = 1n; multiplier < 10n; multiplier++) { for (let lastDigit = 1n; lastDigit < 10n; lastDigit++) { const numerator   = lastDigit * (powersOfTen[numDigits - 1] - multiplier); const denominator = (powersOfTen[1] * multiplier - 1n); if (numerator % denominator === 0n) { const candidate = (numerator / denominator) * 10n + lastDigit; if (candidate.toString().length === numDigits) { total = (total + candidate) % DIGITS_TO_KEEP; } } } } } return parseInt(total); } </ins> ```

Discussion:
The 100 should be a superscript in the last line of this challenge. N/A Should say We may also consider better mathematical formatting? No response All No response
Seems like it has been like this for a while: I will open this up to first timers. The expected fix is to use MathJax (KaTeX-like) to render the following: $$ n: 10 < n < 10^{100} $$ An issue with the first timers only label is open 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
I actually saw a way to roll this into a fix that expands the challenge so that won't work.
Change:
] ], "type": "hike", <del> "challengeType": 6 </del> <ins> "challengeType": 6, "nameEs": "JavaScript Lingo: Matemáticas", "descriptionEs": [ "Hay un objeto estático de nombre 'Math' en JS con muchos propiedades y métodos incluidos.", "Vas a querer investigar más de este cuando manipules números. Consulta la documentación de MDN antes de escribir tus propias funciones, pues ya podrían estar definidas allí. ", "Los ejemplos incluyen <code>Math.random()</code> que devolverá un número aleatorio en un rango y <code>Math.round()</code> que redondeará el número decimal que reciba al entero más cercano.", "Yo utilicé <code>Math.random()</code> cuando construí el generador de citas aleatorias como proyecto de desarrollo de interfaces en FreeCodeCamp.", "Cuando trabajes con números, también debes estar consciente de que JS tiene un atributo interesante llamado 'formato de coma flotante'.", "Dependiendo de la cantidad de números, su tamaño y la cantidad de cálculos, JS puede devolver un número que es inexacto en 0,00004.", "Hay maneras de evitar esto, y en general no plantean problemas, pero es algo que debes tener en cuenta si te encuentras con algunos problemas que parecen no tienen sentido." ] </ins> }, { "id": "56b15f15632298c12f315186",

Discussion:
[ ] JavaScript Lingo: MDN and Documentation [ ] JavaScript Lingo: Value Types [ ] JavaScript Lingo: Variables & camelCase [ ] JavaScript Lingo: Arrays & Objects [ ] JavaScript Lingo: Finding and Indexing Data in Arays [ ] JavaScript Lingo: Manipulating Data [ ] JavaScript Lingo: Math [ ] JavaScript Lingo: Loops [ ] JavaScript Lingo: Regular Expressions
Working on this one
Change:
font-weight: normal; } <ins> .donation-form .btn { white-space: normal; } </ins> .modal-close-btn-container { display: flex; justify-content: center;

Discussion:
!
Could you give a link to the page as then it might be easier to solve the issue?
This should be the case on the user's profile page. You can reproduce by setting the certificate keys to true in the user object.
I could work on this!
I am already working on it.
Thanks for letting me know!
a reasonable fix would be to give the grid that contains the profile a class and on the css, change the button under that class and have . you will end up with something like this. here it is on small and large screens <img width="681" alt="screen shot 2019-02-22 at 2 18 10 pm" src="https://user-"<img width="1095" alt="screen shot 2019-02-22 at 2 17 53 pm" src="https://user-"
Similar solution could be applied to these donate buttons probably. but the selectors should be very specific not to change the styling on other buttons in the platform. <img width="669" alt="screen shot 2019-02-23 at 2 09 14 pm" src="https://user-"<img width="502" alt="screen shot 2019-02-23 at 2 08 51 pm" src="https://user-"
Hey or Can you take this up? just updated us that he will be a bit busy with other things.
I'm on it
Change:
*   <a href='https://forum.freecodecamp.com/t/regular-expressions-resources/15931' target='_blank' rel='nofollow'>Regex</a> *   <a href='https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp/test' target='_blank' rel='nofollow'>Regex.test</a> <del> ![:rocket:](https://forum.freecodecamp.com/images/emoji/emoji_one/rocket.png?v=3 ":rocket:") <a href='https://repl.it/CLjU/39' target='_blank' rel='nofollow'>Run Code</a> </del> ## ![:rotating_light:](https://forum.freecodecamp.com/images/emoji/emoji_one/rotating_light.png?v=3 ":rotating_light:") Advanced Code Solution: function rot13(str) { // LBH QVQ VG!

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:
link = 'http://' + link; } var story = new Story({ <del> headline: sanitizeHtml(data.headline), </del> <ins> headline: sanitizeHtml(data.headline, { allowedTags: [], allowedAttributes: [] }).replace(/&quot;/g, '"'), </ins> timePosted: Date.now(), link: link, <del> description: sanitizeHtml(data.description), </del> <ins> description: sanitizeHtml(data.description, { allowedTags: [], allowedAttributes: [] }).replace(/&quot;/g, '"'), </ins> rank: 1, upVotes: data.upVotes, author: data.author,

Discussion:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Test for this lesson may not check the syntax for any constructor syntax, instead looks like it's tested by output. EIther user provide the constructor(correct/expected way) or not, challenge passes. Browser Name: Chrome Browser Version: 67 Operating System: Win7
I'm on it.
following solution works to passs the test: function makeClass() { "use strict"; / Alter code below this line / class Vegetable { constructor(Vegetable) { this. Vegetable = Vegetable; } } / Alter code above this line / return Vegetable; } const Vegetable = makeClass(); const carrot = new Vegetable('carrot'); (); // =should be 'carrot'
Hello, Unfortunately, this solution doesn't work for me. (The same as in the "Hint": ) Error message: // running tests should return carrot. // tests completed
sorry to hear that! Would you mind posting your solution here so we could take a look?
Hello Kristofer, Thank you for your email. (ES6: Use class Syntax to Define a Constructor Function) I have already got help from FreeCodeCamp. I used the solution from "HINT", but it didn't work. class Vegetable { constructor(Vegetable){ this.Vegetable = Vegetable; } } What worked is the code below: class Vegetable { constructor(name) { = name; } } Thank you. Kind regards, Zsolt
Change:
# --description-- <del> Make the `header` take up the full width of its parent container, set it's `height` to `50px`, and set the `background-color` to `#1b1b32`. Then, set the `display` to use _Flexbox_. </del> <ins> Make the `header` take up the full width of its parent container, set its `height` to `50px`, and set the `background-color` to `#1b1b32`. Then, set the `display` to use _Flexbox_. </ins> # --hints--

Discussion:
There's a consistent grammatical issue. The author uses "it's" to indicate possession, when the correct word is "its". Due to this, I am also willing to look for other grammatical errors. They could cause confusion, or, at the very least, annoyance. /Note: this issue is present throughout the entire challenge/ n/a n/a Device: Macbook Air OS: Mac OS Ventura Browser: Chrome This is more of a writing issue than a tech one. I hope that's ok.
Thank you for taking the time to open this. I am only able to see the use of in 2 challenges: step-8 step-10 Would you mind sharing any more?
An issue with the label is open 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