jiebi/CodeConvo huggingface dataset:
Code change:
challenge-editor should be to the "How to work on practice projects" documentation here:
I'll tackle this today.

Related discussion:
text: npm run create-empty-steps X # where X is the number of steps to create. ``` <del> ## insert-step </del> <ins> ### insert-step </ins> A one-off script that automatically adds a new step at a specified position, incrementing all subsequent steps (both their titles and in their meta.json). The challenge seed code will use the previous step's challenge seed code with the editable region markers (ERMs) removed. **Note:** This script also runs [update-step-titles](#update-step-titles). <del> ### How to run script: </del> <ins> #### How to run script: </ins> 1. Change to the directory of the project. 2. Run the following npm command:
Code change:
challenge-editor should be to the "How to work on practice projects" documentation here:
I'll tackle this today.

Related discussion:
text: npm run insert-step X # where X is the position to insert the new step. ``` <del> ## delete-step </del> <ins> ### delete-step </ins> A one-off script that deletes an existing step, decrementing all subsequent steps (both their titles and in their meta.json) **Note:** This script also runs [update-step-titles](#update-step-titles). <del> ### How to run script </del> <ins> #### How to run script </ins> 1. Change to the directory of the project. 2. Run the following npm command:
Code change:
challenge-editor should be to the "How to work on practice projects" documentation here:
I'll tackle this today.

Related discussion:
text: npm run delete-step X # where X is the step number to be deleted. ``` <del> ## update-step-titles </del> <ins> ### update-step-titles </ins> A one-off script that automatically updates the frontmatter in a project's markdown files so that they are consistent with the project's meta.json. It ensures that each step's title (and dashedName) match the meta's challengeOrder. <del> ### How to run script </del> <ins> #### How to run script </ins> 1. Change to the directory of the project. 2. Run the following npm command:
Code change:
in step 21 of building a piano project, the hint in line 30 is missing code blocks This should be changed to 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 believe I did all this right. This is my first time contributing to open source. Very exciting :))

Related discussion:
text: assert(img?.previousElementSibling === null); ``` <del> Your `img` element should have a `class` set to logo. </del> <ins> Your `img` element should have a `class` set to `logo`. </ins> ```js const img = document.querySelector('img');
Code change:
There is a typo in Understand BCrypt Hashes, is used instead of . Here is the typo 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 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.

Related discussion:
text: Add all your code for these lessons in the `server.js` file between the code we have started you off with. Do not change or delete the code we have added for you. <del> BCrypt has already been added as a dependency, so require it ad `bcrypt` in your server. </del> <ins> BCrypt has already been added as a dependency, so require it as `bcrypt` in your server. </ins> Submit your page when you think you've got it right.
Code change:
It says that plot 1 should have an x label of Month, but it's the second plot that is monthly. It should say that plot 2 should have that xlabel. It should say that plot 2 should have an xlabel of Years It's testing correctly, so it should be an issue only with the assert message ! 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] No response
same thing for the ylabel in plot 2 actually, it says plot 1 there too
Hello, It seems that same thing is for the "testboxplot_titles".
I am opening this for contribution. The PR has to be done on the boilerplate:

Related discussion:
text: h4.negative-10.text-nowrap Community Builder img.profile-image(src='https://s3.amazonaws.com/freecodecamp/branden-byers.jpg' alt="Branden Byers picture") h4.text-nowrap Madison, Wisconsin <del> p.negative-10 "I'm a massage therapist and Stay-at-home-dad. I learned Hypercard, then Rails, but now I feel at home with JavaScript." </del> <ins> p.negative-10 "Cookbook author and stay-at-home-dad. Started coding as a kid, got distracted, but now I'm back in full JavaScript force!" </ins> .col-xs-12.col-sm-4.col-md-3.team-member h3.negative-10.text-nowrap Michael Johnson h4.negative-10.text-nowrap Nonprofit Coordinator
Code change:
It says that plot 1 should have an x label of Month, but it's the second plot that is monthly. It should say that plot 2 should have that xlabel. It should say that plot 2 should have an xlabel of Years It's testing correctly, so it should be an issue only with the assert message ! 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] No response
same thing for the ylabel in plot 2 actually, it says plot 1 there too
Hello, It seems that same thing is for the "testboxplot_titles".
I am opening this for contribution. The PR has to be done on the boilerplate:

Related discussion:
text: h4.negative-10.text-nowrap Live Content Manager img.profile-image(src='https://s3.amazonaws.com/freecodecamp/jason-rueckert.jpg' alt="Jason Rueckert's picture") h4.text-nowrap Seattle, Washington <del> p.negative-10 "My high school job was testing basketball shoes for Nike. I learned code to work smarter, not harder. I have no thyroid." </del>  No newline at end of file <ins> p.negative-10 "My high school job was testing basketball shoes for Nike. I learned code to work smarter, not harder. I have no thyroid." </ins>
Code change:
it should be --important <-- instead of import Learn Bash Scripting by Building Five Programs False. An important operator in that menu is =~. It allows for pattern matching. Using the same syntax but with this operator, check if hello contains the pattern el. ! 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] No response
I'll fix this! Just for reference, I will be fixing this issue in repository.
Hey guys! I'm getting this error when typing in the terminal. Anyone know how to fix? I created a seperate branch that is up to date.
For generating file, the coderoad cli requires for the version branch to exist locally. Detailed guidelines how to contribute to these tutorials can be found on Please refer to the parts about making changes on the branch. Thank you and happy coding!
Perfect. I have the typo fixed and ill make that branch work with coderoad. Thank you for your patience

Related discussion:
text: } ]); <ins> profileValidation.controller('nonprofitFormController', ['$scope', function($scope) { } ]); </ins> profileValidation.directive('uniqueUsername', function($http) { return { restrict: 'A',
Code change:
In this line, there is a missing code block around word false It should be like this here is the file: 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. Happy contribution.
I opened pull request

Related discussion:
text: **Examples** <del> `3 == '3'` returns `true` because JavaScript performs type conversion from string to number. `3 === '3'` returns false because the types are different and type conversion is not performed. </del> <ins> `3 == '3'` returns `true` because JavaScript performs type conversion from string to number. `3 === '3'` returns `false` because the types are different and type conversion is not performed. </ins> **Note:** In JavaScript, you can determine the type of a variable or a value with the `typeof` operator, as follows:
Code change:
A camper mentioned in his comment, that this icon below indicate to them that it's an external link not a popup. ! We can change it to clearer icon that show, that it's a popup. The original comment for context:
I found it interesting, that say you should use ellipsis (…) when there is some additional action required after the action (popup, dialog, confirmation) and it isn't clear by the action itself. This doesn't mean you should use an ellipsis whenever an action displays another window only when additional information is required to perform the action. Consequently, any command button whose implicit verb is to "show another window" doesn't take an ellipsis, such as with the commands About, Advanced, Help (or any other command linking to a Help topic), Options, Properties, or Settings. So maybe an ellipsis of some kind: in button's label or in the icon? More so, it's a part of too. If we were to stick with keeping an icon regardless, this regular feels like a better choice, with the arrow denoting there would be some kind of external interface but the enclosed square representing that it is not an external redirection, thus denoting some kind of popup or modal.
I think these guides are saying that the ellipses should be when the button opens a window that requires the user to enter more information or perform another action. This isn't the case here, so I don't think they are warranted in this instance. If we want to use a new icon then I would suggest we use one that has . I'm not suggesting that we use this exact icon. This is just an example of what I'm suggesting.
I second the use of some kind of variation of that icon. There's a small issue though, there's no such icon in the font awesome library for this so we'll have to find a different way to implement this.
Font awesome has an icon that could have the same meaning: Alternatively Material Icons has a specific preview icon if these can be used?
can you assign me this task?
issues with label, aren't open for contribution yet. You can however browse the label help wanted for open issues
allright sir
Both and both are plausible.
I'd suggest we should move forward to replace the icon with the icon. Should I move ahead and send over a PR? This is the output - !
Sure. Just make sure we don't need to add other dependencies to get that icon.

Related discussion:
text: import React from 'react'; <del> import { faExternalLinkAlt } from '@fortawesome/free-solid-svg-icons'; </del> <ins> import { faWindowRestore } from '@fortawesome/free-solid-svg-icons'; </ins> import { FontAwesomeIcon } from '@fortawesome/react-fontawesome'; import { useTranslation } from 'react-i18next'; import EditorTabs from './editor-tabs';
Code change:
A camper mentioned in his comment, that this icon below indicate to them that it's an external link not a popup. ! We can change it to clearer icon that show, that it's a popup. The original comment for context:
I found it interesting, that say you should use ellipsis (…) when there is some additional action required after the action (popup, dialog, confirmation) and it isn't clear by the action itself. This doesn't mean you should use an ellipsis whenever an action displays another window only when additional information is required to perform the action. Consequently, any command button whose implicit verb is to "show another window" doesn't take an ellipsis, such as with the commands About, Advanced, Help (or any other command linking to a Help topic), Options, Properties, or Settings. So maybe an ellipsis of some kind: in button's label or in the icon? More so, it's a part of too. If we were to stick with keeping an icon regardless, this regular feels like a better choice, with the arrow denoting there would be some kind of external interface but the enclosed square representing that it is not an external redirection, thus denoting some kind of popup or modal.
I think these guides are saying that the ellipses should be when the button opens a window that requires the user to enter more information or perform another action. This isn't the case here, so I don't think they are warranted in this instance. If we want to use a new icon then I would suggest we use one that has . I'm not suggesting that we use this exact icon. This is just an example of what I'm suggesting.
I second the use of some kind of variation of that icon. There's a small issue though, there's no such icon in the font awesome library for this so we'll have to find a different way to implement this.
Font awesome has an icon that could have the same meaning: Alternatively Material Icons has a specific preview icon if these can be used?
can you assign me this task?
issues with label, aren't open for contribution yet. You can however browse the label help wanted for open issues
allright sir
Both and both are plausible.
I'd suggest we should move forward to replace the icon with the icon. Should I move ahead and send over a PR? This is the output - !
Sure. Just make sure we don't need to add other dependencies to get that icon.

Related discussion:
text: onClick={() => togglePane('showPreviewPortal')} > <span className='sr-only'>{getPreviewBtnsSrText().portal}</span> <del> <FontAwesomeIcon icon={faExternalLinkAlt} /> </del> <ins> <FontAwesomeIcon icon={faWindowRestore} /> </ins> </button> </div> </div>
Code change:
The declaration of arr doesn’t need to be guarded by ‘Do Not Change’ comments. There exist many solutions (3 in the guide) that do not need that variable declaration. These comments should be removed or at least moved. All No response
. I lean towards the second option of having only the comments within the function and no extra starter code.
I was thinking something simplier We've ditched a lot of these comments in the rest of the intermediate algorithm challenges. Does the comment help us at all here?
Probably not. I honestly would not even put the . At this point in the curriculum, users should know the function needs to have a statement and they can craft their own.
Sure, then the fix would be: This looks like a good first-timer issue.
Thanks for opening this issue. This looks like 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 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.

Related discussion:
text: ```js function whatIsInAName(collection, source) { <del> const arr = []; // Only change code below this line // Only change code above this line return arr; </del> } whatIsInAName([{ first: "Romeo", last: "Montague" }, { first: "Mercutio", last: null }, { first: "Tybalt", last: "Capulet" }], { last: "Capulet" });
Code change:
In step 31 of the Learn HTML Forms by Building a Registration Form project, the step doesn't explicitly say that it wants the input element to be nested inside the label element. Instead it says: "Add a label with the text Upload a profile picture: , and add an input accepting a file upload." This could be interpreted to mean that the input element should be on the right side of the label element. Only when we attempt this are we told by the Hint "You should nest an input element inside the label element." To clarify the requirement, the step should use the word nest in the exercise as below for eg.: "Add a label with the text Upload a profile picture: , and nest an input accepting a file upload within it.", The step should explicitly state that the input element should be nested within the new label element. No response Not Applicable No response
I think if all of the challenges will have specifications defined explicitly, it will serve no purpose of "challenging" the learners to really think and solve it. In the first place, the solution is already implied from the given code and then, if the learners will still have the hard time solving it, then the feature will definitely do its job.
Agreed. The instructions should be clear to begin with. Making the users guess what the test requires isn't a "challenge", it's just rude.
For what it is worth, the camper has nested an input in a label element a few times in this challenge prior to this step. I am not against adding this reminder to the instructions, but I don't want to lose sight of our goal to keep the instructions more lean and have the hints serve as the reminders.
Definitely. But I looked back at the instructions on the steps where they add the previous inputs and we do explicitly tell them to put the input within the label: step 17: Nest an input element within each label. step 25: within each of the first two label elements, add one input element with type="radio". If we can add that information to those instructions then I think we can add it to this one. And let me just clarify that what I am really concerned about is this correct solution being rejected: I'm working under the assumption that correct code should always pass. So we need to tell the user that only a nested input will pass if that's all the test will accept.
I understand that if someone is working on a series of steps they may not need to be told to nest the input again. However, if they stop and return to the project a few weeks later on, they may not remember that. The hint will remind them sure. I guess this is a minor issue given the hint is quite clear. Personally I like a more explicit instruction.

Related discussion:
text: Moving on to the final `fieldset`. What if you wanted to allow a user to upload a profile picture? <del> Well, the `input` type `file` allows just that. Add a `label` with the text `Upload a profile picture: `, and add an `input` accepting a file upload. </del> <ins> Well, the `input` type `file` allows just that. Add a `label` with the text `Upload a profile picture: `, and nest an `input` accepting a file upload. </ins> # --hints--
Code change:
in step 53, the span elements are missing code elements. Here is the file We can add elements, to both of them. Like step 43: Or delete the first one and add code elements to the second one, but reading previous issues, I think campers may delete both elements wrapping the text and create one that wraps both the text. Note: that sentence is hard to work with in Arabic, and require adding nuances, because the structure of two code elements following each other which is weird in RTL layout.

Related discussion:
text: # --description-- <del> After your last `.divider`, create a new `p` element with the text `Cholesterol 0mg 0%`. Wrap the text `Cholesterol` in a `span` element, and give that `span` element the `class` attribute set to `bold`. Wrap the text `0%` in another `span` element, with the `class` set to `bold`. Finally, nest the `Cholesterol` and `0mg` span elements inside an additional span element for alignment. </del> <ins> After your last `.divider`, create a new `p` element with the text `Cholesterol 0mg 0%`. Wrap the text `Cholesterol` in a `span` element, and give that `span` element the `class` attribute set to `bold`. Wrap the text `0%` in another `span` element, with the `class` set to `bold`. Finally, nest the `Cholesterol` and `0mg` `span` elements inside an additional `span` element for alignment. </ins> # --hints--
Code change:
The following sentence in the Word Blanks lesson should have a code block (three backticks) surrounding the code section which is directly referring to the completed code block below it on the page. Instead of: Consider this sentence - It was really , and we ourselves . It should say: Consider this sentence - The sentence has been translated because of the missing code blocks (and will not make sense as it's a direct reference to the actual code shown below it) The sentence with the blanks should be in a code block that does not wrap. (three backticks above and below it) Instead of: Consider this sentence - It was really , and we  ourselves . It becomes: Consider this sentence - No response n/a No response
Question for those in the know. Do we have a way to keep content from being translated that doesn't involve using the triple back tick code block? I would be cool to use sr-only text "Blank" (or something similar) for those underlines to represent missing text. But we can't do that using the code blocks since they are wrapped in a .
Do they get wrapped in a if they're inline code?
It looks like they are just wrapped in strong tags in crowdin at least. I don't see a pre tag.
pre sounds like a plausible idea. We should go ahead with that.
The challenge require the sentence to not be translated, and element don't stop translation, it gives the choice to the translation to translate or not, which isn't ideal. Here is the file, to solve this issue, change the structure of the sentence to md It was really , and we ourselves . ` 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 prolific contributors will guide you through this.
nope, but we can open an issue for this yes
Can you assign me this issue
Only issues with the or label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the

Related discussion:
text: You are provided sentences with some missing words, like nouns, verbs, adjectives and adverbs. You then fill in the missing pieces with words of your choice in a way that the completed sentence makes sense. <del> Consider this sentence - It was really **____**, and we **____** ourselves **____**. This sentence has three missing pieces- an adjective, a verb and an adverb, and we can add words of our choice to complete it. We can then assign the completed sentence to a variable as follows: </del> <ins> Consider this sentence: ```md It was really ____, and we ____ ourselves ____. ``` This sentence has three missing pieces- an adjective, a verb and an adverb, and we can add words of our choice to complete it. We can then assign the completed sentence to a variable as follows: </ins> ```js const sentence = "It was really " + "hot" + ", and we " + "laughed" + " ourselves " + "silly" + ".";
Code change:
instead of the example command should be: docshow-to-add-cypress- project dependencies to run will see error: instead of the example command should be: No response

Related discussion:
text: For example: ```console <del> pnpm run cypress -- run --spec=cypress/e2e/default/landing.js </del> <ins> pnpm run cypress -- run --spec=cypress/e2e/default/landing.ts </ins> ``` - To create a development build, start the development server, and run all existing cypress end-to-end tests: