{"_id":"q-en-freeCodeCamp-510409e65afd23db2023e0d793687c58d2348302aae33e5af881a8e4545e91db","text":"This isn't exactly a bug, but in the description for the challenge, there is an image that shows how bootstrap lays out elements on a page. This image is way too small to see or read any of the text in the image, and there doesn't seem to be a good way to get a larger version of the image.\nThanks, we've updated the copy to have the image link to the specific section of the bootstrap website!"}
{"_id":"q-en-freeCodeCamp-e3b6da71b738431f56c5e153a472f27b4b15d25d0cfae7f878b6878428a75bd8","text":"Challenge has an issue. It seems that it's more appropritae to show helpful links to: () () instead of: () () Am I right?"}
{"_id":"q-en-freeCodeCamp-1ae6eba9d43a90c468c54b0adf7460baadb9538d5674e7db65c52c459901ee0b","text":"Challenge has an issue. Waypoint requires you to have a 10px border around the img element, but you can pass by with a 5px border. Steps to reproduce: 1) Paste into your code, inside your style tag. 2) Add to your img tag classes 3) Change your to and to inside your style tag. Then the Waypoint allows you to the next challenge even if you don't change your border-width to 10px; !\nLooking at the code, it seems that there's not a test for . Also, property is tested with a RegExp and it yields true if the word 'solid' is written in any place in the editor, it might be better to check it with JQuery's .css function, as in the test for which, by the way, looks for"}
{"_id":"q-en-freeCodeCamp-b4d5dce4ea7dd180d4ee9c9a31de9f8c73118dc4aaafd01a59553dbfa63c905c","text":"Challenge has an issue. December 1st to February 3rd is two months not one month. The test is pretty wordy regardless. !\nI believe it needs to be used in numbers not the name of the month. Sent from my iPhone\nThe numbers and everything in the test are right, it's just the message. The output for is .\nOh because nothing is one month apart look the number format for the year one is 2015 and one is 2016. Sent from my iPhone\nThis 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\".\nClosing as fixed in"}
{"_id":"q-en-freeCodeCamp-62249d204327cfb40994e2a3d3b06a6465d28816182ffefbc2eb70afbb9ac9ea","text":"Challenge has an issue. in JavaScript we can can work with decimal numbers <--- needs full stop.\nmerged to"}
{"_id":"q-en-freeCodeCamp-6e04504e91ab6bac1ecb6baed214c6c157c5c9db7c147c10b8b50b0f9f97337a","text":"Challenge has an issue. ! The last sentence should read Create and call a function called that returns the sum of and ."}
{"_id":"q-en-freeCodeCamp-b20dedd4cb9cd40e4d105a46740fd96c62746e2ee6e6ea40b9e26fc220d11b39","text":"Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. The last line in code is: but for output box to work should be: ( replaced by )\nCreated PR"}
{"_id":"q-en-freeCodeCamp-1520b8ecbf7409f4c0b058a864e38bde3a00fe9f880fe8365832f7a883b65153","text":"Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. Code \"assert(editor.getValue().match(/(//)...../g),\" appears on the left hand checklist. After completing the challenge and running the code, section completion pop-up appears, and if you try to move on to the next section, the section completion pop-up will continuously appear instead of moving on to the next section. Multi-line comments such as this do not pass the test: / hello / <img width=\"1440\" alt=\"screen shot 2015-08-18 at 8 50 03 pm\" src=\"\"\nDear camper, your issue is a duplicate and already fixed: Please see ."}
{"_id":"q-en-freeCodeCamp-e4f3b0b857b2b2d38d18e9182c8e37dc72aee1b8f2a28aa037f6832493c742b5","text":"Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. First line of the challenge has a typo where the word \"use\" comes twice: You can use use spans to create inline elements.\nI have created a pull request that should close this issue. I can't merge it in myself though so we will have to wait until someone with write access to this repository can approve the pull request. Then this issue will be fixed in staging."}
{"_id":"q-en-freeCodeCamp-f4e6799b251988ed729ad8cb9b2b6cc8f66ea0d34237570ab0a66cfa7261d9d9","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.99 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nClosing. Please feel free to re-open with steps and a description on how to reproduce the issue. Happy Coding!"}
{"_id":"q-en-freeCodeCamp-ad8378882f4452e4a5460fe1fab0ff1044406f3082f5153f99b7dece4ed3a74f","text":"Assignment: Let's remove all the values greater than five Assert: You should have removed all the values from the array that are greater than 4. problem arises if user includes 5 in result set"}
{"_id":"q-en-freeCodeCamp-773618e5fb751570c28093293404f80e165427bf30ea73312316ceeb518de5e1","text":"I think \"Each id should be unique to a specific element.\" would be less ambiguous (and more accurate) as \"Each id must be unique on the page.\""}
{"_id":"q-en-freeCodeCamp-87c0cf81cc35d72223733ab87a5ed893cbbcf11b26baff398eacd989563d3eaa","text":"when I finish all challenges, the flash info is Once you have completed all of our challenges, you should join our&lt;a target=\"\"_blank\"\" href=\"\"\"\"Half Way Club&lt;/aand start getting ready for our nonprofit projects.a element will not open HalfWayClub of gitter I'm using firefox 41.0.1 on windows, I think there is something wrong with"}
{"_id":"q-en-freeCodeCamp-86ce6bf6789827c2e71957ad0933ae178575f9e7f6b407808c346514a2ec655c","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. Step 13 should have the \"Q\" capitalized in jQuery. !"}
{"_id":"q-en-freeCodeCamp-a8618945d00a44421a2a382c538d6c7ea7139b86bc538678cf083517711aa3ef","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: The example code should have valid Javascript code but the semicolon at the end is missing. !\n(Sorry, used the wrong branch at first.)"}
{"_id":"q-en-freeCodeCamp-a208cbb024b54c3572fc19ec061d2e7f932cdae90d6cb6a2f8c6a7ac92b43caa","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. The word refered should be written with 2 Rs: referred. !"}
{"_id":"q-en-freeCodeCamp-83eca547f0d3e69a54239f5587b79bf7d0e0b7d58021b5936a170fa0b324dc7e","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: Usually, paragraphs are separated with an empty line but here it is not. Currently, both paragraphs are in one string with a separating the two paragraphs. For this challenge in the file, the second paragraph should be on its own string so the spacing is consistent with all the other challenges. !\nSame goes for this challenge as well:\nHumm, don't know why I did that. Yes, these need a proper line break.\nIs this how you fork? This is my first time.\nI would consult the . It's got a lot of helpful information. The things I can see that need to be changed are: the branch name (it needs to be in the form of so like would be good) and also the issue number should not be in the commit title. It should be in the commit body and say something like . Here's more information about ."}
{"_id":"q-en-freeCodeCamp-48273a10ef403be661ec72df8437346e7b295b44109d7be0ab5acf26dcec5044","text":"[ ] Use Responsive Design with Bootstrap Fluid Containers [ ] Make Images Mobile Responsive [ ] Center Text with Bootstrap [ ] Create a Bootstrap Button [ ] Create a Block Element Bootstrap Button [ ] Taste the Bootstrap Button Color Rainbow [ ] Call out Optional Actions with Button Info [ ] Warn your Users of a Dangerous Action [ ] Use the Bootstrap Grid to Put Elements Side By Side [ ] Ditch Custom CSS for Bootstrap [ ] Use Spans for Inline Elements [ ] Create a Custom Heading [ ] Add Font Awesome Icons to our Buttons [ ] Add Font Awesome Icons to all of our Buttons [ ] Responsively Style Radio Buttons [ ] Responsively Style Checkboxes [ ] Style Text Inputs as Form Controls [ ] Line up Form Elements Responsively with Bootstrap [ ] Create a Bootstrap Headline [ ] House our page within a Bootstrap Container Fluid Div [ ] Create a Bootstrap Row [ ] Split your Bootstrap Row [ ] Create Bootstrap Wells [ ] Add Elements within your Bootstrap Wells [ ] Apply the Default Bootstrap Button Style [ ] Create a Class to Target with jQuery Selectors [ ] Add ID Attributes to Bootstrap Elements [ ] Label Bootstrap Wells [ ] Give Each Element a Unique ID [ ] Label Bootstrap Buttons [ ] Use Comments to Clarify Code\nWorking on this one"}
{"_id":"q-en-freeCodeCamp-4f16cd9c5aa008e12fa44b408eadbada57fad3334b1067b52d0f19fe8d95897e","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: The challenge accepts only (single or double quotes) without any spaces between the end of the call and the dot. For example, neither of the following is accepted:\nRegex should probably be this (escaped for JS): instead of this:\nWe welcome a PR to fix this :smile:"}
{"_id":"q-en-freeCodeCamp-cc128fa3cb2aa38bfd8b83096242de2a49d173c4ada7c01a28e95fc055144192","text":"[x] Chrome Dev Tools: Elements [x] Chrome Dev Tools: Network [x] Chrome Dev Tools: Sources [x] Chrome Dev Tools: Timeline [x] Chrome Dev Tools: Profiles [x] Chrome Dev Tools: Resources [x] Chrome Dev Tools: Audits [x] Chrome Dev Tools: Console [x] Chrome Dev Tools: Summary\nWorking on it"}
{"_id":"q-en-freeCodeCamp-54b85bde8e5a5af5df0206257682ad180f4b5758e3b7ce6ca6e13556fdb9d061","text":"[x] Build a JavaScript Calculator [x] Build a Pomodoro Clock [x] Build a Tic Tac Toe Game [x] Build a Simon Game\nWorking on this one"}
{"_id":"q-en-freeCodeCamp-9f4940d06b254ceaad7e3fdb3d2d88c056e9a7f5f6fe0167302651ba700fdc2f","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: The following test should be reworded from You should have filtered out all values from the array that are greater than 5. to You should have filtered out all values from the array that are less than or equal to 5.\nif we changed the wording on the test, it would then conflict with the instructions. Closing as there is no bug. Happy coding!\nThanks ... late night coding, misread the test."}
{"_id":"q-en-freeCodeCamp-1900eb6c754a31f7f4a4737a49530c75b5d45ee9dc1abb6ba52245f2c91bd944","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.87 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nthe instructions are correct. You'll need to return \"Huge\" whenever . If you get stuck with a challenge, please ask questions to the . Happy coding!"}
{"_id":"q-en-freeCodeCamp-aaf5753eb39e674e331b05fb15d8afe05fa9175903ea67c896f0988d99acdcdc","text":"<!-- FreeCodeCamp Issue Template --<!-- Please provide as much detail as possible for us to fix your issue --<!-- Remove any heading sections you did not fill out --<!-- Insert link to challenge below -- <!-- Describe below when the issue happens and how to reproduce it --This challenge would be a lot more informative if a description of what adding the form-control class to the input field actually does. Something along the lines of: All textual [input], [textarea], and [select] elements with class [.form-control] have a width of 100%.\nThis challenge is currently quite short and it's defiantly worth adding an explanation here. To First Timer: You will need to add the sentence under line. Please, check our and if you need any assistance reach out to the .\nThe code you'll need to add specifically is It should render as\nHey there. I'm a first-timer interested in getting started with contributing to Free Code Camp. I will submit a PR for this issue. Thanks!\nHey What about tests ?? Tests should be for each input.\nhaving issue in style-text-inputs-as-form-controls just give a class=\"form-control\" to before your checkbox's 1st div and finally add here 3)"}
{"_id":"q-en-freeCodeCamp-31db290060f7e3a11ef15434626b4d27b6b937dfc49268e2d510d0f0e4663af8","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: ! As you can see on the screenshot there are two instances of #target5 button in the result. I believe it's incorrect. Issue is also affecting at least next challenge - this one\nDuplicate of Thanks for reporting This a very old and known issue, we have fixed it in the react version of the website, which will be released again soon. Until then please ignore this issue and continue. Happy Coding!\nThanks, I wasn't able to find because I didn't look at closed ones.\nsure thing, no problem. It's quite an old one, lol took me a while to find out as well.\nAmazing! Was about to report the same :)"}
{"_id":"q-en-freeCodeCamp-309ecc532e64605ca7d06fb59f3e8436c4303d2dacfe8bb83c521dc04b552c54","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. content: \"\"; // when you addany extra space outside the empty string will not pass this challenge. Can't you add any whitespace?\nI believe this is by intention, rather than being a bug. You can, but you would do so using a few different means such as margin, padding, or positioning depending on the situation and what you are trying to accomplish. The content attribute of the :before and :after attributes would not interpret arbitrary white space in the way I believe you are asking.\nI see what you mean, the tests are too strict. I could fix this if a moderator approves that the tests need to be changed.\nWe just launched the new curriculum and learning platform. Please take a look at it: Do you still think this challenge is confusing or overly hard? If so, we would welcome improvements to this challenge.\nI will look into the tests tomorrow.\nYou're the man. Thanks! Please keep us posted\nI will prepared this and a couple of others for first timers. If the issue is not taken in a couple of days, I will come back and fix them. Let me know if you want me to fix them immediately The location of the test that needs to be changed: the new line should be: \"testString\": \"assert((/.heart:befores?{[sS]content:s?\"\"s?;/gi), 'The <codecontent</codeof the <codeheart:before</codeselector should be an empty string.');\"\nFYI on the issues page it encourages fist timers to search for the \"good first issue\" label which does not exist. It should say \"first timers welcome\" !\nDoes the issue still exist if not then I would like to work on it?\nsorry for the late response. Yes it is open.\ncould you link me to the page where you're seeing this?  Then I can update it.\nIt is on the issues page when I sign in with my moderator account.\nplease review my PR regarding this issue.\nOK - thanks for letting me know - I still can't see it for some reason so you would be a better person to QA this."}
{"_id":"q-en-freeCodeCamp-ec570f1ef6eb9531c36cac6d7fe7311d9712e96aa359827727d7620a4b499831","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nHi Thanks for reporting this issue. Here are some next steps that you should follow before we can help you with your query: Check first. Please use the or try looking through our for help with a specific challenge and any coding assistance. IMPORTANT: Please NOTE that this tracker is for reporting bugs and enhancements to freeCodeCamp's code base only. Happy Coding!"}
{"_id":"q-en-freeCodeCamp-f1217f2a9876161e822f26088d2ca6cc9e89c477e03ca52a140f2ca9ea85417b","text":"Build a Pinterest Clone Following the link to the gives the following warning in Firefox: 'The owner of midnight- has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website.' Firefox 54.0.1 Mac OS El Capitan 10.11.6\nConfirmed on chrome too. Must have missed this when we changed all the hyperdev links to glitch.\nI would like to tackle this."}
{"_id":"q-en-freeCodeCamp-ebb7c7f050f1d2de841d7580d10247f518cf78c0f481f64970791f556d8788c8","text":"This problem does not work with the freeCodeCamp platform since the description says to use an external file. This is impossible with the platform. After consulting with & it was decided to delete this challenge completely. This needs to be done.\nDoes this involve just removing the problem from the project-euler- file? I can take this.\nYup! Pretty simple. Just delete the entire problem from project-euler- Thanks for claiming this one."}
{"_id":"q-en-freeCodeCamp-4da7a05c0ed6a1ccfcabf7b1bfab7d608f69b3d270b211626d118958b7b823c8","text":"<!-- freeCodeCamp Issue Template --<!-- Please provide as much detail as possible for us to fix your issue --<!-- Remove any heading sections you did not fill out --<!-- NOTE: If your issue is CodePen Project / Test Suite related, please open it using the below URL instead --<!-- --Sass: Use to Map Over Items in a List The challenge always fails on the point 2-3-4, despite the code seems to be correct, the preview works fine and inspecting the html show me the three styles (blue-bg, black-bg, red-bg) properly expanded Browser Name, Version: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36. Operating System: Microsoft Windows 7 Enterprise SP1 Mobile, Desktop, or Tablet: Desktop !\ncheckout this issue"}
{"_id":"q-en-freeCodeCamp-e2e5f4740fe7a01f6808d6a26b475b7abad68b5290e5fdbb1bdb78237790e11e","text":"<!-- freeCodeCamp Issue Template --<!-- Please provide as much detail as possible for us to fix your issue --<!-- Remove any heading sections you did not fill out --<!-- NOTE: If your issue is CodePen Project / Test Suite related, please open it using the below URL instead --<!-- --<!-- Insert link to challenge below -- <!-- Describe below when the issue happens and how to reproduce it --The following text seems to be a typo: Be sure to match both upper- and lowercase vowels. It should say: Be sure to match both upper- and lowercase letters.\nHey, I'm a first timer to open source. Is it alright if I take this issue?\nPR out"}
{"_id":"q-en-freeCodeCamp-ace15fd60933668207dd4c09e6ab6fb05b3247a90b328bb3aaea5de677f02a45","text":"Once we've built the JSON we want to output, I believe we can just use Pug like this for the button to initiate the file download:"}
{"_id":"q-en-freeCodeCamp-3a4a3254065fd8d23357503d7ab6ca69428da36ebb43eb97153845865502deb5","text":"<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --I didn't know where to put this, but in this exercise the example code on line 3 does not define the removedFromOurArray variable with the var keyword. This causes the test to fail if the user follows the exercise explicitly and only changes the code below the commented line. I imagine this would be frustrating to new users. Browser Name: Chrome Browser Version: Version 66.0.3359.181 (Official Build) (64-bit) Operating System: Windows 10 !\nWorking on it\nI think this would need to raised on the repo for learn: cc\nHi we may have created some confusion on where to create issues and PR Issues are welcome to opened on any repo you like learn or the main repo. We ( will take care of moving them around as needed. Just tag us (me, Stuart are actively checking these) when in doubt. But its fine to just report an not worry ! As for which repo to make a PR against: All of the challenge execution logic is now moved to the learn repo. That is to say, it has become our challenge platform. Its based on Gatsby, and is a simple static app.The challenge themselves (just the content, instructions, and the tests) are on the main repo. They are now published as a npm package. And used on learn as a dependency.The main repo, will just serve the welcome page, user settings and portfolio.\nThank you for the information. I am just a beginner student, so I’m sure I’ve done something stupid. I didn’t know where to put this, but thought I’d raise this as it confused me and I thought it would confuse others. Please move this to the correct place or delete if appropriate. Thank you.\nits perfectly alright. Thanks for reporting issues. Please keep it up (on any repo you prefer)"}
{"_id":"q-en-freeCodeCamp-1945137840e61f58a5ea1103c01a779d1d177e9979443bb1462916e75c44ba00","text":"When viewing my Legacy Data Visualization Certificate, the Issued date in the top right corner always displays the current date, not the date the Certificate was completed. See: (appears to always have the current date there)\nI'll also add, although it may need a new thread or belong somewhere else, that the legacy certificates that were already earned should not be rebranded as \"legacy certificates\" because it devalues the work that went into getting them when they were not legacy. The date issued and the certificate should suffice. Universities don't send out new diplomas when they change their curriculum with new information saying your BS/MS/MA/MD degree is \"legacy\".\nRebranding the certificates as \"legacy\" could also cause problems for folks job hunting. Potential employers seeing a \"legacy certificate\" may conclude that the work accomplished is already out of date.\nI see seemingly correct dates for my legacy front-end and back-end certs, but the legacy data visualization is showing today's date. any thoughts on removing the \"legacy\" label - they do make a good point, although there would be two certs with the same name (data visualization) - which could be confusing or cause problems.\nI've been poking around the code a bit for this one. My guess is that in , line 427, completeDate is null, which would always give the current date for the ctor of the Date class when this happens. Which implies that somehow completeDate isn't getting set. I'm still working through lines 418-421 trying to guess what's going on there (my background is C / C++, so declaring const {} on the left hand side is throwing me for a loop).\nso the user object probly looks like this... obviously with a bunch of other properties in the user object as well I think pulls the completedChallenges array from the user object and sets it to the completedChallenges variable - and maybe gives and empty array as a default value if its not found - i think that's how it works this lesson and the ones following it might help...\nThanks . I also found this last night So completedChallenges is an array pulled from the user object using destructuring with a default assignment. completedDate is looking through the completedChallenges array (\".find(...)\") trying to match id with the certId. I'll guess completedChallenges is an array of objects, in which each object includes an id and completedDate field. This code is used for all certs, but only the Legacy Data Visualization has a problem here, so this code in and of itself is probably correct. Which implies that the data being fed into it is a problem, such that it can't find a completedDate for the Legacy Data Visualization cert only. So my thoughts are: Possible mismatch between id and certId. Did this id change inadvertently between the old site and the new site? Were completedDates saved for the old Data Visualization Certificate in the first place? I think the next step to debug this would be to just the values of id, certId, & completedChallenges[] on an instance with access to whatever backend storage FreeCodeCamp actually uses. Should be easy to find from that point on, since this is 100% reproducible. Unfortunately, I don't have that kind of access, so I don't think I'm going any farther with this bug. Hopefully this offers a jump start to whomever picks this bug up in the future.\nnice digging - I wonder if it's a naming conflict, it's the only legacy cert with the same name as a new one\nI cannot reproduce this on my local version - leads me to think that anyone who would claim the certification since the new site went live would not have this problem... I downloaded all my data from the settings page of the live site - I cannot find the string of the \"legacyDataVisId\" anywhere in my downloaded data (the string is from ). I can find the strings of all the other certs I have claimed - So the id got changed somewhere along the lines I'm guessing - the downloaded data is hard to decipher, but it looks like there may have been two sections for data vis that got created when you claimed the cert on the old site... I cut some code out but these are surrounded by projects required for the cert"}
{"_id":"q-en-freeCodeCamp-06a38f5d8a502f52b90138f7f34998c5882602c9d6b56b982fd597fc905ce9d1","text":"<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --The test requires a multi-line comment of the form . However, the test fails if additional ` characters are present at the beginning or the end of the text contained within the comment. Some examples : The regular expression for the corresponding test needs to be updated. Browser Name: Google Chrome Browser Version: 60+ Operating System: Ubuntu 18.04 !\nHi, I would like to have a go to fix this problem\nThat's good, please read .\nTest fails if multiline style comment includes either / File: Line: 33 this regex is the problem"}
{"_id":"q-en-freeCodeCamp-45e73593e6e4bb35574ddd060e5e0bf451b355aabd7e4740f7c40182a647d4a8","text":"This is a response to a user of the forum having issues with the Stand in Line challenge. To quote: This is dead simple, there here are code tags around the word in the description, and we've taught users that code tags, naturally refer to code. Browser Name: any Browser Version: any Operating System: any !"}
{"_id":"q-en-freeCodeCamp-3e49644400f1a38b54d33e39cb589c60416fc6835be301d2dfe6e22d59b38b5b","text":"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.\nFixed in"}
{"_id":"q-en-freeCodeCamp-a645685b48e5309fb800426194b42c5c4929980c90836e094ae098c4cf916dde","text":"Describe the bug PR builds for freeCodeCamp / freeCodeCamp are failing in Travis CI with the following: To Reproduce a minor PR change build in Travis CI (ie: https://travis-) Expected behavior PR should pass all the builds to allow QAs to merge PRs to repo. Screenshots ! Additional context ref:jsdom/jsdom\nCorrect me if I'm wrong but '' is asking for: If this file was missing would that not trip something?\nDid you mean this file: ? I believe all this is unused completely. And some of the files around that as well. If you are investigating, I recommend you look The challenge-markdown-parser is something worth looking at as well. It's in the tools."}
{"_id":"q-en-freeCodeCamp-82c810b4500ee0bbdf69e03a27492ccf234d8aa3100d01a16255b9b7731acbd0","text":"<!-- 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: I commented out the code and then followed the new syntax for the challenge, but because the commented out code had normal function declaration it didn't pass. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Google Chrome Operating System: Mac OS High Sierra If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): // change code below this line const bicycle = { gear: 2, setGear(newGear) { \"use strict\" = newGear } } / const bicycle = { gear: 2, setGear: function(newGear) { \"use strict\"; = newGear; } }; // change code above this line bicycle.setGear(3); (); /\nHi, We used regex to match \"function\" keyword in the code but this instance can be fixed. I'll take a stab at it.\nI think this issue occurs with a lot of the challenges. For an example, and Can a statement just be left in the description saying to not use the keyword even as a comment?\nA better way is how we solved other such problems. We stripped all the comments out with a regular expression and then validated the user did not use what they were not supposed to. I just created PR to fixed this issue,"}
{"_id":"q-en-freeCodeCamp-b0a89ea85ce5c1f9c5c88d50188036b01ae48772c6c0f28c162e134ce0a78ee1","text":"I created a solution for this exercise, and it failed. When I looked at the hint solution, my code was basically the same. When I plug the hint solution into the code and run the test, it fails, also. The output window displays 'rating is not defined' four times. When I copy everything to JS Fiddle and run the code, it works as expected.\nDid you ask this question on the forum and present the code you tried? That is the best place to ask. If you present your code to others on the forum and they conclude it is valid code which should pass the tests, then open an issue and present your code here also.\nThe problem is just that 'rating' has not been declared. The challenge code seems to be fine, but the guide should perhaps be a little stricter."}
{"_id":"q-en-freeCodeCamp-ec5281fd9be05ac2c818b66647f2012c23ec1dee23e62dd1c8c2dd73e05cf9c0","text":"The video for the lecture does not exist.\nTwo videos from that section are missing: \"Add an Accessible Date Picker\" and \"Make Elements Only Visible to a Screen Reader by Using Custom CSS\". It seems both videos are down on the Scrimba platform. In the , both videos seem to be missing. If this video has been uploaded elsewhere, we can replace the URL for now. Otherwise, those two videos may need to be re-uploaded. Side note: The playlists are also incorrectly named. It seems that the Applied Accessibility and Applied Visual Design titles have accidentally been switched."}
{"_id":"q-en-freeCodeCamp-4ef68b7872a6418004b20f92f7629078a450b2fdecfc229c19da06d381b11a7e","text":"Related to . Once that's done, the code blocks will be written in blocks of  into ! while the same code on the guide looks like ! I think this change would make the code blocks easier to read, make the guide and challenges feel more like parts of a unified whole and fit better with the code editor aesthetic discussed in the . I'd be happy to work on this, if this is useful feature What do you think?\nYou should look into for this sort of thing. Goodluck. this is something we would probably be needing and using across Guide and Learn. So, I'll let you chime in and guide on this."}
{"_id":"q-en-freeCodeCamp-72bb2682bd59e62633dd06b6811b4042dd43408796e6690030c5f58a63cd1459","text":"<!-- 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: Challenge is missing a period in its description. ! Add a Link to the page with the problem: Here is the file that needs to be edited:\nBtw, I think there is a typo in the description as well: should be\nLooks like those could both changed."}
{"_id":"q-en-freeCodeCamp-e7fbcb23b866c25a5eeff5c091cd500b8b9b53f1c5deafea6ec8e1c2bee0228d","text":"Describe your problem and how to reproduce it: First Issue: The Basic solution uses call() function but doesn't include any reference to it. Second Issue: The Basic solution doesn't work when you use it as a solution for the challenge. You get the following error on the beta site: I guess setting to fixes this issue. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Mozilla Firefox Browser Version: 66.0.5 Operating System: Windows 10 One more thing. The error generated on the old site is helpful whereas the one on the new site isn't. Probably something to look at.\nThat is a valid point regarding the error message, but that is a different issue related to how the challenge tests are ran. I have gone ahead and created a PR () to address the solution in the Guide, but the last issue you mentioned will have to be discussed in a separate issue (feel free to create it if you have the time). I could not find any outstanding issues regarding why this does not show the error \"assignment to undeclared variable x\" which does show in the actual browser console. Are errors like this being suppressed on showing in the fake console for any reason?"}
{"_id":"q-en-freeCodeCamp-0b87ec43119e6650dd3089deb9a5c288ba75619239319c2be20179b9e309247d","text":"The new buttons hug the top of the panel. <img width=\"347\" alt=\"Screen Shot 2019-08-20 at 10 54 27 AM\" src=\"https://user-\"I can fix this one."}
{"_id":"q-en-freeCodeCamp-e46de5b6a6364a2e085e6a7bafcb6dadbc916d06f6c18e125e1cb893fc0f08ae","text":"When you sign in, you get sent to the \"welcome\" page where it shows the number of donators. The progress bar there is still green. I'm assuming we want to make it some shade of blue or something. <img width=\"652\" alt=\"Screen Shot 2019-08-21 at 9 17 21 AM\" src=\"https://user-\""}
{"_id":"q-en-freeCodeCamp-76dec5e9803dfaf66c1065a535ee57ca6678297cd64f90a3de6acb2fff64963b","text":"to replicate. go to incognito do not sign in go to learn choose a challenge !\nI can take a look at this\nthank you. There might to be other inconsistencies with the theme. If you try different scenarios like switching the theme, logging in logging out, and visiting the challenge page. That should expose any related issues that needs fixing. let me know if I could be of any help.\nin displaytheme is in charge of the code editor's theme. and in the theme colors get injected. we need night mode by default if not signed in\nI haven't tested, but it does look like the cause. Hope you don't mind raising a PR, since I don't want to take your credit\nI pointed it out for you. But yea, I have it ready."}
{"_id":"q-en-freeCodeCamp-65f9bdaa48484b4ac7c481ee8109bc20ff65657b9daad57e218455276941eb88","text":"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.\nThe reason for this is because the element has a class which has !\nI think that can be removed. I don't see any reason to keep it.\nYeah 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\nI 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."}
{"_id":"q-en-freeCodeCamp-41c0f39122fff90b73fa76d291daebafb85da799a60a0961e5973b3d761a0745","text":"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 !"}
{"_id":"q-en-freeCodeCamp-8e4542f91b669ae2b68b983782c1892864cd02b7f65829c964b78000553cf827","text":"Is your feature request related to a problem? Please describe. It currently can take a several key presses to navigate to the editor if it does not have focus. Describe the solution you'd like It should be possible to focus on the editor with a hotkey, for example 'e'. The issue where this was mostly discussed will be closed soon, but some thoughts about implementing this appeared there:"}
{"_id":"q-en-freeCodeCamp-dd6374a03a6b38b5d2b05878e18706e6a348061aae73db34a6e34bd5f82824f6","text":"Describe the bug Functionally, there is no problem with distinguishing between normal and focus state because there is blinking cursor when on focus state. Filled fields will also be selected and highlighted with blue color when navigating with keyboard tab. Aesthetically, there is suggestion from on issue to invert the input boxes with dark background and light text in night mode. Border color change between normal and focus state also need some visual improvements because currently it is hard to see. To Reproduce Steps to reproduce the behavior: to http://localhost:8000/settings to switch between normal and focus state on input boxes with mouse click or keyboard tab to Describe the bug Expected behavior Refer to suggestion in Describe the bug Desktop (please complete the following information): OS: Windows 10 1809 Build .832 Browser Latest Chrome Version 77.0.3865.120 (Official Build) (64-bit)\ni'll take this one"}
{"_id":"q-en-freeCodeCamp-a70a29af2cc8e5511f0fa51a809372a087e4bd1eee35751386a3cf15a6f675fe","text":"<!-- 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: Running on any JS challenge outputs on the console output instead of . Related forum topic: User reported seeing when it actually should be with the following code: Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Firefox Browser Version: 70.0 Operating System: Kubuntu 19.04 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): Screenshot of bug in a different challenge: !\nI don't know anything about this part of the code, but I do see JSON.stringify being used in test- and if you stringify you get back \"null\". Again, not sure if this is related or not just thought I would post it anyway.\nYeah, that's exactly the issue. My current plan is to use if it exists and stringify if not. I'm just not sure how to make sure this doesn't create any weirdness.\nWhat about using the parameter function? Would that be less likely to cause any weirdness?\nthat sounds way better. Do you think you'll have time to put that in a PR?"}
{"_id":"q-en-freeCodeCamp-da99e2606395076974bf641d46ee0c1ffb370af7ecdb12be1ff9ddf117863bab","text":"<!-- 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: I identified three challenges where the for loop validation does not work if newlines are used in the arguments. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Google Chrome Browser Version: 79.0.3945.88 Operating System: Ubuntu 18.04 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! ! !"}
{"_id":"q-en-freeCodeCamp-cd2e75022f114b0287b4b665a88ff8ba96c2988eaa299c1c9380abb53ad09526","text":"Advanced Node and Express section needs package versions to the instructions, as discussed in: Example: \" Add <codepassport.socketio</codeversion <codeX.X.X</code, <codeconnect-mongo</codeversion <codeX.X.X</code, and <codecookie-parser</codeversion <codeX.X.X</codeas dependencies and require them as <codepassportSocketIo</code, <codeMongoStore</code, and <codecookieParser</coderespectfully. \" Before this is undertaken: [x] Wait for to be merged [ ] Discuss which versions to use and how to convey this ( or )\nI am leaning more toward the requirement, myself. With the carat prefix, will install the latest minor version. In theory, updates to the minor version are backwards compatible and shouldn't create any issues with the tests or challenges. However, minor versions can include depreciation notices like . The feature will still work, but this could be confusing to a camper. Using the tilde prefix means will install the latest patch version, which includes bug fixes but shouldn't lead to any depreciation notices. I think this will offer the best long-term compatibility with our tests and challenge instructions.\nWell, it has happened: Last versions which definitely work: I have tested this. Now, discussion: 1) Just ask for to be installed 2) Also change the lesson/code to work with this latest version?\nHey how is this show stopper coming along?\nAh yes... I have updated the label, because it should have been removed by . Can a PR automatically remove an issue's label? Otherwise, this issue is still open and help wanted , as there are many packages which need their versioning fixed. If no one else, I can slot in some time for this tomorrow.\nNo rush. Thanks for confirming, I have removed the assignment since this is no longer a showstopper.\nthank you so much for the Thank you for the suggestion. It helped me alot"}
{"_id":"q-en-freeCodeCamp-fa0dd1af7040c4eaa2f6709f8b8c3e59222b55d77275348444ab208fbbd776a1","text":"<!-- 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 usage of the word \"argument\" ist unclear to me. The title of this challenge uses the word \"parameter\". Then the instructions state: \"If an arrow function has a single argument, the parentheses enclosing the argument may be omitted.\" But the following snippet cited from the instructions shows the parameter \"item\" without parentheses: The functions are never invoked with an argument in the examples. As I understand it the sentence should say: \"If an arrow function has a single parameter, the parentheses enclosing the parameter may be omitted.\" Add a Link to the page with the problem: or, Tell us about your browser and operating system: Browser Name: Browser Version: Operating System: If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):\nHello~! I agree that the verbiage is wrong here. should probably be replaced with in the examples and text, with the exception of the top line (which, at a quick glance, is the only correct use of ):\nThese are the ones that should be changed, I think. In fact, we could use instead.\nI like that approach. Think this could be opened up to first timers?\nI would go for: Just like a regular function, you can pass arguments into an arrow function. If an arrow function has a single parameter, the parentheses enclosing the parameter may be omitted. It is possible to pass more than one argument into an arrow function.\nSure, that works."}
{"_id":"q-en-freeCodeCamp-67a91c4a4d0c2db396218c3a0d28e36827f1d5ec23d8ee48c622ec11bd023197","text":"GitHub yesterday (November 16) which our Cypress CI depended. So, currently all Cypress tests in CI are failing. Just using the latest version of the Cypress GitHub action should do the trick. (We are currently running the outdated action.) !"}
{"_id":"q-en-freeCodeCamp-37a64e2288ca916ba2918ec4345c1a80dd829600e410bd4502fbd7309ca1f75d","text":"Describe your problem and how to reproduce it: While working on the Sudoku solver project, one scenario came up that wasn't clear to me how to handle. The scenario is what do you do, if I ask to check a value of a cell with an existing value? For my project, I chose to return a conflict with the row, column, and region. However, I checked what the example app returns. The results it returns are logically inconsistent, which tells me this use case is undefined. For the example app: https://sudoku- coordinate enter C3, for value enter 2 (the existing value), click Check Placement returns value to 9, App returns value to 1, App returns These response are not logically consistent. For the first one, it appears to be checking against all of the existing values in the puzzle. For the second and third cases, it appears to be checking after replacing the value. I would expect this use case to be defined as either, it's a conflict, because there is an existing value at that cell or to replace the value in that cell and then check if it is valid or not and return the appropriate results. Add a Link to the page with the problem: ://sudoku- Tell us about your browser and operating system: Browser Name: Google Chrome Browser Version: 87.0.4280.67 (Official Build) (x86_64) Operating System: macOS Mojave 10.14.6\nYes, seems odd that you can place a value over an existing spot and it can return as valid Seems like this should be the response Or something along those lines\nI do agree that this should be handled as a valid placement (given that the number is already present in that cell). Unless there is objection/disagreement, I'd be willing to open this up for contribution.\nI also vote to make it behave as if it replaces the cell before checking validity. Or something along those lines. I have opened this up for contributions."}
{"_id":"q-en-freeCodeCamp-68eff5769d3b99738bb5922c6f38676c997029a8851d3ea4d0c7e4b2484a7b70","text":"Describe your problem and how to reproduce it: Challenge description gives slightly different task, to what needs to be done to pass tests. Challenge is about , which looks at the beginning like (skipping zero at start): Challenge description asks to create function returning n-th member of the sequence. However expected values in tests, and sample solution don't match that. sternBrocot(2) should return 3. sternBrocot(3) should return 5. sternBrocot(5) should return 11. sternBrocot(7) should return 19. sternBrocot(10) should return 39. Function matching tests would be one returning at which position in sequence number is encountered for first time. Original challenge on Rosetta Code - have both these variations as a part of task, so that's most likely how it sneaked in. Add a Link to the page with the problem:\nI vote to have the function return the position in the sequence of the argument. We wouldn't need to change the tests, just the description.\nI'm in favour of that approach as well."}
{"_id":"q-en-freeCodeCamp-a6da83dc88ae80bff1a0527505aed14b2eb31f14bbb803088f4c4cc6ca1135f1","text":"Describe the bug Last week, I saw multiple posts where people asking for help didn’t write down what they needed help with. I think the help post template may be confusing some folks. Screenshots ! Additional context “Tell us what’s happening” looks a bit like an overall heading. I suggest the following changes to make it more obvious that people are supposed to write something down: Mockup !\nHello there, Thank you, for taking the time to open this. I believe it would help some Campers understand the need to add more information. However, I suspect the large majority just post without reading any further. The Discourse software does have a lot of cool features aiding the topic creating (e.g. Information about informative titles, showing similar topics). If others are in agreement, this would be an easy implementation, and could be put up for first timers? That being said, I find dedent to be pesky.\nI'm not big on the idea of adding an extra heading. Perhaps just the extra describe prompt: Tell us what's happening: Describe your issue in detail here Your code so far: Your browser information: blah blah blah Mildly related - I think we should add a colon after \"Your code so far\" to match the other headings.\nIf it's a first-timer I'll let somebody do it but if not I can take care of making the changes. Your call!\nAny decision on if we're opening this for first timers?\nCan I work on this issue, being my first contribution to freeCodeCamp?\nplease go ahead.\nHi, I saw that this issue wanted to be done by someone a few days ago, but its still not been closed, I am also an newbie and am really eager to contribute so would be happy to help, and close it today. Was trying to find the template to change it, but couldn't find the file. Would it be possible for someone to point me to the right file? Thanks :)\nHey it's this one -\nThanks"}
{"_id":"q-en-freeCodeCamp-7d1c5a414db938716f86d41ecf03950afa6b7a71864f7673ba551d048fed36fa","text":"Maybe this was done intentionally to give learning programmers more leeway. If that's not the case though, it's a bug. Describe your problem and how to reproduce it: In the -challenge, the request clearly is to add the new tag AFTER the previous p-tag. However, the following code also gets accepted as a correct solution. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Firefox Browser Version: 87.0 (64-bit) Operating System: Linux (Linux Mint) If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! !\nI think this can go either way, but I'm leaning towards changing the directions, and removing the to give the more leeway for newcomers, to somewhat like: This is ofcourse just my opinion, I would love for others to pitch in...\nI like the change. The less explicit version seems to better describe how the page is already behaving.\nI agree that this sounds like a good change :) Maybe is the way to go, to indicate it shouldn't be over the tag.\nAs we do not want any confusion about what the element should wrap. I suggest the following: I am opening this up to first timers An issue with the help wanted or first timers only label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the\nSure, I'll do my best!\nSee . I wrote this. I changed the second line to improve it with , while still keeping it similar to the previous description."}
{"_id":"q-en-freeCodeCamp-af5d1eec538b00eb2549e47e866512b1949fb59e357e34e9b7b4b7033f3131b7","text":"There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved. Error type: Cannot find preset's package (githubwhitesource/merge-confidence:beta)"}
{"_id":"q-en-freeCodeCamp-ee90e34dd48c9238c86500826dfeee57088276c313289d40e50590bfa8448518","text":"<!-- 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: -- Expected to see Clothing withdrawal transactions (-25.55) on output but only seeing the 'transfer from food $50'. Transfer method passes but the food transfer of 50 but it is 0. <!-- Add a clear and concise description of what you expected to happen. --<!-- If applicable, add screenshots to help explain your problem. you can drag and drop, png, jpg, gif, etc. in this box. --<!-- Please complete the following information. --- Device: PC Desktop OS: Windows 10 Browser: Firefox Version: 93.0 <!-- Add any other context about the problem here. --I've since updated my transfer method to use the withdrawal and deposit functions to accomplish the task correctly. It seems the Transfer method test case needs a bit of an upgrade to make sure withdrawals are working.\nThe test for transfer function is not checking if the amount is deducted or , But only checks for the ledger entries. Adding two additional tests for deduction and addition will fix this issue.\nI tossed up a PR for this: I two asserts to the existing test."}
{"_id":"q-en-freeCodeCamp-96958b33bd85ed6a639034c080a281a66250a9c61146f351a07063907e0c8993","text":"In the The Property section of Curriculum File Structure documentation there's reference to file. That file no longer exists, and the relevant helper function is now in file. It's needed to point to the correct file and/or adjust the wording in the section. Here are the files that you should be looking at to work on a fix: 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."}
{"_id":"q-en-freeCodeCamp-7de1b89644aa1ed6c9ead7c06a126f8a8caf4e45436c5c2641e8e1cea69734de","text":"Step 36 says However this is false, anchor tags are not self-closing. I believe it meant to say which is the self-closing tag introduced in the previous steps.  Wasn't sure where to report this so I also posted about it on the forums at .\nGood eye!\nHi ! Thank you for bringing up this issue. This is an easy fix to change anchor elements to img elements. I have the first timers only label for those who are interested in making their first PR.\nCould I take this issue? I'm looking for a good first contribution.\nHi ! Any issue with the first timers only label is up for grabs. The first PR that has the correct changes will be reviewed and merged into the main codebase. Here is the file that needs changing. Happy contributing !"}
{"_id":"q-en-freeCodeCamp-eeedeb2cecde96220ee1197bd11d781b3d19b6807e1c41cd1e85b931108f1538","text":"The following code passes all the challenge's tests, but it is incorrect (it fails to find if is the last element of The code above should not pass the challenge. ! Device: Macbook Pro OS: 10.13.6 Browser: Firefox Version: 97.0.1\nChecking against the solution on the forum, it appears that should return . We could add a test to the challenge that checks this, which would resolve this issue.\nYes, that should be all it takes to resolve this issue.\nI'm going to go ahead and open this up for first time contributors. A PR to resolve this issue will: Add a test to that asserts returns . If you are interested in working on this issue, we recommend starting with our , and you are welcome to join our if you have any questions.\ncan I do the code in python ?\nNo. Our challenges run on Javascript. In this case, you don't need to write a new impl of the algorithm or anything. You just need to add an additional test case that matches the one given above.\nSure, unless wants to take this, I will"}
{"_id":"q-en-freeCodeCamp-3c2395834e687947d5299140d82bbc264d75d7eb419c753f03435ab5b03108be","text":"related to In the new Responsive Design curriculum the words tag and element are used interchangebly The correct use should be element and tag (or at least, element is the whole thing, tag is the one that start with and end with and can be an opening tag, a closing tag or a self-closing tag). Should this be changed in the new curriculum?\nDo we have many/any incorrect uses?\nactually mostly not - there is some ambiguity with in the second step of the accessibility quiz I have been hasty\nMy concern was with these steps, which are about meta tags\nThat does look like something that should be standardised. Thank you, for listing them. I am opening this issue up for first timers only. The files that need changed are listed in the above reply. What needs changed There are a few uses of the word which should be changed to . Example Original: New: Note Not all uses of the word should be changed. Example: An issue with the help wanted or first timers only label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the\nHi - is it ok if i pick this up? First timer here"}
{"_id":"q-en-freeCodeCamp-d103c2d7fe8dc1538a2d7b39689b45deeff9ac14248bed2c41b404e58150d8ed","text":"Steps to reproduce the behavior: on toggle button(code folding) on line 36 of the code editor (check screenshots) error no idea ! ! <!-- Please complete the following information. --- Device: Laptop OS: Windows 10 Browser: firefox Version: 98.0.1 (64-bit) <!-- Add any other context about the problem here. --\nThe UI is designed with the assumption that the editable region is visible and will be surrounded by the instructions and the Check Your Code button. With the editable region hidden the UI will look quite confusing. I think the best solution would simply be to disable folding for project steps. Folding is an editor option, , so we can disable it.\nI'd be in favour of that solution. Should just be a matter of adding to this editor options object right?\nI think so, yeah. We could make it conditional: false if there's an editable region and true otherwise. That might be nice if you're working on a project using the multifile editor, since they can be quite large and don't have editable regions.\nI'll go ahead and open this one up for contribution then"}
{"_id":"q-en-freeCodeCamp-1b6928656d59195bdab13380cdc5fe381c179ee952e3d996c33605867d7c6a11","text":"I see here that we are intentionally supporting confusing but technically correct syntax. In light of this, we should remove the note here All of these are non-standard things that technically work but nobody actually does in practice. We should either go out of our way to support this sort of thing or not. If we are going out of our way to support this sort of thing, then there really isn't much point of letting the users know that it's unconventional syntax. See also: Personally, I think it's valuable to teach the learners how to write code that others expect to see so that it's easier for them to get hired, but we really need to be consistent. We should either help them with conventions or not bother. If we aren't doing anything after making the note, then it's just visual noise and should be removed.\nFor what it's worth: This code fails the \"bracket notation\" test, presumably because of the space. And I'm of the opinion that it should stay that way (I'd be okay with updating the test to allow spacing and adding a third test that clarifies \"you should not have spacing\"). That being said, there are areas where we are more lenient on the spacing/conventional style, which IMHO is okay if that's not the concept being taught/tested.\nFor what it's worth here's what I think about formatting. In practice the likes of prettier have rendered manual formatting unnecessary and unhelpful - I don't need to see diff noise obscuring actual code changes. If we're overly picky about formatting then I can see that creating a frustrating experience. However, we should provide nicely formatted code in the examples. That way learners can pick up good habits simply by copying.\nI'm generally pretty flexible with formatting. I don't think we have any business requiring a specific brace and indentation style. I'll format utterly unformatted code when someone asks for help and explain how it helps me and the learner discuss the code more easily, but that's a very useful context to discuss readability. But the extra spaces in the above three examples are so unusual and uncommon of syntax that it feels strange to make our tests permit them in the recent couple of issues while also calling it out here as something to not do.\nI disagree with both propositions — the note is fine, we should encourage standard style. But also let's not be a PITA. I'll copy my other comment here, so we can have a discussion in a single place:\nIf we aren't going to enforce/test it, it's just pointless noise that needs to be removed. Text that doesn't related to what is being tested just fills the screen. We have enough trouble getting users to actually read the challenge text without including text we intend for them to ignore.\nFrom an accessibility perspective, I don't think we should be strict on formatting that does not affect the execution of the code. One example that comes to mind is people who are listening to the code. Screen readers don't announce spaces by default so it might not be obvious that there is an extraneous space between the variable name and the bracket notation. I don't think the tests should penalize them for this when the code executes just fine. On a side note, you can use the keyboard shortcut in monaco to format the code and it will remove the space between the variable name and brackets (I just tested it). So I suppose we could require everyone to format their code properly before testing, but this seems like overkill. Or perhaps there is a way to auto-format the code when the user clicks the test button?\nI'm not thrilled about intending this syntax to pass, but I find the accessibility concern more compelling than just allowing highly uncommon syntax variations because it can run in other JS environments. But I still say that it we aren't going to test it, then the spacing note should not be there. If its not part of the challenge outcomes, then it's noise. We already struggle to get learners to actually read the parts of the text that relate to their ability to pass the challenge.\nAllow me to revise my previous answer just a little. I think I was assuming that this extraneous space issue was being tested in all challenges, but now I'm realizing that it may apply to only this one particular challenge. If so, then as long as the challenge instructions make it clear that this is a requirement to pass the challenge, and there is a clear error message that indicates the reason the test failed is due to the extraneous space, then I think it is OK to leave this test in there if it's deemed important enough to keep. But in general, I do not think such formatting issues should cause a test to fail (as explained above).\nThanks for the thoughts & Here is what we should do: the note. IMHO you all are correct in assuming it does nothing other than draw attention to a confusing notion. should support the technically correct syntax (ignore testing for it, if we are). may be a good idea, but I am afraid of accidentally introducing something else."}
{"_id":"q-en-freeCodeCamp-6b4e96ec444f037d2fe9d38702a9ccd077ac6135cf68d703ee9316eb31b9e85c","text":"The use of the term \"Gender\" as an objective feature variable type with a categorical code value type seems to be an outdated understanding of gender and can be potentially offensive or insulting to those who would identify with the LQBT+ community as there are potentially too many genders to possibly categorize I would suggest the use of the term \"Sex\" as opposed to \"Gender\" as this will not effect the overall behavior of the project while also ensuring a safe and inclusive environment for those who identify as genders other than man or woman"}
{"_id":"q-en-freeCodeCamp-e26466f30c69f7066ec8d0187bc239cbce324945beab2a67116079da485aea7f","text":"found an issue: Unexpected shorthand &quot;padding&quot; after &quot;padding-bottom&quot; (declaration-block-no-shorthand-property-overrides) It's currently on:\nI'm happy to fix this (and remove the units from zero values also in that file), but I'm not sure what the preferred replacement is for the padding. Should I just remove the padding: and add lines for padding-top: 0; padding-right: 15px; to reflect the styles currently specified by the padding: 0 15px 15px line?\nI would delete , you can start and these question will be answer by reviewers if they need changes later"}
{"_id":"q-en-freeCodeCamp-cbc54c7df1af71f1efe1bed30c8aacd1f8548663fda18389dd765770cf8d40cc","text":"The following test (user story) prevents my previously passing project from passing: Important: Notice I use instead of just I never claimed to be a UI expert Do we want to keep such a test? No response Unrelated No response\nMaybe you should update your project Honestly I think small tweaks are going to be okay - my tribute page fails because the image needs a height now.\nI am also happy with small tweaks, but we did (largely) want to keep the requirements exactly the same. The only change we agreed upon is to add requirements for tags.\nLooks like they accommodated for the tag in that test. Maybe we can just add it here too.\nalthough, I think it's good, that we moved on from the old test. tag is extremely useful in html, it has attribute that help developers use less needed css, which lead to better experience, . it should be accepted to use Edit: if you paste this code in it won't pass although there is a media query but in the html Edit: I changed the for easier testing"}
{"_id":"q-en-freeCodeCamp-2790834968579b8be3dfed36d4b57e30c20e26701ba4242afc1d1c84dcf440d9","text":"! I \"of\" It is missing orginally. there is no code, just lesson typo for the text to read \"front of it\" No response Device: Omen Desktop OS: Windows 10 Browser: Chrome Version: version of? Sry if the System section isnt very clear, its just a typo so i assume it doesnt matter all to much.\nThanks for opening this issue. It looks like this issue is something that \"first-time\" code contributors to this repository can fix. Here are the files that you should be looking at to work on: List of files:  Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in our chat room or the forum if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We prioritize accepting the most quality contribution, followed by the earliest request. Happy contributing.\ni it to my pull request it took me a while to find it lol\nNo clue what to do to help with files or fixing stuff tbh, I'm still pretty new to all this GitHub stuff. Someone might be much better for this than I. But hopefully ill have the experience in the future to help with things like this, big or small.\nI see that it's a perfect start for beginners like me, however using repo or GitHub is not easy that much :D. For this issue, finding correct challenge on my local files and fixing it is an achievement for me. I am excited for more. :)\nContributing to open-source is a rewarding experience. You get to learn so much, things like coding practices, collaboration skills, and most critically, working with folks you have never met (or most likely never will) in person. We encourage you to participate, not just in this community but in many different open-source projects out there. You got this! If you need help, we are here to help you help us. All you need to do is get started. As I mentioned earlier, if you are interested, head over to the contributing docs and jump right in. Cheers & happy coding."}
{"_id":"q-en-freeCodeCamp-5c81b67caffbf65f5097089d461b0a5ef38b208f77e335fd487519e57731cb04","text":"I think that the instructions for the media query are a little difficult for (relative) beginners to understand. Up until now, as far as I can see, they've only been asked to create media queries for CSS rules that they're already somewhat familiar with (, etc.). So, to me, it just feels a little too ambitious at this stage to expect them to have fully grasped the terminology involved (media-rule, values etc.) and to be able to construct the appropriate media query. It doesn't help that the MDN docs page has no examples using either or which also makes it a little more difficult for students to search for help via Google. I feel as though some kind of example would be very useful here, although I do appreciate that it's difficult to provide an example without effectively giving the solution away. Perhaps something like \"reminder - the format of a media-query is (media-rule: value)\" could be ? (at least to the hint if not to the instructions). Alternatively, perhaps add a link to this which does have an appropriate example. 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] Recent forum posts:\nI do agree an example would work, but it isn't the optimal way. It's against freeCodeCamp policy to add an external link, there is an issue with the content of the external link changing. We can change previous media challenge to include this , until media reduce article is written.\nAgreed, users are always free to search if they want to, but we should try to make our lessons self-contained if possible. I just tried doing the lesson myself and found it frustrating to keep getting the hint when I had wrapped the rule correctly, but the rule was wrong. should trigger a different hint. That sounds good to me, though I'd word it slightly differently to be more consistent with the rest of the hints: cc:"}
{"_id":"q-en-freeCodeCamp-6dec883824dd844785e7201cfb8d450f8bccae03dd22f75ecbe549b13cda4355","text":"In step 1 of building a cafe menu, the attribute test is strict with space Here is the markdown file The code above should pass, for this to happen you should change to ! 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.\nCan I work on this issue ?\nYes، feel free to open a pull request"}
{"_id":"q-en-freeCodeCamp-df6182c7220b486a368676ad8dc72bc41f4ae27ef9a251f7fc1331bd8fdd20bd","text":"The challenge text mentions Ryan but there is no Ryan. We should only mention parts of the example that exist, ideally. No response All No response\nwow. Ryan was exist? that is interesting.\nThanks 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: 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."}
{"_id":"q-en-freeCodeCamp-dad59d4a629eb1617ab6ae4b2f4b788b4880b54d983318072c9d77768dce572a","text":"There are three tests that test for non-empty labels: \"Your #name-label should not be empty.\" \"Your #email-label should not be empty.\" \"Your #number-label should not be empty.\" I think the word \"empty\" is slightly ambiguous here. These tests appear to be looking for actual text inside the label. But if the user nests an inside the label without text then the isn't exactly empty: The above will fail because there is no actual text in the but I can see how the user would not think the is empty. N/A Adjust the test descriptions so they clarify that text needs to be inside the . Perhaps something like: \"Your #name-label should contain text that describes the input\". No response N/A No response\nPlease 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."}
{"_id":"q-en-freeCodeCamp-0fdff6d3d52e60383a90cdd02ea2790557efc98adc06de133ac93ff08ece83da","text":"challenge-editor should be to the \"How to work on practice projects\" documentation here:\nI'll tackle this today."}
{"_id":"q-en-freeCodeCamp-30e6a8e64878128b0d314be65a6e4da78cc25444df2b62d946acfac9df330a24","text":"in step 21 of building a piano project, the hint in line 30 is missing code blocks This should be changed to 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.\nI believe I did all this right. This is my first time contributing to open source. Very exciting :))"}
{"_id":"q-en-freeCodeCamp-a59d3501288551bf707f4b3b32ccb2d2a76baeb1dfa13adece3eb47180c04ad0","text":"There is a typo in Understand BCrypt Hashes, is used instead of . Here is the typo 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 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."}
{"_id":"q-en-freeCodeCamp-82667795931f7b2612de039ff1d1d746a2bd03504b84276afe17aff1e6c29b21","text":"It says that plot 1 should have an x label of Month, but it's the second plot that is monthly. It should say that plot 2 should have that xlabel. It should say that plot 2 should have an xlabel of Years It's testing correctly, so it should be an issue only with the assert message ! 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\nsame thing for the ylabel in plot 2 actually, it says plot 1 there too\nHello, It seems that same thing is for the \"testboxplot_titles\".\nI am opening this for contribution. The PR has to be done on the boilerplate:"}
{"_id":"q-en-freeCodeCamp-eeb507e0cc2f904517a215f8a786c9a69667cd3fc0f8e4675416fe0696b7ed77","text":"it should be --important <-- instead of import Learn Bash Scripting by Building Five Programs False. An important operator in that menu is =~. It allows for pattern matching. Using the same syntax but with this operator, check if hello contains the pattern el. ! 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\nI'll fix this! Just for reference, I will be fixing this issue in repository.\nHey guys! I'm getting this error when typing in the terminal. Anyone know how to fix? I created a seperate branch that is up to date.\nFor generating file, the coderoad cli requires for the version branch to exist locally. Detailed guidelines how to contribute to these tutorials can be found on Please refer to the parts about making changes on the branch. Thank you and happy coding!\nPerfect. I have the typo fixed and ill make that branch work with coderoad. Thank you for your patience"}
{"_id":"q-en-freeCodeCamp-e02dce190a185a289d9417c2c17da4e0d4f1ba762360dd83a4bf7873d7075cdf","text":"In this line, there is a missing code block around word false It should be like this here is the file: 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. Happy contribution.\nI opened pull request"}
{"_id":"q-en-freeCodeCamp-31bb7435217889f2d07f7191ba41a186ed8ca1a9e7922fc8ba1e4e80e7e9aba9","text":"A camper mentioned in his comment, that this icon below indicate to them that it's an external link not a popup. ! We can change it to clearer icon that show, that it's a popup. The original comment for context:\nI found it interesting, that say you should use ellipsis (…) when there is some additional action required after the action (popup, dialog, confirmation) and it isn't clear by the action itself. This doesn't mean you should use an ellipsis whenever an action displays another window only when additional information is required to perform the action. Consequently, any command button whose implicit verb is to \"show another window\" doesn't take an ellipsis, such as with the commands About, Advanced, Help (or any other command linking to a Help topic), Options, Properties, or Settings. So maybe an ellipsis of some kind: in button's label or in the icon? More so, it's a part of too. If we were to stick with keeping an icon regardless, this regular feels like a better choice, with the arrow denoting there would be some kind of external interface but the enclosed square representing that it is not an external redirection, thus denoting some kind of popup or modal.\nI think these guides are saying that the ellipses should be when the button opens a window that requires the user to enter more information or perform another action. This isn't the case here, so I don't think they are warranted in this instance. If we want to use a new icon then I would suggest we use one that has . I'm not suggesting that we use this exact icon. This is just an example of what I'm suggesting.\nI second the use of some kind of variation of that icon. There's a small issue though, there's no such icon in the font awesome library for this so we'll have to find a different way to implement this.\nFont awesome has an icon that could have the same meaning: Alternatively Material Icons has a specific preview icon if these can be used?\ncan you assign me this task?\nissues with label, aren't open for contribution yet. You can however browse the label help wanted for open issues\nallright sir\nBoth and both are plausible.\nI'd suggest we should move forward to replace the icon with the icon. Should I move ahead and send over a PR? This is the output - !\nSure. Just make sure we don't need to add other dependencies to get that icon."}
{"_id":"q-en-freeCodeCamp-96104283f9a4fbf0245de80ba67e4fcab39ca33c00194478086c584d94e603fc","text":"The declaration of arr doesn’t need to be guarded by ‘Do Not Change’ comments. There exist many solutions (3 in the guide) that do not need that variable declaration. These comments should be removed or at least moved. All No response\n. I lean towards the second option of having only the comments within the function and no extra starter code.\nI was thinking something simplier We've ditched a lot of these comments in the rest of the intermediate algorithm challenges. Does the comment help us at all here?\nProbably not. I honestly would not even put the . At this point in the curriculum, users should know the function needs to have a statement and they can craft their own.\nSure, then the fix would be: This looks like a good first-timer issue.\nThanks 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."}
{"_id":"q-en-freeCodeCamp-f2df56c6b5ccb3dd109432bad9073886bbbbffb4fcf93cdbfeddd369375d3375","text":"In step 31 of the Learn HTML Forms by Building a Registration Form project, the step doesn't explicitly say that it wants the input element to be nested inside the label element. Instead it says: \"Add a label with the text Upload a profile picture: , and add an input accepting a file upload.\" This could be interpreted to mean that the input element should be on the right side of the label element. Only when we attempt this are we told by the Hint \"You should nest an input element inside the label element.\" To clarify the requirement, the step should use the word nest in the exercise as below for eg.: \"Add a label with the text Upload a profile picture: , and nest an input accepting a file upload within it.\", The step should explicitly state that the input element should be nested within the new label element. No response Not Applicable No response\nI think if all of the challenges will have specifications defined explicitly, it will serve no purpose of \"challenging\" the learners to really think and solve it. In the first place, the solution is already implied from the given code and then, if the learners will still have the hard time solving it, then the feature will definitely do its job.\nAgreed. The instructions should be clear to begin with. Making the users guess what the test requires isn't a \"challenge\", it's just rude.\nFor what it is worth, the camper has nested an input in a label element a few times in this challenge prior to this step. I am not against adding this reminder to the instructions, but I don't want to lose sight of our goal to keep the instructions more lean and have the hints serve as the reminders.\nDefinitely. But I looked back at the instructions on the steps where they add the previous inputs and we do explicitly tell them to put the input within the label: step 17: Nest an input element within each label. step 25: within each of the first two label elements, add one input element with type=\"radio\". If we can add that information to those instructions then I think we can add it to this one. And let me just clarify that what I am really concerned about is this correct solution being rejected: I'm working under the assumption that correct code should always pass. So we need to tell the user that only a nested input will pass if that's all the test will accept.\nI understand that if someone is working on a series of steps they may not need to be told to nest the input again. However, if they stop and return to the project a few weeks later on, they may not remember that. The hint will remind them sure. I guess this is a minor issue given the hint is quite clear. Personally I like a more explicit instruction."}
{"_id":"q-en-freeCodeCamp-4ae32381e7fdcedfea9d2c64ed8d264c8027509309386e343995d92b893daffe","text":"in step 53, the span elements are missing code elements. Here is the file We can add elements, to both of them. Like step 43: Or delete the first one and add code elements to the second one, but reading previous issues, I think campers may delete both elements wrapping the text and create one that wraps both the text. Note: that sentence is hard to work with in Arabic, and require adding nuances, because the structure of two code elements following each other which is weird in RTL layout."}
{"_id":"q-en-freeCodeCamp-a2da53959672c93226540a0c8a867da2453f772128c7d623321490260f6a9706","text":"The following sentence in the Word Blanks lesson should have a code block (three backticks) surrounding the code section which is directly referring to the completed code block below it on the page. Instead of: Consider this sentence - It was really , and we ourselves . It should say: Consider this sentence - The sentence has been translated because of the missing code blocks (and will not make sense as it's a direct reference to the actual code shown below it) The sentence with the blanks should be in a code block that does not wrap. (three backticks above and below it) Instead of: Consider this sentence - It was really , and we  ourselves . It becomes: Consider this sentence - No response n/a No response\nQuestion for those in the know. Do we have a way to keep content from being translated that doesn't involve using the triple back tick code block? I would be cool to use sr-only text \"Blank\" (or something similar) for those underlines to represent missing text. But we can't do that using the code blocks since they are wrapped in a .\nDo they get wrapped in a if they're inline code?\nIt looks like they are just wrapped in strong tags in crowdin at least. I don't see a pre tag.\npre sounds like a plausible idea. We should go ahead with that.\nThe challenge require the sentence to not be translated, and element don't stop translation, it gives the choice to the translation to translate or not, which isn't ideal. Here is the file, to solve this issue, change the structure of the sentence to md It was really , and we ourselves . ` If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our prolific contributors will guide you through this.\nnope, but we can open an issue for this yes\nCan you assign me this issue\nOnly issues with the or 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"}
{"_id":"q-en-freeCodeCamp-ce818bd978147d43529b257bb183bb45ffc7191c6c2eb679f3224889a46baf7b","text":"instead of the example command should be: docshow-to-add-cypress- project dependencies to run will see error: instead of the example command should be: No response"}
{"_id":"q-en-freeCodeCamp-f9cd58cb25280d2deb8301f0687764fd29dc1bec4c1fbfc7ba429a9d8e784782","text":"This part is still tripping people up Usually one piece or another gets lost: Maybe this is clearer Side note - I still don't love the fact that we say like a variable instead of like a string literal. I think that's confusing here. (I know, I know, the style guide hates \"s) No response All No response\nAgreed, it has the potential to be confusing. Can we reword to say: \"If is the string and ...\"\nI'm still not clear on the reason why string literals in inline code blocks are forbidden by the style guide since it makes the instructions less clear in this case. do you have some context?\nI don't remember the full reason, only that it was a decision made as part of our i18n efforts. We reference a discussion in but I can't for the life of me find where that discussion is."}
{"_id":"q-en-freeCodeCamp-53592109330c779128e66264d8319434f8545026b44d41ad6e62a4e860f4d2a9","text":"In the new JS curriculum I found a couple of example where comments have been inside code blocks in the challenge description. These comments are not translatable on Crowdin: We should avoid commenting code blocks or make those comments accessible from Crowdin"}
{"_id":"q-en-freeCodeCamp-53ecc40b1a9b775a4578f7b9b5384e2765ff7f1bf634da41daed7431857c7951","text":"The setup instructions here suggest that I need MongoDB Community Server | 4.2.x. I've tried through docker and through macos homebrew instructions and can't get any 4.2 version. 4.4.x is available. Is that acceptable? If so, should I update this doc? Try to follow one of options for setting up MongoDB Community Server | 4.2.x Maybe 4.4.x is ok? No response\ni searched the tags on docker and no 4.2 is available. this article suggests other ways but the result is always\ni found this pr which suggests that 4.4 should work fine. so i guess i should update the docs? you agree?\nor there are other docker images available of 4.2.x. But people trying to follow directions won't get to them if we point them to starting from here: because mongo only points to their docker images.\ni also see that in there are docker instructions there. should i use that or is that for something different?\nHi thanks for the issue. We recommend asking around in our chat and forum when you are troubleshooting. The docs need to be updated to the version we are using right now. I have created a PR. It will be available soon at I hope this helps.\nI see that the docs have been updated to mongo 5.0. But maybe should the docs point to as the best way to set up mongo? That's what I used and it seems like the easiest option.\nThanks for pointing that out. The directory is a newer API in the works. It will have a full docker-based setup that is more convenient than the current workflow. We will release cleaner and easy-to-follow docs when that happens. Meanwhile we will stick to the docs you see at:"}
{"_id":"q-en-freeCodeCamp-efc1044f1fe01397b30fe4eab8c0cbdfe3964f3cb62f3b6e15094fa9fdb020c8","text":"The formula given for converting from C to F is given as a) But this can also be written as b) These two formulas are producing different results. Using for (which is used in the tests) we get: a) b) If formula is used then the tests for this challenge will fail due to the floating point rounding issue. The tests should pass regardless of where C is placed in the formula. Either we need to do a little rounding in the tests or replace with a different number in the tests that won't produce different results depending on the placement of C in the formula. No response Device: Desktop OS: Linux/Fedora 36 Browser: Firefox Version: 112 No response"}
{"_id":"q-en-freeCodeCamp-e0493aef6c4dd2464d6a92c9352a4d33febc0843c2fba40a141a85b296196240","text":"As i love free code ; I would like to inform the problem and stay as minimal as i can. staight on problem. in : Responsive Web Design Learn More About CSS Pseudo Selectors By Building A Balance SheetQUALITY CONTROL DEGRADING CODE ROBUSTNESS. 47: <tr class=\"data\"48: <thSavings <span class=\"description\"Funds set aside for emergencies.</span</th49: <td650</td51: <td 500</td<td728</td<---------- answered passed without this line of code. </tr! ! Device: [Asus f17 gaming] OS: [ Windows 11] Browser: [Chrome] thanks for such a go tutorial platform!\nHi thanks for the report. Could you share your full code here so that we can dig into what's going wrong?\nEdit: I backticks for clarity.\nThanks for sharing that but the code you shared passes the tests. That's expected, since it has in the correct place. If I remove then it fails, as it should. From your screenshot, it looked like you'd entered invalid code (i.e. without ) and managed to pass the tests. However, I've been unable to replicate this behaviour. If you have an example of invalid code that passes, could you share it here?\nfirst screen shot mentions step 15, the second one shows 16. Isn't the issue in the step 16?\nbut it is there in step 16 code\nyes in hurry i was not able to give accurate problem details. IT IS IN STEP 16 THANKS BRO\nSilly me newbie.\nOkay, that makes sense, thanks for clarifying. To fix this, there needs to be one more test that asserts that is set on the third element.\nsir did u get what i want to say? as if not possible is it allowed to express it on video call? if okay so? like on ms teams.\nHey we understand the issue and have a pull request open to address it. Thank you for reporting. We will get the fix in as soon as we can"}
{"_id":"q-en-freeCodeCamp-88d0a0e1c500b9f01bed1e6a43c440b3437d715f8a2f9cd432a6d1227434699f","text":"The test variable here should be prefaced with an or something like that to prevent colliding with a common user variable name. Valid code should pass No response All No response_\nFrom the individual tests: can be moved to the . This alone would be enough to make it not affected by such collision. Additionally using underscore after that, while not necessary also would be fine.\nThis is entirely user written code above. The user's choice of variable name conflicts with the variable name in the test suite, so we need to use a less common variable name in the test suite. A leading underscore is how I've seen that done in most challenges.\nWhoops - this one was my fault haha.\nTo confirm the fix: Within the , all instances of the variable in the tests should be changed to .\nI have this minor fix Please review Thanks"}
{"_id":"q-en-freeCodeCamp-1868101fab42b0bcda017e628d7d2740abd2abf09983a6f8f1996d7be7354877","text":"The English curriculum was as an upcoming change. A new \"Fill in the blank\" style challenge was created for it. When you go to one of these challenges and try to type an , it doesn't show up (sometimes). If you type it really quickly after a different character, it does show up. I'm quite sure the hotkeys are interfering - if you turn them off, the problem goes away. The is the one that we noticed, but there could be other characters that have this issue as well. Fill in the blank style challenges the codebase with the upcoming changes shown to one of the fill in the blank challenges: http://localhost:8000/learn/a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/right to type an in the blank, it doesn't work of keyboard shortcuts in settings, it does work All keys to work all the time. Related discussion:"}
{"_id":"q-en-freeCodeCamp-ee18ceb9bcccd91edf8c9ff247c3bd6380d5696be795f2f5564c3d5e35a7c882","text":"The following valid code does not pass for of calorie counter project. The issue is with this line here If you remove the semicolon then the test will pass We will need to fix the test to make semicolons optional so the camper can pass with or without semicolons. here is the file you need to fix Please read through the docs first. And we don't assign issues. If you are interested in working on this, work on the fix and create a PR. Happy coding! This code does not pass even though it is valid Semicolons should be optional and the code above should pass 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"}
{"_id":"q-en-freeCodeCamp-bf925e5510cd94fe8882e5a5fc8e56b560da73e3ab9030679837a119e65438cd","text":"The test is failing if there isn't a space between and . This fails: Test should pass without a space between and . No response N/A No response"}
{"_id":"q-en-freeCodeCamp-f9bb0b76e1d1baecb3f89f97bb1398c552090346a8726cc608dc62daa37b8e2e","text":"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\nThank 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.\nHi I've created a PR addressing these changes."}
{"_id":"q-en-freeCodeCamp-fa9d3d896a8feac20b08a2cd7a9fd968b1fe213b20a2af22d9ab18db419f1a62","text":"So the problem is that the “hint” where it tells you what you should’ve have coded it tells you that you should have “data” as key, when you code that and it doesn’t work it tells you you should have “myTaskArr” as key, but that’s wrong it should tell you “myTaskArr” as “value”. So I was trying to have 2 keys, and obviously it was always wrong. The hint should tell you that \"myTaskArr\" is a value, not a key as it currently says. ! Device: Desktop PC OS: Windows 10 Browser: Edge Version: [e.g. 22] 120.0.2210.121\nNote: Due to PR adding one more step, earlier in this project, the relevant step in codebase is 49 now. Although that change did not yet reach the production at this time."}
{"_id":"q-en-freeCodeCamp-a9a20e6fb4828abe2d97db8f2a0dbd64d972923038d3879afd3152d7f904ea02","text":"The description here is missing backticks for the number zero. Here is the new updated description. 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 Here is the correct file that needs to be updated. Note: Even though the file says step 62 instead of step 63 that is on the site, this is still the correct file that needs updating. We recently made changes to the ordering and those changes haven't shown up yet on the live site. Happy coding see explanation above see explanation above 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\nStep 145 has the same issue here Here is the file that needs to be updated here is the correct use of backticks for the number zero in the last sentence here"}
{"_id":"q-en-freeCodeCamp-07d4a66ff07b253f027cbf2a27d3a6c0ff3f63bb8e279ef0254900dc17fa5e4a","text":"Describe the bug Task 37 requires typing in one of the blanks. This can be problematic due to the letter, which might not be present in the used keyboard layout. Expected behavior I don't want to say to use completely different word for the fill the blank, as at some point there might be no other choice. There could be some kind way to ease up procuring of the letter in question, for example including it in the feedback, so it can be copied.\nHi I would love to work on this. If someone could point me in the right direction, that would be amazing!\nHi Thank you for being eager to contribute. This issue has not been triaged yet. Feel free to share your insights and ideas on the matter. However as far as the code contributing, take a look at the issues with label. 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. Thank you and happy coding.\nYes, I think in both of those challenges we can update the \"Don't forget the stress mark.\" in the feedback to: \"Don't forget the stress mark ().\"\nI will open the issue to contribution with this as the solution"}
{"_id":"q-en-freeCodeCamp-aeb123045e55ed3ca93a0b150d76e7738cb3f868f6a3f9473295b5db406483ea","text":"A camper on the forum had issues with passing step 37 of the pyramid project This was their code Their code is correct but the tests expect a certain order of The tests should be updated to expect either correct answer see explanation above see explanation above 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\nconst character = \"#\"; const count = 8; const rows = []; for (let i = 0; i < count; i = i + 1) { (i); } let result = \"\" for (const row of rows) { result = + ; (result); } This worked for me, it took a while but realized I needed to swap the result with the row... This was helpful thank you\nThank you for this,I was really stuck"}
{"_id":"q-en-freeCodeCamp-4be4c06a2e93db01cf60910074389899515ad47983d67a7d1e4df2d184a42091","text":"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\nI agree that both versions should be accepted since they are valid solutions."}
{"_id":"q-en-freeCodeCamp-78f396ad66fdcf58e169a99f61c1bb00ed339fb81f724e2a5abb5503f8116fb9","text":"Currently on step number 5 there's a note that reads Note that when reassigning a variable that has already been declared, you do not use the let keyword. As it stands this note is incorrect and unnecessary. No code, just instructions re-wording. The note could be changed to: Note: You can only re-assign a variables that has been declared with Or we can simply remove it altogether instead. <img width=\"1217\" alt=\"Screen Shot 2024-05-02 at 10 31 38\" src=\"\"- Device: [Laptop] OS: [MacOS 12.7.4] Browser: [Chrome] Version: [124.0.6367.91] No response\nThe note is correct. I think you are interpertering it wrong? It is saying does not need to be used when re-assinging the variable with a new value. edit: It is not saying that you can use any kind of keyword like or\nI understand what's it's trying to convey, but it's written in a confusing way. Here's the text directly copied into ChatGPT for some additional context: <img width=\"820\" alt=\"Screen Shot 2024-05-02 at 11 01 54\" src=\"\"\nText refers to potential situation when both assignments are using , ie: Depending on where exactly both are used, this can result in . - - x = 10; There's no on this line. It's one of the cases when chat doesn't know what it's talking about.\nHi thank you for creating the issue. As Sem pointed out, we don't think the note should be updated to because the new version communicates different information from the original. I think the confusion came from the word \"declared\". The word isn't needed since \"reassigning\" already implies that the variable has been declared, so I'd propose changing the sentence a little: cc'ing for input, since you're much more experienced with this kind of change than I am\nThanks for the input your proposal addresses the issue I presented\nThat change works for me. Let's open it up for first timers 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 js let programmer = \"Naomi\"; programmer = \"CamperChan\"; ` Happy coding"}
{"_id":"q-en-freeCodeCamp-8e65f225c1a5cd51ab405d9298c02ec8e9590c3bfa58ebf801795d278c129122","text":"There is a typo at the following step: It should present the text: Device: Laptop OS: Windows 11 Browser: Brave Version: 1."}
{"_id":"q-en-freeCodeCamp-3cd71940ee3b93ec6139f35e4cb0de31947a1b5a05de8d0c71446a7df21bafd6","text":"In the first paragraph, on the 2nd phrase, you can read: . Rectify to the following: No response . No response\nThanks 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: 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.\nI would suggest we remove \"those\" and keep \"the\" so we are not repeating \"those\". I would also suggest using \"attribute value\"\nThe next paragraph reads pretty bad as well. It's just confusing to read. Maybe we can come up with something better. Edit: take two Or something like that?\nI know the first line already mentioned \"paragraph elements\", so it is presumed that the second line is referring to that type of element. But as a newbie, when I read \"to select the element with that attribute value\", it seems any kind of element. Could we be more specific, and edit to \"(...) to select the paragraph element (...)\"?\nIt is selecting by so the element type doesn't matter. Saying what the element type is seems redundant to me. But if you or anyone else feel it would make it more clear, then I wouldn't be opposed to it.\nYes, you are right. Mentioning is what matters."}
{"_id":"q-en-freeCodeCamp-694a072215ae702ece27c4fe6f7af6c6880197ed837023de6e2418b62fec4be3","text":"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: File: 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."}
{"_id":"q-en-freeCodeCamp-493a68277a02a81ae39ea87707da3484b4270fecb5d444bcc424847a41a088d1","text":"In step 10 of Luhn Algorithm, we teach campers how to create a substring using the operator. I think the explanation is a little short and could improved by: Adding comment next to each example, showing the result of each operation (we are currently communicating the value via the variable name, but I don't think it's clear enough) Mention that the starting index is inclusive, and the ending index is exclusive Additionally, I think we could: Change to to have the syntax more self-descriptive Mention that the default value of is 1 Perhaps the description should be changed to: python mystring = 'camperbot' mystring[0:6] == 'camper' # True my_string[0:6:3] == 'cp' # True `\nDifferent project but same kind of example: I remember we decided not to use because of translations, but using them in the code example and then explain what they mean is fine :+1:\nare we able to open this up for contribution?\nPersonally, I'd prefer to change the snippet into the following: I agree with all the rest.\nI've updated the issue description with Dario's code snippet. This issue is open for contributions. We typically do not assign issues. Instead, we accept the most quality contribution followed by the one that is made first. 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. Happy contributing.\nWhoops, sorry. I just noticed that Farhan is assigned to the issue. Are you working on this or could we mark this one up-for-grabs?\nYeah please mark this as up for grab"}
{"_id":"q-en-freeCodeCamp-867030372fbd448a158e4df3e60290322f4827d743c61b6e1b8c4f4129d6d918","text":"Step 22 of build a Todo app can use a better a hint or a short reminder on destructuring if one can be into the instructions. If we forget to put the curly braces around the parameter names to destructure them, the hint only says: You should destructure id, title, date, description as the parameters of the callback of your forEach(). A better hint would be I think parameter destructuring was only covered once before this project. (though I may recall that incorrectly) here: Either a better hint or a reminder of parameter destructuring in the instructions would be helpful. No response N/A No response\nHello. I would like to work on this issue. Please assign this to me.\nLet's go with this text."}
{"_id":"q-en-freeCodeCamp-51bcc5efa8857f0d5651211ee245bcb79bd0e8cc5266d4e068df8dd9e725a145","text":"The instructions for step 103 of the spreadsheet project request that a range be created from an array. The say: My solution (listed below) tries to do that by passing in the first number found in nums and the last number found in nums as arguments to the range function. This solution is not accepted and the hint says: On reading this initially I have no clue what this hint is attempting to say. Does it want the range to span from the first number of the array to the second number only? Does it want the range property to define a function that takes two arguments? I'm really not sure what it wants. After some investigations though it seems that this step wanted the range to be between the first and second numbers of the array. I think this confusion could have been easily avoided if the instructions just said that. Change the instructions to say: numsnums No response N/A No response\nOne of the tests is checking , so it's clearly intended to use first and second number."}
{"_id":"q-en-freeCodeCamp-d2ee317ccc60294a809a518b2e6dfb985d113573f551aaf8567199e471e68d35","text":"The code should not be centered in the preview modal. or to on button for certification project with code ! ! 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_"}
{"_id":"q-en-freeCodeCamp-3c2973400fe61ed4bcdffcfb8de9b08b6abb6a04e4b848d21be3b6a586e7f28e","text":"typo error on the console warning: If a large straight is rolled, your checkForStraights function should enable the fifth radio button, set the value to 40, and update the displayed text to , score = 0. i recreated the last step to get to the warnings. it's supposed to say :If a large straight is rolled, your checkForStraights function should enable the fifth radio button, set the value to 40, and update the displayed text to , score = 40. ---- not 0. <img width=\"442\" alt=\"Screenshot 2024-08-25 at 8 08 39 PM\" src=\"\"- Device: Mac OS: Ventura 13.6.9 Browser: Brave, Safari Version: Brave - , Safari - Version 17.6 (.3.11.11.7, ) No response_\nThanks 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: 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."}
{"_id":"q-en-freeCodeCamp-55e02a4ddabdb0d3d11c965cc479e6e4748e9a816f8473cf78f8024180ac85db","text":"The challenge or lesson asks the user to provide answer by looking at or by executing the sample code provided in front of him/her but the sample doesn't provide any output in console. When a user try that piece of code he/she should see an output in console. 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\nCan I work on this and just add the myFunction(); at the end?\nhi Thanks for your interest in contributing. This issue has not been triaged yet, and a solution has not been agreed upon. Once the issue is open for contribution, you are welcome to create a pull request to reflect the issue consensus. Please also note that we typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue.\nOk, yes, it makes sense to add a function call in the code snippet. I'm opening this up for contributors to work on. This is the piece of code that needs to be changed: 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.\nHi I'd like to work on this issue and submit a pull request to address it. This will be my first issue. I just wanted to know if the video-solution is correct on that page. Just seems to say '2'. Is that intentional or is it missing a zero. Either way I'll add the function call in the code snippet and send a merge req right away. Thanks!\nHey We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labeled 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."}
{"_id":"q-en-freeCodeCamp-a0576a87f4cf2a28a4895412e10465c1a7b265fb291212aa477a546c7e500330","text":"I suggest changing the phrase 'template interpolation' to 'template literals,' because are correctly referred to as template literals, which support string interpolation. ! 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_\nit should be \"string interpolation\". Template literals are already mentioned a few words before, it would be extremely redundant. I'm opening this issue for first timers to make the change \"template interpolation\" -\"string interpolation\". This change needs to be done twice in this file: 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.\nSorry for the misunderstanding. I need to change the text from 'template interpolation' -'string interpolation'\nHi, I guess has raised his PR with the needed change. I haven't contributed before to any open source project. I thought this was an easy one to do to get started. Please tell any easy code or non-code contributions to be made. Happy to help.\nI am able to make the required change and happy to start open source contribution with hacktoberfest . Kindly assign this issue to me.\nWe typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labeled 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.\nThis pull request resolves the issue of incorrect terminology in the JavaScript curriculum where \"template interpolation\" was used. The correct term is \"string interpolation,\" as template literals support string interpolation. I have made the following changes: Replaced \"template interpolation\" with \"string interpolation\" in the two locations within the file. Fix :\nAfter reading the contributing guidelines, I now understand the mistake I made in my PR."}