jiebi/CodeConvo huggingface dataset:
Change:
"learn-how-to-ask-and-share-about-educational-and-professional-background": { "title": "Learn How to Ask and Share About Educational and Professional Background", "intro": [ <del> "In this course, you'll learn how to ask about another person's educational and professional backgrouns and you'll learn how to share information about your background as well." </del> <ins> "In this course, you'll learn how to ask about another person's educational and professional backgrounds and you'll learn how to share information about your background as well." </ins> ] }, "learn-how-to-talk-about-hobbies-and-interests": {

Discussion:
There is a typo in this file on this line: This is the ONLY file that needs to be changed. PLEASE READ THE CONTRIBUTOR DOCS BEFORE OPENING A PULL REQUEST 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
Change:
} from './utils/env'; import { userRoutes } from './routes/user'; import { donateRoutes } from './routes/donate'; <ins> import { statusRoute } from './routes/status'; </ins> export type FastifyInstanceWithTypeProvider = FastifyInstance< RawServerDefault,

Discussion:
This is a a health check endpoint
Check the issue of internet ping, connect with network [ ]way run of tickettttttttt....... thank
Change:
## --text-- <del> What does Bob want to know about lisa? </del> <ins> What does Bob want to know about Lisa? </ins> ## --answers--

Discussion:
Lisa's name is not capitalized in the question. The question is: The question should be No response Device: all OS: all Browser: all Version: all No response
Thanks for reporting the issue. It's a nice catch! This issue is open to first-time code contributors to this repository. The file that you should be updating is Please make sure you read our as well as our from a pull request, 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.
Change:
## Instructions <section id='instructions'> <del> The navigation bar in the code is labeled with an id of <code>navbar</code>. Change its <code>position</code> to <code>fixed</code>, and offset it 0 pixels from the <code>top</code> and 0 pixels from the <code>left</code>. Notice the (lack of) impact to the <code>h1</code> position, it hasn't been pushed down to accommodate the navigation bar and would need to be adjusted separately. </del> <ins> The navigation bar in the code is labeled with an id of <code>navbar</code>. Change its <code>position</code> to <code>fixed</code>, and offset it 0 pixels from the <code>top</code> and 0 pixels from the <code>left</code>. After you have added the code, scroll the preview window to see how the navigation stays in place. </ins> </section> ## Tests

Discussion:
Describe your problem and how to reproduce it: We were in the middle of a meetup that was oriented at beginners, and a camper that was doing this challenge asked me: what does do? I feel like it works exactly as I showed them that it kept the element in place when the page scrolled. The description says it One key difference between the and positions is that an element with a fixed position won't move when the user scrolls. However, it doesn't provide a visible example where the user can scroll and see that for themselves. Add text and styles to invite campers to scroll the content and see how differs from . Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Google Chrome Browser Version: Version 77.0.3865.90 Operating System: Elementary OS Loki 0.4.1 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! As you can see, the content isn't scrollable
Change:
font-size: 1.2rem; } <del> .completion-challenge-name, </del> .completion-block-name { font-size: 1rem; }

Discussion:
The contains a lot of unused CSS rules, which should be cleaned up. The unused rules/classes are: .challenge-success-modal .btn-lg .btn-cta-big .completion-modal-body .completion-message .completion-challenge-nameRemove the above classes from Test and confirm that the modal displays properly after the changes
Hi, I can help with this If you would like to assign it to me.
Change:
console.log(greeting()); // Hello Anonymous ``` <del> Add a new parameter to your `setPlayerCards` function called `arr` and assign it a default value of `players`. </del> <ins> Add a new parameter to your `setPlayerCards` function called `arr` and assign it a default value of `players`. Remember that you destructured the `players` variable from the `myFavoriteFootballTeam` object on line `175`. </ins> # --hints--

Discussion:
it is confusing whether campers will pass string of 'Players' or variable named . i think the wording should be cleared on the hint. ! Your parameter should have a default value pointing towards the variable named . something like this should be on the hint ? ! OS: [Windows 11] Browser: [Chrome] No response
I think it would be best to update the description to remind campers where came from some thing like
Change:
Text is often a large part of web content. CSS has several options for how to align it with the `text-align` property. <del> `text-align: justify;` causes all lines of text except the last line to meet the left and right edges of the line box. </del> <ins> `text-align: justify;` spaces the text so that each line has equal width. </ins> `text-align: center;` centers the text

