jiebi/CodeConvo huggingface dataset:
Change:
All your code for these lessons goes in the `myApp.js` file between the lines of code we have started you off with. Do not change or delete the code we have added for you. <del> Install Helmet version `3.21.3`, then require it. </del> <ins> Install Helmet version `3.21.3`, then require it. You can install a specific version of a package with `npm install --save-exact package@version`, or by adding it to your `package.json` directly. </ins> # --hints--

Discussion:
Challenge: this challenge need instructions on how to actually install the specified version? On if you search for a package it will just give you the latest version. you run it will add the package with the caret in front of the version number but the test does not allow for that. Should the test allow for the caret?
If changing the tests to allow does not cause any of the versioning issues mentioned previously, then we should go with that. Otherwise, we could add a note that the camper should use :
Just bringing this back up: Are we changing the tests, or changing the instructions to be explicit about the versioning?
Personally, I'd say both. Show the npm command for how to install a specific package version and make the test ignore/accept the caret.
I like that. This kind of lesson is so short, I also think it would be useful to add the information about . I am going to open this up for general help
Hi, I do exactly like npm install --save-exact helmet and helmet = require('helmet'); but still not pass the challenge, anyone, please help me, thanks
Hey , Without seeing your code, or being able to test your project, it will be difficult to assist. Please make use of the to open a topic, and provide as much detail as possible. It will be easier to assist that way.
my code: var express = require('express'); var app = express(); const helmet = require('helmet'); { "name": "fcc-infosec-challenges", "version": "0.0.1", "description": "fcc backend boilerplate", "main": "", "scripts": { "start": "node " }, "dependencies": { "express": "^4.14.0", "helmet": "3.21.3" }, "keywords": [ "node", "hyperdev", "express", "freecodecamp" ], "license": "MIT" } and the test result: // running tests helmet version 3.21.3 should be in // tests completed Please help me to solve this. thanks
As mentioned, please use for questions that involve debugging challenge or project solutions. Thank you.
Change:
return "Yes"; ``` <del> will return `Yes` only if `num` is between `5` and `10` (5 and 10 included). The same logic can be written as: </del> <ins> This code will return `Yes` if `num` is between `5` and `10` (`5` and `10` included). The same logic can be written with the <dfn>logical or</dfn> operator. </ins> ```js if (num > 10 || num < 5) {

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-- <del> When the user has a calorie deficit, the `remainingCalories` value will be negative. You don't want to display a negative number in the result string. </del> <ins> When the user has a calorie surplus, the `remainingCalories` value will be negative. You don't want to display a negative number in the result string. </ins> `Math.abs()` is a built-in JavaScript method that will return the absolute value of a number.

Discussion:
Problem: Simple content description error. It says in the challenge description that when the user has a calorie deficit, the remainingCalories will be a negative (less than 0). It is actually the opposite. For example, if I were to input this in the form: The description of the step must say that it will be a negative value if the input is a surplus (above budget). ! 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
This has been opened 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 Happy coding
Change:
```yml tests: <ins> - text: The <code>quickCheck</code> function should return a boolean (<code>true</code> or <code>false</code>), not a string (<code>"true"</code> or <code>"false"</code>) testString: assert.isBoolean(quickCheck(['squash', 'onions', 'shallots'], 'mushrooms')); </ins> - text: <code>quickCheck(["squash", "onions", "shallots"], "mushrooms")</code> should return <code>false</code> testString: assert.strictEqual(quickCheck(['squash', 'onions', 'shallots'], 'mushrooms'), false); - text: <code>quickCheck(["onions", "squash", "shallots"], "onions")</code> should return <code>true</code>

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: The tests call for the function to return or . I ran into a user on the forums that was failing to get the tests to pass because they were returning and as strings, rather than boolean values. I wonder if the instructions should be made a little more specific to clarify that the function needs to return boolean values. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: Version 83.0.4103.61 Operating System: Windows 10 Home v 1909 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !
Whilst I can understand the confusion, the general adopted format has been: What is within the code tags is exactly what needs to be returned In other exercises, if the user is asked to return a string, it should be I say should be, because I just encountered another exercise where the test string was not following this format, but it is likely to be fixed.
That format makes complete sense to me. The only reason I bring this up is that I know learning to code can be a frustrating experience for some, and an opportunity to eliminate potential confusion and alleviate some of the self-generated stress seems like a good move.
How about catching this with a test?
I like that idea. It provides a little extra clarity on why the test is failing for the user's code.
Change:
"descriptionEs": [ "Seguramente habrás entendido porque los atributos id son tan convenientes para elegir con selectores jQuery. Pero no siempre contarás con estos agradables identificadores para trabajar. ", "Afortunadamente, jQuery tiene algunos otros trucos para elegir los elementos adecuados.", <del> "jQuery usa selectores CSS para elegir elementos, El selector CSS <code>.clase:nth-child(i)</code> le permite seleccionar de los elementos con la clase dada, los que sean los i-ésimos hijos de su elemento padre. En lugar de una clase también puede usarse un elemento", </del> <ins> "jQuery usa selectores CSS para elegir elementos, El selector CSS <code>.clase:nth-child(i)</code> te permite seleccionar de los elementos con la clase dada, los que sean los i-ésimos hijos de su elemento padre. En lugar de una clase también puedes usar un elemento", </ins> "He aquí cómo le asignarás la clase <code>bounce</code> al tercer elemento de cada pozo:", "<code>$(".target:nth-child(3)").addClass("animated bounce");</code>", <del> "Haz que rebote el segundo hijo de cada uno de los elementos de tus pozos. Debes elegir los hijos con la clase <code>target</code>." </del> <ins> "Haz que rebote el segundo hijo de cada uno de los elementos de tus pozos. Debes elegir los hijos de elementos con clase <code>target</code>." </ins> ] }, {

Discussion:
[x] Learn how Script Tags and Document Ready Work [x] Target HTML Elements with Selectors Using jQuery [x] Target Elements by Class Using jQuery [x] Target Elements by ID Using jQuery [x] Delete your jQuery Functions [x] Target the same element with multiple jQuery Selectors [x] Remove Classes from an element with jQuery [x] Change the CSS of an Element Using jQuery [x] Disable an Element Using jQuery [x] Change Text Inside an Element Using jQuery [x] Remove an Element Using jQuery [x] Use appendTo to Move Elements with jQuery [x] Clone an Element Using jQuery [x] Target the Parent of an Element Using jQuery [x] Target the Children of an Element Using jQuery [x] Target a Specific Child of an Element Using jQuery [x] Target Even Numbered Elements Using jQuery [x] Use jQuery to Modify the Entire Page
Checking
Change:
.map-challenge-title { margin-bottom: 0.25rem; <del> max-width: 28rem; </del> <ins> max-width: calc(100% - 80px); </ins> } .block a {

Discussion:
Describe the bug Some challenge titles on the map wrap to a new line while the parent width is big enough for them to display on a single line. <img width="818" alt="Screen Shot 2019-08-23 at 8 42 26 PM" src="https://user-"I think it's due to the rule applied to the tags.
The reason for this is because the element has a class which has !
I think that can be removed. I don't see any reason to keep it.
Yeah we can remove the rule as long as we make sure that the removal doesn't affect anything else. Feel free to make a PR for this
I think it might be nice if the effective left and right margins of the titles were the same. Currently, because they're (roughly) what happens is the left margin is larger, because each has its elements indented slightly by . Try and see what you think. Obviously it's a bit of a compromise (a few more titles will wrap), but I think that'll look better.
Change:
You should use `console.log()` to print out the result of `inputValues`. Write the code for this inside the `sortInputArray` function. <del> To see the result for the `inputValues` array, log out the `inputValues` array to the console. Then click on the sort button and open up the console. You should see an array of strings like this: </del> <ins> To see the logged `inputValues` array, click on the sort button and open up the console. You should see an array of strings like this: </ins> ```js [ '8', '2', '4', '1', '3' ]

Discussion:
The second paragraph of step 8 in the Number Sorter project is awkwardly phrased. The instructions begin as follows: You should use () to print out the result of inputValues. Write the code for this inside the sortInputArray function. To see the result for the inputValues array, log out the inputValues array to the console. Then click on the sort button and open up the console. You should see an array of strings like this: The second paragraph should really say: To see the logged inputValues array, click on the sort button and open up the console. You should see an array of strings like this: It's clearer than the original text. The 1st and 2nd paragraphs together can flow better together as well since the first paragraph just told us to log the inputValues array (so saying again 'log out the inputValues array' sounds wrong). N/A rewrite the 2nd paragraph with clearer text. No response N/A No response
I can work on this issue.
I will open this up as it sounds like a reasonable change. Please make sure you have read the . When an issue has the label, it is not yet ready for a PR. It must be triaged first.
Change:
challengeType?: number; completedDate: number; challengeFiles: ChallengeFileType[] | null; <ins> // TODO: remove once files->challengeFiles is refactored files?: ChallengeFileType[] | null; </ins> }; // TODO: renames: files => challengeFiles; key => fileKey; #42489 export type ChallengeFileType =

Discussion:
When trying to view a JS solution, the following error appears in dev, explaining the issue in production. It seems we followed the expected prop-types too early (ref: ). The object is still an object literal. Reported on forum:
I have the same problem as I said in the forum, the bottom error says it responded with 404 to the request for the certification on JS algorithms and data structures. Seems like there's an issue with the backend reaching that certification. !
Change:
"Largest int from concatenated ints" ], [ <del> "5a23c84252665b21eecc7edd", </del> <ins> "5e4ce2b6ac708cc68c1df25e", </ins> "Last letter-first letter" ], [

Discussion:
<img width="428" alt="Screen Shot 2020-03-26 at 8 07 49 PM" src="https://user-"The rosetta code challenges are all in alphabetical order except those first few. I did some digging and found that regenerated some mongo ID's for the challenge files. But it looks like those ID's we're never updated to match in the . I'm assuming that's the problem. And strangely I can't find them when I search my local DB - This may cause some issues if someone tries to submit one of these - not sure. Edit: that first link is actually to a commit and not a PR - with that commit Seems like there should be a test for this.
Change:
"<span class='text-info'>Bonus User Story:</span> As a user, I can see an icon depending on the temperature..", "<span class='text-info'>Bonus User Story:</span> As a user, I see a different background image depending on the temperature (e.g. snowy mountain, hot desert).", "<span class='text-info'>Bonus User Story:</span> As a user, I can push a button to toggle between Fahrenheit and Celsius.", <del> "Remember to use <a href='/field-guide/how-do-i-get-help-when-I-get-stuck' target='_blank'>RSAP</a> if you get stuck. Try using <a href='http://api.jquery.com/jquery.each/'>jQuery's $.getJSON()</a> to consume APIs.", </del> <ins> "Remember to use <a href='/field-guide/how-do-i-get-help-when-I-get-stuck' target='_blank'>RSAP</a> if you get stuck. Try using <a href='http://api.jquery.com/jquery.getjson/'>jQuery's $.getJSON()</a> to consume APIs.", </ins> "When you are finished, click the "I've completed this challenge" button and include a link to your CodePen. If you pair programmed, you should also include the Free Code Camp username of your pair.", "If you'd like immediate feedback on your project, click this button and paste in a link to your CodePen project. Otherwise, we'll review it before you start your nonprofit projects.<br><br><a class='btn btn-primary btn-block' href='https://twitter.com/intent/tweet?text=Check%20out%20the%20project%20I%20just%20built%20with%20%40FreeCodeCamp:%20%0A%20%23LearnToCode%20%23JavaScript' target='_blank'>Click here then add your link to your tweet's text</a>" ],

Discussion:
Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. Step : "Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON() to consume APIs." incorrectly to this url: It should link to: Unless that misdirection is meant to be tricky for the student ;)
This is a duplicate of
Kind of. This one is referring to a different page (challenge/zipline), but I did notice that all of the Ziplines have the same bug.
This was fixed ages ago, right? Please close.
This isn't actually fixed. The erroneous link still exists in these ziplines: Maybe it's not an issue because we'll be switching over to the content at soon? But I thought you should know that the issue hasn't actually been fixed yet. Actually, the only reason that it isn't an issue on the beta site is that none of the ziplines seem to link directly to the jquery json page.
This was fixed in prior to the branch being available through Now they seem to have changed how the ziplines look, so it wouldn't be an issue regardless. Since all changes seem to happen on the branch before ending up in production, issues that are fixed in should probably be considered fixed, even though it might be better to merge small fixes like this into production at a quicker rate than what is the current reality.
Thanks for the explanation! That makes sense. I'm not privy to staging, so I didn't realize it had been fixed there.
Change:
--- id: 56bbb991ad1ed5201cd392cd <del> title: Manipulate Arrays With shift() </del> <ins> title: Manipulate Arrays With shift Method </ins> challengeType: 1 videoUrl: 'https://scrimba.com/c/cRbVETW' forumTopicId: 18238

