jiebi/CodeConvo huggingface dataset:
Change:
Please check this commit: There is a missing }) on line 524! Should look like this: ! 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
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: The intended change appears to 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.
Hi is anyone working on this issue? If not can I fix it?
Thanks for mentioning the issue. Its seems really easy to fix and I see some pull requests are already there. I am also looking for my first contribution but as per the ethics I should not create pull request for this issue.
Hi, is it still open can i work on it

Discussion:
date: new Date().toLocaleDateString("en-US", { timeZone: "UTC", weekday: "short", month: "short", day: "2-digit", year: "numeric" <ins> }).replaceAll(',', '') </ins> }; const addRes = await fetch(url + `/api/users/${_id}/exercises`, { method: 'POST',
Change:
Some users are encountering the error in the linked video. See the forum for more discussion. All Console error messages should clear so users can run code No response various No response
If I revert the change from it seems to fix it.
I am also facing this issue while doing javascript datastructures and algorithms course. The console errors are stuck and the solution is to refresh the page everysingle time.
I also face this issue while doing a JavaScript data structures and algorithms course. The console errors are stuck and the solution is to refresh the page every single time.
Thanks for tracking that down, it was defintiely the culprit.

Discussion:
challengeFile.fileKey === fileKey ? { ...challengeFile, ...updates } : { ...challengeFile } <del> ) </del> <ins> ), isBuildEnabled: true </ins> }; }, [actionTypes.storedCodeFound]: (state, { payload }) => ({
Change:
Describe the bug When you try to make api call in the setting page, to change your subscription to Quincy newsletter, you will see a failed API call before the new one. To Reproduce Steps to reproduce the behavior: to 'Email Settings' in on unsubscribe from Quincy news-letter alert show before the success alert shown. Expected behavior Wait until the api fail before showing the alert

Discussion:
</FullWidthRow> <Spacer size='medium' /> <FullWidthRow> <del> <form id='form-quincy-email' onSubmit={handleSubmit}> </del> <ins> <form id='form-quincy-email' onSubmit={e => e.preventDefault()}> </ins> <ToggleButtonSetting action={t('settings.email.weekly')} flag={sendQuincyEmail}
Change:
Thanks for noticing this, Sem. As this route has been deprecated for a while, we should be able to safely sunset this route - NOT have it in the new API.
Reopening it as we're migrating deprecated endpoints as discussed in todays API meeting

Discussion:
import security from './plugins/security'; import sessionAuth from './plugins/session-auth'; import { settingRoutes } from './routes/settings'; <ins> import { deprecatedEndpoints } from './routes/deprecated-endpoints'; </ins> import { auth0Routes, devLoginCallback } from './routes/auth'; import { testMiddleware } from './middleware'; import prismaPlugin from './db/prisma';

void fastify.register(devLoginCallback, { prefix: '/auth' }); } void fastify.register(settingRoutes); <ins> void fastify.register(deprecatedEndpoints); </ins> return fastify; };

<ins> import request from 'supertest'; import { build } from '../app'; import { endpoints } from './deprecated-endpoints'; describe('Deprecated endpoints', () => { let fastify: undefined | Awaited<ReturnType<typeof build>>; beforeAll(async () => { fastify = await build(); await fastify.ready(); }, 20000); afterAll(async () => { await fastify?.close(); }); endpoints.forEach(([endpoint, method]) => { test(`${method} ${endpoint} returns 410 status code with "info" message`, async () => { const response = await request(fastify?.server)[ method.toLowerCase() as 'get' | 'post' ](endpoint); expect(response.status).toBe(410); expect(response.body).toStrictEqual({ message: { type: 'info', message: 'Please reload the app, this feature is no longer available.' } }); }); }); }); </ins>

<ins> import { FastifyPluginCallbackTypebox, Type } from '@fastify/type-provider-typebox'; type Endpoints = [string, 'GET' | 'POST'][]; export const endpoints: Endpoints = [ ['/refetch-user-completed-challenges', 'POST'], ['/certificate/verify-can-claim-cert', 'GET'], ['/api/github', 'GET'] ]; export const deprecatedEndpoints: FastifyPluginCallbackTypebox = ( fastify, _options, done ) => { endpoints.forEach(([endpoint, method]) => { fastify.route({ method, url: endpoint, schema: { response: { 410: Type.Object({ message: Type.Object({ type: Type.Literal('info'), message: Type.Literal( 'Please reload the app, this feature is no longer available.' ) }) }) } }, handler: async (_req, reply) => { void reply.status(410); return { message: { type: 'info', message: 'Please reload the app, this feature is no longer available.' } } as const; } }); }); done(); }; </ins>
Change:
Course: Front End Development Libraries Certification Section: Bootstrap Lesson: Add Font Awesome Icons to all of our Buttons The wording is as follows: "Note: The span element is an acceptable alternative to the i element for the directions below." The word "below" is wrong. The instructions are above, not below. Switch word "below" with "above". None/ not applicable to issue. N/A, not applicable to issue Issue is found within the text of the instructions N/a, not applicable This is only a grammatical error found in the instructions for the challenge.
I think the directions mentioned here is the tests.
Yes, this is referring to the instructions in the test text, which is where the element is requested.
Maybe something like this would be clearer
The challenge will accept span elements.
Ahh. So we should probably say something more like
That one works for me. 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: You should update the instruction text to replace: With: 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.
I would like to work on this issue could you please assign it to me
We don't assign issues. We accept the first complete pull request that fully addresses the issue
Very excited