Discussion:
!
If possible please assign this issue to me! as I am new to open source
For future reference, it would help to have a link to the challenge when creating an issue It's To clarify, you want to change: to: That's not bad. What about
Yes, that is better! and sorry for any inconvenience as I am new to open source
Please, can you assign me to resolve that issue? That'll be a great start for my open source journey!
We do not assign issues The first PR that fixes the problem will be accepted. If you have not done so already, you should read the . Thanks for your interest in contributing If you have any questions, feel free to ask - or you can reach out in the
Please review the PR
please be patient, people will review when they can.
Alright!
Change:
template }; } <del> challengeData.theme = theme; </del> return challengeData; };

Discussion:
I did not see anyone raising this issue, but I don't think the background of the preview in default or night mode should be anything other than white unless the coding exercise specifically changes the background to something else. The preview should be exactly what you would see in a browser. In almost all the challenges, the background would be white. !
I share your concerns The reason we changed the color of the display is that a white display is discomforting to the eye on night mode when everything else is dark. so we injected some styles to harmonize the view in general. That convention was carried over to light mode.
It might be better to default to white in light mode, same as the editor. As for night mode, some of the css challenges might need some changes to look reasonable in both modes. For instance, in night mode, looks like this: ! If we change the seed code to it would become ! It would have to be case-by-case, though.
That is a very good point. I will defer this to
Logically, I have to agree with - displaying anything other than what the code in the editor would produce might confuse campers. But it is a little rough on the eyes to have the white background on night mode. And the current theme looks a lot better - so it's a tough call. I scrolled through a number of challenges, and there's quite a few that don't look right with the blue background. So there might be a decent amount of work to go through and fix all of them.
I really like the new theme, but a preview should be a true preview. We want to make this like the real world. Developers working in some kind of night mode on their favorite local editors, still expect to check the "real" result of the code they have written on a browser or in a preview mode in their local editors. The night mode should only apply to the editor or the non-preview part of the FCC site. Anything else is just not realistic.
The preview should be white.
I agree with everyone here on this thread. The preview should remain white. Note that soon the preview won't always be there on the right side "brightening up" the user interface and ruining people's night mode experience.

Soon we will have a single column layout where you the preview only shows up when you click a button to show it, or it loads in a separate tab. - could you update the styling on this so that the preview area is unaffected by our styling?
Definitely.
Change:
```js const afterCalculateTotal = code.split('calculateTotal')[1]; <del> assert.match(afterCalculateTotal, /(s*totals*,s*items*)s*=>s*totals*+s*item.price/); </del> <ins> assert.match(afterCalculateTotal, /(s*totals*,s*items*)s*=>s*(?:totals*+s*item.price|item.prices*+s*total)/); </ins> ``` Your `reduce` call should have an initial value of `0`. ```js const afterCalculateTotal = code.split('calculateTotal')[1]; <del> assert.match(afterCalculateTotal, /thiss*.s*itemss*.s*reduces*(s*(s*totals*,s*items*)s*=>s*totals*+s*item.prices*,s*0s*)/); </del> <ins> assert.match(afterCalculateTotal, /thiss*.s*itemss*.s*reduces*(s*(s*totals*,s*items*)s*=>s*(?:totals*+s*item.price|item.prices*+s*total)s*,s*0s*)/); </ins> ``` # --seed--

Discussion:
When working through the , it's expected from the user to create a method that internally uses a to make a sum, like the following: But when presented the following solution, making the reduce's callback sum the other way around, it doesn't pass: Because of the , the previous presented solution should work. No response Device: Laptop OS: macOS 13.6.6 Browser: Chrome Version: 124 No response
I agree that both versions should be accepted since they are valid solutions.
Change:
const res = await fetch('https://pokeapi-proxy.freecodecamp.rocks/api/pokemon/pikachu'); // Fetch from proxy to simulate network delay if (res.ok) { <del> await new Promise(resolve => setTimeout(resolve, 50)); // Brief additional delay to allow UI to update </del> <ins> await new Promise(resolve => setTimeout(resolve, 1000)); // Additional delay to allow UI to update </ins> const pokemonName = document.getElementById('pokemon-name'); const pokemonID = document.getElementById('pokemon-id');

Discussion:
When testing one camper's code it fails some tests unless I increase all the delays to 1000ms, I tested with 500ms but that was not enough. I also saw the example project fail a test but it does pass more consistently (my guess is it is just faster with fewer async functions). To be on the safe side we should have a longer delay. I know 1000ms is a lot but better safe than sorry. Tests: Valid code should not fail because of "timing" issues. No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] Forum:
As this is a bug with a certificate project I the showstopper label.
Change:
# --hints-- <del> The endpoint `/json` should serve the json object `{"message": "Hello json"}` </del> <ins> The endpoint `/json` should serve the JSON object `{"message": "Hello json"}` </ins> ```js (getUserInput) =>

