jiebi/CodeConvo huggingface dataset:
Change:
const res = await fetch('https://pokeapi-proxy.freecodecamp.rocks/api/pokemon/94'); // Fetch from proxy to simulate network delay if (res.ok) { <del> await new Promise(resolve => setTimeout(resolve, 50)); // Brief additional delay to allow UI to update </del> <ins> await new Promise(resolve => setTimeout(resolve, 1000)); // Additional delay to allow UI to update </ins> const sprite = document.getElementById('sprite'); assert.isTrue(sprite.src.endsWith('sprites/pokemon/94.png'));

Discussion:
When testing one camper's code it fails some tests unless I increase all the delays to 1000ms, I tested with 500ms but that was not enough. I also saw the example project fail a test but it does pass more consistently (my guess is it is just faster with fewer async functions). To be on the safe side we should have a longer delay. I know 1000ms is a lot but better safe than sorry. Tests: Valid code should not fail because of "timing" issues. No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] Forum:
As this is a bug with a certificate project I the showstopper label.
Change:
}, output, tests, <del> submitting, </del> <ins> isSignedIn, </ins> executeChallenge, updateProjectFormValues } = this.props; <del> // TODO: Should be tied to user.isSignedIn const buttonCopy = submitting </del> <ins> const buttonCopy = isSignedIn </ins> ? 'Submit and go to my next challenge' : "I've completed this challenge"; const blockNameTitle = `${blockName} - ${title}`;

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.
Change:
} </style> <del> <img class="responsive-img" src="https://s3.amazonaws.com/freecodecamp/FCCStickerPack.jpg" alt="freeCodeCamp stickers set"> <img src="https://s3.amazonaws.com/freecodecamp/FCCStickerPack.jpg" alt="freeCodeCamp stickers set"> </del> <ins> <img class="responsive-img" src="https://cdn.freecodecamp.org/curriculum/responsive-web-design-principles/FCCStickerPack.jpg" alt="freeCodeCamp stickers set"> <img src="https://cdn.freecodecamp.org/curriculum/responsive-web-design-principles/FCCStickerPack.jpg" alt="freeCodeCamp stickers set"> </ins> ```

Discussion:
We need to replace all images and audio samples for the legacy content with the ones that were just to our freeCodeCamp cdn. Here are all of the files that will need to be updated Here are all of the new asset links
Change:
<del> // executes the given code and handles the result var run = function(code) { var result = { input: code, output: null, error: null, type: null }; try { var codeExec = runHidden(code); result.type = typeof codeExec; result.output = stringify(codeExec); } catch(e) { result.error = e.message; } application.remote.output(result); }; // protects even the worker scope from being accessed var runHidden = function(code) { var indexedDB = null; var location = null; var navigator = null; var onerror = null; var onmessage = null; var performance = null; var self = null; var webkitIndexedDB = null; var postMessage = null; var close = null; var openDatabase = null; var openDatabaseSync = null; var webkitRequestFileSystem = null; var webkitRequestFileSystemSync = null; var webkitResolveLocalFileSystemSyncURL = null; var webkitResolveLocalFileSystemURL = null; var addEventListener = null; var dispatchEvent = null; var removeEventListener = null; var dump = null; var onoffline = null; var ononline = null; var importScripts = null; return eval(code); } // converts the output into a string var stringify = function(output) { var result; if (typeof output == 'undefined') { result = 'undefined'; } else if (output === null) { result = 'null'; } else { result = JSON.stringify(output) || output.toString(); } return result; } application.setInterface({run:run}); </del>

Discussion:
the first line in the function says - it wont pass testing unless you change it to Browser Name: Firefox Browser Version: 60.0.1 Operating System: High Sierra ! <hr!
You don't have to it, but because of strict mode it does need to be declared with , , or .
so its missing the then?
That's how I would update it.

i am suspecting another small bug, the next challenge after succesful code run in Bonfire: Chunky Monkey actually points to itself
Change:
#mainEditorPanel form.code .form-group.codeMirrorView <del> textarea#codeEditor(autofocus=true) </del> <ins> textarea#codeEditor(autofocus=true, style='display: none;') </ins> script(src='/js/lib/bonfire/bonfireFramework_v0.1.2.js')

Discussion:
On first render, camper see's an unstyled textarea. After, codemirror takes over and hides textarea and adds it's own box. This initial flash is hideous and makes puppies cry.
This has not been fixed on the Reactify branch. And I would prefer styling to be to match codemirror instead of just hiding the text area, as this does not prevent flash to the user.
Does styling it like that really not stop the flash? Everything I'm seeing online says it should. I'm only an amateur though. My thought process on the fix was that codemirror is hiding the textarea through javascript and that the flash is be caused by the script running late/slow/delayed/ and is hiding it after the page has already displayed. So I thought since codemirror is hiding it anyway, why not just hide it from the start to prevent the flash.
There are really two flashes, first the text area is shown then hidden by codemirror. The second flash is happening because codemirror does not render until it is loading in the DOM, which is intentional as codemirror relies heavily on DOM manipulation. While hiding the textarea does stop it from showing to the user on initial load, codemirror still needs to load and the user will see codemirror appear from nowhere, ie flash. After thinking about it, hiding the text area might be the best route on the reactify branch as well. If we were to add classes to mimic the styling of codemirror in the text box, the text box is not codemirror and React will still need to re-render that section of the view which will cause a flash. Ultimately what I would like to get done is to completely rewrite codemirror into a self contained React component so that it can pre-render on the server. But that is neither here nor there. I am willing to close this issue when the same styling is applied to the reactify branch that is currently on master. Would you like to give it a try? You can get some exposure to React at the same time. We are all amateurs until we are not. My philosophy is
Just to make sure, this is the branch your referring to? I tried to edit the .jade files in server/views/bonfire/ but nothing happened.

Finally found that changes were being done from common/components/bonfires/ so it looks like the easiest way would just be to apply the style in under bonfire styling? I don't want to submit anything because I'm not sure if I would be submitting changes to the correct file.
Yes I think that should work just fine. Test locally to make sure it is hidden then submit the PR.
I messed up and commited directly to the repo. Sorry about that. Tested code locally and it worked.
Looks like the text area hide is working! Thanks.
Change:
# --description-- <del> Now you need to modify your display text. Change the `innerText` property of the `text` to be `"You enter the store."`. </del> <ins> Now you need to modify your display text. Change the `innerText` property of the `text` variable to be `"You enter the store."`. </ins> # --hints--

Discussion:
In step 41 of the RPG project in the JS beta curriculum, the instruction states: Change the property of the to be "You enter the store.". I believe this sentence is not 100% clear without either removing the word “the” in front of or adding the word “variable” to the right of . As it is, the sentence misleads a bit because it says “the ” which makes it sound like it is referring to some text somewhere, instead of the text variable. so either: Change the property of to be "You enter the store.". or Change the property of the variable to be "You enter the store.". will be clearer. Please look at questions posted on the forum for examples of people missing the point of the request with the current wording. I personally prefer the second one. N/A N/A N/A Example of confused learner:
Change:
const faqItems = t<string, string & FaqItem[]>('landing.faqs'); return ( <del> <Col sm={8} smOffset={2} xs={10} xsOffset={1}> </del> <ins> <Col md={8} mdOffset={2} sm={10} smOffset={1} xs={12} className='faq-section' > </ins> <h2 className='big-heading'>{t('landing.faq')}</h2> <Spacer size='small' /> {faqItems.map((faq, i) => (

Discussion:
! Frequently asked question segment is not aligned with the previous elements on the homepage to down to frequently asked questions the misalignment of frequently asked questions segment with the previous elements The frequently asked question segment should be aligned with the previous elements of the homepage for a better UI ! Device: Laptop OS: Windows 11 Browser: Brave Version: 1.64.122 No response
This issue is because the Certifications section has extra side padding: We can add a class to the FAQ section, and give it , too. I'm not sure if this change would collide with the changes you're making to the landing page. I'm also wondering if the Certification section being so wide (comparing to the one on /learn) is still desired. If it's not, I think we can take this opportunity to update the section.
Yes, we can standardize all of them. My changes are effecting the landing top section.
Thanks, Ahmad. I'm temporarily blocking this issue until the CSS situation is a little less messy. I'll get back to this and come up with a suggestion after is merged.
We will be making changes to the certification section in the near future, so I think we can keep the scope of this issue to just adding some extra padding to the FAQ section, as suggested here: This issue is open for contribution. We typically do not assign issues. Instead, we accept the most quality contribution followed by the one that is made first. 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. Happy contributing.
Change:
.has-success.checkbox label, .has-success.radio-inline label, .has-success.checkbox-inline label { <del> color: rgb(var(--highlight-color)); </del> <ins> color: var(--highlight-color); </ins> } .has-error .help-block,

Discussion:
If I try to select text with my mouse so I can copy/paste it or something - the selected text has the same background as the rest of the page. Making it difficult to see what is selected, and frustrating to try and select, well anything. ! This seems to occur across the entire site. Perhaps it was intentional or something, but I don't think it's a good ux. Note: the text does actually get selected, so you can still copy/paste it. Tested on Chrome and Firefox
Good catch. It'll be this PR: which didn't scope the change to challenge descriptions. I'll put together a quick fix. Edit: nevermind, it's just that has to be passed four values, not two. I don't quite understand how this ever worked.
Change:
assert.isFalse(rulesContainer.checkVisibility()); ``` <del> When your `rulesBtn` is clicked again, your `rulesBtn` should say `Show Rules`. </del> <ins> When your `rulesBtn` is clicked again, your `rulesBtn` should say `Show rules`. </ins> ```js <del> assert.strictEqual(rulesBtn.innerText.trim(), "Show Rules"); </del> <ins> assert.strictEqual(rulesBtn.innerText.trim(), "Show rules"); </ins> ``` # --seed--

