jiebi/CodeConvo huggingface dataset:
Change:
<!-- 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: Challenge criteria are updated but solution is not updated yet. Here's the and hers's the on GitHub which is currently unable to pass all the tests for the challenge. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Google Chrome Browser Version: 81.0.4044.138 Operating System: Windows OS If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !

Discussion:
<section id='solution'> ```js <ins> // The global variable </ins> var fixedValue = 4; <del> const incrementer = val => val + 1; </del> <ins> // Only change code below this line function incrementer (fixedValue) { return fixedValue + 1; // Only change code above this line } </ins> ``` </section>
Change:
This project has two user stories that are listed as !
Thank you, for spotting this. This is an easy fix; Here is the culprit file:
hi , Can I go ahead with this?
Hello , As you are considered a Contributor (made at least 1 contribution), I suggest you leave this open to first timers. Thank you, for your understanding.
Hey I figured I'll mention here. I was not aware that we could not do it ourselves. I apologize for the inconvenience.
Hi can I work on this? I am a first-timer
Hi , I think this issue has already been picked up. Feel free to claim an issue with label .
I think that I sent it through but I'm unsure if I did it correctly. It might still need someone with Write access to accept the edits?
I can check it for you
Hi I'm unsure if I am doing this correctly but I have a pending pull request. It needs approval to be submitted.
Hello , sorry, things are quite busy. You have done what you needed to, and, as it stands, your PR is approved. Thank you, for your patience.
Ok thanks for the heads up!

Discussion:
<strong>User Story #14:</strong> My legend should contain <code>rect</code> elements. <strong>User Story #15:</strong> The <code>rect</code> elements in the legend should use at least 4 different fill colors. <strong>User Story #16:</strong> I can mouse over an area and see a tooltip with a corresponding <code>id="tooltip"</code> which displays more information about the area. <del> <strong>User Story #16:</strong> My tooltip should have a <code>data-year</code> property that corresponds to the <code>data-year</code> of the active area. </del> <ins> <strong>User Story #17:</strong> My tooltip should have a <code>data-year</code> property that corresponds to the <code>data-year</code> of the active area. </ins> Here is the dataset you will need to complete this project: <code>https://raw.githubusercontent.com/freeCodeCamp/ProjectReferenceData/master/global-temperature.json</code> You can build your project by forking <a href='https://codepen.io/freeCodeCamp/pen/MJjpwO' target='_blank'>this CodePen pen</a>. Or you can use this CDN link to run the tests in any environment you like: <code>https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js</code> Once you're done, submit the URL to your working project with all its tests passing.
Change:
Describe the bug Up and down arrow key don't work after typing JavaScript reserved words To Reproduce to a challenge in Basic JavaScript (Example: ) the following code: (or other JavaScript reserved words) in the second line up or down arrow key on the keyboard pointer can't move to the previous or the next line Expected behavior The pointer can move to the previous or the next line Desktop OS: Windows 10 Browser: Chrome Version: 83.0.4103.61
Yeah, I just tested it. It's reproducible.
It looks like it happens if there's a syntax error. Also it can be cleared by typing anything else. I reproduced it by clearing the editor and then typing At which point the cursor will not move up. However, if you press , everything starts working properly again.
Yeah... it's definitely not a big bug. Might cause minor annoyance though.
Agreed. It's not urgent, but it's definitely not working quite right.
I'm guessing it has to do with the changes we made to the editor in I think the arrow input is stuck inside a hidden suggest menu. I would need to look into it some more but here is a gif showing changing as I click the up and down arrow. I suspect this happens after triggering the menu and the arrow up/down input is supposed to be moving up and down inside the menu. ! The menu from the monaco editor playground ! Edit: It is the menu. You can pick an item from it. let down arrow Enter is replaced with (see screenshot above for the location of length in the menu)

Discussion:
dragAndDrop: true, lightbulb: { enabled: false <del> } </del> <ins> }, quickSuggestions: false </ins> }; this._editor = null;
Change:
Is your feature request related to a problem? Please describe. Currently the certificates lack any white space along the top border, making them difficult to screenshot and/or print: ! We should add some white space to the top of the page so the certificate is centered.