Discussion:
The word json should be capitalized in the hint text: The endpoint /json should serve the json object {"message": "Hello json"} Referenced challenge file: curriculum/challenges/english/05-back-end-development-and-apis/basic-node-and-express/serve-json-on-a-specific- Use capitals instead of lowercase letters when referring to JSON No response Not applicable No response
Change:
dashedName: task-55 --- <del> <!-- (audio) Tom: Those are great traits for someone in her position, I think. What does she do as our team lead? --> </del> <ins> <!-- (audio) Tom: Those are great traits for someone in her position, I think. What does she do as the team lead? --> </ins> # --description-- <del> Now you will practice listening for the correct form of `do.` Listen carefully to how Tom asks about Maria's job as a team lead. </del> <ins> Now you will practice listening for the correct form of `do`. Listen carefully to how Tom asks about Maria's job as a team lead. </ins> # --instructions--

Discussion:
The fill-in-the-blank sentence doesn't match what the character says. The written sentence is: The character says: Note the "the", instead of "our". No response Device: all OS: all Browser: all Version: all No response
Thank you for reporting the issue. Note for maintainers: Step 54 () uses "our" instead of "the" in the quiz. I think it's fine as-is since there isn't associated audio/caption text, but I'd vote updating it, too, for consistency. This issue is open to first-time code contributors to this repository. Requirements: In Change the text in the tag from to In Change the text in the tag from to Change the fill-in-the-blank text from to Change the backtick placement in the description text from ` In Change the text of the answers from to 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 I've created a PR addressing these changes.
Change:
# --description-- <del> Add another `p` element with the text `Total Carbohydrate 37g 13%`. Like before, use `span` elements to make the text `Total Carbohydrate` and `13%` bold. Also add an additional `span` element to wrap the `Total Carbohydrate 37g` text in a span element so to have it aligned to the left, and `13%` to the right. </del> <ins> Below your last `p` element, add another `p` element with the text `Total Carbohydrate 37g 13%`. Like before, use `span` elements to make the text `Total Carbohydrate` and `13%` bold. Also add an additional `span` element to wrap the `Total Carbohydrate 37g` text in a span element to have it aligned to the left, and `13%` to the right. </ins> # --hints--

