jiebi/CodeConvo huggingface dataset:
Change:
<section id='solution'> ```js <del> // solution required </del> <ins> const createPerson = (name, age, gender) => { "use strict"; return { name, age, gender }; }; </ins> ``` </section>

Discussion:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --1) Add any code into the challenge field (other than a valid solution) that will not result in a syntax error. 2) Run the tests Expected result: The test should fail Actual result: The test passes Browser Name: Firefox Browser Version: 61.0 Operating System: 10.12.6 !
The problem is this test in the : It returns true if returns an object with no keys, or just not-an-object. I assume we should really be using something like to check the expected object and the user's output object are the same.
Working on a fix.
Change:
This demonstrates an unusual property of 142857: it is a divisor of its right-rotation. <del> Find the last 5 digits of the sum of all integers $n$, $10 &lt; n &lt; 10100$, that have this property. </del> <ins> For integer number of digits $a$ and $b$, find the last 5 digits of the sum of all integers $n$, $10^a &lt; n &lt; 10^b$, that have this property. </ins> # --hints-- <del> `numberRotations()` should return `59206`. </del> <ins> `numberRotations(2, 10)` should return `98311`. </ins> ```js <del> assert.strictEqual(numberRotations(), 59206); </del> <ins> assert.strictEqual(numberRotations(2, 10), 98311); ``` `numberRotations(2, 100)` should return `59206`. ```js assert.strictEqual(numberRotations(2, 100), 59206); </ins> ``` # --seed--

Discussion:
The 100 should be a superscript in the last line of this challenge. N/A Should say We may also consider better mathematical formatting? No response All No response
Seems like it has been like this for a while: I will open this up to first timers. The expected fix is to use MathJax (KaTeX-like) to render the following: $$ n: 10 < n < 10^{100} $$ An issue with the first timers only 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
I actually saw a way to roll this into a fix that expands the challenge so that won't work.
Change:
} .video-quiz-options { <del> background-color: var(--tertiary-background); </del> <ins> background-color: var(--primary-background); </ins> } /* remove bootstrap margin here */

Discussion:
<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.
Change:
} button { <del> outline: none; </del> cursor: pointer; text-decoration: none; background-color: var(--light-yellow);

Discussion:
The default CSS provided for the Calorie Counter in step 1 has the property set to for the element. I'm going to assume this was just an oversight, and not because you all are trying to cause me an early death by raising my blood pressure. Remove the property completely from the element. No response N/A No response
Change:
```js const meta = [...document.querySelectorAll('meta')]; <del> const target = meta?.find(m => !m?.getAttribute('name') && !m?.getAttribute('content') && m?.getAttribute('charset') === 'UTF-8'); </del> <ins> const target = meta?.find(m => !m?.getAttribute('name') && !m?.getAttribute('content') && m?.getAttribute('charset')?.toLowerCase() === 'utf-8'); </ins> assert.exists(target); ```

Discussion:
The value for is case-insensitive. Not sure if I missed any, but here are case-sensitive ones I found. Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-accessibility-by-building-a-quiz Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-css-animation-by-building-a-ferris-wheel Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-intermediate-css-by-building-a-picasso-painting Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-responsive-web-design-by-building-a-piano Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-the-css-box-model-by-building-a-rothko-painting a lot Both are valid The value for should be case insensitive for all challenges. 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]
Change:
<del> require('dotenv').config(); </del> <ins> const env = require('../config/env'); </ins> const { createFilePath } = require('gatsby-source-filesystem');