Discussion:
Use Font Awesome to add an `info-circle` icon to your info button and a `trash` icon to your delete button. <del> **Note:** The `span` element is an acceptable alternative to the `i` element for the directions below. </del> <ins> **Note:** You can use either `i` or `span` elements to complete this challenge. </ins> # --hints--
Change:
This is a a health check endpoint
Check the issue of internet ping, connect with network [ ]way run of tickettttttttt....... thank

Discussion:
} 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,

void fastify.register(donateRoutes); void fastify.register(userRoutes); void fastify.register(deprecatedEndpoints); <ins> void fastify.register(statusRoute); </ins> return fastify; };

<ins> import { setupServer, superRequest } from '../../jest.utils'; describe('/status', () => { setupServer(); test('GET returns 200 status code with pong', async () => { const response = await superRequest('/status/ping', { method: 'GET' }); expect(response.body).toStrictEqual({ msg: 'pong' }); expect(response.status).toBe(200); }); }); </ins>

<ins> import { type FastifyPluginCallbackTypebox } from '@fastify/type-provider-typebox'; export const statusRoute: FastifyPluginCallbackTypebox = ( fastify, _options, done ) => { fastify.get('/status/ping', async (_req, _reply) => { return { msg: 'pong' }; }); done(); }; </ins>
Change:
In module, the users are supposed to add their code after the provided code snippet. Keeping that in mind, the comment ( within the provided code snippet ) should be changed from to . In module, the provided code snippet should look as follows: ! Device: Laptop OS: macOS 13.0.1 Browser: Chrome Version: 107.0.5304.110

Discussion:
<p>Lets render this to the DOM</p> </div> ); <del> // Change code below this line </del> <ins> // Add your code below this line </ins> ``` # --solutions--

<p>Lets render this to the DOM</p> </div> ); <del> // Change code below this line </del> <ins> // Add your code below this line </ins> ReactDOM.render(JSX, document.getElementById('challenge-node')); ```
Change:
On , the task is to use the spread operator to copy an array. JS semantics allow the spread operator to have whitespace between it and the object it is being applied to. The following is valid: However, in the challenge, any whitespace between the operator and the value will cause the test to fail. The issue is with the test regex here: Which should probably be amended to: NOTE: this issue was , I am submitting it on their behalf. Whitespace between the spread operator and the object it is being applied to should not cause the test to fail. 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
Looks like a good beginner friendly fix to me
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.

Discussion:
The `copyMachine` function should utilize the `spread operator` with array `arr` ```js <del> assert(code.match(/...arr/)); </del> <ins> assert(code.match(/...s*arr/)); </ins> ``` # --seed--
Change:
Looking forward for reporting a security issue: Please report security issues by following our security policy: Describe the bug A clear and concise description of what the bug is. Gitpod can't be used to develop right now. Or maybe it's possible but someone new wouldn't know what steps they need to take. Should i add a note in how-to-setup-freecodecamp- so that new people know? To Reproduce Steps to reproduce the behavior: instructions in how-to-setup-freecodecamp-locally to develop with gitpod, fails with message
Thanks for letting us know On the pnpm side this should be resolved by any idea why our .gitpod.Dockerfile isn't already using the latest version of pnpm?
Because I have forsaken the local config to focus on: For this repo, I have just been manually running . Personally, I do not like everything running from the get-go, but realise many like the one-button setup. This is so quick to fix, I will just PR it before the long-term fix is ready.

