jiebi/CodeConvo huggingface dataset:
Change:
```js assert( (function () { <del> const initialState = store.getState(); store.dispatch(incAction()); const incState = store.getState(); </del> <ins> const initialState = _store.getState(); _store.dispatch(incAction()); const incState = _store.getState(); </ins> return initialState + 1 === incState; })() );

Discussion:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --<!-- Add a link to the coding challenge with the problem. -- <!-- Copy and paste the code from the editor that you used in between the back-ticks below: --<!-- Add a clear and concise description of what you expected to happen. --This should be accepted as a correct answer, as it solves the challenge. <!-- Please complete the following information. --- Device: PC OS: Windows 10 Browser: Firefox Version: 97.0.1 <!-- Add any other context about the problem here. --The problem arises if the user tries to test their Redux store functionality After checking the source code of the challenge, the problem seems to be the method used to check if user initiated state correctly or not found in This is resulting in a false assert because the user has modified their state (with Tests) I don't know of a way to assert that the user initialized state other than the way mentioned above Maybe add a note that the user should remove their tests before checking their answer? Sorry if this was mentioned before, but I didn't find it so decided to open the issue.
Rather than adding note, more convenient might be creating new store during the test, off the , and checking initial state of that one.
I agree with gikf's suggestion here. We could create an section under and declare a which we could pass to the tests.
Change:
# --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";

Discussion:
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
Change:
# --description-- <del> Remember that arrays have a `.some()` method. Use the `.some()` method to check if testing your `msg` on any of your `denyList` regular expressions returns `true`. </del> <ins> 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()); ``` Use the `.some()` method to check if testing your `msg` on any of your `denyList` regular expressions returns `true`. </ins> Use `regex` as the parameter for the callback function, for clarity.

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:
timezone ) { let finalChallenge; <del> const updateData = { $push: {} }; </del> <ins> const updateData = {}; </ins> const { timezone: userTimezone, completedChallenges = [] } = user; const oldChallenge = _.find(

Discussion:
Completing projects from the settings page, submitting a url, dose not increment the points a user has. We need to push a new timestamp to the users array.
Hi I can help out with this. Am I correct in thinking that this should be done in the file? If so, I'll look at for some guidance.
Change:
```js const aVisitedColor = new __helpers.CSSHelp(document).getStyle('a:visited')?.getPropertyValue('color'); <del> assert(aVisitedColor === 'grey'); </del> <ins> assert(aVisitedColor === 'grey' || aVisitedColor === 'gray'); </ins> ``` # --seed--

Discussion:
I set the a:visited color to “gray” which changed the link color in the preview pane and even displayed the color picker box in the view with the color gray but when I clicked Check Your Code it didn’t accept my answer. I had to change it to “grey” with an ‘e’, not an ‘a’ to get the Step completed message. Now it does have the word “grey” with an ‘e’ in the directions, but I spell gray with an ‘a’ so that is what I did naturally. Do you want to accept a value of “gray” and “grey” as correct answers or will you only accept “grey”. If you only accept “grey” would it be possible to add a message asking the user to check their spelling? Otherwise, users may get frustrated and confused if they used “gray” and then they don’t understand why the answer is wrong. ! <!-- Please complete the following information. --- Device: [Laptop] OS: [Windows 10] Browser: [brave] Version: [Version 1.33.106 Chromium: 96.0.4664.110 (Official Build) (64-bit)] <!-- Add any other context about the problem here. --
Change:
<script src="https://unpkg.com/docsify-pagination/dist/docsify-pagination.min.js"></script> <script src="https://unpkg.com/docsify-remote-markdown/dist/docsify-remote-markdown.min.js"></script> <del> </html> </del>  No newline at end of file <ins> </html> </ins>

Discussion:
Is your feature request related to a problem? Please describe. I noticed that there is a difference between the headers in and . Describe the solution you'd like Everything else is consistent except for the header. A solution would be to have it consistent throughout. Have it display "Learn to code at home" in both links. On the second line. Additional context Add any other context or screenshots about the feature request here. <img width="1095" alt="without home" src="https://user-"<img width="1093" alt="with home" src="https://user-"
Change:
const { children, navigate, isSignedIn, ...restProps } = props; return ( <Button <ins> bsStyle='default' className={(restProps.block ? 'btn-cta-big' : '') + ' signup-btn btn-cta'} </ins> href='/signin' onClick={createOnClick(navigate, isSignedIn)} {...restProps} <del> bsStyle='default' className={(restProps.block ? 'btn-cta-big' : '') + ' signup-btn btn-cta'} </del> > {children || 'Sign In'} </Button>

Discussion:
I'm testing beta. Describe the bug When submitting a challenge using Ctrl+Enter it automatically completes also the following challenge. To Reproduce Steps to reproduce the behavior: a logged out user to the first challenge it Ctrl+Enter marks as solved also the following challenge and you can go ahead Expected behavior It should solve the current challenge and present the following one. Screenshots As you can see I can submit multiple challenges: ! Desktop (please complete the following information): OS: Ubuntu Browser Firefox Version 69.0.1 Additional context I've been able to reproduce it on but I could skip only one challenge. On my local dev I managed to skip 4.
I've digged a bit on this issue, and I think the problem is somehow related to this line: As this is triggered also when I'm submitting the finished challenge. If I comment that line out everything works fine, meaning I can Ctrl+Enter to run the tests and submit and the bug disappear. I'm going to dig a bit more, but does that makes any sense to you?
Thanks for testing our beta version and reporting this! You rock. /cc
Thanks It looks like I didn't test the logged out behaviour. so, what do we want to happen for logged out users? The issue I see is that it currently says 'Submit and go to the next challenge', but clearly they can't submit. For now, do we just want them to see the same as logged in users (and quietly not submit)?
Here is what I would do: ! Of course the modal should close as well like you mentioned. The signin button can link to same as the home page CTA. And we could remove from the first button
Turns out it's not working properly even when the user is logged in. I think it's a race condition between and . was quite right, the problem is on that line. It shouldn't be called if the modal is open since it's listening to as well.
yes I think it's with the in the editor and the in the . I can give a further look later if you wish.
Thanks for the offer but I think (with your help!) I've fixed it. It seemed only fair, since I introduced the bug.
Excellent!
Release on its way, should be available within the hour.
Change:
<strong>User Story #4:</strong> When I enter GitHub flavored markdown into the <code>#editor</code> element, the text is rendered as HTML in the <code>#preview</code> element as I type (HINT: You don't need to parse Markdown yourself - you can import the Marked library for this: <a href='https://cdnjs.com/libraries/marked' target='_blank'>https://cdnjs.com/libraries/marked</a>). <strong>User Story #5:</strong> When my markdown previewer first loads, the default text in the <code>#editor</code> field should contain valid markdown that represents at least one of each of the following elements: a header (H1 size), a sub header (H2 size), a link, inline code, a code block, a list item, a blockquote, an image, and bolded text. <strong>User Story #6:</strong> When my markdown previewer first loads, the default markdown in the <code>#editor</code> field should be rendered as HTML in the <code>#preview</code> element. <del> <strong>Optional Bonus (you do not need to make this test pass):</strong> When I click a link rendered by my markdown previewer, the link is opened up in a new tab (HINT: read the Marked.js docs for this one!). </del> <strong>Optional Bonus (you do not need to make this test pass):</strong> My markdown previewer interprets carriage returns and renders them as <code>br</code> (line break) elements. You can build your project by forking <a href='http://codepen.io/freeCodeCamp/pen/MJjpwO' target='_blank'>this CodePen pen</a>. Or you can use this CDN link to run the tests in any environment you like: <code>https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js</code> Once you're done, submit the URL to your working project with all its tests passing.

Discussion:
The Optional bonus User Story was removed from the testable suite because it is no longer relevant. The User Story should also be removed from the web page.
Fixed in
Change:
); ``` <ins> `insertionSort([5, 4, 33, 2, 8])` should return `[2, 4, 5, 8, 33]`. ```js assert.deepEqual(insertionSort([5, 4, 33, 2, 8]), [2, 4, 5, 8, 33]) ``` </ins> `insertionSort` should not use the built-in `.sort()` method. ```js

Discussion:
function insertionSort(array) { for(let i=1; i; i++){ let toInsert = array[i]; let j = i-1; while(j = 0){ if(toInsert &lt; array[j]){ array[j+1] = array[j]; } else{ array[j+1] = toInsert; break; } j-- } (array) } return array; } insertionSort([5, 4, 33, 2, 8]); Will make the challenge pass even though the code is not correct which my example shows. The test in the challenge passes, because by chance the first element in the test array is also the smallest and doesnt have to be changed. So adding a second test array with a first element not being the smallest element would solve that issue. Browser: Chrome
I am able to confirm this bug.
Would either of you like to add the necessary test?
I will defer to for the opportunity to make a contribution. If they do not want to make this change, then I can go ahead and do so.
Change:
module.exports = Object.assign(locations, { locale, stripePublicKey, <del> algoliaAppId, algoliaAPIKey </del> <ins> algoliaAppId: !algoliaAppId || algoliaAppId === 'Algolia app id from dashboard' ? null : algoliaAppId, algoliaAPIKey: !algoliaAPIKey || algoliaAPIKey === 'Algolia api key from dashboard' ? null : algoliaAPIKey </ins> });

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:
data-cy='submit-challenge' onClick={() => submitChallenge()} > <del> {isSignedIn ? t('buttons.submit-and-go') : t('buttons.go-to-next')} <span className='hidden-xs'> {isMacOS ? ' (Command + Enter)' : ' (Ctrl + Enter)'} </span> </del> <ins> {buttonText} </ins> </Button> <Spacer size='xxSmall' /> {this.state.downloadURL ? (

Discussion:
We are using the class to conditionally hide some text on mobile screens: This class comes from Bootstrap, which is something we are going to remove (). So instead of using the class, we can use an check, like this (which is also a little more consistent with how we've handled this kind of conditional rendering): Update the file to replace the class with an check. I noticed that we are using multiple methods for mobile device detection, so I think the check should be standardized, and there should be a shared util for this check. But I'm leaving this out of the scope of this issue, and will create a separate issue for it.
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.
I already have a pull request that technically resolves this. While it is done the same way we did the lower-jaw i.e checks for a desktop instead of being mobile , it does solve the problem and pass the tests.
Change:
When the user clicks on the `Show rules` button, the rules for the game should display on the screen. When they click on the button again, the rules should be hidden. <del> Use an event listener to invert the value of the `isModalShowing` variable, toggle the visibility of the `rulesContainer`, and change the text of the `rulesBtn` to `Show Rules` or `Hide Rules`. </del> <ins> Use an event listener to invert the value of the `isModalShowing` variable, toggle the visibility of the `rulesContainer`, and change the text of the `rulesBtn` to `Show rules` or `Hide rules`. </ins> # --hints--

Discussion:
Initial text of the button is . After step clicking button is expected to change text to , capitalizing the second word. Clicking it again is expected to change text to . Which is too differing from initial capitalization. n/a Capitalization should be consistent throughout the project. Either Show rules and Hide rules; or Show Rules and Hide Rules. No response n/a No response
We will do this option
Change:
return "No"; ``` <del> will only return `Yes` if `num` is greater than `5` and less than `10`. The same logic can be written as: </del> <ins> This code will return `Yes` if `num` is greater than `5` and less than `10`. The same logic can be written with the <dfn>logical and</dfn> operator. </ins> ```js if (num > 5 && num < 10) {

Discussion:
Similar to issue Please also update another step that has the same issue and should get a similar fix: The sentence: "will only return Yes if num is greater than 5 and less than 10. The same logic can be written as:" should be changed to: "This will only..." (adding This is enough to fix it as a reference to the previous code block) And similarly for this step as well: Multiple As described above No response N/A No response
Proposed change: Question - do we use or for string literals?
"yes" i think
Please assign this issue to me i think can fix this and make my first contribution to open source
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.
I have created a pull request, what should i do next ?(It's my first contribution, don't mind my stupid questions please)
Change:
## Description <section id='description'> <strong>Objective:</strong> Build a full stack JavaScript app that is functionally similar to this: <a href='https://fcc-voting-arthow4n.herokuapp.com/' target='_blank'>https://fcc-voting-arthow4n.herokuapp.com/</a> and deploy it to Heroku. <del> Note that for each project, you should create a new GitHub repository and a new Heroku project. If you can't remember how to do this, revisit <a href='/challenges/get-set-for-our-dynamic-web-application-projects'>https://freecodecamp.com/challenges/get-set-for-our-dynamic-web-application-projects</a>. </del> Here are the specific user stories you should implement for this project: <strong>User Story:</strong> As an authenticated user, I can keep my polls and come back later to access them. <strong>User Story:</strong> As an authenticated user, I can share my polls with my friends.

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: In some of the take home projects there is a broken link in the description - - which leads to a 404. Add a Link to the page with the problem:
Here is a breakup of the action items (can be done in parallel, by multiple contributors): . we were hoping you could point us in the right direction by helping us with the source code repo link? [ ] This Glitch project can then be published and the challenge updated with the link and the verbiage. [ ] Finally we would also need to point the link for getting started use our standard intro for other projects.
if I have the original challenge link I could start on this.
I would like to work on this .
please let me know if you are still interested in making a pull request for this issue.
Please inform on the status of the work on this issue, otherwise I would like to have a go at it.
I would like to know the status. Do we have the correct link available or not?
What is the original challenge link which attempts to link to?
please let me know once the actual link is confirmed. I would like to work on this issue.
I'm not sure where the original link is. I thought it was in Apis And Microservices in the legacy site, but I can't find it. We may have to re-create this page? It is supposed to let users know how to create a repository and deploy to heroku. For some of these apps, users can also just use glitch.
It has to be somewhere in the history on Github. When using Git, it is not possible to lose content.
I'm not sure the very latest instance of the file, but it's the best I could find. If there's a way to find the latest version, I'd love to know how! Regardless, you might be able to get some inspiration from there, but unfortunately the specifics are all out of date.
That link is in four of the take home project descriptions - I didn't see it anywhere else. Maybe we should just remove that line from them... Note that for each project, you should create a new GitHub repository and a new Heroku project. If you can't remember how to do this, revisit
Yes please.
Change:
], "tests": [ "assert.deepEqual(friendly(['2015-07-01', '2015-07-04']), ['July 1st','4th'], 'ending month should be omitted since it is already mentioned');", <del> "assert.deepEqual(friendly(['2015-12-01', '2016-02-03']), ['December 1st','February 3rd'], 'one month apart can be inferred it is the next year');", </del> <ins> "assert.deepEqual(friendly(['2015-12-01', '2016-02-03']), ['December 1st','February 3rd'], 'two months apart can be inferred if it is the next year');", </ins> "assert.deepEqual(friendly(['2015-12-01', '2017-02-03']), ['December 1st, 2015','February 3rd, 2017']);", "assert.deepEqual(friendly(['2016-03-01', '2016-05-05']), ['March 1st','May 5th, 2016']);", "assert.deepEqual(friendly(['2017-01-01', '2017-01-01']), ['January 1st, 2017'], 'since we do not duplicate only return once');",

Discussion:
Challenge has an issue. December 1st to February 3rd is two months not one month. The test is pretty wordy regardless. !
I believe it needs to be used in numbers not the name of the month. Sent from my iPhone
The numbers and everything in the test are right, it's just the message. The output for is .
Oh because nothing is one month apart look the number format for the year one is 2015 and one is 2016. Sent from my iPhone
This is not a problem with the logic of the test or based on my input – it's just a typo. Yes the years are different but the two dates are only two months apart, therefore the year of the second argument doesn't need to be outputted because it can be inferred. The test should say something along the lines of, "two months apart can be inferred, even if it is the next year".
Closing as fixed in