jiebi/CodeConvo huggingface dataset:
Change:
This is a common error on this Step - we should modify the hint to point out the capitalization User should receive hint that helps them see the capitalization error 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] No response
The current hint is: "The new element should have a attribute with the value . You have either omitted the value or have a typo. Remember that attribute values should be surrounded with quotation marks." Technically, the attribute value doesn't need to be wrapped in quotes since there are no spaces in the value. Also, it will pass if you don't use quotes for the value, so this part of the hint seems unneeded and should probably be removed. Are you thinking that we should have a separate test just to check whether the value has been capitalized? Or do you think we just add a warning to the current hint reminding them that capitalization (or lack thereof) matters?
I'm not quite sure what the best way forward would be. I just know what most questions for this step on the forum are related to Loving vs loving.
We do have dynamic hints we can use:

Discussion:
assert($('input[type="checkbox"]')[0]); ``` <del> Your checkbox should still have an `id` attribute with the value `loving`. You may have removed the attribute or changed its value. </del> <ins> Your checkbox should still have an `id` attribute with the value `loving`.  Expected `--fcc-expected--`, but found `--fcc-actual--`. </ins> ```js <del> assert($('input[type="checkbox"]')[0].id === 'loving'); </del> <ins> assert.equal($('input[type="checkbox"]')[0].id, 'loving'); </ins> ``` The text ` Loving` should no longer be located directly to the right of your checkbox. It should be wrapped in a `label` element. Make sure there is a space between the two elements.

assert(labelElem.hasAttribute('for')); ``` <del> The new `label` element should have a `for` attribute with the value `loving`. You have either omitted the value or have a typo. Remember that attribute values should be surrounded with quotation marks. </del> <ins> The new `label` element should have a `for` attribute with the value `loving`.  Expected `--fcc-expected--`, but found `--fcc-actual--`. </ins> ```js const labelElem = $('input[type="checkbox"]')[0].nextElementSibling; <del> assert(labelElem.getAttribute('for').match(/^loving$/)); </del> <ins> assert.equal(labelElem.getAttribute('for'), 'loving'); </ins> ``` The text `Loving` should be nested within the new `label` element. You have either omitted the text or have a typo.
Change:
In the hint below it ask to add variable, but it's similar to how we ask colors to be , which cased confusion to a camper I propose, applying the same approach in ieahleen pull request to skyline variables name, . Although it feels like giving answers outright, variables are case-sensitive and require specific syntax, which I think we should give their steps some lay way in the hints. original issue:
For that you need to use . First argument of is the found value, and can be referenced with . Second argument of is the expected value, and can be referenced with in the hint text. The tests would need to be changed a bit for this to be possible. And I am not even sure how to apprach it, as it's complex values, and there is this annoying thing called spaces.
I thought will trim the spaces, but as showing in the image below it doesn't. That looks like a nightmare, so let's ignore my original suggestion ! the camper mentioned the lack of keyword, what about adding in the hints something like or

Discussion:
assert.include(new __helpers.CSSHelp(document).getStyle('.bb1a')?.background, 'linear-gradient'); ``` <del> You should give the `background` a `linear-gradient` starting from `--building-color1`. </del> <ins> You should give the `background` a `linear-gradient` starting from `var(--building-color1)`. </ins> ```js assert.include(new __helpers.CSSHelp(document).getStyle('.bb1a')?.getPropVal('background', true), 'linear-gradient(var(--building-color1'); ``` <del> You should give the `background` a `linear-gradient` ending at `--window-color1`. </del> <ins> You should give the `background` a `linear-gradient` ending at `var(--window-color1)`. </ins> ```js assert.include(new __helpers.CSSHelp(document).getStyle('.bb1a')?.getPropVal('background', true), 'linear-gradient(var(--building-color1),var(--window-color1))');
Change:
The documentation opens on port 3200 The challenge editor uses ports 3200/3300 There is a clash there. It may need to move one of the two
What do we have to change to fix this issue?
Heya The quickest fix would probably be to change this line: Replacing 3200 with 3400.
And here! So the documentation is updated together
I can make this change if you wouldn't mind!
Thanks for your interest in contributing! You've already contributed to our codebase, however - we prefer to leave issues for folks who are new to our codebase so they have a chance to familiarise themselves.
that's fair! I guess now I know how to do it so it wouldn't make sense for me to contribute.
Reopened because the docs section still need to be updated If you're going to update the docs, update the English file only
is this issue still open
yes the docs tells people to expect port:3200, while we are using port:3400, which may cause confusion. opening a pull request to change the docs will solve this issue for good
do you mind checking it again ,because I think it has already been edited its showing 3400 now
no worries, can you link the change because the documents is talking about port:3200 Here is the docs, that I am talking about
I was talking about the main branch ,the link you sent just now ,it is not main branch
so do I have to make changes in this branch ??
Nope, I was simply confused