Discussion:
RUN bash -c 'VERSION="18"  && source $HOME/.nvm/nvm.sh && nvm install $VERSION  && nvm use $VERSION && nvm alias default $VERSION  <del> && npm i -g pnpm@8' </del> <ins> && npm i -g pnpm@8.6' </ins> RUN echo "nvm use default &>/dev/null" >> ~/.bashrc.d/51-nvm-fix
Change:
I've run into this enough in the forums that it might be time to fix it. A lot of people leave off the closing tag when turning the image into a link. The hint they get is: "You should only add one opening anchor (a) tag. Please remove any extras." Which is confusing since the objective of the step is to add a second link to the page and the hint makes it sound like there should only be one. Instead, the hint should probably remind them that an anchor element needs both an opening and closing tag. Whether we want to spell it out even further by telling them that they are missing the closing tag I will leave up to the hive mind. If we don't want to be too explicit we could do something like: "Hint: Creating a link with the anchor element requires both an opening and closing tag." Or: "Hint: You must use both an opening and closing tag to create a link." Or if we want to be more direct: "Hint: You are missing a closing tag after the image." No response N/A No response
I think being explicit about a closing tag being needed is the way to go this early in the curriculum
Let us go with this.
Yeah I read through your Issue and it is quite confusing to get this hint. The explicit hint you mentioned is the way to go.
Can I make that change ? I just did this locally and works.
This has a help wanted tag, so anyone is free to open a PR for this.
I think that we need to decide exactly what to change - just changing the text of the hint without changing the associated test will cause more problems
Is this designed just to discourage newbies like me? Over an hour on this step. No previously posted code nor clarifications helped... just sent me down new rabbit holes. You need to know code to decipher the clarifications. Must be part of a hazing process. THIS code works as of the date of this posting: <a href=""<img src="" alt="A cute orange cat lying on its back."</a (eliminate the space between the closing anchor "a" and the "" <h 1Now I know I am crazy enough to continue down this road/ rabbit hole universe</h 1(extra spaces for effect, LOL)
please use the freeCodeCamp forum if you have questions about your code or you get stuck. This content is hard, but there is no intentional 'hazing'.

Discussion:
assert(document.querySelectorAll('a').length >= 2); ``` <del> You should only add one opening anchor (`a`) tag. Please remove any extras. </del> <ins> You are missing a closing (`a`) tag after the image. </ins> ```js assert(document.querySelectorAll('a').length === 2);
Change:
Currently, the instructions in module happens to be as follows: The instructions tell the users that instead of setting the font size property to a number ( i.e. 72 ), they can optionally set the font size property to but don't inform the user that needs to be enclosed within quotes i.e. needs to be a string value. Furthermore, the word units in the second sentence should be changed to unit because in this particular case, we are just referring to a single unit i.e. . Considering this, I think the instructions of module should be reworded as follows: The instructions in module should be as follows: <img width="517" alt="image" src=""- Device: Laptop OS: macOS 13.0.1 Browser: Chrome Version: 107.0.5304.110
Hello there, I would like to contribute by fixing this issue,I wanted to ask whether I have to be assigned to this issue to contribute of I can start right away? Also, can you please guide me on where can i find that component to contribute? Thanks :)
Oh~ I see. I was so confused why 72px doesn't work. Good thing I found this issue. Thanks for posting
I'm not sure about this. The instructions explicitly mention that this is a JavaScript Object, which at this point in the curriculum is something that campers should be familiar with. I would be okay with something like:
Or maybe just update the literal value shown. Considering the part "or write it as" it should show the actual value to write.
Thanks for the feedback , ! I think having it as looks like a good solution to this issue. Thanks guys for the input. I'll go ahead and create a PR. Cheers!

Discussion:
Add a `style` attribute to the `div` in the code editor to give the text a color of red and font size of `72px`. <del> Note that you can optionally set the font size to be a number, omitting the units `px`, or write it as `72px`. </del> <ins> Note that you can optionally set the font size to be a number, omitting the units `px`, or write it as `"72px"`. </ins> # --hints-- The component should render a `div` element.
Change:
Some steps are placing unnecessary horizontal scrollbars on plain text content. The content is being treated as a code example and thus is not line wrapping normally. Also, the content is coded as one continuous line with no newlines, thus causing a very long horizontal scroll and making it more difficult to copy. There are exceptions for having horizontal scrollbars in WCAG, but those exceptions are for content "which require two-dimensional layout for usage or meaning" (). Actual code examples can fall under this exception, but I think it would be much harder to argue that pure text content like this "requires" that it not line wrap normally in order to be understood. There are several instances of this in the CSS Magazine course: Steps 11, 12, 13, 15, 16, 17. These are the ones I know of. N/A Present this non-code content on the page in a way that it is allowed to line wrap normally. I am able to do this by removing from the element. I'm noticing we are using to code this in the challenge files: markup Soon the freeCodeCamp curriculum will be 100% project-driven learning... This causes the element to have the class . If we are only using for these types of non-code examples then perhaps we can use that class to remove the property. No response N/A No response
Hello can I work on this issue

Discussion:
text-shadow: none !important; } <ins> /* remove horizontal scrollbars for text-only code */ code[class='language-markup'] { white-space: normal !important; } </ins> /* a11y color adjustments */ :not(.dark-palette) .token.comment, :not(.dark-palette) .token.prolog,
Change:
Currently, the second paragraph in module, happens to be as follows: The first line of the second paragraph seems to be a bit incomplete. Considering that, I believe the first line of the second paragraph should be as follows: The first line of the second paragraph of module, should be as follows: <img width="513" alt="image" src=""- Device: Laptop OS: macOS 13.0.1 Browser: Chrome Version: 107.0.5304.110
This issue is still open?