Discussion:
Is there any reason not to put the real and in ? I reflexively put in a dummy key when I set this up, but now that I revisit this, that seems like a mistake.
Yes, actually it broke the .dev build unsurprisingly , I think noticed it and reported in the team chat. My bad for not catching this previously. The real fix is to ignore and move ahead when the keys are not available are default. We do this with google application credentials.
Oh, I assume it broke the build because .dev isn't using I didn't think of that... So, we should implement the fix and add the public keys to , right?
I was thinking something more along the lines of (example from api-server): I would try to avoid hundreds of contributors hitting the indexes locally. Ideally people should get their own keys. While the key and index is public, it's still not recommended to hit it?
As for the production keys, it's actually fine because the build should fail. I have since the keys in the build pipeline.
One thing: if we don't want contributors spamming search (fair enough!) I think there should be some docs that let people know what's what. Either that search isn't available in development or the steps they need to take to make it work.
I agree. We should add some docs on getting keys, or perhaps creating a test index and sharing that instead
Change:
"Create an <code>ordered list</code> of the the top 3 things cats hate the most.", "HTML has a special element for creating ordered lists, or numbered-style lists.", "Ordered lists start with a <code>&#60;ol&#62;</code> element. Then they contain some number of <code>&#60;li&#62;</code> elements.", <del> "For example: <code>&#60;ol&#62;&#60;li&#62;hydrogen&#60;/li&#62;&#60;li&#62;helium&#60;/li&#62;&#60;ol&#62;</code> would create a numbered list of "hydrogen" and "helium"." </del> <ins> "For example: <code>&#60;ol&#62;&#60;li&#62;hydrogen&#60;/li&#62;&#60;li&#62;helium&#60;/li&#62;&#60;/ol&#62;</code> would create a numbered list of "hydrogen" and "helium"." </ins> ], "tests": [ "assert($('ul').length > 0, 'You should have an <code>ul</code> element on your webpage.')",

Discussion:
Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. What I see: You can apply a class to an HTML element like this: <h2 class="blue-text"CatPhotoApp<h2What I expected to see: You can apply a class to an HTML element like this: <h2 class="blue-text"CatPhotoApp</h2
Markdown's getting in the way, see screenshot. !
Change:
"knip": "npx -y knip@1 --include files", "knip:all": "npx -y knip@1", "prelint": "pnpm run -F=client predevelop", <del> "lint": "npm-run-all create:shared -p lint:*", </del> <ins> "lint": "NODE_OPTIONS="--max-old-space-size=7168" npm-run-all create:shared -p lint:*", </ins> "lint:challenges": "cd ./curriculum && pnpm run lint", "lint:js": "eslint --cache --max-warnings 0 .", "lint:ts": "tsc && tsc -p shared && tsc -p api",

Discussion:
Linting fails on local environment in some cases. Issue did not reproduce on GitPod. update-email to the root directory Execution fails with the message under Linting should be successful No response Device: Macbook Air M2 OS: MacOSThis issue was originally raised in Discord: Thread created with the full error log: A contributor also ran into this issue in the past: Note that the lint operation in this one ran against the entire project () rather than a single file.
Thanks for opening this issue. I'm not able to reproduce the issue locally, so I'll need your help with this: Add: after this line: Commit this change using the flag Make a change to and check if you can commit the change without the flag This is to check if those rules are the culprit as I did run into some performance issues with them in the past. Here is our eslint current performance, in case anyone is interested: <img width="521" alt="Screenshot 2023-12-18 at 13 58 26" src=""
Thanks for your help I am still facing the issue. I the two lines after line 89, committed with --no-verify. I a space to and tried to commit without the flag. Attached the stack trace.
It seems like the memory allocation on your machine is capped at 2 GB. I tried reducing the limit to 512 MB using the following command, but could not reproduce the issue still: I'm wondering if it works if you increase the value on your end to . So please try this: In the root, add the following line to the "scripts" block: Then run in the terminal
Fixed it! I tried running but that did not seem to update the memory allocation when I ran Instead, I ran something similar to your command in the terminal - This fixed it. Thanks a lot! Should we add this in the documentation?
Change:
"description": [ "Sometimes you want to add <code>a</code> elements to your website before you know where they will link.", "This is also handy when you're changing the behavior of a link using <code>jQuery</code>, which we'll learn about later.", <del> "Replace your <code>a</code> element's <code>href</code> attribute with a <code>#</code>, also known as a hash symbol, to turn it into a dead link." </del> <ins> "Replace the value of your <code>a</code> element's <code>href</code> attribute with a <code>#</code>, also known as a hash symbol, to turn it into a dead link." </ins> ], "tests": [ "assert($("a").attr("href") === "#", 'Your <code>a</code> element should be a dead link with a <code>href</code> attribute set to "#".')"

Discussion:
Says: Replace your a element's href attribute with a #, also known as a hash symbol, to turn it into a dead link. I think it is kind of unclear - would potentially be better as "Replace the value of your a element's...." Tripped me up at first. Submitting a pull request for the change
Change:
export function getGuideUrl({ forumTopicId, title = '' }) { title = encodeURIComponent(title); return forumTopicId <del> ? `${forumLocation}/t/${forumTopicId}` </del> <ins> ? `https://forum.freecodecamp.org/t/${forumTopicId}` </ins> : `${forumLocation}/search?q=${title}%20in%3Atitle%20order%3Aviews`; }

Discussion:
Now it points to a Chinese forum post and shows nothing when people click "Get a Hint" button in the challenge of Chinese curriculum, for example, (). <!-- A clear and concise description of what you want to happen. --We may translate the hints into Chinese and other languages on Crowdin.
It should be possible to create something analogous to our current workflow, as long as the Discourse API allows it. i.e. GET the current articles for upload and then POST the translations once they're approved. Nick probably has a better idea about this than I do, though.
The biggest challenge is going to be figuring out how to update the front matter in the curriculum files to link the appropriate forum post.
I think a really long time ago in one of our conversations with Randy, it was deliberated that the complexity & time involved in working on a way to translate the hint comments, vs working on the new editor & new curriculum was not worth it. But I could be wrong.
That's probably true, but what do we want to do with the "Get a Hint" button? Some options: Link to the English page Remove that button for the Chinese challenges
I think linking to the English page is better~
Can we just link them to English pages?
That should be fine, yeah
Change:
.night .landing-page #top-right-nav li > a, .night #top-right-nav li > span { color: #fff; } <ins> .night .landing-page a { color: #006400; } .night .landing-page a:hover { color: #001800; } </ins> /* End night mode override */ .black-text {

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: At the moment, the clickable area of footer links are spanning the full width of their parent div. I'm not sure if this is on purpose, but IMHO, they should fit to their content instead, since a user could get navigated to another page if they accidentally click somewhere within the clickable area. This issue is on , but it is down for maintenance at the moment. The screenshot is of my local fCC. !
Is that actually a problem, though? I think having list items spread like that is pretty common. It could be a problem if you aimed for, say, Learn and got News, but there's a reasonable amount of space between them. How about if the box were subtly highlighted on hover?
Thanks for the threads
Tbh, this is the first time I have seen footer items spread like that, though it is common to me to see that on a navbar. I have no problem with leaving it as is, but adding background color on hover would be great.
I, personally, would prefer if only the text was clickable - but it works either way.
Personally I like the wider boxes, because I'm lazy and click in the general vicinity of things. So, I've a PR for the highlight approach, since that was a really easy fix. If that doesn't seem right we can always shrink the links onto the text.
Change:
## --text-- <del> What Python library has the `.read_html()` method we can we use for parsing HTML documents and extracting tables? </del> <ins> What Python library has the `.read_html()` method we can use for parsing HTML documents and extracting tables? </ins> ## --answers--

Discussion:
! the sentence needs to be fixed removing the second "we" 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: 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.
Wow
Just submitted a pull request after fixing this typo! This is my first time contributing to open source, so please let me know if there're things that I should've done. Thank you for providing this opportunity for first-time contributors.
Change:
- Seed the database ```bash <del> pnpm run seed </del> <ins> pnpm run seed:certified-user </ins> ``` - Develop the server and client

Discussion:
I had a facepalm moment when I was working on a set of Playwright tests. The tests passed locally but failed in CI, and turned out I was seeding my DB with demo user () while we seed CI with certified user (): The failure was expected then, because the tests were working with different user data. I'm now wondering if we should recommend developing with over in general. If we are okay with this, we will need to update the following section of the : <img width="1088" alt="Screenshot 2023-11-09 at 17 12 23" src=""If we still recommend developing with , then we should add a note in the following section of the to ensure is run before tests are written and executed: <img width="1074" alt="Screenshot 2023-11-09 at 17 15 49" src=""
I think most people want to use the 'new' user and we do mention , so the setup docs seem fine. However, it's definitely not correct to recommend in the Playwright guide. Seems like a simple enough fix, though: the Playwright should say .
I think updating the playwright guide would be enough - but we could add a note in the main area that says something like "Use this if you are going to run playwright tests"
Change:
## --text-- <del> Which of the following describes the affect of a `using` statement? </del> <ins> Which of the following statements is true about showing/removing the curly braces for code blocks associated with an `if` statement? </ins> ## --answers-- <del> Affects only the first code block in the code file. </del> <ins> The curly braces can't be removed from the code block for `else if` and `else` statements. </ins> --- <del> Affects only the current code block in the code file. </del> <ins> If the curly braces are removed from the code blocks of an `if-elseif-else`, the white space must also be removed. </ins> --- <del> Affects all of the code in the code file. </del> <ins> Always choose a style that improves readability. </ins> ## --video-solution--

Discussion:
The "Control Variable Scope and Logic Using Code Blocks in C#" in the "Add Logic to C# Console Applications" has an question that doesn't really feel quite right for this section. The question is "Which of the following describes the affect of a statement?". The thing is statements aren't covered in the foundational MS Learn Path. It'd be a little unfair to new learners to answer this question with the given material. N/A When answering questions on the FreeCodeCamp foundational certification path, prior C# knowledge should not be required to answer questions. A question like the following might be better suited for this particular lesson. What is the scope of a local variable declared inside a method in C#? a) It's accessible only within the method where it's declared. b) It can be accessed from any method within the same class. c) It's accessible globally from any part of the program. d) It's only visible within the same class, but different methods can't access it. No response Device: Desktop OS: Windows 10 Browser: FireFox Version: 117 I only checked out this certification path for practice reasons.
I came across the same issue. I had to read up on the using statement using different resources in order to answer the question and be able to continue my learning path.
I've created a pull request to fix this issue. Since all the other questions are taken from the "Knowledge Check" portion of related tutorial, I just used the first question found here:
Change:
# --description-- <del> Arrays have a `.some()` method. Like the `.filter()` method, `.some()` accepts a callback function which should take an element of the array as the argument. The `.some()` method will return `true` if the callback function returns `true` for at least one element in the array. Here is an example of a `.some()` method call to check if any element in the array is an uppercase letter. ```js const arr = ["A", "b", "C"]; arr.some(letter => letter === letter.toUpperCase()); ``` </del> Add a `someeven` property to your `spreadsheetFunctions` - use the `.some()` method to check if any element in the array is even. # --hints--

Discussion:
In the building a spam filter project's step 's instructions, we are told: "Remember that arrays have a .some() method. " However, we cannot remember as it was not taught. In fact it is not actually taught until step 100 of the building a spreadsheet project as far as I'm aware: I suggest that the part of lesson 100 that applies to teaching the some() method be moved into the spam filter project's step 12. N/A Adding the missing lesson for some() before or during step 12 of the building a spam filter project. No response N/A No response
Hello I am a first timer, can i take up this issue? because adding the .some() function explaination to step 12 will solve this issue and i think it will be pretty easy to do that..
Change:
"challenges": [ { "id": "bb000000000000000000001", <del> "title":  "Trigger Click Events with jQuery", </del> <ins> "title": "Trigger Click Events with jQuery", </ins> "description": [ "In this section, we'll learn how to get data from APIs. APIs - or Application Programming Interfaces - are tools that computers use to communicate with one another.", "We'll also learn how to update HTML with the data we get from these APIs using a technology called Ajax.",

Discussion:
[x] Trigger Click Events with jQuery [x] Change Text with Click Events [x] Get JSON with the jQuery getJSON Method [x] Convert JSON Data to HTML [x] Render Images from Data Sources [x] Prefilter JSON [x] Get Geo-location Data
Trabajando en esta
Change:
"lint:ts": "tsc && tsc -p config && tsc -p tools/ui-components && tsc -p utils && tsc -p api", "lint:prettier": "prettier --list-different .", "reload:server": "pm2 reload api-server/ecosystem.config.js", <ins> "preseed": "npm-run-all create:*", </ins> "seed": "cross-env DEBUG=fcc:* node ./tools/scripts/seed/seed-demo-user", "seed:certified-user": "cross-env DEBUG=fcc:* node ./tools/scripts/seed/seed-demo-user certified-user", "serve:client": "cd ./client && pnpm run serve",

Discussion:
In chapter, we have files that run scripts when the is finished, it use and for this, we can do the same here to solve the issues related to installing needed files, copy and stuff a like, and provide a easier way to setup the curriculum for newer developers. This should stop issues which these PRs try to solve, like and , that are related to setting up freeCodeCamp. Here is the file in chapter , for more context.
I dislike post/pre -install scripts a lot. Actually, I dislike most life-cycle scripts. However, I would be fine with adding a script. Essentially, what is missing with the seed step is:
can we not add to the npm script?
Adding it to the postinstall script would duplicate the run in the CI and deployment pipelines, since it is also included in prebuild. I'd lean more toward Shaun's solution.
I don't mind, as long as the issue is solved, one more agreement and we can open it for contribution.
I see what you mean, it does add a bit of an overhead. It does solve this particular issue albeit with a bit of an overhead. I am not sure of the overall impact, but I'd presume it is minimal? I am happy to re-write it to what was suggested above. But does it make more sense for it to be part of the install lifecycle () script or the develop () lifecycle? let me know your thoughts. Thanks.
I have no idea, I don't meddle with the config files, or scripting tools. This is outside my scope, I just hate that new contributors are facing issues installing the repo.
It should be as a script, like Shaun suggested:
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.