Discussion:
"develop": "npm-run-all build:curriculum -p develop:*", "develop:client": "npm run build:curriculum && cd ./client && npm run develop", "develop:server": "npm run predevelop && cd ./api-server && npm run develop", <del> "docs:serve": "docsify serve ./docs -o --port 3200", </del> <ins> "docs:serve": "docsify serve ./docs -o --port 3400", </ins> "e2e": "npm run e2e:dev:run", "e2e:dev:run": "start-test develop ':3000/status/ping|8000' cypress:dev:run", "e2e:dev:watch": "start-test develop ':3000/status/ping|8000' cypress:dev:watch",
Change:
Just transcribing issues from crowdin. In this line: There is an extra comma before the anchor element that has to be removed. In this line: There is an incorrect use of parenthesis. It should become 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.
Hey, I would like to work on this.

Discussion:
# --description-- <del> As a reminder, this project is being built upon the following starter project on ,<a href="https://replit.com/github/freeCodeCamp/boilerplate-mochachai" target="_blank" rel="noopener noreferrer nofollow">Replit</a>  or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>. </del> <ins> As a reminder, this project is being built upon the following starter project on <a href="https://replit.com/github/freeCodeCamp/boilerplate-mochachai" target="_blank" rel="noopener noreferrer nofollow">Replit</a>  or cloned from <a href="https://github.com/freeCodeCamp/boilerplate-mochachai/" target="_blank" rel="noopener noreferrer nofollow">GitHub</a>. </ins> `deepEqual()` asserts that two objects are deep equal.

Convert a given date from the Gregorian calendar to the Discordian calendar. <del> Note that in the Discordian calendar (Chaos 1, 3188 YOLD) is (January 1, 2022), in the Gregorian calendar. </del> <ins> Note that the day Chaos 1, 3188 YOLD in the Discordian calendar is the day January 1, 2022 in the Gregorian calendar. </ins> # --hints--
Change:
This markdown table is missing backticks around the variables (third column). 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.
Hi , this seems like an issue that i can handle. I am new to freecodecamp repository and would love to contribute
Thank you for your interest! I suggest looking at issues that do not have linked PRs already

Discussion:
| Feature | Variable Type | Variable      | Value Type | |:-------:|:------------:|:-------------:|:----------:| <del> | Age | Objective Feature | age | int (days) | | Height | Objective Feature | height | int (cm) | | Weight | Objective Feature | weight | float (kg) | | Gender | Objective Feature | gender | categorical code | | Systolic blood pressure | Examination Feature | ap_hi | int | | Diastolic blood pressure | Examination Feature | ap_lo | int | | Cholesterol | Examination Feature | cholesterol | 1: normal, 2: above normal, 3: well above normal | | Glucose | Examination Feature | gluc | 1: normal, 2: above normal, 3: well above normal | | Smoking | Subjective Feature | smoke | binary | | Alcohol intake | Subjective Feature | alco | binary | | Physical activity | Subjective Feature | active | binary | | Presence or absence of cardiovascular disease | Target Variable | cardio | binary | </del> <ins> | Age | Objective Feature | `age` | int (days) | | Height | Objective Feature | `height` | int (cm) | | Weight | Objective Feature | `weight` | float (kg) | | Gender | Objective Feature | `gender` | categorical code | | Systolic blood pressure | Examination Feature | `ap_hi` | int | | Diastolic blood pressure | Examination Feature | `ap_lo` | int | | Cholesterol | Examination Feature | `cholesterol` | 1: normal, 2: above normal, 3: well above normal | | Glucose | Examination Feature | `gluc` | 1: normal, 2: above normal, 3: well above normal | | Smoking | Subjective Feature | `smoke` | binary | | Alcohol intake | Subjective Feature | `alco` | binary | | Physical activity | Subjective Feature | `active` | binary | | Presence or absence of cardiovascular disease | Target Variable | `cardio` | binary | </ins> ## Tasks
Change:
There is a typo in Step 45, the word is misspelled. Here is the typo it should be in step 26, is incorrect grammar, it should be or 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.
Is anybody working on this issue? if not I would like too
Hello.. I would like to contribute to this issue.. Kindly assign me the same