Discussion:
margin: 0; padding: 0; } .certification-namespace h1 { margin: 12px 0; } .certification-namespace.container { max-width: 1500px; width: 100%;

align-items: center; min-height: 100vh; flex-direction: column; <ins> padding: 50px; </ins> } .certificate-outer-wrapper .donation-section { <del> padding: 20px 0px; </del> <ins> padding-bottom: 100px; </ins> } .certificate-outer-wrapper .donation-section hr {

} .certification-namespace .information { <del> margin-top: -20px; </del> height: 380px; text-align: center; background-color: var(--gray-05);

} } <del> @media (max-width: 767px) { .certificate-outer-wrapper .donation-section { padding: 20px 20px; } } </del> @media screen and (max-width: 992px) { .certification-namespace header { height: 160px;
Change:
Describe your problem and how to reproduce it: The output does not align with the question, nor does it align with the code. I suspect this is what the output was meant to be: Also, I would suggest the formatting of the code to change. Ie. spacing between numbers and , and spacing between numbers. 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): !
Thanks for catching this I remember copying the output directly from the console, but I must have messed up the spacing while adding the hashes. Took another look and this is what the console outputs: So perhaps it can be: Or with the spacing at the end like you suggest:
, well. What was your intent? I assumed the output was there as an example for what the end result should become. Ie. after performing: Or, was the output just another representation of the output of the ? I suggest it be the expected output of the code the user needs to select, as this helps the user clarify what needs to be done.
right, my intent was to show what the expected end result would be after running . So really the output should be not like it is now. My mistake. I must have forgotten to change the output when I was writing these questions.
Is someone working on this? Can I work on this?
, I am unsure of anyone working on this. You can go ahead, if you want.
Okay. I will be working on it.

Discussion:
a = np.array([[1, 2, 3, 4, 5], [6, 7, 8, 9, 10]]) # Output: <del> # [[ 1  2  3  4  5] </del> <ins> # [[ 1  2  20  4  5] </ins> # [ 6  7 20  9 10]] ``` answers:
Change:
<img width="492" alt="Screen Shot 2020-05-28 at 1 29 28 PM" src="https://user-"<img width="511" alt="Screen Shot 2020-05-28 at 1 28 37 PM" src="https://user-"<hr<img width="518" alt="Screen Shot 2020-05-28 at 1 53 35 PM" src="https://user-"
thanks for catching the code blocks in the answer section looking off. Didn't notice it at first -- maybe it required a refresh? But yeah, looks off with the darker background. Tested this locally and it seems like we can just remove the language (py or python) from the triple backticks: ! I also think it would be better to have all the code in markdown. It's a bit finicky in conjunction with YAML, but makes it much easier to control the formatting/spacing than tags.
How about something like this: ! this is with a background of and using to enable highlighting. I'm not sure what the best background is. This one looks a little better than white and is a bit better from a contrast perspective.
I would like to see the same background color for answers like in Kris's photo, but the code highlighting, like in Oliver's. I think the only way to achieve this is to change some styles after the fact in the css.
Here are some options: ! the first two being white and prism's default (#). The issue being they look progressively better, but get progressively harder to read. in particular starts to fade into the background. That's what got me thinking about this , so I think it's fine to go with the prettiest version as long as we address the a11y issues.
what about changing the whole box to white... <img width="446" alt="Screen Shot 2020-05-29 at 3 41 42 PM" src="https://user-"Kinda solves both issues
Makes sense to me. They might look a little better with a dark border, but either way, I think the white background is the way to go.

Discussion:
} .video-quiz-options { <del> background-color: var(--tertiary-background); </del> <ins> background-color: var(--primary-background); </ins> } /* remove bootstrap margin here */