Discussion:
Describe the bug Having special character in the slug, title, or heading of the challenges lead to broken structure as shown in the image below. Originally reported by ! These challenges are the translation of these. ! Although we can not add them in the Arabic translation, this is a fix to the side effect, because Arabic isn't the only RTL language with translation efforts. I think it's better to not include special characters in the heading, if they aren't wrapped in spaced, example 'the Logical And Operator &&'. So I suggest two solutions: Delete special character, if they aren't wrapped around spaces, like change "push()" to "push". Add code block around functions and methods, to be something like .
Would it be acceptable to spell these out a little more? Instead of We could do Not only do we get rid of the special characters but it possibly makes it a little clearer for people listening to the page.
In translation, that's perfectly fine . Good call.
Change:
const propTypes = { children: PropTypes.any, external: PropTypes.bool, <ins> sameTab: PropTypes.bool, </ins> to: PropTypes.string.isRequired }; <del> const Link = ({ children, to, external, ...other }) => { </del> <ins> const Link = ({ children, to, external, sameTab, ...other }) => { </ins> if (!external && /^/(?!/)/.test(to)) { return ( <GatsbyLink to={to} {...other}> {children} </GatsbyLink> ); <ins> } else if (sameTab && external) { return ( <a href={to} {...other}> {children} </a> ); </ins> } return (

Discussion:
The top nav items on the forum and news does not open in a new tab. We would like the same functionality on learn for consistency.
Do we want all external links to navigate without opening a tab? A quick search suggests that all the links in the footer open new tabs, as do a couple in . I think it's better UX to leave tab opening to the user, but I thought I'd check.
If you decide to go ahead with this, I'd like to have a go at this
I think we want this to remain as is except for the navigation links up top on the navbar, which are the most used links on the platform. This is to make it consistent with the behaviour on forum and news. can you proceed and make the changes. This will likely affect some of the routing. I would like to test this before working on the client app for chinese curriculum.
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 sprite = document.getElementById('sprite'); assert.isTrue(sprite.src.endsWith('sprites/pokemon/25.png'));

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:
# --description-- <del> To elaborate a question using `there is` you just need to change the order of the verb to be, like so: </del> <ins> To elaborate a question using `there is` you just need to change the order of the verb `to be`, like so: </ins> `There is an ATM nearby` -> `Is there an ATM nearby?`

Discussion:
needs to be wrapped in backticks ( ``) in the first sentence needs to be wrapped in backticks. Here also needs to be wrapped in backticks. 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 the 3 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.
Change:
export const challengeMetaSelector = state => state[ns].challengeMeta; export const challengeTestsSelector = state => state[ns].challengeTests; export const consoleOutputSelector = state => state[ns].consoleOut; <ins> export const isChallengeCompletedSelector = state => { const completedChallenges = completedChallengesSelector(state); const { id: currentChallengeId } = challengeMetaSelector(state); return completedChallenges.some(({ id }) => id === currentChallengeId); }; </ins> export const isCodeLockedSelector = state => state[ns].isCodeLocked; export const isCompletionModalOpenSelector = state => state[ns].modal.completion;

Discussion:
In the new beta (currently at ), it would be great if a challenge page indicated somehow when the challenge has already been completed. Currently, since user inputed code is not saved, there is no indication on a challenge page that it has already been completed.
We need a check mark in the title or a badge or to indicate the same?
The most elegant thing I can think of to have something like the little circular check mark next to the title like how it is on the learn homepage - only if it's been solved, and don't show anything if it hasn't.
That would be a nice way to handle it. Please go forth if you are interested in this?