Discussion:
# --description-- <del> The variables you have assigned have all had values that are numbers. JavaScript has multiple different data types. The next one you will be use is the <dfn>string</dfn>. Strings are used to store things like words or text. Strings are surrounded with double quotes, single quotes, or backticks. Here is an example of declaring a variable with a string: </del> <ins> The variables you have assigned have all had values that are numbers. JavaScript has multiple different data types. The next one you will use is the <dfn>string</dfn>. Strings are used to store things like words or text. Strings are surrounded with double quotes, single quotes, or backticks. Here is an example of declaring a variable with a string: </ins> ```js let developer = "Naomi";

# --hints-- <del> You should use dot notation to access the `innerText` propertry of `text`. </del> <ins> You should use dot notation to access the `innerText` property of `text`. </ins> ```js assert.match(code, /text.innerText/);
Change:
There is a typo in Step 108, the word is single while it should be . Here is the typo in step 102, there is a missing code block in this line it should be this in step 81, there are three missing code blocks in these line they should be If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first. Happy contributing.
I would like to work on this.
feel free to open a pull request, after you have read .
I have opened a PR please let me know if there are any changes or improvements that needs to be done.

Discussion:
assert.equal(weapons[0].power, 5); ``` <del> Your second `weapons` object should have the `name` set to `dagger` and the `power` set to 30`. </del> <ins> Your second `weapons` object should have the `name` set to `dagger` and the `power` set to `30`. </ins> ```js assert.equal(weapons[1].name, 'dagger'); assert.equal(weapons[1].power, 30); ``` <del> Your third `weapons` object should have the `name` set to `claw hammer` and the `power` set to 50. </del> <ins> Your third `weapons` object should have the `name` set to `claw hammer` and the `power` set to `50`. </ins> ```js assert.equal(weapons[2].name, 'claw hammer'); assert.equal(weapons[2].power, 50); ``` <del> Your fourth `weapons` object should have the `name` set to `sword` and the `power` set to 100. </del> <ins> Your fourth `weapons` object should have the `name` set to `sword` and the `power` set to `100`. </ins> ```js assert.equal(weapons[3].name, 'sword');

assert.match(sellWeapon.toString(), /golds*+=s*15/); ``` <del> You should set `goldText.innerText` to gold. </del> <ins> You should set `goldText.innerText` to `gold`. </ins> ```js assert.match(sellWeapon.toString(), /goldText.innerTexts*=s*gold/);

Now you can start the code to fight monsters. To keep your code organized, your `fightDragon` function has been moved for you to be near the other `fight` functions. <del> Below your `weapons` array, define a `monsters` variable and assign it an array. Set that array to have three objects, each with a `name`, `level`, and `health` property. The first object's values should be `slime`, `2`, and `15`, in order. The second should be `fanged beast`, `8`, and `60`. The third should be `dragon`, `20`, and `300`. </del> <ins> Below your `weapons` array, define a `monsters` variable and assign it an array. Set that array to have three objects, each with a `name`, `level`, and `health` properties. The first object's values should be `slime`, `2`, and `15`, in order. The second should be `fanged beast`, `8`, and `60`. The third should be `dragon`, `20`, and `300`. </ins> # --hints--
Change:
I have pass all test case of "Exercise Tracker" challenge except the 7th test case("you can POST to /api/users/:id/exercises with ..."), I tried many way but still can't pass this test case. When i open the console of Chorm, i found the bug "(...).subtingr is not a function" when i click on the button "I've completed this challenge" to submit the `` the console of brower the link into Solution Link on "I've completed this challenge" error This error should be disappear ! Device: [Laptop] OS: [Windows 11] Browser: [Chrome] Version: [106.0.5249.103] No response
~Please provide the link to the project that you submitted~ EDIT: still half asleep sorry, ignore that
Thanks for opening this issue. This looks something that can be fixed by "first time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: Line contains the typo, should be . 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.
Hello, I am interested in working on it
hey there, I suggest reading our contributing guidelines! as it says, all issues with and labels are up for grabs
I have fixed this issue and raised a PR.

Discussion:
const res = await fetch(url + '/api/users', { method: 'POST', headers: { 'Content-Type': 'application/x-www-form-urlencoded' }, <del> body: `username=fcc_test_${Date.now()}`.substingr(0, 29) </del> <ins> body: `username=fcc_test_${Date.now()}`.substring(0, 29) </ins> }); if (res.ok) { const { _id, username } = await res.json();
Change:
There is a typo in Step 174, the structure of the phrase is harming translation effort as mention in crowdin by translator here is the sentence Here is the original issue they have recommended using I recommend something else Removing the code tags, the word if is used as an English word hinting about the keyword, and there is a hint about keyword in the hints, so I don't see an actual use for the code tags.
Your suggestion LGTM
You mean this? That would totally work I think

Discussion:
# --description-- <del> Since you subtracted health from the player, you need to check `if` the player's `health` is less than or equal to `0`. If it is, call the `lose` function. </del> <ins> Since you subtracted health from the player, you need to check if the player's `health` is less than or equal to `0`. If it is, call the `lose` function. </ins> # --hints--
Change:
in the document, the instruction header says this: because how the following instruction looks I agree with the camper suggestion, in the original issue Can we clear the empty line in the code block, it's annoying me here is the file here is the original issue
hiii, Please accept the pull request
Hello Please is this still open? And how can I work on it?

Discussion:
git cherry-pick <commit-hash> ``` <del> 4. Resolve any conflicts, and cleanup, install run tests </del> <ins> 4. Resolve any conflicts, cleanup, install dependencies and run tests </ins> ```console npm run clean
Change:
There is a typo in Step 156, the word is used to refer to the operator. Here is the typo it should be Can you change the lowercase that refers to the operator in the file, to uppercase , as well? to follow the docs of Mozilla 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.
Hello, I would like to work on this issue.
hello,can i resolve the issue?

Discussion:
# --description-- <del> We don't want a player's only weapon to break. The logical or operator checks if two statements are true. </del> <ins> We don't want a player's only weapon to break. The logical AND operator checks if two statements are true. </ins> <del> Use the <dfn>logical and</dfn> operator `&&` to add a second condition to your `if` statement. The player's weapon should only break if `inventory.length` does not equal (`!==`) one. </del> <ins> Use the <dfn>logical AND</dfn> operator `&&` to add a second condition to your `if` statement. The player's weapon should only break if `inventory.length` does not equal (`!==`) one. </ins> Here is an example of an `if` statement with two conditions:

assert.match(attack.toString(), /ifs*(Math.random()s*<=s*.1/); ``` <del> You should use the logical and operator `&&`. </del> <ins> You should use the logical AND operator `&&`. </ins> ```js assert.match(attack.toString(), /ifs*(Math.random()s*<=s*.1s*&&/); ``` <del> You should use the logical and operator to check if `inventory.length` does not equal `1`. </del> <ins> You should use the logical AND operator to check if `inventory.length` does not equal `1`. </ins> ```js assert.match(attack.toString(), /ifs*(Math.random()s*<=s*.1s*&&s*inventory.lengths*!==s*1s*)/);
Change:
in the document, there is a sentence saying this: But this section is talking about assigning proofreading, it should be changed to this: here is the file here is the original issue 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.
I can take this up

Discussion:
This will open the user management tools, you will be able to see the list of all the users. <del> Search for the user that will become contributor. Use the three dots menu on the user row to open a menu and select "Add to team". The proofreader teams have a standard name of `Proof Readers (<language>)`, you can search the team using the language name. Once you have selected the team, use the "ADD" button at the bottom of the page to finalize the thing. </del> <ins> Search for the user that will become proofreader. Use the three dots menu on the user row to open a menu and select "Add to team". The proofreader teams have a standard name of `Proof Readers (<language>)`, you can search the team using the language name. Once you have selected the team, use the "ADD" button at the bottom of the page to finalize the thing. </ins> The user is now a proofreader.
Change:
There's a consistent grammatical issue. The author uses "it's" to indicate possession, when the correct word is "its". Due to this, I am also willing to look for other grammatical errors. They could cause confusion, or, at the very least, annoyance. /Note: this issue is present throughout the entire challenge/ n/a n/a Device: Macbook Air OS: Mac OS Ventura Browser: Chrome This is more of a writing issue than a tech one. I hope that's ok.
Thank you for taking the time to open this. I am only able to see the use of in 2 challenges: step-8 step-10 Would you mind sharing any more?
An issue with the 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

Discussion:
A useful property of an _SVG_ (scalable vector graphics) is that it contains a `path` attribute which allows the image to be scaled without affecting the resolution of the resultant image. <del> Currently, the `img` is assuming it's default size, which is too large. Correctly, scale the image using it's `id` as a selector, and setting the `width` to `max(100px, 18vw)`. </del> <ins> Currently, the `img` is assuming its default size, which is too large. Correctly, scale the image using it's `id` as a selector, and setting the `width` to `max(100px, 18vw)`. </ins> # --hints--

# --description-- <del> Make the `header` take up the full width of its parent container, set it's `height` to `50px`, and set the `background-color` to `#1b1b32`. Then, set the `display` to use _Flexbox_. </del> <ins> Make the `header` take up the full width of its parent container, set its `height` to `50px`, and set the `background-color` to `#1b1b32`. Then, set the `display` to use _Flexbox_. </ins> # --hints--