cursor: pointer; display: flex; font-weight: normal; <del> border: 2px solid var(--secondary-background); </del> <ins> border-left: 4px solid var(--tertiary-background); border-right: 4px solid var(--tertiary-background); border-top: 2px solid var(--tertiary-background); border-bottom: 2px solid var(--tertiary-background); } .video-quiz-option-label:first-child { border-top: 4px solid var(--tertiary-background); } .video-quiz-option-label:last-child { border-bottom: 4px solid var(--tertiary-background); </ins> } .video-quiz-input-hidden {
Change:
I got all the certs on .dev and got this email... ! The link should be updated to

Discussion:
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,
Change:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: The tests call for the function to return or . I ran into a user on the forums that was failing to get the tests to pass because they were returning and as strings, rather than boolean values. I wonder if the instructions should be made a little more specific to clarify that the function needs to return boolean values. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: Version 83.0.4103.61 Operating System: Windows 10 Home v 1909 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !
Whilst I can understand the confusion, the general adopted format has been: What is within the code tags is exactly what needs to be returned In other exercises, if the user is asked to return a string, it should be I say should be, because I just encountered another exercise where the test string was not following this format, but it is likely to be fixed.
That format makes complete sense to me. The only reason I bring this up is that I know learning to code can be a frustrating experience for some, and an opportunity to eliminate potential confusion and alleviate some of the self-generated stress seems like a good move.
How about catching this with a test?
I like that idea. It provides a little extra clarity on why the test is failing for the user's code.

Discussion:
```yml tests: <ins> - text: The <code>quickCheck</code> function should return a boolean (<code>true</code> or <code>false</code>), not a string (<code>"true"</code> or <code>"false"</code>) testString: assert.isBoolean(quickCheck(['squash', 'onions', 'shallots'], 'mushrooms')); </ins> - text: <code>quickCheck(["squash", "onions", "shallots"], "mushrooms")</code> should return <code>false</code> testString: assert.strictEqual(quickCheck(['squash', 'onions', 'shallots'], 'mushrooms'), false); - text: <code>quickCheck(["onions", "squash", "shallots"], "onions")</code> should return <code>true</code>
Change:
<!-- 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.

Discussion:
```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>
Change:
Describe the bug There's some formatting inconsistency in the issue templates. To Reproduce Steps to reproduce the behavior: to create an issue the issue template and you'll find the formatting inconsistency Screenshots !
Good catch Also want to thank you for helping a new contributor with the process of submitting a pull request.

Discussion:
**Desktop (please complete the following information):** - OS: [e.g. iOS] <del> - Browser [e.g. chrome, safari] - Version [e.g. 22] </del> <ins> - Browser: [e.g. chrome, safari] - Version: [e.g. 22] </ins> **Smartphone (please complete the following information):** - Device: [e.g. iPhone6] - OS: [e.g. iOS8.1] <del> - Browser [e.g. stock browser, safari] - Version [e.g. 22] </del> <ins> - Browser: [e.g. stock browser, safari] - Version: [e.g. 22] </ins> **Additional context** Add any other context about the problem here.
Change:
<!-- 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: A couple of concerns were brought up in the Discord server regarding the verbiage on this challenge. First, the language "make sure no space exists between both the variable and the and the value and " is not particularly clear, and could possibly be re-written to something like "make sure no space exists between the variable, the , and the value." Second, it seems that Glitch has a GUI to the .env file which is confusing some users. We could either add text to the instructions to say "We recommend you click to switch the .env file to a text view", or change the instructions to match Glitch's format. I definitely recommend the first option, as it would be more universal to other IDE platforms. This change would likely need to be made in a few places, though. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: Operating System: Windows 10 Home 1909 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): Glitch's new GUI !
I agree. The instructions can be made simpler. Also, we should teach how to use the proper syntax in file.... not the GUI that Glitch offers.

Discussion:
# --instructions-- <del> Add `mongodb` and `mongoose` to the project’s `package.json`. Then, require mongoose as `mongoose` in `myApp.js`. Store your MongoDB Atlas database URI in a private `.env` file as `MONGO_URI`. Surround the the URI with single or double quotes, and make sure no space exists between both the variable and the `=`, and the value and `=`. Connect to the database using the following syntax: </del> <ins> Add `mongodb` and `mongoose` to the project’s `package.json`. Then, require mongoose as `mongoose` in `myApp.js`. Create a `.env` file and add a `MONGO_URI` variable to it. Its value should be your MongoDB Atlas database URI. Be sure to surround the URI with single or double quotes, and remember that you can't use spaces around the `=` in environment variables. For example, `MONGO_URI='VALUE'`. When you are done, connect to the database using the following syntax: </ins> ```js mongoose.connect(<Your URI>, { useNewUrlParser: true, useUnifiedTopology: true });
Change:
<!-- 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: On Python curriculum challenge, the correct answer is already selected. Just so we're having the learner do something, I guess either rearranging the options or at the very least not having the correct option already selected should be made. If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !
I assume this applies to all of the Video Challenges with a solution of 1?
It should be that case, even though I haven't personally verified it
Could we avoid the problem by leaving the radio buttons unselected at the start? It's slightly weird UX, since people expect radio buttons to always have one selected, but it should not be too confusing in the context of a multiple choice question.
It is a valid workaround
/cc
That works. Unselected radio buttons seems to be a convention for multiple choice questions. Additionally, we could display the multiple choice questions as a button group and avoid having the users select the multiple choice question and click on the Check Your Answer.
Just to check, do you mean: remove Check Your Answer and have the modal pop up as soon as the user clicks on the correct answer? Also, since we're discussing UX, keyboard navigation is a bit tricky. There's no visible indicator when you have the answers selected.
Just to check, do you mean: remove Check Your Answer and have the modal pop up as soon as the user clicks on the correct answer? Yes, what do you think?
Sounds good. The only concern I have is that we don't want to encourage people to just guess. However, forcing them click back and forth between the radio buttons and 'Check your answer' probably does not solve that and it's definitely irritating.
For now, let us unselect radio buttons and we take it from there.
w.r.t , should we leave this issue open?
since it's already been moved to 'done' on the project board, I'll create a new feature request to track the remaining points.

Discussion:
this.state = { subtitles: '', downloadURL: null, <del> selectedOption: 0, </del> <ins> selectedOption: null, </ins> answer: 1, showWrong: false, videoIsLoaded: false
Change:
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

Discussion:
const MonacoWebpackPlugin = require('monaco-editor-webpack-plugin'); <del> exports.onCreateWebpackConfig = ({ stage, plugins, actions }) => { </del> <ins> exports.onCreateWebpackConfig = ({ stage, actions }) => { </ins> const newPlugins = [ <del> plugins.define({ HOME_PATH: JSON.stringify( process.env.HOME_PATH || 'http://localhost:3000' ) }), </del> // We add the shims of the node globals to the global scope new webpack.ProvidePlugin({ Buffer: ['buffer', 'Buffer']

<del> /* global HOME_PATH */ </del> import { ofType } from 'redux-observable'; import { tap, ignoreElements } from 'rxjs/operators';

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()
Change:
We previously attempted this in , which had its own set of issues. We need the Plyr to work natively with Youtube or alternatively make the YouTube embed not show related videos.
Can I work on this ?
I think this is resolved by a recent PR. We are keeping this open for verification. We have lots of other issues open which we could use your help with. Thanks.

Discussion:
} onReady={this.videoIsReady} opts={{ <del> rel: 0, </del> <ins> playerVars: { rel: 0 }, </ins> width: '960px', height: '540px' }}
Change:
In the instructions and unit tests are ambiguous with the word "required". It states: "The Items component should include a propTypes check that requires quantity to be a number." This is unclear as "requires" could mean that this check just simply needs to exist for the test to pass or that quantity should be a number that is required. I suggest either changing the above wording, or adding an additional unit test: "The Items component should include a quantity propType that is required."
! I think the lesson instructions are pretty clear, but I do agree that the test case wording is ambiguous. I would propose that the test message be edited to mirror this instruction.
I do not think the test text should just be a duplicate of the instruction. That would be redundant. Instead, we need to rewrite the text to reflect was is being tested. See below for the current testString prettified: The important part of the test is in the return statement. We are validating that we see the text "" and "Items.propTypes='" after removing whitespaces from the code. There probably is a better testString that could be written also.
I cannot think of a more effective testString, personally. But for the test text, perhaps something like "The component should include a check to require a value for quantity and ensure that value is a number."
Has the same clarity issue, thanks!
I agree that the text should be updated. I just got caught up by the unclear instructions. The way it is, I thought that what was 'required' was that quantity be a number. It doesn't suggest to me that a quantity is required.
Opening this PR for contributions. The test text should be changed to: The Items component should include a <codepropTypes</codecheck to require a value for <codequantity</codeand ensure that its value is a number.

Discussion:
testString: assert((function() { const mockedComponent = Enzyme.mount(React.createElement(ShoppingCart)); return mockedComponent.find('ShoppingCart').length === 1; })()); - text: The <code>Items</code> component should render. testString: assert((function() { const mockedComponent = Enzyme.mount(React.createElement(ShoppingCart)); return mockedComponent.find('Items').length === 1; })()); <del> - text: The <code>Items</code> component should include a <code>propTypes</code> check that requires <code>quantity</code> to be a <code>number</code>. </del> <ins> - text: The <code>Items</code> component should include a <code>propTypes</code> check to require a value for <code>quantity</code> and ensure that its value is a number. </ins> testString: getUserInput => assert((function() { const noWhiteSpace = __helpers.removeWhiteSpace(getUserInput('index')); return noWhiteSpace.includes('quantity:PropTypes.number.isRequired') && noWhiteSpace.includes('Items.propTypes='); })()); ```
Change:
Describe your problem and how to reproduce it: and parameters are swapped in the starting code. As description and tests suggests second parameter should be separator character and third one escape character. Add a Link to the page with the problem:
Thank you, for pointing this out. Not a major issue, but makes sense to change. I am opening this up for first-timers

Discussion:
<div id='js-seed'> ```js <del> function tokenize(str, esc, sep) { </del> <ins> function tokenize(str, sep, esc) { </ins> return true; } ```