Discussion:
`dispatch` method is what you use to dispatch actions to the Redux store. Calling `store.dispatch()` and passing the value returned from an action creator sends an action back to the store. <del> Recall that action creators return an object with a type property that specifies the action that has occurred. Then the method dispatches an action object to the Redux store. Based on the previous challenge's example, the following lines are equivalent, and both dispatch the action of type `LOGIN`: </del> <ins> Recall that action creators return an object with a type property that specifies the type of action that has occurred. Then the method dispatches an action object to the Redux store. Based on the previous challenge's example, the following lines are equivalent, and both dispatch the action of type `LOGIN`: </ins> ```js store.dispatch(actionCreator());
Change:
Currently, the instructions in module, mention about subsection, which is a subsection of a completely different course ( i.e. course ). At the moment, those instructions in module, only mention the name of the "Managing Packages with NPM" subsection and no link has been provided to that particular subsection. Keeping that in mind, I believe to make it easier for the user to navigate to the subsection from within the instructions of module, a link to the subsection should be provided within the module. Hence, taking the above point into consideration, I believe the last line in the first paragraph of module, should be changed from: To The last line in the first paragraph of module, should be changed to: <img width="1440" alt="image" src=""
can i can solve the above issue?
Hello! can I solve this bug.
Personally, I would entirely remove that sentence. It is not common to maintain the links across the challenges, and it does not really provide useful information, as Campers are not expected to go directly to the npm section. On top of that, I would remove the mention of in all sentences - npm != React; there is nothing special about import statements, and there is no direct link between npm and import statements.
Thanks for the feedback your comment makes a lot of sense. Taking your suggestion into consideration, what do you think about the following:
Hello, can I resolve this issue?
Iooks decent. I would leave in the bit about:
Thanks for the confirmation ! I will go ahead and create a PR then. Cheers!

Discussion:
# --description-- <del> Congratulations! You finished the lessons on React and Redux. There's one last item worth pointing out before you move on. Typically, you won't write React apps in a code editor like this. This challenge gives you a glimpse of what the syntax looks like if you're working with npm and a file system on your own machine. The code should look similar, except for the use of `import` statements (these pull in all of the dependencies that have been provided for you in the challenges). The "Managing Packages with npm" section covers npm in more detail. </del> <ins> Congratulations! You finished the lessons on React and Redux. There's one last item worth pointing out before you move on. Typically, you won't write React apps in a code editor like this. This challenge gives you a glimpse of what the syntax looks like if you're working with a file system on your own machine. The code should look similar, except for the use of `import` statements (these pull in all of the dependencies that have been provided for you in the challenges). </ins> Finally, writing React and Redux code generally requires some configuration. This can get complicated quickly. If you are interested in experimenting on your own machine, the <a href="https://www.freecodecamp.org/news/install-react-with-create-react-app/" target="_blank" rel="noopener noreferrer nofollow">Create React App</a> comes configured and ready to go.
Change:
Unnecessary borders are displayed around each line in the solution code of certification projects. For example: to someone's certification page on 'View' ('View Code') to see the solution code Each line in the solution code should not have borders around it ! Device: Laptop OS: Windows 10 Browser: Chrome Version: 114.0.5735.199 (Official Build) (64-bit) The border seems to be in
Hi the borders on the code doesnt seem to be a good UX. I would like to take up this issue.
Hello! I would like to work on this issue. Seems to be a quick fix.
Hey. Contributions are very welcome. Please take a look at to get started.
! Would this sample look better ?
I have fixed the issue and created a pull request . Please review it and let me know if there are any concerns.
To solve the issue move the properties in , to CSS selector that affects the challenges' layout, or doesn't affect the setting layout.
Simply removing the border property in fixes the issue ! ! Is it fine if done this way? I have reverted the changes I made to the bootstrap file back to its original form.
How can we find those code files from the repo ? If the particular link to the file is not provided in the issue.
Hello I would like to request to be assigned to fix this
Hi! I would like to take up this issue

Discussion:
border-color: var(--tertiary-color); } code { <del> border: 1px solid var(--secondary-color); </del> padding: 1px 4px; background-color: var(--quaternary-background); color: var(--tertiary-color);

overflow-wrap: anywhere; } <ins> :not(pre) > code { border: 1px solid var(--secondary-color); } </ins> .challenge-instructions code { white-space: break-spaces; }

code[class*='language-'], pre[class*='language-'] { border-radius: 0; <del> border: none; </del> } pre {