jiebi/CodeConvo huggingface dataset:
Change:
} from 'lodash'; import { compileHeadTail, setExt, transformContents } from '../utils/polyvinyl'; <del> import { nightThemeStyle } from './displayStyle.js'; </del> const htmlCatch = 'n<!--fcc-->n'; const jsCatch = 'n;/*fcc*/n';

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:
isOnlineSelector, isServerOnlineSelector, userFetchStateSelector, <ins> showCodeAllySelector, </ins> userSelector, ( isSignedIn,

Discussion:
The page gets stuck and goes blank with you leave the relational database challenges. to 'Start the course' the fCC logo/button in the nav goes blank and nav disappears Page not to go blank. Clicking fCC logo should go to /learn No response Same on Chrome and Firefox Console errors: <img width="671" alt="Screen Shot 2023-02-16 at 11 44 19 AM" src="https://user-"
Change:
# --description-- <del> After the unordered list, add a new image with an `src` attribute value set to: </del> <ins> After the unordered list, add a new image with a `src` attribute value set to: </ins> `https://cdn.freecodecamp.org/curriculum/cat-photo-app/lasagna.jpg`

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:
--- <del> `What does he does as our team lead?` </del> <ins> `What does he does as the team lead?` </ins> ### --feedback--

Discussion:
The fill-in-the-blank sentence doesn't match what the character says. The written sentence is: The character says: Note the "the", instead of "our". No response Device: all OS: all Browser: all Version: all No response
Thank you for reporting the issue. Note for maintainers: Step 54 () uses "our" instead of "the" in the quiz. I think it's fine as-is since there isn't associated audio/caption text, but I'd vote updating it, too, for consistency. This issue is open to first-time code contributors to this repository. Requirements: In Change the text in the tag from to In Change the text in the tag from to Change the fill-in-the-blank text from to Change the backtick placement in the description text from ` In Change the text of the answers from to 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.
Hi I've created a PR addressing these changes.
Change:
)} {isTopContributor && ( <div className='badge-card'> <del> <div className='badge'> </del> <ins> <div className='camper-badge'> </ins> <TopContibutorBadgeEmblem /> </div> <div className='badge-card-description'>

Discussion:
A2 English blocks have challenges whose title is displayed next to a completion indicator. The indicator is having a right margin, which creates a gap between the indicator and the text. <img width="746" alt="Screenshot 2024-05-31 at 22 49 13" src=""This issue is because the indicator has a class: This class was harmless as it didn't have any CSS rules associated, until we badges to the user profile page, which caused a class name collision: Remove the class from: Rename the class in to to avoid future collision
I can take this one, but I don't seem to have the permissions to assign myself to 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.
Awesome, thanks for clarifying!
Change:
height: 100%; padding-bottom: 100%; position: relative; <ins> background-color: var(--primary-background); </ins> } .testimonial-image {

Discussion:
Looking forward for reporting a security issue: Please report security issues by sending an email to instead of raising a GitHub issue. Describe the bug The heights of the SVG files on the landing page vary, which causes the certification chart to look inconsistent. To Reproduce <img width="946" alt="zoomfloatingvideowindowandLearntoCode—ForFree—CodingCoursesforBusyPeople" src="https://user-"Desktop (please complete the following information): OS: Mac Browser: Chrome Version: Version 88.0.4324.96 (Official Build) (x86_64)
Hi Quincy, I let know about this already.
in min height, so should take care of it.
Change:
display: flex; flex-direction: row; flex-wrap: wrap; <del> margin: 0px; </del> <ins> margin: 0; </ins> } .footer-col {

Discussion:
found an issue: Unexpected shorthand &quot;padding&quot; after &quot;padding-bottom&quot; (declaration-block-no-shorthand-property-overrides) It's currently on:
I'm happy to fix this (and remove the units from zero values also in that file), but I'm not sure what the preferred replacement is for the padding. Should I just remove the padding: and add lines for padding-top: 0; padding-right: 15px; to reflect the styles currently specified by the padding: 0 15px 15px line?
I would delete , you can start and these question will be answer by reviewers if they need changes later
Change:
} @media screen and (max-width: 991px) { <del> .challenge-success-modal .btn-lg { font-size: 1rem; } .challenge-success-modal .btn-cta-big { max-width: 100%; font-size: 1rem; } .completion-modal-body { min-height: 340px; } </del> .progress-bar-wrap, .progress-bar-background { height: 10px;

Discussion:
The contains a lot of unused CSS rules, which should be cleaned up. The unused rules/classes are: .challenge-success-modal .btn-lg .btn-cta-big .completion-modal-body .completion-message .completion-challenge-nameRemove the above classes from Test and confirm that the modal displays properly after the changes
Hi, I can help with this If you would like to assign it to me.
Change:
```js const exampleArr = ["This", "is", "a", "sentence"]; <del> const sentence = exampleArray.join(" "); // Separator takes a space character </del> <ins> const sentence = exampleArr.join(" "); // Separator takes a space character </ins> console.log(sentence); // Output: "This is a sentence" ```

Discussion:
Hello, I believe there is a typo in the join() method example on Learn Basic String and Array Methods by Building a Music Player - Step 18 I expect: should actually be: It's just a typo in the example explaining the join() method. ! N/A No response
Good catch. I will open it up for first timers contribution
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 The code example in this step needs to be updated to reference the correct array name Happy coding
Change:
assert.equal(allSongs[2].duration, "3:51"); ``` <del> The third 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 third 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[2].src, "https://cdn.freecodecamp.org/curriculum/js-music-player/still-learning.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:
<ins> import React from 'react'; function B1EnglishIcon( props: JSX.IntrinsicAttributes & React.SVGProps<SVGSVGElement> ): JSX.Element { return ( <> <svg aria-hidden='true' viewBox='0 0 175 170' fill='none' xmlns='http://www.w3.org/2000/svg' {...props} > <path fillRule='evenodd' clipRule='evenodd' d='M138 9H83V79.476H147V18C147 13.029 142.971 9 138 9ZM147 88.476H83V156H138C142.971 156 147 151.971 147 147V88.476ZM74 79.476V9H18C13.029 9 9 13.029 9 18V79.476H72H74ZM9 88.476H74V156H18C13.029 156 9 151.971 9 147V88.476ZM18 0C8.059 0 0 8.059 0 18V147C0 156.941 8.059 165 18 165H138C147.941 165 156 156.941 156 147V18C156 8.059 147.941 0 138 0H18ZM27.54 64.394H36.151V48H42.8115C45.3948 48 47.489 50.0942 47.489 52.6775V52.6775C47.489 55.2608 45.3948 57.355 42.8115 57.355H36.151V64.394H45.63C50.9366 64.394 55.377 60.3669 55.8938 55.0854V55.0854C55.9643 54.3647 55.9435 53.638 55.8317 52.9225L55.5571 51.1642C55.24 49.1331 54.153 47.302 52.5219 46.0509L50.5 44.5L52.0247 43.495C53.9086 42.2532 55.1806 40.2735 55.527 38.0439L55.8246 36.1287C55.9411 35.379 55.9657 34.6179 55.8979 33.8623V33.8623C55.3799 28.0899 50.5423 23.667 44.7467 23.667H27.54V64.394ZM42.04 41.545C45.0494 41.545 47.489 39.1054 47.489 36.096V36.096C47.489 33.0866 45.0494 30.647 42.04 30.647H36.151V41.545H42.04ZM100.301 64.394V57.355H111V45.5C111 44 111 39 111 37.5C111 38.661 111 36.2586 111 37.5C111 38.574 111 36.339 111 37.5C111 38.693 111 36.307 111 37.5C111 35.5 111 35.569 111 35C112.194 35 109.5 35 111 35C111 36 111 34.069 111 35C109.5 36 105 39 104 39.5C103.5 38.5 101 34.5 100.5 33.5C99.2921 35.4577 102 31.069 100.5 33.5C102 32.5 111.5 25.167 114 23.667C118.5 23.667 119 23.667 120.5 23.667C120.5 24.7787 120.5 22.5 120.5 25C120.5 28 120.5 27.931 120.5 29.931C120.5 32.431 120.5 33.154 120.5 35.5C120.5 37.038 120.5 39 120.5 40.5C120.5 42.285 120.5 44 120.5 46C120.5 48.5 120.5 55 120.5 57.355H129.335V64.394H100.301ZM27.54 142V101.273H54.983V108.372H36.151V118.077H53.571V125.176H36.151V134.901H55.063V142H27.54ZM131.605 142V101.273H123.034V126.886H122.676L105.097 101.273H97.54V142H106.151V116.366H106.449L124.168 142H131.605Z' /> </svg> </> ); } B1EnglishIcon.displayName = 'B1EnglishIcon'; export default B1EnglishIcon; </ins>

Discussion:
The B1 English icon isn't available, so we are temporarily using the A2 icon for this superblock. <img width="709" alt="Screenshot 2024-09-11 at 05 43 53" src=""An icon for B1 should be created (it should look similar to the A2). Link to the A2 icon: You will need to make the following change to your file in order to see the B1 superblock:
Change:
assert.match(getStandardDeviation.toString(), /standardDeviations*=s*Math.pow(/); ``` <del> Your `standardDeviation` variable should use the `variance` variable. ```js assert.match(getStandardDeviation.toString(), /standardDeviations*=s*Math.pow(s*variances*,/); ``` Your `standardDeviation` variable should use the `1/2` exponent. </del> <ins> Your `Math.pow()` function should have a base of `variance` and an exponent of `1/2`. </ins> ```js assert.match(getStandardDeviation.toString(), /standardDeviations*=s*Math.pow(s*variances*,s*1s*/s*2s*)/);

Discussion:
I struggled with the error message, see screenshot below. The error message asks challengers to use the variable, which I clearly did. So, it was not only unclear why the code didn't pass the test, but also misleading because the error message does not point to the real problem here: a second argument for (arg1, arg2) is missing. Since the instruction also doesn't provide a clear description of the syntax of (), I suggest that the syntax information of () be to the instruction. Albeit a minor issue, because anyone can look it up, I believe it would still make the instruction clearer. The error message should alert the challenger about a necessary second argument to pass in () if the variable is already passed in as the first argument. ! Device: Laptop OS: Windows 11 Browser: FireFox Version: 125.0.1 (64-bit) No response
For the new updated description, we could use this js (base, exponent) js const base = 4; const exponent = 0.5; // returns 2 (base, exponent); as for the hint text, it looks like the tests are broken up into two for In this case, I think it would be better to just have one test like this js (getStandardDeviation.toString(), /standardDeviations=sMath.pow(svariances,s1s/s2s)/);
Why step-51 in codebase is different also there is 58 steps showing when im running freecodecamp locally.But here there is only 55 steps.
The project is in beta which means the steps will be changing. So a recent update was made to the stats calculator project which means the step numbers were updated.
Change:
script(type='text/javascript', src='/js/lib/jailed/jailed.js') .row(ng-controller="pairedWithController") <del> .col-xs-12.col-sm-12.col-md-4.col-lg-3 </del> <ins> .col-md-4.col-lg-3 </ins> .scroll-locker(id = "scroll-locker") .innerMarginFix(style=' width: 99%') #testCreatePanel.well

Discussion:
A camper relayed this to me: There is some problem with the first challenge ending button on android with firefox browser. And in this moment I tried in chrome too, the issue is the same, the button is not active after the challenge is done. Xperia Z1 compact, android: 5.0.2, firefox: 39.0 Chrome: 43.0.2357.93
This is an issue whenever the screen size is small. It will also happen on a desktop if you resize the window to half screen or less.
Change:
.col-xs-12.col-md-1 label.control-label.control-label-story-submission(for='name') Link .col-xs-12.col-md-11 <del> input#story-url.form-control(placeholder='Paste your link here', name='Link') </del> <ins> input#story-url.form-control(name='Link', ng-model='submitStory.url', disabled="disabled", ng-init='submitStory.url="#{storyURL}"') </ins> .form-group .col-xs-12.col-md-1 label.control-label.control-label-story-submission(for='name') Title

Discussion:
I tried submitting a URL to camper news and somehow it got as a blank URL. The link I tried to add was but it just links to http:// I also can't edit or delete it, so I can't try fixing it.
Yup, I confirmed this with that URL. Did you make a change to disallow blank URLs that might affect this?
Nope. Didn't realize this was possible.
I see the mistake I made, I clicked "Submit" then typed in the url and hit "Submit" again. Then on the next page the title is auto-filled out but the URL is not copied over so I hit submit again, which let it be a blank URL. URL should copy from previous page into the new textbox.
I think I may have done the same thing.
For some reason the url value is not copied from the page URL. This requires some adjustments in the jade template. I will fix that.
Change:
padding: 25px; text-align: justify; justify-content: center; <ins> background-color: var(--primary-background); </ins> } .landing-top, .as-seen-in,

Discussion:
Looking forward for reporting a security issue: Please report security issues by sending an email to instead of raising a GitHub issue. Describe the bug The heights of the SVG files on the landing page vary, which causes the certification chart to look inconsistent. To Reproduce <img width="946" alt="zoomfloatingvideowindowandLearntoCode—ForFree—CodingCoursesforBusyPeople" src="https://user-"Desktop (please complete the following information): OS: Mac Browser: Chrome Version: Version 88.0.4324.96 (Official Build) (x86_64)
Hi Quincy, I let know about this already.
in min height, so should take care of it.
Change:
import PropTypes from 'prop-types'; import { Grid, Col, Row } from '@freecodecamp/react-bootstrap'; import { createSelector } from 'reselect'; <del> import { reduxForm } from 'redux-form'; </del> <ins> import { connect } from 'react-redux'; </ins> import { graphql } from 'gatsby'; <del> import normalizeUrl from 'normalize-url'; </del> import { executeChallenge,

Discussion:
Describe the bug Submitting the solution link as "" produces an error. Submitting "" does not. Whenever we submit a solution link "" it is appended with "/api/" so resultant solution gives "Not Found/Timeout error" and the same link submitted without "/" like "" gives solution as accepted. To Reproduce Steps to reproduce the behavior: to on 'solution input box' "https://freecodecamp-" solution gets accepted. "https://freecodecamp-" error Expected behavior This should be tackled as Chrome appends "/" by default to any domain URL you copy, so people who would copy URL from search bars will get URLs appended with "/" hence producing wrong results. This file shows the testString is directly appended with "/api" without checking if the input URL contains "/" at the end or not. Screenshots ! Desktop (please complete the following information): OS: Ubuntu 18 Browser: Google Chrome Version 73.0.3683.75
I am not having this problem - my project will pass the tests with or without the trailing https://fcc-manage-npm- and https://fcc-manage-npm- both pass for me in chrome Can you share a share a screen shot of the error?
Updated
hmm, it's strange that my project will give a good response when that string is appended but not yours https://fcc-manage-npm- - package as response https://freecodecamp- - not found as response not sure what is causing this - the only difference seems to be that I'm using glitch and you're using heroku in fact mine will work like this... https://fcc-manage-npm- so maybe how the two websites process a route or something? can they do that? glitch strips out the extra or something? weird Either way - I think a solution like you suggested would probably work - check if the submitted URL ends in a and remove it if it's there. This same problem probably occurs throughout the whole backend area all over the place.
Weird, would u check with an alternative hosting if the problem persists? If the problem persists the last solution would be stripping the las from input url
Did you try this Above is the actual link processed in the test with an appended , It gives a response with the same as it is shown in the screenshot I posted. So I guess the problem is with the routing of Heroku.