jiebi/CodeConvo huggingface dataset:
Change:
A <code>version</code> is one of the required fields of your package.json file. This field describes the current version of your project. Here's an example: ```json <del> "version": "1.2", </del> <ins> "version": "1.2.0", </ins> ``` </section>

Discussion:
I noticed this while looking at another issue. Glitch is giving me an error when using version "1.0" in my file. It only seems to work when I use a third number: "1.0.0" - I'm not sure if this has always been the case since I don't think it threw this error in the past. But suggests to use a two digit version. It should probably be changed if this isn't allowed. EDIT: actually the project will still run with the invalid version - I thought it was causing the project not to run. But glitch does still give an error about it.
made a PR :+1:
Change:
"<code>});</code>" ], "tests":[ <del> "assert.deepEqual(array, [1,2,3,4], 'message: You should have removed all the values from the array that are greater than 4.');", </del> <ins> "assert.deepEqual(array, [1,2,3,4,5], 'message: You should have removed all the values from the array that are greater than 5.');", </ins> "assert(editor.getValue().match(/array.filters*(/gi), 'message: You should be using the filter method to remove the values from the array.');", "assert(editor.getValue().match(/[1,2,3,4,5,6,7,8,9,10]/gi), 'message: You should only be using <code>.filter</code> to modify the contents of the array.');" ],

Discussion:
Assignment: Let's remove all the values greater than five Assert: You should have removed all the values from the array that are greater than 4. problem arises if user includes 5 in result set
Change:
Are you interested in contributing to our open source projects used by nonprofits? <del> Also, check out https://www.freecodecamp.org/contribute/ for some fun and convenient ways you can contribute to the community. </del> <ins> Also, check out https://contribute.freecodecamp.org/ for some fun and convenient ways you can contribute to the community. </ins> Happy coding,

Discussion:
I got all the certs on .dev and got this email... ! The link should be updated to
Change:
```js var ourStr = "I come first. " + "I come second."; <del> // ourStr is "I come first.  I come second." </del> <ins> // ourStr is "I come first. I come second." </ins> ``` </section>

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: Example on the page has a double space instead of a single. var ourStr = "I come first." + "I come second." // ourStr is "I come first._I come second." Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Safari Browser Version: 13.1.1 Operating System: macOS If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): <img width="620" alt="Skjermbilde 2020-06-04 kl 21 13 12" src="https://user-"
I can confirm this. Thank you, for spotting it, and pointing it out.
Okay, I believe I have corrected this error.
Change:
<section id="description"> Sass中的<code>@if</code>指令对于测试特定情况很有用 - 它就像JavaScript中的<code>if</code>语句一样。 <blockquote> @mixin make-bold（$ bool）{ <br> @if $ bool == true { <br> font-weight：bold; <br> } <br> } </blockquote>就像在JavaScript中一样， <code>@else if</code>和<code>@else</code>测试更多条件： <blockquote> @mixin text-effect（$ val）{ <br> @if $ val == danger { <br>红色; <br> } <br> @else if $ val == alert { <br>颜色：黄色; <br> } <br> @else if $ val == success { <br>颜色：绿色; <br> } <br> @else { <br>颜色：黑色; <br> } <br> } </blockquote></section> ## Instructions <del> <section id="instructions">创建一个名为<code>border-stroke</code>的<code>mixin</code> ，它接受一个参数<code>$val</code> 。 <code>mixin</code>应使用<code>@if</code> ， <code>@else if</code>和<code>@else</code>检查以下条件： <blockquote>光 -  1px纯黑色<br>中等 -  3px纯黑色<br>重 -  6px纯黑色<br>没有 - 没有边界</blockquote></section> </del> <ins> <section id="instructions">创建一个名为<code>border-stroke</code>的<code>mixin</code> ，它接受一个参数<code>$val</code> 。 <code>mixin</code>应使用<code>@if</code> ， <code>@else if</code>和<code>@else</code>检查以下条件： <blockquote>光 - 1px纯黑色<br>中等 - 3px纯黑色<br>重 - 6px纯黑色 </blockquote> 如果<code>$val</code>不是<code>light</ code>，<code>medium</code>，或者<code>heavy</code>，则边框应该设置为<code>none</code>。 </section> </ins> ## Tests <section id='tests'>

