diff --git "a/freeCodeCamp/c2i/dev/corpus.jsonl" "b/freeCodeCamp/c2i/dev/corpus.jsonl"
new file mode 100644--- /dev/null
+++ "b/freeCodeCamp/c2i/dev/corpus.jsonl"
@@ -0,0 +1,131 @@
+{"_id":"doc-en-freeCodeCamp-b2069b3c57a9b071d733e1e6e2c4d046c2011dfe13ff248c0c859beb27109278","title":"","text":"In RWB, the placement of the instructions interrupts the code and makes indentation unclear, especially for a beginner that may not know what to look for yet. I noticed several instances where putting longer, uninterrupted part of the code in the highlighted editor might help with clarity. <h2Examples</h2<a href=\"\"Step 21</a: change the error message or expand the highlighted code. (Error message when h3 is in the wrong location: \"There should be an h3 element right above the second section element's closing tag.\") <a href=\"\"Step 23</a: include in highlighted editor to match the instructions (\"A figure caption (figcaption) element is used to add a caption to describe the image contained withing the figure element.\") and to show the placement of within . <a href=\"\"Step 50</a: include in highlighted editor to match the instructions (\"The legend element acts as a caption for the content in the fieldset element.\") and to show the placement of within . <h2Proposed solutions</h2- Expand the code on case-per-case basis. Permanently move the instructions box on top of the code editor. (I think that would make everything clearer and more accessible with well defined sections on the page, but I imagine it would be harder to implement now.)\nI don't believe we would go this route, as the instructions UI was specifically designed to allow us to highlight the section of code a camper should be editing. I do agree some of these regions could be tweaked a bit\nThank you for reading through it! I will admit I that secondary suggestion because of a personal issue as well, as I find the page a bit overwhelming and every time I click on the next step, it takes me a while to find and re-focus on the editor. I think there's just a lot going on visually, but I'm not a UI/UX designer so I don't have specific suggestions except for the fixed placement.\nI'm fine with changing the three lessons mentioned here, but we could maybe use a discussion on how those regions should be. There's probably going to be many steps where the editable region could be bigger or smaller or different. Maybe we need some hard rules on how to apply them. Something like - for HTML steps, include the parent element in the region. For CSS steps, include the whole selector."}
+{"_id":"doc-en-freeCodeCamp-b0cf46839763ada4c682cd2d75858172e09be4772a7b94059a0e810521c2ce6c","title":"","text":"There may be instances where rules like that don't work out so well. Like for the first steps of the Cat Photo project, we may want to be more specific about where to add code - and on later steps or projects, more vague. So I don't know.\nI did bring this up, but we were on the fence with:\nYeah it seems like something that's more of a case-by-case basis than to have hard and fast rules for. My proposed \"general\" approach would be to encapsulate anything the instructions mention. So if the instructions say \"write a h2 below your h1\", the h1 should be within the editable region.\nTo try and get this issue resolved, I vote for these changes: step 21: change the hint to \"There should be an img element right after the closing tag.\" step 23: use op's suggestion step 50: use op's suggestion\nThank you for reporting this issue. An easy fix would be to scroll the editor so the instructions are always almost at the top of the \"page\". That way the eyes know where to go on each challenge. (right now it scrolls to the center) I am interested in knowing more about this: \" it takes me a while to find and re-focus on the editor.\" Are you having difficulty locating the instructions? do also look around for the tests and the submit button? More context is appreciated. We ultimately need to usability test this with people who have not seen the curriculum.\nHello, sorry for the late reply. After seeing this notification, I opened the curriculum on a random step to see if I could provide you with more information. I mostly forgot how the page was structured and my eyes just ran across the page in no specific order. \"Check your code\" was the first text I read, as it draws the most attention, and then \"\". I believe that would be very helpful! (I think it would also be nice if the navigation breadcrumbs were more subtle, and if the buttons like \"\", \"\" and \"preview\" looked more like toggle buttons – now they remind me of tabs but disconnected from their sections, and they also draw more attention than is perhaps needed?) Thank you for checking in on this!\nThank you for your feedback."}
+{"_id":"doc-en-freeCodeCamp-bc7b9b8a758504b5c8e59c4a936a443badbcc26126dc45781f483889454d9f25","title":"","text":"Describe the bug Sass pages with invalid syntax occasionally timeout To Reproduce Steps to reproduce the behavior: to in in the console (sometimes) Expected behavior The following should appear in the console: Since this is intermittent, here's a gif to demonstrate: ! Additional Context When the error appears it does so very quickly, so it is unlikely that this is due to a genuine timeout.\nHey Oliver, When I clicked on the link, I reset the code, and completed the challenge as it should be completed. I came across a error, and was unable to run the tests. However, after resetting the code, refreshing the page, and pasting in the code you provided (missing ), the error you mention appeared, but does not disappear. So, I suspect it has to do with the page first load, because I can get the error only if I: 1) reset the code 2) Duplicate the tab 3) Input the incorrect code (missing ) !\nI tried method but that didn't produce the bug. I am able to reliably reproduce the bug on Chromium & Firefox with the following steps: the page (new tab & refresh can both produce bug). delete & re-add the character from line 9, fast enough that the new state does not display in the console. step 2 on deleting the . If done correctly the message will display instead of an error, even though the console input is incorrect. approximately 3-5 seconds for the timeout message to appear. Note: it can also be reproduced where by in step 2 you end on re-adding the but it's harder to tell if the bug has happened. It must have something to do with the console state change and the output error check conflicting.\nI worked on this issue on my old computer that is very slow and on my main PC (with a dual boot). On my old computer I have the same result as regurlaly timeouts. On the new one to have this issue I have to paste 3 times the piece of code to reproduce it. But everytimes, this is a real timeout (5ms, I put 'new Date()' on the code)."}
+{"_id":"doc-en-freeCodeCamp-c8789507c66999cca207524f16d1c267e9bce8e16ee622494734330875dff426","title":"","text":"We can upgrade the source code one \"execute-challenge-\" with this kind of stuff to have a best message, but still the problem : <prelet errMsg = 'error'; if (err === 'timeout') { // eslint-disable-next-line no-ex-assign errMsg = ; } else if (Array.isArray(err) && err.length0 && err[0] === 'timeout') { // timeout: 5ms errMsg = ; } else { errMsg = err; } (errMsg); yield put(updateConsole(escape(errMsg))); </preso the result will be \"Server response timeout\"\nWhile this is old, it's still reproducible, unfortunately. A PR to improve the warning would be welcome.\nI’m currently taking a look into a possible solution on this!"}
+{"_id":"doc-en-freeCodeCamp-919ddc19acc4dba1018af106a645ad52a7f5124c05632006b0bfbd171296c80a","title":"","text":"Describe the bug When you enter a challenge using a mobile device, the tabs below the main header are displayed with untranslated text To Reproduce Steps to reproduce the behavior (mobile device): to untranslated tabs below the main header Expected behavior Tabs text should be translated. Screenshots Spanish site ! Chinese site ! Desktop (please complete the following information): OS: [Windows 10] Browser: [chrome] Version: [88] Additional context Those strings are not available yet on the Crowdin platform."}
+{"_id":"doc-en-freeCodeCamp-1cda39b0cf17a9d6add07c9f522b747fcb98ca9bcc31d7cb2beda8ce32210224","title":"","text":"Keywords in the following sentence should be wrapped within . Update the file with this change:\nThis issue is open to first-time code contributors to this repository. The file that you should be updating is linked in the original post. 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.\nI can work on this.\nAre you still working on this?\nI submitted a pull request () that is waiting to be reviewed.\nI would like to work on this.\nI can work on this."}
+{"_id":"doc-en-freeCodeCamp-a24c8c7ebd91053e16ddaba858c286afd488b6139f8aba41b662626472e3e7a1","title":"","text":"We have instances which is used to provide spacing for both side of the component to wrap it up in specific space Example: We can make the Spacer component smarter, and allow it to accept children, so the code be like. But in doing so, we need to: change the current values and how the padding is calculated, the old layout shouldn't change with the new spacers. change which padding has the new value, I think paddingBlock, which is paddingTop and paddingBottom, is the new padding property . I am requesting this because this will make live simpler, and we have to worry about less elements while controling the layout, and if we have specific cases, we can still use\nThere is an abstraction with , we need address, it's better if we can specify the direction of the padding. but this can be sorted in another issue, for now to solve this issue please allow to have children prop inside of it, but the current styles of the curriculum shouldn't change. 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.\nHey I have few questions while looking into this issue are few files where we have used Spacer, so may I just change wrap the content where ever needed or it would be handled in new issue? (I guess it must be done in other issue, as it would be easy to maintain) have implemented the children props, so may I raise a PR? Will break this issue in 2 other issues as well. 1 for wrapping the places it has been used, and 2nd for specifying the direction. I was wrapping and trying it out, I found out that Spacer has been used at every 2nd-3rd line of code, so do we need such a wrapper which would give spacing to all components present inside it or only to the parent component? EG: If we have 2 divs wrapped inside Spacer, then does both div have the spacing around them or only the outmost div."}
+{"_id":"doc-en-freeCodeCamp-c9dffb843102fc40079dcdac44da2aaf489b00d7ac16701bd29f6d263fda09b0","title":"","text":"sorry for the delay, it was difficult to understand what you mean without looking at an example of code, so to answer you: yes the direction will be in a second issue, but the spacing and values should still be in this issue, so the pages won't look different Of course, please raise a PR after reading the guideline, nicely done . The Spacer shouldn't affect the children inside of it, think of it as creating a container with margin-block to space the area of the children inside of it from other areas\nI guess we could close this issue\nwill be closed when the height is removed in the other PR"}
+{"_id":"doc-en-freeCodeCamp-7e3bad1c6d71dcafc418f1cb8a12be4a9cc226f55372a4ae8a2365dad536b189","title":"","text":"Is your feature request related to a problem? Please describe. Currently the certificates lack any white space along the top border, making them difficult to screenshot and/or print: ! We should add some white space to the top of the page so the certificate is centered."}
+{"_id":"doc-en-freeCodeCamp-4ef68b7872a6418004b20f92f7629078a450b2fdecfc229c19da06d381b11a7e","title":"","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":"doc-en-freeCodeCamp-7742d5b906bce0f1ffb52b837fddbeba046261289ad4db79db8432293b520a1d","title":"","text":"please clarify the instructions for step 39 of JS Beta Build a Music Player Currently they consist of 2 sentences: \"Add an else block to handle the current song’s position in the playlist. Within the else block, set the currentTime property of the audio object to the value stored in userData?.songCurrentTime.\" The first sentence doesn't seem to relate to the second. It is not clear how 'the current song's position in the playlist\" is affected by the actions requested of setting the audio object's currentTime? This makes me think that there's a mistake in the first sentence (or maybe I've misunderstood what it is trying to say so it needs more clarification) N/A N/A No response N/A No response\nI don't think it has anything to do with the playlist order. The only thing is used for is pause/play (it gets reset everywhere else). Maybe it can just be:\nMy thoughts was that the else block was designed to continue playing the song at the place you stopped it. The current song has been chosen and it's same id of the song. In the block, we're setting the time to zero. In the else block, we're setting it at the old time.\nFYI: I attempted to test pausing and restarting the song but it always restarted from the beginning.\nIn what step did you test it? If you go to the last step, the play/pause should work as intended (or to whatever step has it implemented). Pausing saves the audio element's current time to , and playing restores it back to the element's current time when is available.\nI see, I thought I would be able to pause and play something else then come back to the original selection and it would start from where I stopped (but I don't think the code was created for that).\nNah. It only resumes and plays back for the current song. Once you switch songs, it forgets where you left off on the old one.\nI would be fine adding something like \"This allows you to resume the current song at the point where it was paused.\"\nThis looks like something that can be fixed by \"first time\" code contributors to this repository. Here is the file that you should be looking at to work on a fix: Change: To: Please make sure you read , we prioritize contributors following the instructions in our guides."}
+{"_id":"doc-en-freeCodeCamp-9fa85a30ec2ddbaf736927fb0466d9f3c273dd712b32d25b6c74e3e871d6c7ea","title":"","text":"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-requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing."}
+{"_id":"doc-en-freeCodeCamp-1db1238151c9c444f5bb1bca550446df338bdfda6f68358dc812c4955455ff09","title":"","text":"The instruction are not clear, right now it says Edit: This is actually step 120 in the main branch Set monsterHealth to monsterHealth minus the power of the player's current weapon. Remember you have the currentWeapon which is not initialized variable and the power property on weapons array. No response Device: Laptop OS: macOS Browser: Chrome I think it should be more detail about what and where is currentWeapon, power property and how to access it like in previous.\nIt looks like currentWeapon is initalized with the value of 0 here Then it is updated over time throughout the project. I think for that second sentence it should be clear about syntax on how to access those values since beginners are still struggling with that. Being more explicitly will help with confusion on the forum posts. Let's go with this change.\nThis has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the Happy coding"}
+{"_id":"doc-en-freeCodeCamp-8e4542f91b669ae2b68b983782c1892864cd02b7f65829c964b78000553cf827","title":"","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":"doc-en-freeCodeCamp-77146a36414f6764fb892d5b7c3ef1ea7f02dbd1fa36e4987ba1b72bef152033","title":"","text":"Throughout the curriculum, we often have campers name variables that represent booleans with the prefix of or which follow standard convention. But we never really explain that to them. I think that step 17 would be a good place do that. js let isRunning = true; let hasCompleted = false; ` 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\nThis has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the Happy coding"}
+{"_id":"doc-en-freeCodeCamp-ef25c32cbb98365a4e2f9d068fd3426122246a4e306436235b64cf14102a3749","title":"","text":"The copy here seems misleading especially for those coming from no knowledge of javascript. It looks as though jQuery isn't also Javascript. ! [] 1) jQuery is a powerful tool for manipulating HTML elements. 2) It's a lot easier to use than JavaScript itself, so we'll learn it first. 1) jQuery is a powerful javascript framework for manipulating HTML elements. 2) It's a lot easier to use than plain JavaScript itself, so we'll learn it first."}
+{"_id":"doc-en-freeCodeCamp-354848720ae081f596015b05abd7038ec76bf14e0a952b8cfd2f8b33a60969e9","title":"","text":"<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --In the challenge below, the alt text for the diagram is set to \"a diagram of non-overlapping concentric circles\". But if my understanding is correct, they are not \"concentric circles\" (circles which share the same center). <!-- Add a link to the coding challenge with the problem. --Coding Interview Prep Project Euler Problem 199: Iterative Circle Packing <!-- Add a clear and concise description of what you expected to happen. --The alt text should be changed to \"a diagram of non-overlapping circles\" or something. (I'm not a native English speaker, so please fix it if there is a better description.) <!-- 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: Laptop OS: Windows 10 Browser: chrome Version: 96.0.4664.45 <!-- Add any other context about the problem here. --Originally reported in a comment on Crowdin duing translation.\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 like to work on this.\nHey Issues are typically not assigned to a specific person, other than long-time contributors. You can read more about this at Issues labelled with or are open for contributions for all. Please make sure you read . Join us in or if you need help contributing, our moderators will guide you through this.\nsorry about that, as this was my first time in freeCodeCamp, I'll make sure to read the contribution guidelines"}
+{"_id":"doc-en-freeCodeCamp-4f6e61eed23a55eb403fbe4975c3f1827bc5fc1b16a5555b494571c1e656d1a6","title":"","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: using the code in this file: the challenge is passable by uncommenting lines 56-59 if (curr === null) { (curr, \"curr\") return null } The wording of the test is \"Trying to remove an element that does not exist should return null.\" yet the assertions only test for removing a node that does not exist in an empty tree. What about removing nodes that do not exist in a tree that has nodes? ` Add a Link to the page with the problem: My pull request: 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):\nTo summarize the issue: Test checks only if trying to remove non-existing element from empty tree will return null. It doesn't check if the same happens for removing non-existing element from non-empty tree. This can lead to implementation, which doesn't handle the second case at all (and even as in example above can end up with error), and still pass challenge."}
+{"_id":"doc-en-freeCodeCamp-768dfbef6fd2c8db4b27f92ceeadb0f42e1aa8878a8cb424c7316efbd14a5113","title":"","text":"This step comes up a lot on the forum and I think it is because we have never really explained what method chaining is or showed an example. Let's update the description to include an example so they know what to do. We should also explain why the join method is needed here so they better understand what is going on. js const exampleArr = [\"This\", \"is\", \"a\", \"sentence\"]; const sentence = (\" \"); // Separator takes a space character (sentence); // Output: \"This is a sentence\" js ().join(); ` 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\nThis has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the Happy coding"}
+{"_id":"doc-en-freeCodeCamp-e7e80ee67e6103b5fcfce5a405ddcc1b524bf1ab209f31815d534e2fe68558dc","title":"","text":"In the following test-case expected ['TWENTY', 80.00], but only ['TWENTY', 60.00] available. I'm going to fix it and make a pull request."}
+{"_id":"doc-en-freeCodeCamp-f94d87e06310cc47d72a0c37f54a22280bb0a66f651b9b1675c4846288b3d28e","title":"","text":"There is a bug in the challenge learn-basic-debugging-by-building-a-random-background-color-changer/step-8 | when entering it passes the test; ! Device: [MacBook Pro 10.15.7] OS: [ iOS Catalina] Browser: [Brave, Chrome] Version: [...] passes test, when it shouldn't`\nVery interesting and confusing finding! This is the passing test: Here's part of the explanation why it passes: Setting to also would pass."}
+{"_id":"doc-en-freeCodeCamp-a32974bd7a772fefe3f95908cbd249b18af2204d04611d85e04e7fc572c5101c","title":"","text":"No need to use here since the array is not re-assigned in later steps. We used for other arrays in this project that aren't reassigned. No response All No response\nHello, I fixed this by doing the following: 1) went to 2) found the ID of step-162 () 3) went to the repositories code and searched for the markdown file through ID. 4) the markdown file 5) Updated the markdown file to use 'const' instead of 'let' ! After this commit is approved, this should be able to be closed.\nAll of the seed code for subsequent challenges would also be changed.\nI am not sure what you mean by this. Is there anything I can do to learn this? Are you referring to all references of 'let' initialization to be changed to 'const' in future steps?\nNot quite - the answer to this step becomes part of the starting code for all future steps. If we change the instructions to use here, then then starting code on all future steps needs to be swapped to reflect that.\nHi, I raised a PR to fix this"}
+{"_id":"doc-en-freeCodeCamp-19d48e16168913b86bd67627c69fd5caf1bdaa359d113da7aff7e0d166561401","title":"","text":"We previously attempted this in , which had its own set of issues. We need the Plyr to work natively with Youtube or alternatively make the YouTube embed not show related videos.\nCan I work on this ?\nI think this is resolved by a recent PR. We are keeping this open for verification. We have lots of other issues open which we could use your help with. Thanks."}
+{"_id":"doc-en-freeCodeCamp-6f50ec08ac22750037b3a5bcb887e450cb35ba4c3a953c6ceeefe2d2af9e6d53","title":"","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: This challenge has an example of sorting like this: ` This example uses a bad compare function. In recent changes to Chrome the following example no longer properly sorts the array: The compare function needs to return a number to be able to sort an array properly. This can be fixed by changing the compare function to return a number: Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: 70 Operating System: Windows 10\nThe above return statement only returns 1 or -1. To preserve the original order for elements which have the same value, you need to test for the condition where they are equal. For example, to preserve an elements original order when equal, you would write: While in this particular example, you may not be able to see the difference, I will show a different example below, where the difference can be seen. Let's say you have the following array of objects: The 2nd and fifth elements have the same letter, but they are in different positions. Let's say you want to sort the objects in alphabetical order and preserve the original sort order of the elements with the same letter (in this case those with letter 'b'). This means, after the sort, letters should look like: If you just create the following sort function without specifying a return value of 0 when the letters are equal, it would not sort correctly in the new version of Chrome: The above produces: instead of the correct version: To preserve the original sort order for objects with the same letter, you must use the following sort function: I think the example should reflect the better practice of specifying a return value of 0 for elements which are equal in value. This matches the actual requirements of the compare function of returning a value of 0, -1, or 1, so I believe the example should be written like:\nI am interested working on this issue\nAlthough the example used in the original text doesn't require ordering I agree adding would be fine. As much as I like ternaries, I'm not in favor of nested ternaries. As a general rule they . If possible I'd keep the text challenge clean and readable."}
+{"_id":"doc-en-freeCodeCamp-a26ac6c001e075b7e4f9ab552a4ad3336196ab144309edb6a2e3737a46bbb717","title":"","text":"Maybe the good ol' if statements are fine here:\nLet's see what says after my last reply, before we assign it to you.\nYeah, even I think it is better to make it in the form of as many people still get confused with nested ternaries.\nI would take a different perspective here. For the purposes of the tutorial, I suggest that nested ternaries are the way to go. If people do get confused, this will encourage them to look up their doubt and they will be better versed with ternaries for later. I have opened a PR with the edit implementing nested ternaries.\nOn second thought, and the fact we already have a nested ternary lesson in basic JS section. I think it's fine to use a nested ternary. Good point as well.\nMake sure to reference that it closes this issue # if you have not already done so.\njust remember to ask first before you create a PR as there might be other people waiting to do one, like had asked here before if he could work on it? sorry about not getting to do a PR for this issue, there are other issues you might take a look at.\nI will take care of this in future PRs. Apologies for my mistake .\nComment on issue\nWhat are these PRs you have referenced?\ncould be spam.\nThe sample code on the FCC website is still the old version. I noticed on the challenge's GitHub page the sample code is different than what I saw on the live FCC website. I did this challenge on December 19, 2018. The sample code on the FCC website website is the old version (different from the GitHub version). I thought that the GitHub version of the challenge was reflected on the FCC site. Does this happen at regular intervals, or do updated challenges need to be pushed live to the site? As a side note, the sample code on the GitHub page and the live FCC site doesn't work in Chrome 70+ for reasons addressed above. May I update the sample code to a version that works? In this case, the description would also need updating to explain the code. Should I make the changes as a pull request? Sorry, I'm really new to FCC and Open Source contributing in general. I just want to make sure I do things in the most efficient way."}
+{"_id":"doc-en-freeCodeCamp-e0d5abeab1d95d61e01b17d7929bba42758121c2f436eabd4b67ba25f84d86b8","title":"","text":"I propose the following (the opposite of the reverse alphabetical sort suggested above): The old version that doesn't work in Chrome 70+: Here's the screenshot: ! Here is the link to the GitHub page:\nNot sure if I misunderstood you, by \"sample code\" do you mean the guide? is a PR for the guide, although it seems to be missing the fix for reverseAlpha ascendingOrder version of sort where the compare function is using subtraction is only (to be) used with numbers, not strings. Which is not explained, nor is the function name very explicit about that fact. On a side note: Personally, I would like to see the use of parentheses as I feel it makes the nested ternary more legible. Maybe also a version using (maybe just in the guide) I would also like to see a link to the MDN docs (and maybe a short explanation of how the method and callback works).\nRE: Sort an Array Alphabetically using the sort Method Challenge... Maybe not the cleanest but simply running this code: worked in my case :)\nHi I was not referring to the guide, but instead to the live/production and the GitHub version. (Now that you mentioned it, I checked out the PR you linked and noticed that even in the guide, the first example for an ascending sort does not work in Chrome 70+. I'll comment on that PR as well.) Here are screenshots and tables below summarizing the issue. In short, the sample code on the FCC site for ascending sort is an example of how to sort numbers. It works for numbers but does not work when applied to letters/strings in Chrome 70+. The sample code for the reverse alphabetical sort also doesn't work in Chrome 70+ but does in FireFox. I think it would be best to have sample code that applies to the challenge, and works across major browsers. ! ! PASS PASS PASS PASS Note: there is a typo in the second sample code block of the GitHub version screenshot. The PR you linked addresses that as well. Hope this info helps. Please let me know if anything is unclear.\nHi I like the brackets in the nested ternary. This may be minor, but I think a different arrangement of the nested ternary would be even more intuitive and brackets wouldn't really be necessary. I my suggestions as comments to the code blocks below."}
+{"_id":"doc-en-freeCodeCamp-52437a441bd683cd5e69fe7ad7683b6fd3384f66253716f103e9cfcf8c230f64","title":"","text":"They match the code on the MDN page, which states that the ternary operator is right-associative (details below). What do you think? MDN: Conditional (ternary) operator \nThe TLDR; The only bug is, Chrome used to accept boolean return values like Firefox still does. After Chrome changed their sort it no longer does. This is not a bug in Chrome, but incorrect usage of the compare function in the assignment text, this has now been fixed (site is not updated yet). The comparefn is supposed to return numeric values: 0 (a must be equal to b) 1 (a is greater than b by the ordering criterion) -1 (a is less than b by some ordering criterion) If the comparefn does not return numeric values it is not consistent and the sort order is implementation-defined (which is spec compliant). ascendingOrder (return a - b) version is not meant to work with strings, in any browser. It is an example of using a compare function for sorting an array of numbers using subtraction. You seem to be mixing the number (ascendingOrder) and string versions (alphabeticalOrder/reverseAlpha), not sure why. Your screenshot and table are confusing and as far as I can tell must be wrong. The screenshot shows Chrome failing to sort an array of numbers, using ascendingOrder, which is incorrect. Then your table shows Firefox passing on an array of strings, using ascendingOrder, which it does not. For both browsers, using ascendingOrder on an array of numbers sorts the array correctly. Using ascendingOrder in Chrome on an array of strings leaves the array unchanged. Using ascendingOrder in Firefox on an array of strings reverses the array but does not sort it. Just to be clear, ascendingOrder is meant to sort the array, not reverse it. It just happens to be shown in the example text on an array of numbers that is in reverse order and so sorting the array effectively reverses it. can't put the alphabeticalOrder version in the assignment text, that is the solution to the assignment. That is why I asked. deeply nested ternaries your last style example is pretty common, however, for what we have in the assignment I think a single line expression is better. My format suggestion is based on how prettier formats the code."}
+{"_id":"doc-en-freeCodeCamp-e458e885463275e60c62bea59a810160493d8ee982fd28b67b4c195e09c77970","title":"","text":"Last I'm not sure if this conversation on a closed issue is considered proper etiquette or not, I simply don't have enough experience.\nThe above analysis is spot on. Thank you for the great explanation and its fine to have a discussion in a closed issue as long as its on topic. Otherwise you can always create new issue.\nfunction alphabeticalOrder(arr) { return ((a, b) =a !== b ? (a < b ? -1 : 1) : 0); }"}
+{"_id":"doc-en-freeCodeCamp-2fe42f2b9517eac2800be886239fafcef2f043214b072fcbfc178850424aae7e","title":"","text":"Point 7. of instruction says: There is missing underscore near eye in the result text. The correct solution for this test is text: eye is a palindrome (with underscore) Instruction text at Point 7. changed to: ! 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\nThe result looks correct to me because the instructions have this note in the beginning If we remove all special characters from then we would be left with\nLook at the instructions for tests 16 and 17. The string includes all of the non-alphanumeric characters. But for test 7 the underscore is left out of the string.\nI see it now. I misread that as returning the string without non-alphanumeric characters. In addition to updating the test description the hint text will also need to be updated This is 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 User story 7 will need to be updated and the hint text here will need to be updated"}
+{"_id":"doc-en-freeCodeCamp-7615be58271d8c1729683fd3b316e25e1669309a926af6789852707bea7684be","title":"","text":"All numbers for descriptions should be in backticks. Here is the updated description Here is the file you will need to change 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. 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\nid like to pick up this, can you assign it to me pls\nWe do not assign issues to anyone other than long-time contributors and core team members. This issue is free to pick up for anyone interested in working on it. 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":"doc-en-freeCodeCamp-efc1044f1fe01397b30fe4eab8c0cbdfe3964f3cb62f3b6e15094fa9fdb020c8","title":"","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":"doc-en-freeCodeCamp-20d980aeecce55d0b063454aa1f299ae34f0959cab880ad4b64fbe0249292b16","title":"","text":"I followed Step 4 instructions. As I finished typing out the element, by habit I press + , and noticed that it accepted it, even though it shouldn't have as I was still missing the element It should have failed, as it's still missing the that Step 4 asked for ! Device: PC OS: Window 11 Version 23H2 Browser: Firefox 127.0.2 (64-bit) No response\nThis seem to also happen in other parts of the same course, such as Step 7 ! As you can see, it is missing its closing tag As well as Step 11 ! It's missing its closing tag yet the Step still validate it\nCan you please open a new issue for the form element. I'm guessing the browser is auto closing it, and we don't have a regex test for it. It should result in a valid form element, because the browser will close it. However, the element technically does not have any \"Tag omission\" so it should have an end tag in the HTML (even if it gets to the DOM by the browser).\nDone"}
+{"_id":"doc-en-freeCodeCamp-9b35ea78e3f08c63240778bd827d61747b01a83c240affe1a9d19f0458c9e9f8","title":"","text":"Currently the map looks like this: ! I think it would look a lot better if we made more use of the available space. Something like this: !\nI can fix the css in a separate PR, if you like. Unless you're already handling it, of course.\nI think it is handled now in the PR already. I moved things into the Grid system\nThat PR still has the heavy indentation: !\nYou are correct, if you have something going please go ahead and push to the PR. I am done with the basic consolidation of the views that I was going for."}
+{"_id":"doc-en-freeCodeCamp-429fb45acbc69ad73c608e1f9733956d129d85266c80cd4335c7322112cb48aa","title":"","text":"Following the conventions decided upon in , we should change the instruction in the \"Remove Elements from a Linked List\" challenge - to Add a Link to the page with the problem: The file to be changed is . Since this is a simple change, we would welcome Pull Requests from first time contributors.\nI can do it. Should i make the same change in the portuguese version too?\nNo, just make the change for the English version."}
+{"_id":"doc-en-freeCodeCamp-96104283f9a4fbf0245de80ba67e4fcab39ca33c00194478086c584d94e603fc","title":"","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":"doc-en-freeCodeCamp-10c0af9624d12d94236e5337205975d63639fb79ec6da4b9fa07c03879222dc0","title":"","text":"The instructions are really confusing and could be rephrased. ! I don't think what is referred to as a conditional is a what people are going to think of as a conditional. It is just a Boolean expression that is being asked for. No action or assignment is being given depending on truthiness of the expression. It seems like it is looking for an if, switch, ternary or bare conditional, and I believe only ternary or a bare conditional can be placed inside of an array (Not being nested inside of IIFE) which is knowledge a novice probably won't have. The difference, although small, is that a condition takes an action based on the result of a Boolean expression. No conditional action is being taken, so it is just an expression. Might ask for the first element in the array to be a Boolean expression of the sum of the player's position, height and velocity greater than or equal to the platform's position. There are various steps that follow that refer to Boolean expressions as conditionals. The concern is people learning incorrect terminology and getting mixed up in the field.\nYes, you are correct we should update the terminology for steps 78-81 to say boolean expression instead of conditional statement. I have opened this up for contribution.\nFor each of the steps, make sure to make the change mentioned above in all of the descriptions. Also, go through and check all of the hint text to make sure the correct terminology is used as well\nIt is bigger than a few steps. I did not track all the steps but kept seeing it through to the end of the course. It happens everywhere that we later do conditional action based on the Booleans stored in arrays. For each array we made, (I think there were 3? player, platform and checkpoints), the instructions use the same wording.\nLooks like we have a PR to address the few steps I mentioned earlier. We can review that and merge it in which will close this particular issue. But then I can audit the project to find the other steps and create a second PR to remove the rest\nDid a search and replace for the english files and found five more files total where the change needed to be applied. Here is the PR to resolve that."}
+{"_id":"doc-en-freeCodeCamp-d518f43ee59e304bba40cd47090316d7d8e2a5a77ea13081e0cb58293db33fea","title":"","text":"Describe your problem and how to reproduce it: Data with test cases is in wrong place in challenge template. This makes it inaccessible when tests are run and makes challenge virtually unsolvable, unless test data is manually copied to the user code. Tests in this challenge uses three arrays, containing two inputs for the function and function outcome - arrays , , . They are called this way: Those variables are currently at the end of sample solution in challenge template. Simple moving them to more appropriate place - or section in the section - as shown in the , would deal with the issue. Add a Link to the page with the problem:"}
+{"_id":"doc-en-freeCodeCamp-dcd7e5e8848577f2ce6fb98c727c98c16254e87ccaf257c8e1c91b5d13120bde","title":"","text":"All the data viz projects were created on our .rocks domain. We just need to replace the codepen URL's with the new addresses in the curriculum files of those five projects. Here's the URL's: https://bar- https://scatterplot- https://heat- https://choropleth- https://treemap- And the\nHey Just to make sure you want this replaced with https://bar- ?\nI want to contribute to this project. Please assign me this task.\nthank you for your interested in contributing, but this issue is not open for contributions, please look at issues with labels or"}
+{"_id":"doc-en-freeCodeCamp-53ee6e76691f8011d5826b4de63ba27f8b1a5ea0efcf56f56dbd288f241c6723","title":"","text":"I would suggest removing the second paragraph for step 66 (as a quite novice coder I guess the wording caught me up and I thought the challenge would lean on the side of more difficult rather than easy). I re-read it quite a few times but didn't realize that it was just explaining a later step. It took me a bit of time until I realized that only the first paragraph was needed to solve the solution. I just have an issue with the wording. Nothing else. Sorry if I did something wrong. This is my first time submitting an issue request No response Device: Desktop OS: Windows Browser: Chrome Version: 10 Just had issues with the wording and was recommending it being changed. Sorry if I did something wrong. This is my first github issue request\nIt looks like the original intent was to describe what the function was going to be about. I think removing it all together would leave the step in a place where campers are just asked to create a new function with no clue as to why or what it does. It would be better to provide some explanation on what they will be doing in the next few steps. A rewording would be better. Something like could work I'll open it up for discussion by the other maintainers to hear thoughts on wording. You didn't do anything wrong. It is a good issue\nI am going to go ahead and open this up for contribution"}
+{"_id":"doc-en-freeCodeCamp-0da3f8fd01951213d474721f8d9234a31f9ec8d2454dec0838bd4ad2dc1d41a1","title":"","text":"This endpoint needs to use jwtaccesstoken in the same way that web login does."}
+{"_id":"doc-en-freeCodeCamp-a4f17b18f34bedd6a449ede1355cff82f41e729284c86843d6d2df54cacf09d9","title":"","text":"and are not being replaced by their values in hints: ! While in the console the actual and expected values are visible: ! To reproduce, go to any challenge that uses and/or :\nHappening for me in hints for step 76:\nThank you for mentioning, but the fix has not been deployed yet."}
+{"_id":"doc-en-freeCodeCamp-a45bf0db83b480e1aa01f42f5b21e1fa79f2440675c67ea97e5132b4278a83cd","title":"","text":"I got a mini heart attack as I randomly tested the Storybook page of the component and found that the component failed a11y checks. <img width=\"1680\" alt=\"Screenshot 2024-03-06 at 00 49 32\" src=\"\"This is because: We pass as an empty string to the component in the Storybook demo: We use the operator in the computation of the button's label, which would only fall back to if is either or : Note that this issue is only in Storybook and not in /learn as we do pass a to there: In , replace the operator with the operator In , make an empty object instead of containing empty and\nI do not care much about the implementation, BUT, surely if a label of is never valid, then it is best to make the optional, and not pass one to the component? That is, I can imagine passing to a component because I do not want one, but was forced to pass one because it is not optional.\nFor this particular component, I agree that can be optional or can even be removed as a configuration option, since I don't think we need any customization here (the button's label should just be \"Close\" rather than something else). In fact, is already an optional prop of . However, has a limitation, which is that the library is not localized, so we still want to pass strings from /learn in order to have them translated. Semi-related, there was a discussion a while back regarding whether or not we should expose for consumption outside of . We decided to export the component because: The component in doesn't have a close button, but its version in /learn (which is called ) has one, so was built. (I wasn't around during the development of most of the components so I don't have the full context of the technical design) The limitation mentioned above."}
+{"_id":"doc-en-freeCodeCamp-2dbfa805e9eefe596ec2f45e271e02b00569b5b0072b10523941533a55ed0944","title":"","text":"Uploads: Everyday Downloads: Twice a week This should suffice our deployment targets which are usually Tuesdays? and Thursdays (optional) at around UTC+3 We can shake it up so that PRs can be merged on Mondays and Wednesdays?\nSo downloads should be triggered on Mondays and Wednesdays?\nYes, or a day before, for all we care. As long as they are: a week only on Mondays and Wednesdays for deployments on Tuesdays and Thursdays"}
+{"_id":"doc-en-freeCodeCamp-1a459effd3c963c987c02b67dada6335b0c65c344db98ac66e86c4206fd691cc","title":"","text":"Since the code is included in the URL after every change, once the user has made any code changes the back button will not work as expected as the browser history gets filled up with entries pointing to the same page but with different code in the URL. !"}
+{"_id":"doc-en-freeCodeCamp-fd4938c8fb24093f07dfa9a6f68151d1cf7590e9e780c95d68974d26fe4391b2","title":"","text":"There's typo in two hints. Instead of element it mentions . - - This is 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 was making a PR for a different issue and saw this, so I the fix to the PR."}
+{"_id":"doc-en-freeCodeCamp-5bf228542adb831e80b73ecadc504c6523f9191b974214ccf25afb01e07df884","title":"","text":"According to Google Analytics, the is way too hard, and is taking campers an average of 6 minutes and 35 seconds to finish (if they finish - a lot of them seem to give up). According to this table, campers spend more time on it than they do on the algorithm challenges. ! We need to either reword this or simplify the challenge so it can be completed in closer to 3 minutes. Otherwise, we should move it back to the algorithm section.\nThis challenge does have a large amount of constant strings which could cause users to take a longer time than a typical challenge. Maybe we could provide an array of the responses in the seed code. Make the seed code: This could help in two ways. The first is the users can save time by not having to type out each response. The second is this approach could minimize errors from typos in the response phrases (i.e. Hole-in-one! vs. Hole in one!). We could remove the number of different responses. Maybe remove Eagle and Double Bogey.\nyes - that is a great suggestion. I think leaving all the names is fine but we should pre-populate the array with the names. Since this was your suggestion, would you be interested in tackling this and submitting a PR?\nYes, I would like to tackle this and submit a PR.\nThe Golf Code challenge did take me longer that the other challenges. I did not initially realize that golfScore() had BOTH strokes and par as parameters. With the other IF ELSE challenges we were only dealing with one argument to pass into the IF ELSE condition. I found myself in that \"flow\" and completely overlooked that two parameters were available to work with in the IF ELSE condition. I also found myself looking at the Strokes/Par table thinking, \"How will IF( <= par-2) work?\" After a little head scratching, I realized the values under the Strokes column were what you were supposed to compare Strokes to (i.e. IF (strokes <= par-2)). Hopefully, this feedback is helpful. I think the confusion is coming from the wording of the challenge and suddenly going from using one passed in parameter to two in your IF ELSE condition.\nAwesome. has a PR open already. Could you take a look at that first and let me know what you think of his proposed changes?"}
+{"_id":"doc-en-freeCodeCamp-87ae906442cac325cd019d0ad8001150993fbe1a68b27b70f7fbad51fe95115c","title":"","text":"I agree with MiloATH's proposed changes. Would definitely reduce the potential for typos when working the problem. As a side note, feel free to let me know if I am breaking any GitHub etiquette at any point. Zero experience providing input on collaborative projects. Looking for to learning and have really enjoyed FreeCodeCamp thus far. You guys and gals are doing awesome work. :)\nSure - we will let you know in a polite way if you break GitHub etiquette. Thanks for being receptive to feedback :)"}
+{"_id":"doc-en-freeCodeCamp-88dd4e8cb8609fe352a95efab1d5d7c7dd2f451928ac32d92df583a2216111bb","title":"","text":"<img width=\"1074\" alt=\"Profile_freeCodeCamp_org\" src=\"https://user-\"\ncan I take this issue?\nThank you and for your interest. This issue might need a little more investigation before arriving at the final solution. I encourage you to find similar issues to tackle in the meantime. should I only audit the copy to replace profile with portfolio or you would rather changing the profile instances in the client and the api-server entirely?\nI would like to get it assigned..\nthis should come as a cosmetic change to the copy only, do not change any endpoints or code (functions, objects, files) etc. It can be done to both API and the client where copy edit is needed."}
+{"_id":"doc-en-freeCodeCamp-dcff858c91d28037f2b884d46237402a5238c73ac0b263f0fecf7838786531bf","title":"","text":"<img width=\"927\" alt=\"Settings_freeCodeCamp_org\" src=\"https://user-\""}
+{"_id":"doc-en-freeCodeCamp-ba5842a1ee3f3719be39993a598d55e7b48add043cb0fff19aab6cbb9be338e6","title":"","text":"This wasn't always the case, but right now the formatting for smaller screens isn't great: ! Smaller screens used to have tabs letting you switch between the instructions, editor and so on. You can see them briefly (in the gif) at medium screen sizes, but not for mobile. If we still want to support this, I can look into restoring it.\nLooks like they're just hidden behind the search bar.\nThanks for reporting this, we are still figuring out the final state for the nav. Once that is settled, this issue will be resolved automatically.\nThis wasn't entirely resolved by , as the challenge tabs are still displaying incorrectly: !"}
+{"_id":"doc-en-freeCodeCamp-8a41e2e10894adee0d7bb500f3fde822b43910cac613afffbb86c8645be0d1b5","title":"","text":"<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. -- This is the starter code: The starter code for this challenge is strange. 1) Why the space between the function name and the ()s for the arguments? 2) I get that the idea is to have the learners change the function signature, but it is a bit strange having a mismatch between the function signatures and the function calls in the starter code.\nThe linked PR in this issue. For , we could probably move away from having variables in the seed code and instead assert the function returns the expected value"}
+{"_id":"doc-en-freeCodeCamp-b629a954d269acc2047034dad567acbeae8515bbb189fc31baf3f80796e436c9","title":"","text":"Challenge has an issue. This is backwards and should read: \"Add two div elements inside your \"col-xs-6\" elements both with the class \"well\" - or something similar. !"}
+{"_id":"doc-en-freeCodeCamp-09ced1f9665b0fae87151a85dae26151262c2f4e2a9f7c56accd249f1853c841","title":"","text":"Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. There seems to be a conflict between the last paragraph above the \"Go to Next Challenge\" button, and the first test-item below the \"Reset/Help/Bug\" buttons (see screenshot, below). It is not clear if the <div class=\"well\"'s should go inside the <div class=\"col-xs-6\"'s, or vice versa. If I were to follow ALL the directions to the letter, I'd have two <div class=\"col-xs-6\"'s nested inside each of two <div class=\"well\"'s, each of which is inside an outer <div class=\"col-xs-6\". I think this is just a text-editing problem, because my code passes when I did what I expected the waypoint to be looking for: an empty <div class=\"well\"inside each of the previously-placed <div class=\"col-xs-6\"'s; this is included in the screenshot, as well. Also, I am fairly the text is missing a \"<\", where I've sloppily drawn it in on my screenshot. !\nI ran into this also. The challenge validates when you follow the instructions in the explanatory text. It does not validate when you only follow the instructions in the checkpoints."}
+{"_id":"doc-en-freeCodeCamp-fda7a8939eba0db294f6ec724c63e5308bb203c3c27965e1a018df968b828f85","title":"","text":"In step 12 of the Learn HTML by Building a Cat Photo App, the following two line numbers 7 & 8 exist at the start of the step: The instructions tell the user to make the text that appears inside the sentence of the element a link. The instructions do not explicitly state to remove the existing anchor element that is below the element. Instead, it just has a last sentence that says . Step 13 starts off only showing the following for line 7: The original link that appeared in step 12 is gone. In my opinion, an easy solution is to just change the last sentence in step 12 to: OR n/a n/a 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\nI think this instruction above is enough to tell what the end result should be\nBut it doesn't appear to be as this particular step comes up a lot in the forums. I agree with we need to make this a little clearer. If the intent is for the user to remove the existing link below the then I think we should tell them exactly that. Here's my attempt at making the instructions clearer: the words in the element into a link using the same value for the attribute as the link below the element. the link below the element. I thought turning this into two steps might make it a little clearer, but it can easily be two sentences instead. I'm not sure what the purpose of this step is, so my instructions may be unwittingly stepping on the goal here.\nI think a better word is than in but that's nitpicking. I do fully agree changing the hint. Edit:\nWe're also teaching vocabulary here. I would use slightly more consistent language with the previous steps:"}
+{"_id":"doc-en-freeCodeCamp-b145e733d37bd663475ab31491b761ee6992b63564d5188050e2447eab871df7","title":"","text":"It looks like a lot of people on the forums and discords are confused on the syntax for this step. we could add an updated description with code example to guide campers. js \" \" + \"string\" ` 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\nThis has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the Happy coding\nStep 63 You should now see the same bunch of characters in your console. Your padRow function is doing the exact same thing you were doing earlier, but now it's in a reusable section of its own. Use the addition operator to concatenate a blank space \" \" to the beginning and end of your repeated character string. Remember that you can use the + operator to concatenate strings like this: \" \" + \"string\" This is what i got and it was accepted function padRow(rowNumber, rowCount) { return \" \" + (rowNumber) + \" \" }"}
+{"_id":"doc-en-freeCodeCamp-2c2ad73efc3421e1098783042a4f5a1bc807de7ef8f33a47211b425e5bb916e0","title":"","text":"Describe the bug When we accept the academic honesty policy and hover over the text, it feels like a button. The cursor should be auto. To Reproduce Steps to reproduce the behavior: to the settings page sure you have accepted academic honesty policy over \"you have accepted academic honesty\" button Desktop (please complete the following information): OS: Windows 10 Pro 32 Bit Pro Browser: Chrome Version: 77.0.3865.90\n, we can make this button disabled, no? I tried it and it seems good, as it is a button but doesn't have to be clicked again..\nPlease feel free to make a PR.. Here are the lines that you probably need to touch: [ ] The panel can be a button and disabled. [ ] We would need some tests for these as well. Thanks.\nPlease follow our\nSure, I'll do it as soon as I can, after work.\nI went ahead and created a PR for this, along with unit test. Hope it's fine."}
+{"_id":"doc-en-freeCodeCamp-c052065146737056949addbb6f20f0f4daba46befdfd9fcf0173874ade27c352","title":"","text":"Describe the bug When you go to a challenge and the donation modal appears a stack overflow error occurs To Reproduce Steps to reproduce the behavior: Chrome go to on the dev console error Screenshots ! Desktop (please complete the following information): OS: Ubuntu Browser Chrome Version 76.0.3809.100 (Official Build) (64-bit) Additional context Removing removes it, so presumably it's a clash between that and the modal.\nYou are correct, I think there could be a race condition between the two."}
+{"_id":"doc-en-freeCodeCamp-556e23cda3d5648452dbb8665a336ab6bbde308538b8d68dca052c38120cfc11","title":"","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: --<!-- Add a clear and concise description of what you expected to happen. --Tests should fail because the text is incorrect (it should not be surrounded by spaces or newlines). You see the hint: Also, it's quite easy to fail this challenge by having spaces or newlines around the \"Camper Cafe Menu\" string. It might be nice to have an additional test specifically to catch that.\nThe title element isn't stripped away, so I think we could query the DOM and look at the ."}
+{"_id":"doc-en-freeCodeCamp-a1dbdb73779bec2ec0052fb5b86bb3f82a96b50d51df5b571df75d2367a43f47","title":"","text":"We have had a few campers create the wrong variable name for step 22 of pyramid project. Here is an example A few campers are wanting to call it instead of . I think a change in directions will fix this. Here is the updated description here are the updates to the first two hints js (code, /popped/); js (code, /lets+popped/); 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\nThis has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the Happy coding"}
+{"_id":"doc-en-freeCodeCamp-c8809491495231e9b1f4d64ec7b8d19d9caeb11a42f898181286d9fc8f3978fa","title":"","text":"step 68 of the platformer project doesn't provide a useful hint when the solution contains this line: Note the value given to the function is 400 not 40 as requested. The hint when you write this code says: We can probably give a more useful hint if the height property has been defined but with an incorrect value? for eg we could say: You should assign the height property . step should detect that has been defined and give a better hint when the value is incorrect. No response N/A No response"}
+{"_id":"doc-en-freeCodeCamp-62e6311310831531068b857f4a6a7fe2b7a35d7f3dfd60c789a4d826d2d117b3","title":"","text":"Reference URL: on espanol ! Night mode active: !\nTo expand: Donation component also breaks on night mode: !\n<img width=\"1440\" alt=\"Screen Shot 2021-02-08 at 11 02 37 PM\" src=\"https://user-\""}
+{"_id":"doc-en-freeCodeCamp-7f6975463d799bf6317b9720acaef33fcaece79abc83d47758a702f6f7742824","title":"","text":"Describe the bug A clear and concise description of what the bug is. When navigating to the home page, the Menu and Sign In buttons in the top right corner are missing. Can not sign in to profile. To Reproduce Steps to reproduce the behavior: to '' to locate Menu & Sign In error: Missing Menu and Sign In buttons on top navbar. Expected behavior A clear and concise description of what you expected to happen. Expected to be able to sign in and continue coursework or see profile. Screenshots If applicable, add screenshots to help explain your problem. ! Desktop (please complete the following information): OS: macOS Big Sur v =11.2.3 Browser:Safari v14.0.3 Additional context I haven't actually helped on any open source project yet. I'm pretty new, but in my senior year of CS degree. I would love to work on this issue.\ncould you check this out on Safari? First off, thanks for letting us know about the problem! And, yes, you're very welcome to work on this issue. If you haven't already taken a look, it's worth reading our to contributing to freeCodeCamp.\nI get a loader on /learn's navigation and the page itself. it seems like near 8% of users are affected. How long have you been experiencing this issue? should we have a script that detect the browser and shows a flash accordingly? \"For a better experience ... <img width=\"1438\" alt=\"Screen Shot 2021-04-22 at 11 03 40 AM\" src=\"https://user-\"\nSure, what did you have in mind?\nAdding in a small detail, the same issue(menu button missing and learn infinite loading) is on iOS devices also and in any browser on the phone.\nHey all, this is likely my fault with: I used a lookbehind in the regex, which I believe Safari does not support: !\nYou can open a PR and see if it fixes it."}
+{"_id":"doc-en-freeCodeCamp-7f1ea2bc1a97f2298fad81309d962f8dfa47d7c3639a9ca5e13d688d756e9101","title":"","text":"Hello. I noticed that the modals containing the user solution of the resolved corresponding certification challenge are not vertically scrollable when they should be so. A .modal{overflow:auto} css rule should be in the main stylesheet file of freecodecamp or the user-settings-section's one (if there is any), so modals become scrollable when they are full of text that they stretch beyond the viewport. here is a screenshot of the issue: !"}
+{"_id":"doc-en-freeCodeCamp-5d2bd5bf49db724cdf83149564aa2977323670da0073ff1d65a39f5cd9fbb19d","title":"","text":"Stray code is populated in the boilerplate for the Cash Register project User should have blank project to start No response All No response\nI believe this was actually intentional as to show campers the correct data structure for the cid array. thoughts?\nHmm, its in there without an explanatory comment and has confused at least one user.\nIt looks like the boilerplate code is possibly referenced here but being more explicit would be better. we could rework this section here price: the price of the item as a floating point number. cash: the amount of cash provided by the customer for the item, which is provided via an input element on the page. cid: cash-in-drawer, a 2D array listing available currency in the cash drawer.\nI think the proposed version looks good."}
+{"_id":"doc-en-freeCodeCamp-1d2b01c073bd7f432e69e66a807302d1ed3749d673db612eb1867b3cdbba1c60","title":"","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: --Code from the : <!-- Add a clear and concise description of what you expected to happen. --If the while loop is removed from the , the following should fail (if 3 or more items ), but it does not: <!-- Please complete the following information. --- Device: Laptop OS: Windows 10 Browser: Chrome Version: 96 <!-- Add any other context about the problem here. --The is only testing with 2 items to a linked list. The test should fail if a third item is and the while loop is removed from the because the third item would would be to the linked list, but it would orphan the second item. My suggestion for an improved test:\nCan I take this one?"}
+{"_id":"doc-en-freeCodeCamp-dd6374a03a6b38b5d2b05878e18706e6a348061aae73db34a6e34bd5f82824f6","title":"","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":"doc-en-freeCodeCamp-3bf6f6f9987899fa32059002bd41d01516c59e2a782e3bd9da73fe27134fdd68","title":"","text":"in the document, there is a sentence saying this: But this section is talking about assigning proofreading, it should be changed to this: here is the file here is the original issue 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.\nI can take this up"}
+{"_id":"doc-en-freeCodeCamp-acf681db0605b1c9dfaae09bd6805cbf79c01eb6547dac93c4e2ea93a4536355","title":"","text":"I was translating of project-euler and noticed that the NOTE is a little bit weird. I checked the . The description is \"Which starting number, under one million, produces the longest chain?\" and \"NOTE: Once the chain starts the terms are allowed to go above one million.\" If we change the description to \"Which starting number, under the given , produces the longest chain?\", should we change the NOTE? change the NOTE from \"\" to \"Note: Once the chain starts the terms are allowed to go above .\" !\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":"doc-en-freeCodeCamp-54406df0f44ad76421dc759d36536fc5c098d4f6314e78668b008cf5ee0c707e","title":"","text":"!\nHi, this could be resolved by removing the width of the -class. Should I do that and create a PR?\nYou should check locally if the fix will have any unintended side effects, of course a PR is welcome. Thanks.\nI changed the to so the progress reports still align on mobile screens."}
+{"_id":"doc-en-freeCodeCamp-b0d32d7d830e8714f3cf3f36f2edb0876c5a18df4c4700836e29d1a89cdcd4be","title":"","text":"In you can see the dialogue text in night mode, but not otherwise. The issue is that the font changes colour, but the background image does not.\nHa, this explains why I didn't think there were any captions, I never looked at it in dark mode.\nI had the same thought haha"}
+{"_id":"doc-en-freeCodeCamp-ec5281fd9be05ac2c818b66647f2012c23ec1dee23e62dd1c8c2dd73e05cf9c0","title":"","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":"doc-en-freeCodeCamp-694a072215ae702ece27c4fe6f7af6c6880197ed837023de6e2418b62fec4be3","title":"","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":"doc-en-freeCodeCamp-99e9c302d06aa91fa3b249bc61e2d3a21453520e86e830005ad5efcba51340f5","title":"","text":"CSS Learn Typography/Nutrition Label: Step 31 “Create an .small-text selector and set the font-size to” the “an” should actually be an “a”. Windows 11/ Chrome browser Version 110.0.5481.78 (Official Build) (64-bit)\nIt helps if you use the New Issue template. ! Link to challenge: Suggested correction:\nWould you like to solve this issue? Or shall I go for it? Feel free to try\niam new to opensource i love to work on this issue.\nAn issue 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\nTo solve this issue, change this line from to 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 prolific contributors will guide you through this."}
+{"_id":"doc-en-freeCodeCamp-b82eb997785d82bf01400968408dc0f39f93a9420d4b2c0ef8857d71c04359ea","title":"","text":"Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. Code broken: assert(editor.getValue().match(/(//)...../g), 'Create a // style comment that contains at least five letters'); Create a // style comment that contains at least five letters Should only show; Create a // style comment that contains at least five letters\nDear camper, your issue is a duplicate: Please see ."}
+{"_id":"doc-en-freeCodeCamp-1520b8ecbf7409f4c0b058a864e38bde3a00fe9f880fe8365832f7a883b65153","title":"","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":"doc-en-freeCodeCamp-610aa5237777ea7d6503541e8247bcdba09e784ffbed3372b433fb43f314bc01","title":"","text":"In order to pass the test for this waypoint, the comment for the slash-start-start-slash type of commenting has to be on the same line as the first slash-star, otherwise it doesn't work. ! Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible.\nDear camper, your issue is a duplicate: Please see ."}
+{"_id":"doc-en-freeCodeCamp-59b6a1f26171cad096e3431b3645c733a6527c496db0520cac633885796cf9c3","title":"","text":"Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. Left side error checking seems wrong !\nI couldn't get this to work until I entered the following: //Not hello world /(asterisk)Still not hello world(asterisk)/ Note that the /(asterisk) and (asterisk)/, apparently, have to be on the same line. Using Chrome 45.0.2454.85 on Mac OS 10.10.5."}
+{"_id":"doc-en-freeCodeCamp-454d289a7bce64af87d6766709578b35800bee5de594f2b4ed4bda7ad181515c","title":"","text":"Describe the bug If the user's code does not build there are no logs informing them of this. To Reproduce Steps to reproduce the behavior: locally, to (a); ('a'); </preinto the editor the tests that test output does not log 'a' or report any errors. Expected behavior The user should get some feedback, even if the code in the editor is broken. Perhaps just some output to the dev console, since there are various challenges that pass since they ignore the build errors. I think it should not appear in the test output area. It would be a little confusing for a new coder to get told something is wrong even though their code is passing. However, if they dig a little deeper there should be something (so they can see why their aren't working, for instance). Additional context The behaviour in production is different - it automatically fails tests (with output) if the build fails."}
+{"_id":"doc-en-freeCodeCamp-9b44dc872f4958d022d0a42cd72fe550fac6da83faf0d516cd135ff0f8d229b4","title":"","text":"You can pass the test by assigning 10 to the variable after decrementing it past that value. It also doesn't seem like the... is not working. Incorrect code that is passing: Forum: Challenge: Tests:\nI am happy with this being changed, but, personally, I see no issue here: The lesson teaches the operator, and that has been used. If the lesson were to give an element the text , and you did this, I would not expect you to fail the tests: Aside I might be becoming pessimistic in my teaching pedagogy, but we cannot truly expect to keep changing all these lessons forever, as more and more cases are found - there is a \"good enough\" point, IMO.\nYes, I believe that if a user uses the solution that stated, they know how works already, which fulfills the objective of the lesson.\nI don't think your example is equivalent at all. The end value is supposed to be the result of decrementing, not just assigning a final value. Clearly, they do not if they can not decrement the starting value to the final value that is asked for. I see no reason why anyone that understands what the challenge is asking for would do that assignment. We are not just blindly looking for the operator to be used. We are looking for the value to be decremented to using the operator. An example would be a lesson where you ask someone to use a word in a sentence and they use the word incorrectly. They may have used the word but if it is used incorrectly they do not understand the word. Using it in a sentence means correctly using it, not just blindly shoving it into a sentence. I would think a test with a regex that looks for an assignment to be good enough here.\nYou're right, my bad. As I understand it, you want to use regex to check if an assignment is present, and if it is, fail the test? I think that would work well.\nsecond test should be updated. Right now you can leave the initial code even though the test says it should be replaced. It should test that is not present in the code. that no assignment is used.\nI see, thank you for the clarification!"}
+{"_id":"doc-en-freeCodeCamp-597619ec3990f3729f030bb875de9982a398b37e83f1798cb88c24a0dcfdab5b","title":"","text":"Describe your problem and how to reproduce it: When you try to change contibution guidelines language - you'll see how the languages table's order is desynchronized and in several languages you cannot find new Greek language. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: Version 74.0.3729.169 (Official Build) (64-bit) Operating System: Windows 10 Pro 1809 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !"}
+{"_id":"doc-en-freeCodeCamp-071939cb05f6b34b77d786ee7f089bab734ec0cac8146f18aaf9d6f23247c71d","title":"","text":"<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --From CSS variable lesson, I just want to inform that IE doesn't supports as well as it's fallback value. It'd be great if your team will curate those lessons/challenges or add alternate CSS property with that. Started from lesson. Browser Name: Chrome Browser Version: 67+ Operating System: Windows 10\nThanks for raising this. Fallbacks as described in this lesson are not for older browsers that lack CSS variable support, they are for when the variable has not been defined yet, or otherwise not able to be resolved. The technique you mention of using a preceding more broadly supported CSS rule is also referred to as a fallback. Ideally, I think there should be two lessons, one describing each. whats the situation with adding additional lessons?\nyes we are open to adding new lessons.\nwhat did you have in mind for additional lessons? How about just a message in the first variable lesson that or something\nIn my opinion: needs corrected additional lesson should be after the lessons in screenshot below, lesson to show how to use this principle to form resilient css - ie fallback behaviour for css rules not understood by browser !\nI'd like to work on this. Should I lump this all into on PR or separate it into two since part one is technically a fix while part two is a feature?\ngreat! Looking forward to seeing what you come up with. I would say it's better to have two separate PRs, one for the fix and another for the new lesson."}
+{"_id":"doc-en-freeCodeCamp-823d74767c360ac20339219724f539d063ab949833d1d0b96d4fa814cbc73808","title":"","text":"I'm no language genius but I don't think the requirement is correct. I'm not sure you are supposed to use two full stops in a row after an abbreviation. Not sure if both are correct or what? ,full%20stops%20in%20a%20row Maybe don't end the sentence in an abbreviation if it makes it unclear. Or do not require two full stops. No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] forum:\nI agree that this could be unnecessarily confusing. I also believe that it is technically incorrect to end a sentence with two full stops (periods) even when the sentence ends with an abbreviated word. As I understand it (grammatically) the single full stop serves a dual purpose in this case.\nShould we add comma to first full stop or any other suggestion? If yes i am happy to do so?\nI suggest changing the sentence to not end with the abbreviation. I think it is more important to teach the use of a period to denote an abbreviation, than it is to teach \"no two periods in a row\". Maybe that could be another lesson.\nI would agree with that. But I would assume that's also more work than just removing the period at the end.\nOh. Right. I completely forgot the video/audio matched the sentence. In that case, I change my suggestion to just removing the period oat the end.\nThis issue is open to first-time code contributors to this repository. The change you should be making is to remove the period at the end of the sentence, under the section. The file that you should be updating is 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":"doc-en-freeCodeCamp-b20dedd4cb9cd40e4d105a46740fd96c62746e2ee6e6ea40b9e26fc220d11b39","title":"","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":"doc-en-freeCodeCamp-672efd9815edee6f612c272483aa38e48e54b7f693fd2349bc86fd27e4f3c940","title":"","text":"in step 43 of the js beta music player project, we are asked to: add an if to check if userData?.currentSong is falsey. But if you type an if like below, it is accepted even though that's not a falsey check? I also looked at the code in step 44 and the condition doesn't seem to be a general falsey check there either, so maybe this step 43's instructions should be updated to say \"add an if to check if userData?.currentSong is null\"? a rewrite of the instructions is needed to be clearer about not requiring a falsey check but just a check against null. No response N/A No response\niirc the tests were updated to be more accepting of conditions that would still work for the project but weren't what the user stories ask\nHmm. I am not sure this issue fits the behaviour? It is really the description that is too restrictive in this case and doesn’t match the test?\nThere was change from requiring to falsey Further steps still have in the seed code.\nIt looks like when someone tried to fix the tests to allow the falsey answer they also changed the description in reverse to make it more restrictive than it was? (That is, a falsey condition requires that many conditions like false “” null and undefined are checked, but a null check is much simpler?)\nAllowing any falsy value, through type coercion, implicitly allows all falsy values. However, we are not expecting the value to be an empty string or , so allowing explicit falsy value checks that isn't wouldn't be correct. is the explicit falsy value used by the code to denote \"not set\" or \"unset\", so allowing an explicit check for that value is fine. But I don't think the test should allow for an explicit value check. I don't believe there is a code path where the property being means the same as it being . If it is , I would assume something went wrong. Not that I thoroughly looked at the code. So if anything, we should update the test to not allow an explicit check but keep the check. Edit: Just to be super clear. I understand allowing is implicitly the same as allowing any explicit falsy value check. However, when reading code, explicit value checks signals something to the reader which a implicit check does not."}
+{"_id":"doc-en-freeCodeCamp-144de9033e5c08f747f689e73399e28aef2ee67a3cb37a8a66a5e84cd59550cb","title":"","text":"So if I was reviewing the code, I would ask for an implicit falsy or an explicit check.\nMy confusion remains with the description. Someone sees this step’s description and posts on the forum with their code only checking for null, my first instinct is to say: hey, the instructions said check for a falsey not check for null. (This actually happened by the way which is why I opened this). Then I found out that actually the test didn’t care that the person wrote code that only checked for null. My point is this; if the test wants a null check then pls make the step ask for a null check and not a falsey check.\nI assume we wanted to allow a falsy check instead of only a literal check, and in doing so we also change the written requirements to say a falsy check. I don't have an issue with removing the literal and part of the regex test. But the requirement doesn't state how the falsy check should be preformed, that is, it doesn't say it has to be an implicit coercion. So we might want to allow using as well.\nI'm in the opposite camp (lasjorg's original camp?). There are other conditional points in the code flow that use an explicit check, and the property is initialised to in the code. It does not make sense to then allow a falsy condition in the step. We should revert the tests to require an explicit comparison.\nI'm inclined to agree, but it is more an opinion. Strictly speaking, is used as an intentional value and other falsy values are not expected. Could you check for a by using implicit coercion? Sure. But in doing so, you are allowing potentially unexpected values to pass the check.\nI will give my vote to revert the change back to a strict check. A falsy check seems too broad and allows for unexpected values.\nI'm going to open this up for contribution. A PR which resolves this issue will update the instructions and tests for the linked step to require an explicit null check.\n/assign\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."}
+{"_id":"doc-en-freeCodeCamp-9aa02ff0bc43e044d7e994143434a48cf07c22b5997157969712fadf8e53a4ba","title":"","text":"A sentence in the description is missing the word \"object\". It currently says: It should say: The word \"object\" is missing. The sentence should say, \"A NodeList is an array-like object...\" ! Device: MacBook Air OS: MacOS 12 Browser: Opera Version: 112.0.5197.53 No response\nWould love to be assigned to this issue. I am a first-time contributor and fixing a typo seems like a great first contribution to make to freeCodeCamp! Thanks!\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":"doc-en-freeCodeCamp-411d0326fd0c3184c14b482b60e730694c775e51ce430454512f0776982a5429","title":"","text":"Looking forward for reporting a security issue: Please report security issues by following our security policy: Describe the bug When using the challenge editor, upon saving changes, the confirmation alert that pops up reads: . It should instead read simply: . Affected Pages Error will appear after saving on on any challenge editor challenge. For example: (http://localhost:3300/07-scientific-computing-with-python/learn-string-manipulation-by-building-a-cipher). To Reproduce the challenge editor with to (http://localhost:3300) to any specific challenege. the save changes button will then produce the alert with the unformatted message. Expected behavior The alert should display: . Screenshots Currently, the alert displays like this: <img width=\"448\" alt=\"broken\" src=\"\"When instead it should look like: <img width=\"452\" alt=\"fixed\" src=\"\"System Device: Macbook Pro OS: Ventura 13.1 Browser: Chrome Version: 123.0.6312.59 (Official Build) (x86_64) Recommended fix or suggestions The code that handles requests for the challenge editor does not correctly handle saveRoute requests because it expects the incoming object to have the fields and . I propose a fix where we edit the route handler to check if the incoming objeect posses a field, and if so, the message directly instead of using . Additional context I will be monitoring this issue closely for the next few hours and I am ready and willing to fix this issue.\nSounds good I think we would accept this change. Feel free to make a PR."}
+{"_id":"doc-en-freeCodeCamp-e8fa330be6a2136bff26e78ff21fdec497c50e3284a71f403bfaf4997d296107","title":"","text":"<!-- FreeCodeCamp Issue Template --<!-- NOTE: ISSUES ARE NOT FOR CODE HELP - Ask for Help at --<!-- 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 --In the discussion and questions concerning big-o notation, O(N^2) is referred to as \"exponential time\", which is wrong. O(N^C), where C is any constant greater than 1 (e.g. 2) is called \"polynomial time\". Exponential time looks like O(C^N), where the input variable (N) is in the exponent. Roughly speaking, the complexity class P (polynomial time solvable) is what we (or complexity theorists) consider \"easy\" - or at least solvable. Exponential time algorithms typically have no hope of being solved on large inputs (and therefore are good candidates for heuristics, or approximations). For a bit more intuition, an algorithm with O(N^2) complexity may not be a good candidate for real-time processing in your web app - but it may be perfectly suitable for less time critical tasks. With an algorithm like this, you might decide to pre-compute some solutions as a workaround. With an exponential time algorithm O(C^N), on the other hand, the sun may burn out before your computation ends. Concerning O(infinity) - notice the lack of an input variable (N), and that infinity isn't a number. It's probably best to replace that idea with a statement about non-terminating routines. This might lead into a discussion about the halting problem, for example.\nTo contributors, needs to be changed to\nHi, I would like to work on this issue.\nI wonder if this lesson might need more done to it than just a simple one sentence fix. The lesson text and quiz questions map directly to the video lesson, so correcting them while the video is saying something different would probably be confusing. This text fix might need to wait until there's a video fix. Or maybe we could add an errata at the top or bottom of the lesson text until the video is corrected?\nI can work on creating a new video tomorrow afternoon."}
+{"_id":"doc-en-freeCodeCamp-15e4bc3f1da9a52078f054c0a46864d844bea4957f3aa5e5af4ff1e495709385","title":"","text":"Originally reported by the editor region doesn't render when camper submits a challenge. https://user- This hide the instruction and lowerJaw, whenever this bug occurs\nWhat browser/OS were you using to trigger this? I'm not able to replicate with either FF or Chrome on Windows/Linux. Or perhaps there is some trick to this that I'm not seeing in the video?\nTo be honest, I don't think this is a browser specific. she mentioned that chrome was used, my guess is that somewhere in the JavaScript files, it has if statement that stop editor region from rendering, because old PRs do account for this failing. The true solution is to findout, what changed and what isn't pleased. Otherwise, we can add , that fallback to a basic component with instruction and submit button. Or we can add another tab in the upperJaw, for instruction if editor region is It won't have editor region, but it's better than the current nothing. Sorry, I can't include all of it, but here is the discord discussion.\nmy user agent info (on Windows 11) User Agent is: <codeMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36</code\nHere's a report on the forum with a similar issue (but on a different project) and the user had to move to their cell phone to complete the step and a recent one with the same issue but again, different project and step:\nThis should hopefully be fixed when gets in.\nHere is a brand new report of someone having the same issue on the forum\nAnother report of this issue:\nUsually, people can fix it by clearing the cache and closing and reopening the browser. Switching browsers also helps (likely for the same reason, fresh code). I get the feeling that this bug might not be reproducible in dev mode. It also seems like skipping steps and returning to them later is somehow involved. But I'm not sure what the exact steps are. Is there any information we can gather from people having this issue that can help debug it? Should we try sending people to this issue so we can collect information?\nnot reproducible. Feel free to open this issue again if it occurs."}
+{"_id":"doc-en-freeCodeCamp-598d461b53a16b2d945aa7c93316568dc5ed74b6f49ef2065d0f2bab0eb36a61","title":"","text":"I don't think this is completed just because we can't reliably reproduce it. It still happens, I have had it happen recently in one of the Python curriculum steps. I still have the step in the bugged state. 'm not sure it is reproducible in dev mode. 'm almost positive skipping steps, going back using the browser history (back button), and other such actions are involved. only affects a single step at a time. It is not like it happens and all your steps are broken. The one before and the next are fine. the cache is not enough you have to clear the cookies and other site data (Chrome wording). The storage (, etc.) is cleared when doing so. localStorage: Chrome bugged - and are empty Chrome working - and have content. Is there anything else I should look at? I'm almost positive if I clear the localStorage the bug will go away. But before I confirm that I will keep it as is in case someone has a suggestion for anything I should post that might help debug this. Fairly sure, the order of the event was I skipped a step forward and used the back button. But I can't really remember and I don't know if I did anything else. I suggest we keep this open to acknowledge the issue. As I suggested, it might be helpful if we gather information from people to help debug it.\nWeird, I just randomly reproduced it in my test browser. Clearing the fixed it. I can do it reliably. With the dev tools open, completed the challenge, reset it, and resized the window by dragging the border. Edit: it is on this step It looks like the same bug but it is triggered by the layout change which I hadn't seen before. I'm guessing the reload when going back to the previous challenge can trigger it as well.\nwithout your reliable way to reproduce, none of this would be possible. My findings doesn't show that submitting is necessary for the problem to appear. It's all in resetting challenge, with a twist. It's possible this is still not the original problem, but looking the same and caused by something different. Reproducing: anything in the initial contents. challenge. and are empty - invalid. This is the point when error can appear. everything still looks okay."}
+{"_id":"doc-en-freeCodeCamp-75a913ffc244c8a78103630ecb12224818f8d95b644a56573707e639124ebb6e","title":"","text":"At this point: If anything is modified in editor contents - and are going back to normal. Crisis averted! Any action that makes editor reload (if that's right word here) results in missing editable region. This includes layout change as shown above. More code involved rundown: is reset. action is performed - and boundaries are filled from seed. prop is set to . of triggers effect is called. It changes the value (contents) of the editor , to the initial text contents. triggers of the Monaco editor. updates props of the challenge. Because the function uses the current state of the , which just had contents changed. There's no editable regions (decoration ranges) that are relevant for that at this time. Therefore is empty array. is performed, writing empty and to props for the challenge. 'm not entirely sure how's the timing for the other calls from the change effect. That effect triggers the change of . My tests suggests that is still when executes. is laying in wait."}
+{"_id":"doc-en-freeCodeCamp-6c06b7dbbb5e5e8fcbf172e560bedb2ebb68d8e1fdbc928303cbd00bdb300f4a","title":"","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 --Correct solution doesn't pass. Maybe I am missing something but code does exactly what is asked in challenge description but last test doesn't pass. \"When text is entered into the input element and the button is clicked, the MagicEightBall component should return a p element that contains a random element from the possibleAnswers array.\" - this test appears failed. <!-- Describe your workspace in which you are having issues--Browser Name, Version: Chrome, Version 64.0.3282.140 (Official Build) (64-bit) Operating System: Windows 10 Mobile, Desktop, or Tablet: Desktop <!-- If relevant, paste all of your challenge code in here --<!-- Add a screenshot of your issue --!\nYou have the correct solution. This should be an error with the challenge tests. I've reproduced this both in production and locally, on staging. I will start working on a fix—the PR should be opened tomorrow morning (Feb 4, EST).\nI found the bug. Can I submit a PR?\ncustomarily, you would give the original responder a day or two to propose his/her solution. I had made my intentions clear in my previous comment. Nevertheless, I've tested his solution locally and it works well.\nHey ! Thanks guys, for pitching in and reporting and fixing this. Sorry about the delay, we will review and merge soon. Happy coding!\nseems fix solution doesn't pass for the challenge.\nThe fix has not been deployed yet, it may take us a while to get into the beta server.\nStill a bug on main site. Its keeping me from passing this exercise.\nI thought I was going crazy. I cannot pass this challenge even with the correct answer either.\nIt might be helpful for you guys so I'm reporting that the bug is still there when using safari (logged in and out). When I tried to test with Chrome it just passed."}
+{"_id":"doc-en-freeCodeCamp-d5ee9f7e6e06fb754ceb7a58e130260f79457fe7153134eabd34f538c5dc899f","title":"","text":"Same with this challenge: Browser User Agent String: Mozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.1 Safari/605.1.15\nYou used the solution shows above? If so, can you confirm this? I just tested this on production and seems to work fine (at least in Chrome, Edge, and Firefox).\nsafari is not passing with the code in the OP, firefox does pass. It only fails the last test\nAny guess why?\nI'm not sure what's happening here, I tried taking a closer look at the last test (the one that always fails). And when logging the info used in the assert, it looks like it should pass.... ! ! The two conditions in the assert are true, and it still fails. The test is complex and difficult to pinpoint what the problem is, or why it only seems to be failing in safari. By lowering the timeout at the beginning of the test from 250ms to 50ms it will pass some of the time, but still fail sometimes as well. I don't know, that's where I'm at."}
+{"_id":"doc-en-freeCodeCamp-d098be9c9cf904d6bb25248f3ad96ee04f50efec7b14e4a74f2a3513d897048f","title":"","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 have gone through the Guides of freeCodeCamp and I think there should be Guides on Some Static Site Generator like Hugo, Jekyll, Next, Hexo etc The guides have already which is also used to generate the static site\nHi I think it is fine to do that. If you really want to do it write, I would suggest first creating a new article on Static Site Generators that would be located at . Then, in the same PR, I would suggest moving the existing to be a sub folder of the folder you create like . Then, you contributors can create other folders/files like: However, please do a quick search of the repo to see if you can find existing articles which may already cover these. I believe I have seen some of these mentioned in detail in some existing Guide articles, so we don't want to be duplicating content if we can keep from it. In fact, before creating a PR, I suggest you document here where you find any of these and we will figure out the best strategy of how to organize everything.\nAny progress on this\nyeah I have gone through the guides I think the only static site generator based file in freeCodeCamp is I am working on to add more guides on static site generator like and\nTake the time you need. It was just a while since any activity here so I thought I would check in."}
+{"_id":"doc-en-freeCodeCamp-fcb7723586b714c17a3736be9fcb4a92ba291a9710e3b9ea61ea0d4a1965761f","title":"","text":"Describe your problem and how to reproduce it: The test \"Call functionWithArgs with two numbers after you define it.\" doesn't passes if the function call doesn't end with semi column. As in js semi columns are not required it should pass even if user doesn't add semi column Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: latest Operating System: windows 10 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! !\nThere has been an on and off discussion for a while about whether to enforce the use of end-of-line statement semi-colons. W FYI - This debate about semi-colons is not new to FCC. This is a debate that has been going on for a long time. See the following link how not using semi-colons could cause unexpected errors. This debate is similar to whether or not you should require { and } if there is only one statement in the code block. For example: is the same as: but FCC's current linter settings expect the { and } to be used. Both are valid JavaScript, but it is thought using { and } makes it clear especially when you have a line after like below: OR Both of the above accomplish the same thing, but reading the code could get confusing especially if indentation of the second line was accidentally written as: Someone coming from Python might thing the second line is far of the if statement block when it is not. As far as the semi-colon debate goes, I don't care which way it is done, just as long as it is consistent throughout the curriculum. Currently, there are challenges which do not require the semi-colon and some which do (which you have observed).\nWell as these tutorials requires user to type regular JavaScript code. It would make sense to treat the code same as regular javascripts treats it's. If the function returns correct result. Code should pass the test.\nAre you referring to semi-colons or the curly brackets now?\nI have eleborate my answer. And I am taking about semicolons.\nI have asked those in charge to make a final decision about this issue. Once I get some feedback, I will let you know the verdict. This decision will affect many challenges."}
+{"_id":"doc-en-freeCodeCamp-e000de8468cf92e80fc5027d5f20c4e4fa6b11b8bc4cc7cbdf31450e4f3fa5b5","title":"","text":"Hi, By any chance have they took a decision about this issue? I can confirm that this is still an issue after 3 months. When you get used to code using the standardJS style(), for example, it's not immediately obvious that the \"Call function\" test is not passing due to a missing semicolon. I don't mind whether you decide to keep the semicolons or let them be optional, as it comes to coding style. But a failing test should indicate the real problem, and I feel that failing a test named \"Call function after you define it\" when you actually called your function properly, can be confusing to new developers. Cheers, Mike\nYes, would you be interested in making the semi-colon optional for this challenge to pass the tests?\nsure! Just let me get familiar with the code base and as soon as I have a better grasp, I will send the pr's for this challenge and the next one (that is under the same situation).\nAny progress on this I agree that the semi-colons should be optional - If a camper is failing a challenge with valid javascript, that seems like a problem that might confuse them."}
+{"_id":"doc-en-freeCodeCamp-56dfe088b36a50101905f4542894e2bc77d1e39933027d6176a414428b831909","title":"","text":"Lesson text repeats itself: \"You can use radio buttons for questions where you want the user to only give you one answer. Radio buttons are a type of input. Each of your radio buttons should be nested within its own label element. All related radio buttons should have the same name attribute. Here's an example of a radio button: <label<input type=\"radio\" name=\"indoor-outdoor\"Indoor</label. Add to your form a pair of radio buttons. Each radio button should be nested within its own label element. They should share a common name attribute. One should have the option of indoor and the other should have the option of outdoor.\"\nIt is a style choice of whoever wrote this lesson. A bug would be error in the code that stopped the script or program from executing as intended."}
+{"_id":"doc-en-freeCodeCamp-d8d0960958b64e6aed9346a0786cfa8d4022a9790125cd4449e6bdbe785daa4d","title":"","text":"For , the answer is already provided for them. The starting seed code needs to just be the button element without the onclick. Here is the file that needs changing If you are interested in working on this please read through the first We do not assign issues. If you are interested, work on the issue and then create a PR for the fix. Happy coding! incorrect start code This should be the correct starting seed code 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":"doc-en-freeCodeCamp-773618e5fb751570c28093293404f80e165427bf30ea73312316ceeb518de5e1","title":"","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":"doc-en-freeCodeCamp-1ef5f499af9bd004f949a7375d9adf56e8e1ed673c2f3b93074920af859a892f","title":"","text":"I want to suggest that, at this point, in addition to the comment about the block element ' stretch to fill your page's entire horizontal space.', there is a comment that any element following it will flow to a \"new line\". You could argue that is [almost] \"assumed\". But I believe it should be stated."}
+{"_id":"doc-en-freeCodeCamp-6dd0d0bc5661bd994fe07860f6e1e76a31899abd37b6dbc00b44ad55792568d2","title":"","text":"I think the video for this challenge should be updated. It does not show the proper nesting of both the p elements inside the main element. It also has one error as one of the p elements are not closed properly.\nAny comments?\nAgreed with lasjorg, In this exercise a new paragraph should be below the first, with a main tag then to wrap around both paragraphs. In the video, the main tag is around the newly second paragraph only, plus the newly paragraph has an opening p tag at the end instead of a closing p tag. For contrast, the very next video has the main and paragraph tags the way they should be. Discovered this error when my daughter ran into difficulty with this exercise, and when she watched the video became even more confused.\nAny thoughts?\nI will redo that video."}
+{"_id":"doc-en-freeCodeCamp-77940463e084852fa0d9c2113ab1ceb09603895c38e017c8e2c2a733080d7261","title":"","text":"Within the challenge it instructs you to create bullets by replacing all the p elements with(no spaces of course) < li elements to get a bulleted list. When I follow it as instructed it leaves my style coding visible (class=\"red-text\") is then displayed. When I remove the end closure < l i (obviously no spaces), it leaves everything intact but the practice won't allow me to advance without adding the closure... even though the closure is at the end of the style portion of my closure Example: For it to look right I remove the end closure making it < l i this happens: <li class=\"red-text\"Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</liBUT for it to be marked correctly I have to Complete the closure < li class=\"red-text\"Kitty ipsum...... and it looks like this: <liclass=\"red-text\"Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</liSo In order to fix it, and still make sure my code isn't displayed on my final work, i'd have to remove my styling from the code or simply leave it exposed See below for the link to the segment and below that is my full code Challenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/601.1.56 (KHTML, like Gecko) Version/9.0 Safari/601.1.56</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nWhat the instructions for this challenge mean to be asking is for you to completely remove the bottom two paragraphs and put an unordered list at the bottom instead. This avoids the problem you're running into of having an anchor tag in the middle of your block (which is not valid markup). I agree that the wording is confusing since there is another tag earlier in the page with other types of tags in between. This should be clarified to reflect that the bottom two tags should be removed and a three item list created in it's place.\nI can't complete the challenge either"}
+{"_id":"doc-en-freeCodeCamp-86c0cfcf8af8a2b66b87e0e6629b2ca16452e8f717cc09c6d4baf225b3ba9354","title":"","text":"Challenge has an issue. The commented code sample at the top of the challenge is missing commas between properties. <img width=\"1158\" alt=\"screen shot 2015-08-16 at 5 01 57 pm\" src=\"\"\nAnd on this challenge, too."}
+{"_id":"doc-en-freeCodeCamp-ab4171f89237b65a805ab0b1456dbefa7421edb7f804f8cc4048975c2f408035","title":"","text":"The creation of the help wanted forum post should be changed to use correct Python comments for files. Right now the posts are created with the wrong type of comment. !\nI want to work on this issue\nWe typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labelled with or are open for contributions. Please make sure you read . We prioritize contributors following the instructions in our guide. Join us in or if you need help contributing - our community will be happy to assist you."}
+{"_id":"doc-en-freeCodeCamp-4bafc34f9f0eedc57ae03f155d05551de54638bd575964bff05cfd1bf97a20d5","title":"","text":"Describe your problem and how to reproduce it: SVG image in the challenge description is affected by SVG logo in navbar. They share some element s, what results in malformed image in description. Changing s to make them not overlap should deal with the issue. The simplest way seems to be, to change one of the images (probably one in the challenge), for example by adding unique prefix to s. That wouldn't eliminate completely the chance for some other conflict in future, but that's probably not something to worry about much. Add a Link to the page with the problem: If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): Current look ! Proper image !"}
+{"_id":"doc-en-freeCodeCamp-e3b6da71b738431f56c5e153a472f27b4b15d25d0cfae7f878b6878428a75bd8","title":"","text":"Challenge has an issue. It seems that it's more appropritae to show helpful links to: () () instead of: () () Am I right?"}
+{"_id":"doc-en-freeCodeCamp-5710c410b2fdda6888e754827143ecaed3ace3caec9a3a99f3ea92c115376c5c","title":"","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 formatting of the header-tag page in the guide is wrong. I checked the codebase and there are missing back-ticks for some of the html tags in the markdown page. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: Version 70.0.3538.102 (Official Build) (64-bit) Operating System: MacOS 10.14.1 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !"}
+{"_id":"doc-en-freeCodeCamp-a41301bad1f4b90e84a5ce3c4c2c333bcb4a10c2fce464342e03c43cf87b8c3f","title":"","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (X11; Linux x8664) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: I was asked to use \"the first few words of this kitty ipsum text\". I copied the first two words, but it failed validation. I tried copying the first three words instead, and that worked. Google defines 'a few' as \"a small number of\". synonyms: a small number, a handful, one or two, a couple, two or three_. Edit: it appears that copying 3 or more words works, but copying just 2 of them doesn't.\nThis isn't bike-shedding. It is rejecting valid solutions very early on in the first lesson, when it is important not to discourage people. Are reports like this not wanted?\nJust discovered this. Yeah, \"first few\" should be \"first three\". Why have the ambiguity?\nHaving worked through most of the rest of the programming exercises I wonder if the aim is to get programmers used to working from low-quality specifications. Even if that is the case, I think having a poorly specified problem this early on runs too high a risk of putting people off forever.\nThat's certainly an interesting idea. I could imagine some sort of course where you must sort through (intentionally) ambiguous and unintelligible requirements to potentially satisfy an irate product manager or customer with unrealistic deadlines. Call it \"Worse-case scenario\" training :D\nCall it: Situation Normal training.\nYes. FreeCodeCamp(now with Situation Normal Training)"}
+{"_id":"doc-en-freeCodeCamp-da90abe8a504dc8a00d9460baa1ecbd89fb74e36d901ca34e3477b9e960341db","title":"","text":"I have pass all test case of \"Exercise Tracker\" challenge except the 7th test case(\"you can POST to /api/users/:id/exercises with ...\"), I tried many way but still can't pass this test case. When i open the console of Chorm, i found the bug \"(...).subtingr is not a function\" when i click on the button \"I've completed this challenge\" to submit the `` the console of brower the link into Solution Link on \"I've completed this challenge\" error This error should be disappear ! Device: [Laptop] OS: [Windows 11] Browser: [Chrome] Version: [106.0.5249.103] No response\n~Please provide the link to the project that you submitted~ EDIT: still half asleep sorry, ignore that\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: Line contains the typo, should be . Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.\nHello, I am interested in working on it\nhey there, I suggest reading our contributing guidelines! as it says, all issues with and labels are up for grabs\nI have fixed this issue and raised a PR."}
+{"_id":"doc-en-freeCodeCamp-497a6933ec17eeeade5a1ca1e91be8554ee61c3c012e8620a831da26246cfbb8","title":"","text":"I found a subtle bug while doing the “React: Write a Simple Counter” challenge. If you look at the code below you’ll see that I binded this in to the this .decrement method. It should be: The consequence of this error is that clicking the reset button which calls does not reset the counter and decrements it instead. However, when I run the tests, all the tests are passed and the error is not detected! I think we need to add an additional test for that specific scenario. Browser Name: Chrome Browser Version: 67 Operating System: Mac OS X\nI run to this same error just now. Accidentally, I entered which is wrong but it passed the test.\nI think we need to check this with a RegEx. What are your opinions and ?\nIs there any update on this issue? I could work on this bug.\nAs of yet, we have not come to a conclusion about what to do on this issue. Although, since this is a confirmed issue, please suggest how you'd like to go ahead with this over here\nIn terms of the buggy code provided in this issue, I think only the last test case is wrong. Left part is the original version. Right part is the new version I made. ! I checked if my changes work on local host. After I made the change, we can see that the last test fails when I provide the wrong solution codes. ! And the last test passes when I provide the correct solution codes. !\nThis looks pretty good to me. I see you've made a PR, that's great, we'll QA that soon"}
+{"_id":"doc-en-freeCodeCamp-5e96f7832f0791dd570f51422c29706208bb64afb414048c7e9104ff9df4e5e8","title":"","text":"This step will fail with code and will pass removing the semicolon at the end of the third line. It doesn't look like this test allows for semicolon"}
+{"_id":"doc-en-freeCodeCamp-1df14985f2f22bd2bd8a0b4b069263a70c604fc17383ad873d984bb71711e5d9","title":"","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 --Link to external page with anchor elements <!-- Describe below when the issue happens and how to reproduce it --In the translation to Spanish, the instruction is: \"Create an element which links to and have the anchor text \"fotos de gatos\". The validator says: Your a element should have the anchor text of \"cat photos\". This will be a trouble in all translations when the validator looks for a string given in a specific language. <!-- Describe your workspace in which you are having issues--Browser Name, Version: Operating System: Mobile, Desktop, or Tablet: <!-- If relevant, paste all of your challenge code in here --<!-- Add a screenshot of your issue --!\nI can do this!\nI guess an overhaul of the challenge JSON structure could go something like: But this would be a big overhaul :D"}
+{"_id":"doc-en-freeCodeCamp-f0d062f6253ff68ec0909256c4212bb6cd370b16c834af05a6c3eb183931e460","title":"","text":"The description of Working With Text Question D should read \"in an tag\" instead of \"in a tag\". <img width=\"788\" alt=\"Screenshot 2024-03-29 at 23 05 44\" src=\"\" Change \"in a tag\" to \"in a tag\" in\nThis issue is open to first-time code contributors to this repository. The file that you should be updating is linked in the original post. Please make sure you read our as well as our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing."}
+{"_id":"doc-en-freeCodeCamp-aaf5753eb39e674e331b05fb15d8afe05fa9175903ea67c896f0988d99acdcdc","title":"","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":"doc-en-freeCodeCamp-3171f3aa63680d86aa1f3045d68ffac7b4436fe074b1b78bbb896e28e77effcd","title":"","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: While helping a camper with their work on this solution, I took a look at mine and discovered it passes when it should not. If you paste this code into the editor, you can see that has been modified from to but the test does not catch this fact. I believe it may be due to the tests for array modification calling the function without an parameter: If I assign a default value of in the function, then the tests catch this behaviour as expected. As such, I believe updating these function calls in the tests should correct this error. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: 85.0.4183.102 Operating System: Windows 10 v 1909 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !\nI believe so. Essentially if you invoke without , the value of is and from the solution you have given, will be which is . Therefore : As a result and remain unmutated. What i am not sure of is whether invoking the function without was an oversight or intentional.\ncalling the function without an stops various loop solutions from being accepted. I do not know if it was intentional\nIs it to force learners to use / since it is a splice-slice challenge?\nThere is no requirement to use splice or slice. It is an algorithm challenge. We do not care how they solve the problem.\nSo, to be clear - you are thinking to put a value in for on those two tests you shared would catch this.\nYes, updating the test call to: should correct this bug"}
+{"_id":"doc-en-freeCodeCamp-47d352bed3aa04251c3f0216f9606484b6b499b76fcc3da5e7728f5d754e4443","title":"","text":"We had this issue on the forum where the camper was unable to pass the test for step 71 with the following code. The test is expecting the use of inside the loop. But is valid too. After a quick scan of the final solution, it looks like the loop is used four times. I have checked the tests, but it is possible that all 4 instances have the same issue where is expected. Update all 4 instances of the tests to accept the use of or multiple pages 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\nI verified other for loops at step 35, 38 and 57. All these accepts the use of let or const or var."}
+{"_id":"doc-en-freeCodeCamp-265e88350c4cd448cd67840a819c05d3fef31d5e1591978e60a21c75ebd29faf","title":"","text":"None of the GET request examples/Tests mention to be able to GET with id param, However during one of the PUT request tests there is a GET request sent with an ID, i struggled to find this Bug in my code, i feel adding one extra Functional test for GET request specifically requiring to be able to GET by IDs, If using mongoDB like i was the ID needs the toString Method in order to be read as a string. i attached a screen shot shows the PUT test with the GET request at the bottom Either extra functional test requiring to be able to GET with an ID, or Updated with GET example that shows GET with an ID ! Device: [Desktop] OS: [Windows 11 WSL Ubuntu 22.04.3 LTS] Browser: [Chrome] Version: [122.0.6261.70 ] No response_\nThis requirement would be covered by: I'd be fine adding another check inside that existing test to look at the param.\ni see now the \"any field\" and value, this was a lack of knowledge at the time, being able to get data by an \"id\" is imperative. Id like to propose a solution to the test above, change query of to GET the post created by carol and assigned to eric, this keeps the get Multiple aspect but returns 1 doc the of to GET and assert that of is equal to of\nI'm hesitant to rewrite the entire tests, when instead we could update the test I indicated to try a query by ID (which we know won't break existing projects because a later test relies on that functionality).\nAgreed my proposed solution would be for the existing GET test that you indicated, you could just drop in and after existing , this adds a query by ID. The current tests only query by and !\nAh, I see. Yes, that would be a good approach. I'll go ahead and open this one up."}
+{"_id":"doc-en-freeCodeCamp-87c0cf81cc35d72223733ab87a5ed893cbbcf11b26baff398eacd989563d3eaa","title":"","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":"doc-en-freeCodeCamp-1efef2817f6b5e2bb2b212997ae8ea656bbec202552c8ac82e2ba550eec97294","title":"","text":"Describe your problem and how to reproduce it: After commenting the code in a , the tests are passing. I think the issue is with this particular challenge only as I have solved many challenges and I haven't observed this bug in any of them. ! Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: 76.0.3809.132 (Official Build) (32-bit) Operating System: Windows 10 Pro\nThis is not unique to the beta site. Many of the challenges don't ignore comments. We have a helper function which can be applied to the tests which removes comments. We can not use it across all challenges, because there are challenges which involve validating the comments. Since there are only a few challenge tests where we need to be able to check the actual HTML, CSS, or JavaScript comments, maybe we can figure out a way to pass an extra property named with a value of only when comments should not be removed from a specific testString's use of the variable. That way, the default behavior would always be to remove comments from a test. It might be simpler to just add the to the frontMatter of the challenge, so all the tests of a challenge would not remove the comments and the s could be adjusted to account for the comments not being removed from the variable.\nI do not like the idea of changing the schema again though. What we really need is a parser to sanitize comments.\nSome of the challenges are actually checking the comments, so you can not just sanitize all the challenges' comments.\nDid someone say ?\nOoops, been a while since I have been on GitHub. Using an AST will help remove those awful regex tests that many of the older challenges rely on. The is built with . Is wouldn't take much to create a library of helper functions to use in tests.\nHow do this look? The idea is to provide a challenge test utility to replace the need upon horrible RegEx tests. I have this passing locally as a POC. <img width=\"568\" alt=\"Screenshot 2019-09-15 at 14 19 32\" src=\"https://user-\"\nThis would be really nice to be able to update those quirky tests. Can you please throw in you changes in a PR?"}
+{"_id":"doc-en-freeCodeCamp-8db23cca45110ac3d2007308287624efcc78cf59c80d9d786bbe0db32ba7d92c","title":"","text":"<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Affected page Your code Typical user code: Expected behavior We've had an uptick of people blindly copying the help video from this challenge without reading the instructions: This leads to campers failing the requirement (This is generally a problem with the help videos, unfortunately - copying with zero understanding.) Does this video link need to be updated or removed? Screenshots If applicable, add screenshots to help explain your problem. you can drag and drop, png, jpg, gif, etc. in this box. System (please complete the following information): Device: [e.g. iPhone6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.4] Browser: [e.g. chrome, safari] Version: [e.g. 22] Additional context Add any other context about the problem here.\nlet's remove it, it's already that direction with other videos, once there is a discrepancy, the challenge win and the video is removed\nSeeing as this is an easy fix (I assume we just remove the URL) I will open this up to first-timers. If anyone disagrees feel free to remove the label.\nThanks for making this a first timers only. The only additional step I would be recommending is using as an example to add clear instructions for first timers. I am going to go ahead and take care of that here. 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: Edit this file and remove the line containing . 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-requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.\nThanks for the help. I have the template to a saved reply. Hopefully, I will remember to use it. Also, I have a stupid question. How do you best \"quote\" the code and line numbers of a .md file?"}
+{"_id":"doc-en-freeCodeCamp-2818dcd5b2df3bd1b0e03ba0a5aa4dd25a97408662baa004d5eeb2fb79f54ae4","title":"","text":"Do you just use the blame view or look at a commit/PR? I don't understand the commit link you have in your quote. It looks to be for something else?\nOh - I just use the code view for a markdown file and then grab the permalink. <details<summaryDetails</summaryOpen file in code-view: It's the icon on the left at the top right of the file. Looks like this: ! Getting the permalink by selecting the line (host shift for more lines): ! </details\nRight, but you can only get to the code view from inside a commit, right? I mean I do not see the source view for .md files when just looking at the file. Anyway, I will figure it out sorry to bother you with this I know you are a busy man.\nYes, that is correct. I browse the repo with top commit at the time of making a comment. But again, you do not have to spell out every little detail for the first-timers, it's just a \"the more the better\" type thing."}
+{"_id":"doc-en-freeCodeCamp-184810aeb454894a7700b5f3f683adac3bce2defda434c879ae84ebadb8efdce","title":"","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."}
+{"_id":"doc-en-freeCodeCamp-584601a4f9b5b7e2ed735b7b1fea20fb8b57976494ca85f41b92421ef49e6113","title":"","text":"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."}
+{"_id":"doc-en-freeCodeCamp-94cf9313c2e16bf16b299803af5ad2c1cf44183f4639acb93ade2baff9e90120","title":"","text":"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":"doc-en-freeCodeCamp-fb5d9c4f0dee0cae5c862a862392dfb7c77b977f1c97c11724245c552381e8db","title":"","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 test error messages do not indicate anything about resolve and reject’s strings. This may throw some people off as the message error just indicates the if statement did not fire. Add a Link to the page with the problem: Test Code: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: 4044.124 Operating System: iOS 81.0.4044.124 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! !\nHey , I just looked at the page, and want to make sure I got this right, Currently, the test cases only pass if \"We got the data\" and \"Data not received\" are the strings inside resolve and reject; if anything else is entered in then the tests fail. If I'm correct, the strings don't really matter, it's just having resolve and reject inside the if and else statements with a string inside. I just wanted to clarify what is needed before starting. BTW, I'm a CS student who's just getting into Open Source and thought it would be awesome to contribute here! I've used freeCodeCamp in the past to help me learn the basics of Web Development, and it really has changed how I look at coding overall. Attached are a couple of screenshots of what I tested. <img width=\"1540\" alt=\"Screen Shot 2020-05-09 at 2 24 41 PM\" src=\"https://user-\"<img width=\"1533\" alt=\"Screen Shot 2020-05-09 at 2 28 13 PM\" src=\"https://user-\"\nHey Thanks for jumping in! The instructions do say that the string does matter, however I believe the test messages should have something pointing the user in the right direction. Eg: Perhaps additional tests should be created for edge cases IDK . The file that needs to be altered for a PR should be:\nJust my two-cents: As much as it would reduce posts asking for help on the forum etc., many (if not most) of the challenges require the user to be precise, and follow instructions well."}
+{"_id":"doc-en-freeCodeCamp-d55f5a0e573719515a0e9cc59701ec8820b794aec5447301f9358a7071eefb3e","title":"","text":"Sure, we could change many tests in other challenges, but I would much rather have the tests as is, teaching users to debug their own code. In programming outside of tutorials, debugging is a massive portion of the process, and programmers do not always write their own tests. In my opinion, the tests are well-suit for teaching programming skills.\nJust took a second look and it makes sense now, didn't see the part that specified what the strings had to be. I'll probably just add a couple of tests to check for what the strings are inside of resolve/reject and change the test messages depending on which ones were passed. BTW, if you don't mind me asking, why do you guys have all of your files in Markdown? I'm just curious for the sake of learning.\nThat’s a question or or some of the moderators could artIculate a better answer, but I think the theory is that markdown is an easy to read input for feeding the curriculum engine/logic.\nTL;DR: Markdown is easy on editing. We used to have a json object (schema) for the challenges in the earlier days, but ever since we moved to - A static site generator, we started using markdown. It is easy for contributors to edit a text file. More often than not when making a quick contribution, you do not need to know how the underlying infra works, because maybe you are changing the instructions a little bit, fixing a typo, you get the idea. We wrote a custom parser (and a schema that it needs to be compliant with) to get the content out of the markdown and build the HTML pages (which is implemented as a Gatsby plugin of course). You are welcome to dig into the package to learn how it works. P.S: All questions are welcome, do not be shy :)\nThat makes a lot of sense thanks for the response, I have a couple more questions actually If you don't mind me asking, Since the challenges are made using Gatsby, how do you guys test your code? Do you make your own site and run it on there? Or do you use extensions on whatever IDE/text editor you use? Also, what does YML mean? I'm assuming YAML, but I honestly don't know, I think however that If I know what that means I can figure it out."}
+{"_id":"doc-en-freeCodeCamp-b994e134fa546f2f9718cefaacd48c5d1aa4fe3ac3a631bbdc951583d717b3d0","title":"","text":"Here's what I have so far:  What I want to do is change the first two tests to just resolve and reject with empty strings inside, then have the last two be with the correct string inside. These are probably very simple questions but I think they would help me out a lot as I contribute more this summer!\nhave you made a PR yet? When you do put the PR # in this thread so we can test your tests. If you need any help with this let me know. EDIT: Yes, YML stands for YAML files (yet another markup language). If you read the instruction on installing FreeCodeCamp locally there should be instructions for testing locally as well. To test curriculum: To test everything: Check out for all the commands for the project.\nAlso we have some documentation here: if you want to learn more.\nI'm working on setting up my repo locally and getting a basic idea of the codebase, as I've never worked with YAML; if anyone else wants to fix this issue don't hesitate! I can work on something else. Like I said I'm new to open source so all of this stuff is new to me, apologies for me taking this long, I will be a lot more productive once I have more time on my hands."}
+{"_id":"doc-en-freeCodeCamp-5590567a3c560b5f0b00e5d51fc445d7e6c1f5b9a3dec929db1a030f16f5969e","title":"","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."}
+{"_id":"doc-en-freeCodeCamp-a02bc5b556846f1526aa176610f5c8ff0b89e88dbfc312bbb35a650208a0ff7d","title":"","text":"I 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":"doc-en-freeCodeCamp-b21b795ed10c6982c3777d55f00204bd3d7ac2d8fece1af10040189a715a256d","title":"","text":"The instructions state \"In your fourth tr element, add a th element with the text Total Liabilities.\" However it is not really clear that the user should or should not include a period. Users will have failed previous tasks if the period was omitted (periods are required on previous exercises) , therefore they will most likely add the period which will result in a failed test case. Also, if the period is included after \"Liabilities\", the error message gives \"Your th element should have the text Total Liabilities.\" Which does not highlight the actual issue. Maybe making a different test case message that looks for the period would make it more understandable? The code above should highlight the issue of the period being present. The test case that is currently in place can confuse users that they have a spelling issue/spacing instead of the actual issue being the period at the end of \"Liabilities\". No response Device: Desktop OS: Windows 10 Browser: Chrome Version: Version 108.0.5359.125 No response\nI was thinking, that we could change to But this doesn't make a coherent sentence. I am in favor of adding a new test.\nI also think a new test case would be good.\nHi! We just opened a to fix it, but it was not accepted . Could you please kindly inform us some feedback about what was going wrong and what else we need to do? So that we can know where to focus. We appreciate any help, thank you!!\nHi Thanks for reaching out and creating a pull request. For reasons of sanity, we can't accept PRs from forks that organizations maintain. You should make a PR from your own personal GitHub account. You can collaborate with others and have commits made by multiple people, but one person needs to create the PR, and then others may push to the same PR should they wish. It is OK if you want to use the draft mode while collaborating. The person making the PR is responsible for ensuring the checklist is followed, tests are working, and so on. You can also commit on someone's behalf. See: Also, please create good, small, and succinct commit messages and PR titles. Keep your commits clean and avoid any merge commits unless you have conflicts to resolve. The final PR should not have dirty commits from collaborating on an organization fork like the previous PR."}
+{"_id":"doc-en-freeCodeCamp-9d2a5a0b6c5d030b6c6af424004e4a087b3225ef2d662faabdc5747b17f2fba6","title":"","text":"The reason is the maintainers of this project will need to validate your changes and the source of the commits. Keeping it clean makes everyone's lives easy. Thanks and happy coding!\nHi Mrugesh! Thank you for your precious feedback! I've switched back to my personal GitHub account, and made a pull request . This time the commits are clean and the messages are concise. Thank you for taking time reviewing! I appreciate any feedback. :D"}