Discussion:
The instructions do not state clearly where the new element should be . I believe they are relying on the fact that the previous two steps a element to the end of the div and thus they assume the user will continue this trend in step 55. But I just ran into a forum post that the element after the div, so I'm not sure that's a safe assumption. Step 54 tells the user to add the element "Below your last element" and I think we should do the same thing here. N/A Change the beginning of the instructions to read: "Below your last element, add another element with the text..." 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
Quick question, do you think we have a typo in the instruction as well?
Yes, you're correct. The phrase "so to have it aligned to the left" can be revised to "to have it aligned to the left" for a better concise expression.
When will be waiting for triage label removed
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: A pull request which resolves this issue should: 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, do you think the sentence could be made more effective by removing the redundant phrase 'span element' that occurs twice in the same line?
I agree that the "in a span element" part is redundant and should be removed, but I'm not sure about the extra comma there as it makes the sentence disjointed. We might want to just ditch the commas altogether:
Agreed. Two commas seem to break the sentence unnecessarily. I already raised a PR () suggesting the removal of the redundant part, which was not merged. Should I push changes in the same PR, or create a new one?
Change:
const Project = ({ challenge }: { challenge: ChallengeWithCompletedNode }) => ( <Link to={challenge.fields.slug}> {challenge.title} <del> <span className=' badge map-badge map-project-checkmark'> </del> <ins> <span className='map-badge map-project-checkmark'> </ins> <CheckMark isCompleted={challenge.isCompleted} /> </span> </Link>

Discussion:
A2 English blocks have challenges whose title is displayed next to a completion indicator. The indicator is having a right margin, which creates a gap between the indicator and the text. <img width="746" alt="Screenshot 2024-05-31 at 22 49 13" src=""This issue is because the indicator has a class: This class was harmless as it didn't have any CSS rules associated, until we badges to the user profile page, which caused a class name collision: Remove the class from: Rename the class in to to avoid future collision
I can take this one, but I don't seem to have the permissions to assign myself to this issue.
We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labelled with or are open for contributions. Please make sure you read . We prioritize contributors following the instructions in our guide. Join us in or if you need help contributing - our community will be happy to assist you.
Awesome, thanks for clarifying!
Change:
# --description-- <del> Inside your `select` element, add the following five `option` elements with these corresponding values for the option text and `value` attribute: </del> <ins> Inside your `select` element, add the following five `option` elements with these corresponding values for the `option` text and `value` attribute: </ins> **Value Attributes:**

Discussion:
There are some small issues that need to be fixed in the following files: optionfor elementsinline"Check your code" String` This looks like something that can be fixed by "first-time" code contributors to this repository. The files you should look at to work on a fix are those linked above. 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 I'd like to work on this issue. Thanks
Hey We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labelled with or are open for contributions. Please make sure you read . We prioritize contributors following the instructions in our guide. Join us in or if you need help contributing - our community will be happy to assist you.
Change:
userSelector, isOnlineSelector, isServerOnlineSelector, <ins> showCodeAllySelector, </ins> userFetchStateSelector } from '../../redux/selectors';

Discussion:
The page gets stuck and goes blank with you leave the relational database challenges. to 'Start the course' the fCC logo/button in the nav goes blank and nav disappears Page not to go blank. Clicking fCC logo should go to /learn No response Same on Chrome and Firefox Console errors: <img width="671" alt="Screen Shot 2023-02-16 at 11 44 19 AM" src="https://user-"
Change:
You should have an `if` statement that checks if the right key was pressed and if the `isCheckpointCollisionDetectionActive` is true. ```js <del> assert.match(code, /ifs*(s*keys.rightKey.presseds*&&s*isCheckpointCollisionDetectionActives*)s*{s*(.*?)s*}/); </del> <ins> assert.match(code, /ifs*(((s*keys.rightKey.presseds*&&s*isCheckpointCollisionDetectionActives*)|(s*isCheckpointCollisionDetectionActives*&&s*keys.rightKey.presseds*)))s*{s*(.*?)s*}/); </ins> ``` # --seed--

Discussion:
step 78 of the platformer game project wants the user to type: but if we type the checks in reverse like: It is not accepted. Stumbled on this one because to me writing the long variable name first is easier because I copy and paste it directly from the step and then I spend a little longer looking up how to tell the right key is pressed so I put that second. Since the order of conditions is not specified though in the step, the check should not be so picky. (see above) less strict checking when the order of comparisons in the if makes no difference to the result (or please specify that order matters in the instructions or the hint) No response N/A please note that step 80 has the same issue as well:
Change:
import { wrapHandledError } from '../utils/create-handled-error'; const authRE = /^/auth//; <ins> const confirmEmailRE = /^/confirm-email$/; </ins> const newsShortLinksRE = /^/n/|^/p//; <ins> const publicUserRE = /^/api/users/get-public-profile$/; const publicUsernameRE = /^/api/users/exists$/; </ins> const resubscribeRE = /^/resubscribe//; const showCertRE = /^/certificate/showCert//; // note: signin may not have a trailing slash const signinRE = /^/signin/; <ins> const statusRE = /^/status/ping$/; </ins> const unsubscribedRE = /^/unsubscribed//; const unsubscribeRE = /^/u/|^/unsubscribe/|^/ue//; const updatePaypalRE = /^/donate/update-paypal/; const _whiteListREs = [ authRE, <ins> confirmEmailRE, </ins> newsShortLinksRE, <ins> publicUserRE, publicUsernameRE, </ins> resubscribeRE, showCertRE, signinRE, <ins> statusRE, </ins> unsubscribedRE, unsubscribeRE, updatePaypalRE

Discussion:
These should be available without any access tokens: [x] Used for public profile views. [x] Used for confirming and email. [x] Health Check
Change:
import { CompletedChallenge } from '../../redux/prop-types'; import { getSolutionDisplayType } from '../../utils/solution-display-type'; <del> import './solution-display-widget.css'; </del> import '@freecodecamp/ui/dist/base.css'; interface Props { completedChallenge: CompletedChallenge;

Discussion:
contains a single CSS rule: This rule is not needed as the underline of the is already turned off by the component library. Remove Remove the class from
This issue is open for contribution. Please make sure you read our as well as our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. 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.
Change:
if (this.state.downloadURL) { URL.revokeObjectURL(this.state.downloadURL); } <ins> this.props.close(); </ins> } render() {

Discussion:
Describe the bug If you complete a challenge, navigate back (taking you to the curriculum), then open a new challenge the success modal will still be open. To Reproduce Steps to reproduce the behavior: to the challenge -enter the success modal back to that the modal is still present Expected behavior The modal should be closed every time you leave a challenge. Screenshots !