Discussion:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Issue Description Following the given instructions. The test will fail for the border-stroke($val) { $val === light { border: 1px solid black; } if $val === medium { border: 3px solid black; } if $val === heavy { border: 6px solid black; } { border: none; } } The checkmark at the bottom left says: "Your mixin should have an statement to set the border to none." and it will pass if using "none" but not "no border" as suggested. My suggestion is to replace "no border" from the instructions with "none" Link to the page with the problem: browser and operating system: Browser Name: Chrome Browser Version: Version 71.0.3578.98 (Official Build) (64-bit) Operating System: MacOs Sierra Version 10.12.6
Are you still facing this problem because on my end the code is working fine?
Hi yes. I still have the same issue. Following the instructions, the last test doesnt pass ! If I put 'border: none' in the statement it passes !
I believe the instruction is little misleading. It should have been 'no border - none' instead of 'none - border' as border doesn't doesn't have a property called "no border" but does have a property called "none". I could change the description of it to reduce confusion. Please let me know if this clarifies your concern or if it is a completely different issue.
yes, it has clarified my issue. Thank you for your help.
Change:
overflow-y: auto; scrollbar-width: auto; /* lang menu should always be full height */ <del> height: 19.9rem; </del> } /* main menu must be at least as tall as lang menu (when displayed)

Discussion:
The language selection menu is not intuitive about the no. of available options. It's a bit paradoxical at the moment: You will not notice additional options until you start scrolling while being on top of the options. You will not start scrolling until you know there are additional options. to '/learn' on 'Menu' down to 'Change Language' the cursor on the options Scrolling while being in the area of the listed options. menu should be very clean and intuitive. "Cancel Change" option should have some form of visual separation. https://user- Device: All Devices OS: All OS Browser: All Browsers Version: All Versions No response
this will start becoming evident with more languages on the list. The quickest and simplest way this can be handled is by slightly increasing the height of the list and decreasing the height of the hover-state highlight (each item). That will leave some space at the bottom of the last item, intuitively letting the user know there is more to be looked at. Currently, the perfect-sized (height) items and the overall height of the list make it difficult to notice more entries. Finally, that "Cancel" option should be a different color or have some form of visual separation.
is this issue still being worked on? If not, I would like to take it.
That makes sense, I thought we fixed that. should be removed for and
or anyone else interested, this is up for grabs.
This is what makes the language menu full length so no vertical scroll bar appears. Originally, I had the language menu set so that a vertical scroll bar would appear if it was taller than the main menu. But it was decided that there shouldn't be a vertical scroll bar, the language menu should be as tall as necessary so no scroll bar was needed. Is this what we still want? Even as we continue to add even more languages?
thanks for bringing this up. Ideally we would need to show as many languages as possible in a viewport and display a minified scroll bar if the list exceeds the height viewport minus of the navigation. We could show a scrollbar initially as you recommended, but the dropdown needs expand further than the main menu if needed.
Change:
"<div class='hidden-xs row media-stories'>" + "<div class='media'>" + "<div class='media-left'>" + <del> "<a href='/'" + data[i].author.username + "'>" + </del> <ins> "<a href='/" + data[i].author.username + "'>" + </ins> "<img class='img-news' src='" + data[i].author.picture + "'/>" + "</a>" + "</div>" +

Discussion:
Task no. 7, says: "You can view the portfolio pages of any camper who has posted links or comments on Camper News. Just click on their photo." However, clicking a photo simply licks back to the homepage. Clicking their username links to their profile. So the instruction needs to be updated.
Thank you for finding and reporting this! I went the other way and fixed the bug instead of the instructions, seemed more appropriate ;)
No problem. Glad I could help.
Change:
Now you can start the code to fight monsters. To keep your code organized, your `fightDragon` function has been moved for you to be near the other `fight` functions. <del> Below your `weapons` array, define a `monsters` variable and assign it an array. Set that array to have three objects, each with a `name`, `level`, and `health` property. The first object's values should be `slime`, `2`, and `15`, in order. The second should be `fanged beast`, `8`, and `60`. The third should be `dragon`, `20`, and `300`. </del> <ins> Below your `weapons` array, define a `monsters` variable and assign it an array. Set that array to have three objects, each with a `name`, `level`, and `health` properties. The first object's values should be `slime`, `2`, and `15`, in order. The second should be `fanged beast`, `8`, and `60`. The third should be `dragon`, `20`, and `300`. </ins> # --hints--

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:
Create a rule that targets both `.one` and `.two` and increase their `blur` effect by 1 pixel. <del> Here's an example of a rule that increases the `blur` of two elements: ```css h1, p { filter: blur(3px); } ``` </del> # --hints-- <del> You should have a `.one, .two` selector. </del> <ins> You should have a `.one, .two` selector list. </ins> ```js const oneTwo = new __helpers.CSSHelp(document).getStyle('.one, .two');

Discussion:
It would make more sense for step 34 to have the filter syntax example, instead of it showing up in the next step. Explain and show the syntax. 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]
Yes, that totally needs to be done what about step 35? there I think the example is to remind people how to give same rules to multiple selectors. Should that be removed? double blur example?
Not sure if we need a selector list example as long as the hint text shows the selector. But I would like for the hint text to actually specify it as a selector list.
Change:
title, description, superBlock, <ins> block, </ins> translationPending } },

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:
<label>Do you have any questions:</label> </div> <div class="answer"> <del> <textarea rows="5" cols="24"> Who is flexbox... </textarea> </del> <ins> <textarea rows="5" cols="24" placeholder="Who is flexbox..."></textarea> </ins> </div> --fcc-editable-region-- </div>

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. -- The final instructions for this step say: "Then, give the placeholder text describing an example answer." Since the instructions mention "placeholder" I think it is safe to assume that some people will think they should use the attribute on the to fulfill this requirement. But the code check test checks the of the : So using the attribute will result in the following hint: "You should give the placeholder text describing an example answer." Which does not make it clear that the example answer should be embedded in the instead of using the attribute. Based on the current instructions I think most users will assume that the attribute should be used to complete this step and the test should be updated accordingly. <!-- Please complete the following information. --- Device: Desktop OS: Linux/Fedora 34 Browser: Firefox Version: 95.0.2
On
I was going to fix this issue by updating the test in step 38 to check the placeholder attribute on the textarea but then I realized that if we make this change then the HTML in each step after 38 would also need to be updated to use the placeholder attribute as well. So the question is, do we want to use the placeholder attribute and update all of the remaining steps or do we want to reword the instructions in step 38 to make it clear that you should embed the question text in the textarea and not use the placeholder attribute?
That's a good question. The placeholder text matches wording from referring to the attribute. That would make me think, the intention is to use the attribute.
Agreed, this should probably be updated to use the placeholder attribute. Looks like I've got a lot of updates to include in the PR.
Thank you, for opening this. When I wrote this, I vaguely remember reading a resource mentioning using the attribute on was not the recommended approach. However, as I cannot find that, I agree using the attribute in this case seems like the better option. Yes, this will require a rewrite for all subsequent lessons. However, this usually is a simple Find and Replace.
Perfect. I'll submit a PR for this in just a bit.
Change:
export default function hardGoToEpic(action$, _, { location }) { return action$.pipe( ofType(types.hardGoTo), <del> tap(({ payload = HOME_PATH }) => { </del> <ins> tap(({ payload }) => { </ins> location.href = payload; }), ignoreElements()

Discussion:
While Gatsby allows us to create globals in we also make use of for that purpose. We should DRY this out and use one ( seems the best). See
Change:
"description": [ "<code>data structures</code> have <code>properties</code>. For example, <code>strings</code> have a property called <code>.length</code> that will tell you how many characters are in the string.", "For example, if we created a variable <code>var firstName = "Charles"</code>, we could find out how long the string "Charles" is by using the <code>firstName.length</code> property.", <del> "Use the <code>.length</code> property to count the number of characters in the <code>lastNameLength</code> variable." </del> <ins> "Use the <code>.length</code> property to count the number of characters in the <code>lastName</code> variable." </ins> ], "tests": [ "assert((function(){if(typeof(lastNameLength) !== "undefined" && typeof(lastNameLength) === "number" && lastNameLength === 8){return(true);}else{return(false);}})(), 'lastNameLength should be equal to eight.');",

Discussion:
Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. The last paragraph: Should read:
Change:
assert.equal(allSongs[1].duration, "4:15"); ``` <del> The second object in your `allSongs` array should have an `src` property set to the string `"https://cdn.freecodecamp.org/curriculum/js-music-player/can't-stay-down.mp3"`. </del> <ins> The second object in your `allSongs` array should have a `src` property set to the string `"https://cdn.freecodecamp.org/curriculum/js-music-player/can't-stay-down.mp3"`. </ins> ```js assert.equal(allSongs[1].src, "https://cdn.freecodecamp.org/curriculum/js-music-player/can't-stay-down.mp3");

Discussion:
I noticed that we are using both "a attribute" and "an attribute" in challenge descriptions. And we even use both in the same challenge (): <img width="596" alt="Screenshot 2024-05-21 at 22 44 29" src=""I think both are acceptable, since the articles depend on how we pronounce "src" ("es-ar-see" vs "source"), but I think we should stick to one for consistency. I'll let native English speakers make the call
I always pronounce it as , so I vote
I'm with Jessica on this one. The second sentence should be changed to .
This issue is open to first-time code contributors to this repository. The files that you should be updating are: 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.
Hi everyone. This is a great pick up! I am happy to help out there and will get a initial PR up for review today :)
I have reviewed the changes made in PR, all the related file have been fixed correctly and checked locally.
Hello, This is my first Open source contribution so if you guys can give me feedback on what i did wrong and how i should correct it please guide me. from the seven files mentioned above, I have created pull request for each one which is as below. sorry if i messed up, as it is my first try. I am actively looking for any advice, suggestion, criticism. Thank You.
Change:
}; const StepPreview = ({ <del> disableIframe }: Pick<PreviewProps, 'disableIframe'>) => { </del> <ins> disableIframe, previewMounted }: Pick<PreviewProps, 'disableIframe' | 'previewMounted'>) => { </ins> return ( <Preview className='full-height'

Discussion:
On the initial loading of a Step the preview is showing in the preview pane, but if you either open the preview in the pop-out window or toggle the preview pane off/on then the preview does not load again. All Steps in New RWD preview in pop-out window (preview does not load) page Preview button to toggle preview pane off/on (preview does not load) Preview should load in both pop-out window and after the preview pane has been toggled off/on. No response Verified with Chrome/Firefox on both Linux and Win11. Possibly related to issue , but I think this is newer and slightly different.
Just discovered that if you make any change in the editor (such as adding a single space) then the preview will refresh and display again. But you have to do that every time you either open the pop-out window or toggle the preview pane.
When the preview is blank the iframe attributes are not updated either (which makes sense I guess, it looks to be the default values). Blank before updating: After updating: It feels like a state issue.
The preview also disappears if you toggle the Instructions on any of the certification projects.
Yes, that's a separate issue. I dig around at this a bit, seems to have caused the problem. Before it, these issues aren't present.
Change:
while (done !== count) { done++; rows.push(padRow(done, count)); <del> if (done === count) { </del> <ins> if (done === count) { </ins> continueLoop = false; } }

Discussion:
In the JS Beta project to build a pyramid gen., steps 82 and 83 both show an if statement block in the code editor that is not correctly indented within the while loop it is in. This may confuse new learners if they are relying on the indents to understand the logic and should be fixed to keep the presented code in acceptable shape for learners. N/A the if statement should be indented within the while loops block ! ! N/A No response
Change:
When you use the `relative` value, the element is still positioned according to the normal flow of the document, but the `top`, `left`, `bottom`, and `right` values become active. <del> Instead of `static`, give you `.cat-head` a position of `relative`, and leave both `top` and `left` properties as they are. </del> <ins> Instead of `static`, give your `.cat-head` a position of `relative`, and leave both `top` and `left` properties as they are. </ins> # --hints--

Discussion:
Here's the last paragraph in the instructions: Notice that where is says "... give you .cat-head..." should actually be "... give your .cat-head ..." N/A N/A ! Device: Laptop OS: Windows 10 Browser: Chrome Version: 116.0.5845.111 Didn't see a better way to report a spelling issue directly from the website.
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: 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.
Can I Contribute on this issue?
attempting
Hey 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.
please check out the update.
Hey yout PR is targeting branch of your own fork, not the .
i think its targeting the right one now.
if you want to tackle some other grammatical errors I found, I know there is a missing space in a step somewhere, and missing punctuation in another. I've forgotten where, but I know they both happened prior to this step I reported here, but not before "Learn the CSS Box Model by Building a Rothko Painting". Both were on different steps.
Change:
import { certMap } from '../../resources/cert-and-project-map'; import { completedChallengesSelector } from '..'; import { <ins> certTypes, certTypeIdMap } from '../../../../config/certification-settings'; import { </ins> updateUserFlagComplete, updateUserFlagError, validateUsernameComplete,

Discussion:
Describe the bug I have completed the necessary requirements to get the Legacy Full Stack Certification, whenever I click on the claim certification button, it displays nothing, leaving the page as it is, I emailed the support team about this, they agreed i've fulfilled the requirements to get Legacy Full Stack certified and they said its a bug, and I should open a github case about it, so here I am. please help. Desktop (please complete the following information): OS: [Windows] Browser: [chrome] Version: [102.0.5005.115 (Official Build) (64-bit)] Additional context My username is muhammedctgr and my name is Popoola Muhammed
to investigate
hi pls whats the status on this?
it needs to be investigated
says page not found....
noted, thank you. i'll wait.
Many thanks to the dev team, I really appreciate the this mean its been fixed? Still unable to claim the cert tho.
Once the next production build is deployed, this fix should be in. We typically do 1 - 2 deployments each week.
This should be live now!
appreciate this, I've been able to claim the full stack cert. Promise to make FCC proud.