Discussion:
Initial text of the button is . After step clicking button is expected to change text to , capitalizing the second word. Clicking it again is expected to change text to . Which is too differing from initial capitalization. n/a Capitalization should be consistent throughout the project. Either Show rules and Hide rules; or Show Rules and Hide Rules. No response n/a No response
We will do this option
Change:
readonly?: never; } | { <del> value: string; </del> <ins> value?: string; </ins> onChange?: never; readonly: boolean; } | { <del> value: string; </del> <ins> value?: string; </ins> onChange: (event: React.ChangeEvent<FormControlElement>) => void; readonly?: never; }; export type FormControlProps = React.HTMLAttributes<FormControlElement> & { <del> id?: string; className?: string; </del> testId?: string; componentClass?: 'textarea' | 'input'; <del> placeholder?: string; </del> name?: string; required?: boolean; rows?: number; type?: 'text' | 'email' | 'url'; } & ChangibleValues; <del> export interface FormControlVariationProps { className?: string; children?: React.ReactNode; id?: string; testId?: string; } </del> <ins> export type FormControlVariationProps = Pick< FormControlProps, 'className' | 'children' | 'id' | 'testId' >; </ins>

Discussion:
onChange: func value?: string componentClass?: string placeholder?: string name?: string required?: string rows?: 4 type?: 'text' 'url'FormControl FormControl.Feedback
Form control for chapter: Need to alter the props to account for chapter needs, here is the link to the chakira component
Which prop is being used in the chapter that we are not passing in the component library? Since chapter views are limited, it might be easier to create the components with learn specifications and use those props to control the component. does that make senes?
Instead of checking the chaikra library and comparing it with the current component, I am better off checking chapter itself for prop it's using. for example, in this file we are using and , so I note these down and check if these 2 props are different from the props we are using. depend on how different they are, I may do from the follow: Add new value to existing prop. Add new prop to the component. Do nothing.
Here is what I propose we do. We could continue building the components with the learn spec and ship them. For the second sprint, we collect the Chapter requirements and update the components accordingly.
Change:
*/`; function ShowClassic({ <del> challengeFiles: reduxChallengeFiles, </del> <ins> challengeFiles, </ins> data: { challengeNode: { challenge: { <del> challengeFiles, </del> <ins> challengeFiles: seedChallengeFiles, </ins> block, title, description,

Discussion:
During development adding or modifying the head or tail code ( and ) don't seem to be updated in the challenge. Tested locally and on gitpod. Steps to reproduce the behavior: /modify the or in challenge. For example one of the steps in the JS curriculum. I was adding function and variables to it, and then was attempting to use them in tests. and wait for challenge to be updated. () the challenge page, or visit it for the first time. running tests, referencing the function/variables from head/tail code, there will be reference errors. Changing head or tail code, should update the challenge to use it. Login status don't seem to affect issue. During changing the code, thinking I might do something incorrectly, there were handful times when challenge was updated with the head/tail code. Not sure what was the exact reason. What makes it stranger is stopping client develop and starting again, is not necessarily solving the problem. At some point I thought that's working to get challenge fully updated, but right now that doesn't seem to work.
I might have seen this as well. I remember trying to save a regex in to use in multiple tests, and it didn't seem to work. Kind of just thought I was using it incorrectly, but maybe this was the issue.
Thanks for the detailed investigation of another tricky bug. It was another example where saved code messes things up. They're always a pain to debug because everyone sees something different, depending on whether or not they have something saved. Hopefully this is the last of them!
What's the most throwing off, that wasn't even code saved manually!
Weird. Is there nothing in your local storage?
Hmm, well there is after running tests. That must have been the point when saving mishap happened.
Oh, that's right. No mystery beyond "how did I forget this?" :face_exhaling:
Change:
.docsify-copy-code-button { font-size: 0.7em !important; } <ins> /****** Anchor Headings ******/ a.anchor { padding-top: 48px; } .markdown-section h2 { margin: 0 0 0.8em; } </ins>

Discussion:
!
Sample URL:
, I am trying to work on the docs locally, and I have cloned the latest push of the repo, but my docs do not have the navbar. Am I missing something about running the docs locally?
See:
If you have installed and set up freeCodeCamp locally, you can simply do: which should prompt a URL at which its serving the site.
Right. I did all that. Turns out, I was syncing with my fork, and not fCC's.
Change:
right for you. The following editors are all cross-platform and free to use or evaluate. <del> ## <a href='https://www.sublimetext.com/' target='_blank' rel='nofollow'>Sublime Text</a> ![Sublime Text Icon](//discourse-user-assets.s3.amazonaws.com/original/2X/1/1249e18855b9c9ef177e636e6c4e308b4877bf2d.png) </del> <ins> ## <a href='https://www.sublimetext.com/' target='_blank' rel='nofollow'>Sublime Text</a><img src="https://i.imgur.com/3ALtws1.png" width="50px"> </ins> <del> ![Sublime Text Screenshot](//discourse-user-assets.s3.amazonaws.com/original/2X/6/63f774c31a7b1a439bcef9d11e95463b6998310e.png) </del> <ins> ![Sublime Text Screenshot](https://i.imgur.com/Jk2aJod.png) </ins> Sublime Text is a very popular editor that has been around <a href='https://www.sublimetext.com/blog/articles/one-point-oh' target='_blank' rel='nofollow'>since 2008</a>. There are many options and <a href='https://packagecontrol.io/' target='_blank' rel='nofollow'>extensions</a> available,

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: There are many broken image links and the Visual Studio Code icon is way too large. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: n/a Browser Version: n/a Operating System: n/a If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !
I can work on this.
I can work on this.
has already submitted a PR which will most likely be accepted to resolve this issue. We have a backlog of PRs, so it will be a while before it gets merged. There is no need to create any additional PRs for this issue at this time. PRs are merged in the order they are received. Thank you.
Change:
title: Source Code Editors --- <del> ##Source Code Editors </del> <ins> ## Source Code Editors </ins> Source code editors are the programs that allow for code creation and editing. Any text editor can be used to write code. But dedicated code

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: There are many broken image links and the Visual Studio Code icon is way too large. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: n/a Browser Version: n/a Operating System: n/a If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !
I can work on this.
I can work on this.
has already submitted a PR which will most likely be accepted to resolve this issue. We have a backlog of PRs, so it will be a while before it gets merged. There is no need to create any additional PRs for this issue at this time. PRs are merged in the order they are received. Thank you.
Change:
bsSize='large' onHide={handleSolutionModalHide} show={isOpen} <ins> size='lg' </ins> > <Modal.Header closeButton={true}> <Modal.Title id='solution-viewer-modal-title'>

Discussion:
The modal for viewing code solutions on the timeline page is more narrow than all the other modals. to view -code for one of the new RWD cert projects narrow modal modal -click view -project wider modal to the same two modals, they're both the wide version All of them to be the wide version
It's simple. Because the "modal-lg" class is not present in the code along with "modal-dialog" class. Can I add this here and take the issue please?
Go for it
Hi Tom, Its my first open source contribution. I have made the change in my local copy and it is working. I have it in my forked repo here - Can you please help me out and guide me on who approves the change?
Hey Here's page from contributing guidelines covering basics of opening pull request - Join us in or if you need help contributing, our moderators will guide you through this. Happy contributing.
hey , I have sent a pull request regarding the issue Thanks for the help