freeCodeCamp/c2i/test/corpus.jsonl

{"_id":"doc-en-freeCodeCamp-42b7b7536815d7c41479457e730829ada4fe262f26672a14e8233f846d200fd7","title":"","text":"Faulty method of the class can expose itself only during function tests. Case when number of balls to draw is higher than number of balls in hat is not tested explicitly, but it can fail function test, as it includes such experiment. - - Depending on the number of balls to draw and number of balls in Hat: Remove the required number of balls randomly selected, from the Hat. If number of balls to draw is higher than the number of balls, return all the balls. Test for the method checks only the first case: The second behavior is not checked explicitly, but it's a part of the second sub-case in the function test. This creates situation where passing method test and failing function test, can suggest to camper that issue lies in the function. Example with faulty method: Error: Adding test to check second behavior of the method would make debugging easier for campers, as it would show more clearly where is the issue. No response n/a No response"}
{"_id":"doc-en-freeCodeCamp-3493c3754f389860ad5986c988281f978a5c5a71a0c790349d33d0f4c00f883a","title":"","text":"I have created this issue so we can come to a final conclusion about the best format of notes when they are to the or sections of a challenge file. Below are all the combinations I have seen scattered throughout the curriculum. There may be others, so please let me know and I will update the list. This only applies if there is a single note. For multiple notes (which in my opinion starts to get unnecessary), see later in this topic. Example 1: Example 2: Example 3: Example 4: Example 5: Example 6: Example 7: Regarding situations where two or more separate notes are , I have seen: Example 1: Example 2: Example 3: If everyone can cast a vote for their preference of both a single note and multiple notes, this will help us in deciding on one way and then we can update the Styling Guide for challenges in the documentation.\nI will cast my vote as I prefer Example 7 for single notes, because it takes up less space and adds one additional space between the word and the content. I like Example 3 for multiple notes, because I like the to be bold.\nI'll vote for number 6 for the single notes and number 3 for multiple notes. I don't really see the need for extra space between and whatever comes after it, a simple space is fine\nAlso to add on, perhaps we can have a background-color for all Note sections as we want users to pay attention to those sections particularly. Something like this: ! Color code used: #C9F8CF\nThis is the style guide contain freeCodeCamp's Brand colors: https://design-style- . We try to deviate as least as possible from this and I'm yet to see a major deviation\nAlso, the note is not the most important thing in the challenge. The actual instruction is. We don't want to highlight anything that is not relative to the instruction. Most of the time, these notes are FYIs.\nI vote for example 6 and example 3, The says to use something in none of the examples for single notes, the output would be the same as example 2, I think - Also, the guide doesn't say anything about multi-notes\n6 and 3.\nI vote for example 6 in single notes and example 3 in multiple notes.\nI think it is settled then."}
{"_id":"doc-en-freeCodeCamp-39f4a067726eca648831b029ec622589cffc0e4357a267a838a1e3cbbb26159e","title":"","text":"6 and 3. What do you think?\nAgreed, with you all. Thanks. Please proceed with pull requests.\nI would like to work on this. Is there a way to assign my name under the assignee? I am not able to do so\nHi Go ahead with PR. We cannot assign you the issue. It's unfortunately a limitation from GitHub. Feel free to make a PR. We usually allow the first open and valid PR to go in as a fix. Thanks.\nThe suggestion in the PR above says to make a multi-note different from the example - so I did some testing to see the outputs and thought I should share.<brthese codes.... <img width=\"570\" alt=\"screen shot 2019-03-05 at 10 26 56 am\" src=\"https://user-\"produce the following...<br<img width=\"415\" alt=\"screen shot 2019-03-05 at 10 27 51 am\" src=\"https://user-\"The first two here produce the same result (same as example 3 above)... I'm not sure I like that extra space in there - I suppose it's fine, but I made a few others to see if I could make it look more like how I think it should look. So basically, I'm saying, I'm having second thoughts on how we should do the multi-notes.\nI found more cases for single note. Perhaps you can update the list Case 1: Case 2: Case 3: Case 4:\nAre you going ahead with a PR to put it somewhere into the docs?\nAre you converting them to the suggested style And have you come across many multi-notes?\nIn challenges like , we have this sentence: Note that property names with spaces in them must be in quotes (single or double). So, should that sentence also be converted to: or can we ignore such cases?\nyes i am following the example 6 for single note (as voted) Have not come across multiple notes yet. Will re-check.\nGood points. Maybe multiple notes should just be different sentences in the same style as for a single note. Which ends up looking like: <strongNote(s):</strongFirst note goes here. Second note which is a bit longer goes here. Third note which is the longest note of all goes here."}
{"_id":"doc-en-freeCodeCamp-05e979c5221ca67c85f2326430d74be25210a8a1085ef4e6edc186afc63f88d6","title":"","text":"That's a judgement call I think it could be converted. I would hold off on the mult-notes for a little bit - and if you're going to make a PR, it's probably best to try and keep it to maybe one section or so at a time, or maybe a few sections if there's only a couple files changed.\nI have a doubt: in , Is the note section considered multi-note or single note? The note section has more than one sentence. Does it qualify as multi-note then?\nThat one looks like you could probably just put the two sentences together in a single note. Since they are so related. And we aren't sure yet what we want a multi-note to look like.\nI agree if they are related a single paragraph note will be fine. However, if it gets to long it may be more difficult for the user to parse the information, and should then be broken up into individual lines. Any Notes section with more than one sentence should still be described as Notes My opinion on the multi-line notes - we should use markdown bullets. It may put a bit of space between items, but they are much simpler to manage when making changes to the markdown. They automatically insert line breaks after each item and don't require verbose HTML wrapping the text. Visually it also looks like a bulleted list. Spacing between bullets can be modified in CSS if needed. It's also easy to replace the bullet with numbers if the order of the note matters. Note vs Notes should be explicit, Note(s) is only useful if you expect someone to add a second Note and they will forget to update Note to Notes, something we should quickly catch in review with the requirement of multiple reviewers. After some conversation with I agree that it really doesn't make sense to have too many notes in a document - we should work to insert the notes into the curriculum, or provide a place for additional information that may not be directly related to the exercise but provide valuable insights/information/resources.\nI believe the corresponding Guide article for the challenge is the place where extra information is supposed to go, to avoid cluttering up the challenge itself.\nthat may be the case but the way it's conveyed is not great IMO. The only link to the guide article is Get a Hint, something many won't click, especially if it's a fairly simple exercise."}
{"_id":"doc-en-freeCodeCamp-07b62f07d9058d050747d7d6b1bc4e86c88b73ae6ad61f1d9e8a56d18ab197d6","title":"","text":"I also don't see the guide article at all when I search for the exercise title, something we should look into, unless that is by design.\nI see guide links when searching for a lesson title (none of the links work right now) - perhaps you searched for a lesson where the guide article is still a stub, and they don't show up or something.\nThe search indexes have not been updated in over 12 months, so that could be part of this problem.\nI just remember that Quincy prefers not to have links going to other places when a user is on the challenge. He believes the challenge should stand on its own or rely on previously introduced material as much as possible. We want people to stay on the challenge until they just can not, which is where the Get a Hint or Ask for Help buttons come into play.\nSo the single note structure was to the guide with the PR above. The multinote issue wasn't exactly concluded - do we want to continue the conversation? I'm thinking we can close this, and mods should just keep notes small when we can. And multinotes can just be combined into a single paragraph after a\nI don't know how many multi-notes there actually are, but I say we just combine them like you suggest in the same paragraph. I can create a PR to reflect this. Then, as we come across the multi-notes, we can first figure out if there even needs to be a multi-note and then probably just make it a single paragraph. How does that sound?\nA PR to describe this in the guide? Sure"}
{"_id":"doc-en-freeCodeCamp-bcd6dcaab088bf825da4110f1d36be2f4f135b69cca6dddecf82fa7abc7b7046","title":"","text":"In [()] step it is written but in the html file there is no selector instead there is selector present. ( In [()] step it is written but in the html file there is no selector instead there is selector present. either change the to or remove the totally from the step to do. No response\nPage File: the seed content doesn't have , and the step after it do include it as well. we should swap with This looks 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: file: 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 issue. Please assign this issue to me .\nWe don't give assignment unless to an old time contributor to the repo. Edit: sorry should have provided more info. There were times when people assigned an issue and didn't commit to it, because of that the guide mentions we don't assign people and seek quality and fast commits. Sorry if my original answer was uninformative. I hope you have a good day and happy coding."}
{"_id":"doc-en-freeCodeCamp-99346b1228c2e61a23d92963736ac346f651b6b95800068881f4d1eb5df5bc64","title":"","text":"Description and question refers to the Here's the main office area. And over there, let me show you, that's the conference room. text. However the audio mentions let me show you in context of showing to the desk. n/a Audio used in task should match the description context. Or the other way around. No response n/a No response\nYes, this is a problem. None of the answers are correct. Here's how I'd fix it: change the option \"the conference room\" to \"the desk\". This should solve the problem. We could also: simplify the question to \"What is Maria directing attention to?\" simplify the example to \"Here's the main office area. Let me show you to the conference room.\"\nI am fine with the suggestion. You could use as the example. What do you think\nAgreed I'm going to add the help wanted label."}
{"_id":"doc-en-freeCodeCamp-9d27e28b6b11322ffffb0f46b75f04ed33aa399425d47feda2dd65c299432fae","title":"","text":"The certification files () have been uploaded to Crowdin for translation. However, the React Component itself does not use the translation helper for the text within the certification (such as ). The component and files should be updated to allow this."}
{"_id":"doc-en-freeCodeCamp-e8fbe3a4067c30478ac04bd8f2a513d1b6e3ea591cc4b6a8a303472bc364c629","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 challenge wants the user to do a (\"Hello World\"); which sounds simple enough but it doesn't specify that it has to be in the but it eventually does with the error \"hello world is not in the \" or a similar error but when you go to the you see this: /* PLEASE DO NOT EDIT THIS FILE the verification process may break / It's jarring for someone who doesn't know about this language or system yet. I suggest changing \"file\" into \"file section\" or \"section of the file\" just to prevent confusion. As one material (the challenge page) is telling me to edit the file while the other material (the glitch material) is telling me NOT to edit the file. Add a Link to the page with the problem: 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):**\nI agree, we can clarify the instructions to something like: To get started, just print the classic \"Hello World\" in the console. You need to modify the file. The file shouldnt be modified at all. There is in which you can add and the latter challenges code.\nCan I take this issue?\nIf I remember correctly, that's what I did first. I did the on the and it gave me the error of \"log isn't in the server\"(paraphrased). Just to clarify that that's what happened. If you mean that the challenge should instead change so that it's the that should be manipulated, then I think that's better.\nSure! I'm still very new and inexperienced so I leave it to your more capable hands! 8D\nI have started course and in my Glitch app there is no file, also putting console log in is also not working\nYou need to use the boilerplate project mentioned in the introduction challenge."}
{"_id":"doc-en-freeCodeCamp-dda446cc2d8f1157d7f4a99483de7f4fb00e0b069c08f4955133c38125615f0a","title":"","text":"Okay just to make it clear... First I cloned the Github boilerplate-express-gomix template... I'm not a big fan of Glitch... So if I have a project on Github at similar URL then logically file would be located at Now my question is pretty simple... JUST WHICH EXACT URL should I use in this case... this is a bit confusing... I managed to pass the whole previous Managing Packages with Npm section, still I had a bit of of hard time finding the proper URL to point to I found the main way to make it work in my case was to select the file, then click on Raw button. That would give me a similar URL which I later passed in the URL. Any hint on how to make the boilerplate project URL work with Github Thank you...\nI think this should be to the Hint: \"Use the new Glitch link for this episode\" See this forum posts:"}
{"_id":"doc-en-freeCodeCamp-db5155f8448eb2a30d794622f9a023801ed89768de48e5ae3637faccab7ec38e","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. Behavior of \"Preview\" page matches challenge description but these tests don't pass: When a number of less than 18 is entered into the input element and the button is clicked, the button's inner text should read You Shall Not Pass. }; When a number greater than or equal to 18 is entered into the input element and the button is clicked, the button's inner text should read You May Enter. }; Once a number has been submitted, and the value of the input is once again changed, the button should return to reading Submit. }; <!-- 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 --<img width=\"422\" alt=\"react-use-a-ternary-expression-for-conditional-rendering\" src=\"https://user-\"\nThe bug seems to come from the first boolean, . An alternative to checking a string's emptiness——works fine. I'm guessing that at some point during the tests, is not actually a string. For instance, if at some point becomes a (which does not have the attribute) then we're in trouble.\nFound the bug: as predicted, there was a and mix-up. In the tests, the values sent into the input element are numbers, making undefined and failing the tests. These tests should not be sending numbers into input elements. As written in the MDN web docs for , the attribute of the Input Element in HTML is always of type String. Yet, the in the challenge has , so shouldn't the user still account for this? The MDN web docs say otherwise: Notice that the type attribute only alters the \"type of control to display\"."}
{"_id":"doc-en-freeCodeCamp-887b95aa8886cc9328fcb050a229c8c5286d6c083faaeb029ccd7296b7d17cf3","title":"","text":"When type is set to \"number\", only numbers are allowed to be entered, yet the value is still stored as a . Therefore, the value attribute of the input element still returns a data type.\nI've opened a pull request to fix these tests. Luckily, this \"input-number-value problem\" only afflicted this particular challenge.\nthanks for explaining and for fixing :+1:\nanytime :smiley:\nHi guys, thanks for taking the time to report and fix, we will get this reviewed soon. Happy contributing!\nHi, why this solution is not working. It's working fine if I enter a value greater than 18 but fails when I enter a value lesser than 18.\nit won't work for values lesser than 18 as it this is an invalid expression (buttonThree && buttonOne) Instead, try the below solution : { ( == '' ? buttonOne: ( < 18 ? buttonThree : buttonTwo) }"}
{"_id":"doc-en-freeCodeCamp-1b7a410995df310c23abf7571c94f4a6394f2075d8cce94596e834a2244850fa","title":"","text":"There appears to be a slight typo in the English instructions on Step 41 of \"Learn Typography by Building a Nutrition Label\". The instructions are displayed on the file and read as: The typo is with the text: . The and <p class=\"bold right\"% Daily Value </p% Daily Value ` as part of the exercise. The following code is what the challenge starts with - where the instructions are displayed The expected instructions would read with instead of : This would match the actual text value for the paragraph element the instructions are referencing. ! ! Device: PC OS: Windows 10 Browser: Chrome Version: Version 115.0.5790.110 (Official Build) (64-bit) I would like to point out that I have only seen this issue with English and I am not sure if other languages are also impacted.\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-1fd9b84c423cde751068d2c13137b77609857b4d6bcf4fa15ef3b335ad0822aa","title":"","text":"We recently a lot of updates to this project. So the step numbers in the main branch don't match up with what is currently on production. Here is the correct file you need to look at We had this issue reported on the forum If you try to use the wrong variable name like this then the hint text tells you this: it looks like the third test here will need to be updated You should declare a variable named . 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"}
{"_id":"doc-en-freeCodeCamp-0bbcf19033fb2d33ea5a461840ac96bae5f2dcf8491e07a1a1bb991acd0681b9","title":"","text":"Potentially, upgrading to MongoDB 4 has broken the GitPod Development. I am looking into it, but here are the errors: Shortened Error (me trying to restart Mongodb, after an initial crash): <details<summarymongod --version</summary</details<details<summaryFull Error</summary</details<details<summaryPotentially relevant client error</summary</details\nTo the best of my knowledge no code changes were made to upgrade MongoDB on GitPod. The base image using MongoDB 4 needs to be looked at. In other words, the move to MongoDB 4.0.x (not same as 4.x) breaking GitPod is coincidental?\nTo be honest, I have no idea. The base image: Source: Docs: From what I can see, the docker hub provides no information about the image, but the GitHub repo suggests the image has not been updated in 4 months. To me, this suggests an issue definitely on our side.\nThat is pretty easy to confirm. On GitPod you should be able to checkout a commit (any commit) that was best known to working from a few days ago. A diff should bring you closer to the root cause, say for example a dependency update somewhere. But to prevent beating around the bush, I think we instead provide our own base image with requirements set in the local setup file. Let me know if you need help with this & thanks for looking into it.\nUpdate: There is a high likelyhood I have been looking into the wrong section for where the problem is. Here is the original error which lead me to look into the database stuff: <details<summaryClient Error</summary</detailsSteps to reproduce: 1) Open any instance off fCC GitPod 2) Wait for client to finish developing 3) Open browser preview of app 4) See client crash with above error I tried killing the database, restarting it, and restarting the client, but the app crashes, everytime the browser tries to load.\nI can't reproduce this, sorry! If I go to it just works. I know we've talked about this before, but do you have any special settings for GitPod besides Enable feature preview? Environment variables are the only thing I can see that might cause an issue.\nOther than the Feature Preview, everything is bog-standard. I will try to disable FP."}
{"_id":"doc-en-freeCodeCamp-d705618c350241e8237cab48fc185e44fb359f6141b7304d63620c1e17239c6f","title":"","text":"Disabled Feature Preview Rebased fork against upstream <details<summaryNew Client Error (similar, but different)</summary</details\nIf you have a lot of work in progress branches, I would suggest pushing them up to your fork and starting with a clean workspace, then on you should delete everything that is old/stale. As a best-practice I would start with a new workspace (provided the work is saved elsewhere like pushing up to th remote fork) and getting rid of older workspaces.\nFork? That could be relevant. Could you drop the Gitpod link that you're using here.\nI might be using the wrong word... all I meant is: Here is the link I sometimes use - depends on whether I am testing with changes or not:\nAll of my testing (outside of the open PR branch) has been with a new workspace. I regularly clean the workspaces. Positive this is not part of the issue on my end.\nQuick question: Are you using the preview browser within the GitPod environment? What happens if you ignore the crash on the preview browser and just use the \"open in a new tab\" button: ! If you reload there, is it the same behavior?\nI never use the preview browser - always the new tab view (full). Had not thought to try it there, but, if I am relegated to using the preview, I still would not use it...\nHmm, I was able to reproduce with a link from your fork in your previous comment. But the link from this main repo works A-OK. Is it the same case for you? Or is it broken no matter what you do? I know you rely on GitPod quite a bit, we are totally cool with you pushing branches directly up to the main repository as an exception considering the massive amounts of work you put into contributions. If there is anything we can do to unblock you we would be happy to assist. Sorry about not being able to troubleshoot. :(\nI've one idea left to try, that's updating my own fork and seeing if I can repro. I'll have a go tomorrow.\nThis is the same for me. A workspace from appears to work as expected. So, it is just my fork (unless proved otherwise by Oliver)... I will report this to the GitPod GitHub. Thank you, both, for your time in this."}
{"_id":"doc-en-freeCodeCamp-25cf816ab1b54a9f4321f1079d4c12191af62df0c8db92ae40a7df02d960aa06","title":"","text":"If there is anything in particular I need to work on, then I will take you up on this. Thanks\nJust to confirm: it seems like it's some weird problem with Shaun's fork. It's worth trying my fork , but I suspect it'll just work when you use my link.\nWorst case you would need to delete and recreate your fork and PRs, which is going to be a pain.\nStrangely, his fork doesn't work locally also.\nAfter all of that, pointed out the issue - Gatsby had enrolled me into their super secret testing club, and the development server-side rendering broke the build. Is it worth it me opening a PR with the change to prevent this? Or, am I really just that lucky?\nWell, congrats on being the secret list that you never subscribed to (I hope?)!! Please make a PR to make sure no else gets on the exclusive club list and is surprised. We wasted so much time for no reason. Lolz.\nSorry this has been breaking you. This error line: comes from This generally works as most people run from the root of their site so equals the root of their site. I'm not sure what your setup is but I'm guessing you're starting the dev server differently? This isn't what we normally do — we have a more robust way to get the public directory that's not being used here that I'll switch this too which should unstick you.\nHey Thanks for getting back to us. You are correct we do have a non-common setup. We essentially use in parallel mode for spinning our API and the client (Gatsby) apps. Even within the client, we need to do a pre-Gatsby develop step. We package a few things (with Webpack) to for one of our client-side runtimes before bringing up Gatsby to start the dev server the normal way. Anyways while we do not understand the internals of Gatsby for this particular feature yet owing to time (BTW, Gatsby 3.x is fast, congrats to the team on shipping it! ), we understand that turning off the flag did resolve the issue. We will be happy to troubleshoot if you point us to some documentation about the \"discovery\" process for the public directory in your comment. Thanks again.\nThanks for confirming the issue!"}
{"_id":"doc-en-freeCodeCamp-ff4b18c01c8f893da58fef976e4fdaaeb927661adcadbe3281e4a79badb8434d","title":"","text":"No need for you to do anymore work — I'll fix this upstream so once DEV_SSR is enabled for everyone, it won't cause you (and others with similar setups) to have any trouble."}
{"_id":"doc-en-freeCodeCamp-12c7fd51a1ccc04281888ae216b52f3021eba150cb48d94ef9492d2e99d13f8e","title":"","text":"I'm a new contributor to this project and have run into a few confusing points on that I'd like to clarify for other new contributors. .io - From a few other contributors, I've been told this is no longer used. I'd suggest removing this from the contributor's guide. npm dependencies. This project has a dependency to which is confusing to set up for new NodeJs developers. I'd propose to mention this link to get new Node developers started, especially for Windows, since it involves some unusual installations like Visual Studio for the C++ compiler. isn't any mention of running tests before submitting a pull request. This is something that could be easily missed and cause a pull request to fail the TravisCI build. I've learned that one pre-test dependency, JSONLint, doesn't work for the Windows filesystem. As a workaround, I'd suggest all contributors on Windows to run the tests directly by skipping the pre-test lint run. An additional step could be to manually run JSONLint on individual files, without using the problem-causing wildcard *. For non-Windows contributors, it should be mandatory to run before a pull request.\nThese all sound like reasonable changes. Go ahead and get a PR going for it.\nI'll get started on it."}
{"_id":"doc-en-freeCodeCamp-20d676f0299087cb0c930fd51a82f4b9071cc28e28dede9c16aa55c3ba99fd20","title":"","text":"When working with the , it mentions the following instructions to complete the challenge: And that's alright, but when running the following correct solution, it doesn't pass and throws the following error: The current test error that it throws is misleading and it's happening because there's a missing test for the above code, which is expecting an implicit return. A test should be to let the user know that an implicit return is expected and can reach to the expected solution: Updating the challenge instruction would be appreciated too. On the other hand, there's a similar case where a correct test is running. When executing the following solution, this happens: This is tested using the following test: ! Device: Laptop OS: macOS 13.6.6 Browser: Chrome Version: 123 No response\nHi that makes sense: regarding the challenge text I would modify it as it follows: What do you think about it? Talking about code that’s right, we should add a test for the listed case in order to fix this. If updated text is ok I’ll proceed adding missing test.\nHey how about being more specific like other the other challenges? Something like the following: And the test error text should be the same when the condition is not met: That's my opinion, ofc. Appreciate that you ask. When able, please submit the PR and let's see what the maintainers think\nHi and I've submitted a PR using juan suggestion about instructions; then I a test assertion just to give explicit error on implicit return. Supravisor PR just fixed text instructions but not a test, so I did it."}
{"_id":"doc-en-freeCodeCamp-9e4ac0c7b6f2f6669f93cdc03dcd7203c8bb49e1b8cdc9c434540b4f3a8aeb5d","title":"","text":"\"Bash a script\" should be \"a Bash script\" This looks like something that can be fixed by \"first-time\" code contributors to this repository. The files you need to fix are the two above. Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing."}
{"_id":"doc-en-freeCodeCamp-82902e2171d51c2dbc95a9b6349fe79005c0b9d817b60694f97c5ee0678f9bdf","title":"","text":"There is an option being displayed as a code block, rather than inline code like its siblings: <details<summaryScreenshot</summary! </detailsMake the following change: js --- (); --- ();` To\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'm limiting comments in this issue to reduce noise. If you're interested in contributing, everything you need is provided in the thread."}
{"_id":"doc-en-freeCodeCamp-77fa2267faf21689977d82962de5705196c39cb21eba3b4f6c425be07064105f","title":"","text":"In the 5 certification projects for the Data Visualization certificate, the phrase \"(non-virtual) DOM elements\" is used without any prior explanation (I checked the Data Visualization curriculum and no such phrase was introduced at any point). It is not clear therefore to the learner what the requirement \"Required (non-virtual) DOM elements are queried on the moment of each test.\" could actually mean. Now, maybe it means \"actual DOM' vs \"virtual DOM\" from the React curriculum. But requiring that a priori knowledge to understand a Data Visualization project requirement seems like overkill? I propose that this requirement in all 5 projects be stated simply as \"Required DOM elements...\" The chance of someone not understanding that we mean 'actual DOM elements' seems miniscule to me in the context of these challenges, but I'm not a web developer, so if there is a valid reason to use the term 'non-virtual DOM elements', it would be very interesting for me to learn/hear of it. ps. should this issue be accepted, please also fix the phrasing \"on the moment\" to be \"at the moment\" which I believe is what was actually meant. update all 5 certification project statements referring to (non-virtual) DOM elements as per the above discussion. No response N/A No response\nI think this is more of a note for advanced campers, similar to mentioning that the tests might not work with a framework like Vue.\nYes I think so too, but it is too confusing to someone who is not that advanced. If we didn't say it, what is the chance an advanced camper will run into a problem?\nIt likely wouldn't - though I also haven't seen much mention of beginners who do have confusion.\nI agree that I haven't seen questions on this either but since the rule-of-thumb is to not include undefined technical terms in the challenges and projects, we should do something about this one. (Either define it or drop it)\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: In these files, the text should be updated to . Please make sure you read our , we prioritize contributors following the instructions in our guides."}
{"_id":"doc-en-freeCodeCamp-cf7821208f520f7ad7bacdd1b6a940cfc117d1a63a8c84b504f32ecb823a09ef","title":"","text":"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-8356c2c3f3033648b0e2f9664e315ac80d05d157f582a17b36279f226048ba47","title":"","text":"In RTL, these texts will be broken, because they are a mix of special character, numbers, which follow different direction in RTL than LTR. ~1.2.13 1.2.x 1.x.x To fix these, add code elements around the version number. File: change to there are multiple instances in these files All of them should be wrapped in code elements Speaking of weird interactions. Using special characters that relay on direction will break in RTL, because it will be reverted, in example. will be we can wrap in\nI want to contribute towards this issue. Can you assign this issue to me.\nThe first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the"}
{"_id":"doc-en-freeCodeCamp-68e0419807b807c436b32c982a406be9146db1e62db89af1a019897ed73ce507","title":"","text":"Some users can claim python, new QA, and new infosec certifications without submitting their required projects on .dev. It seems the api does not find the cert challenge and proceeds by setting the related cert flag on the user object to true. The issue can be resolved by reseeding the db locally. I cannot reproduce this issue at the moment, but I will keep this open in case other users are experiencing the same issue.\nHello! I tested this issue, and I was able to claim the certifications without completing the projects.\ncould you check if you can see the certification after claiming it? I'm just wondering if this is purely a client-side issue.\nI am able to see the four certificates I could claim, yes.\nThanks for checking that. In that case, while it seems likely that it will fine if the database is migrated, the api should definitely default to rejecting certifications it does recognise.\nYes We Can Claim Python Certification Without submitting the Projects.\nthat's really serious"}
{"_id":"doc-en-freeCodeCamp-044fe684ebc2824ffd87ded241ed9a6aaf20921aff186a92d0dc27abc68d9b61","title":"","text":"Currently when you complete/claim a certificate there's an entry on the timeline: <img width=\"582\" alt=\"Screen Shot 2020-05-27 at 9 37 55 AM\" src=\"https://user-\"This doesn't seem to be working for the new Scientific Computing with Python, Data Analysis with Python, and Machine Learning with Python certificates.\nI'm a new contributor but I'd like to help out on this.\nI think this is mostly working. You just need to refresh the page before it shows up... <img width=\"598\" alt=\"Screen Shot 2020-05-27 at 11 34 12 AM\" src=\"https://user-\"Edit: hmm, it seems to be working locally, but not on .dev - the \"view cert\" button is there in both environments - it just doesn't show on the timeline on .dev\nAh, interesting. This does seem to work locally but not on .dev for some reason.\nThis may be a one off issue related to where the new/split certificates (Quality Assurance, Information Security, Scientific Computing with Python, Data Analysis with Python, and Machine Learning with Python) were not seeded to the .dev database for some reason. I can confirm this is working locally like mentioned above. thank you for your interest in contributing. Please check out issues with the label for other things we need help with."}
{"_id":"doc-en-freeCodeCamp-f1503703827dc288193bcd3ab9c49c2287f246944f7c1e2c3f24325d93a22f49","title":"","text":"<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --1) The Full Stack Cert claimed date will only show as the current date and not the date it was claimed on. I claimed mine on the 7th of September and checking back regularly I noticed the claimed on date was always the current date. 2) The Full Stack Cert appears as the Legacy Full Stack Cert on a users profile page, clicking this leads to an error as the legacy cert does not exist. It should be in with the new certificates. That being said, on the settings page the link to view the certificate is linked correctly. ${username-here} /full-stack ${username-here} N.A 1) Just the claimed on date. No screenshot necessary. 2) !\nSimilar to\nI am having the same issue with my Full Stack Certificate\nMine as well. Has this been addressed?\nSame here - The issued date shows the current date and not the date on which it was originally issued -\nRelated\nHave the same problem: the date of Full Stack Certificate is always a current date.\nIf there are no records for a fullstack certificate, a good fallback would be going thought the date of the modern certificates and displaying the date of latest claimed certificate.\noptimally, we should add a completion timestamp and an id when campers claim a fullstack certificate with a fallback to the last earned cert if a timestamp is not found.\nMy full stack certification also updates with the current date not the claimed date.\nThe date on my full stack certificate is showing the date i claim my Responsive Web design certificate ( the first certificate ). and now if i want to see the certificate it is asking me to claim certificate when i claim it will say is like u have claim the certificate and it will not show me the certificate.\nThis is an ongoing issue, please use the reactions instead to assert \"me too\". Potential approach for fixes: and\nAlso related to the Full Stack cert – the date seems to be the date the first certification was claimed, not the date the full stack certification was claimed:\nThe fallback is not working properly and I should have caught that. It's not a tricky fix, but I'll make sure it works this time!\nOk thenks On May 5, 2020 11:04, \"Oliver Eyton-Williams\" <:"}
{"_id":"doc-en-freeCodeCamp-45a5b30c76aed3845de14a520d94fb88ea951eba5609175b9195e4cb1858a9af","title":"","text":"Since newItem, which references an array should be to the original array (per the instructions), I expected to pass the test. Instead it says \"nonMutatingPush([1, 2, 3], [4, 5]) should return [1, 2, 3, 4, 5].\", which would be concatenating the two arrays, but it isn't a non mutating alternative to as the instructions suggest. <img width=\"1437\" alt=\"fcc-challenge\" src=\"https://user-\"<!-- Please complete the following information. --- Device: [laptop] OS: [macOS] Browser: [chrome] <!-- Add any other context about the problem here. --\nthe function should return (newItem). You put the newItem in an array literal, due to which the test is failing.\nI see what you are saying. Really, the challenge is asking you to replicate the effect of using push with the spread operator. I'm not sure what change to the wording would make this clearer. Do you have any suggestions?\nit also fails without literal syntax, e.g.: I know that it will pass when I write but this is the problem, because the instructions say: would result in arr having the value . So i suppose a function named \"nonMutatingPush\" should have a similar effect as push namely creating a \"two dimensional\"-Array in this case, like in the example in the instructions, and not do something entirely different (ie. merging the content of the two arrays into a new array)\nThe challenge doesn't say anything about using a spread operator, instead it asks users to \"Change the nonMutatingPush function so it uses concat to add newItem to the end of original instead of push\". Pushing an array to an array would produce an array in an array. Since \"The concat() method is used to merge two or more arrays\" () to replicate the effect of push one needs to put the array about to be \"pushed\" into a new array, so the outer array gets merged and the inner array stays intact. My suggestion would be, if replicating the push behaviour isn't the case, but merging the two given arrays, the instructions should ask users to \"Change the nonMutatingPush function so it uses concat to merge newItem with original, without altering and \"\nYeah makes sense to me."}
{"_id":"doc-en-freeCodeCamp-483118ba383c588b49360deec232ecc07adedbaa57bdbf54de6b126efcf19fe0","title":"","text":"And since merging two arrays is taught in the previous lesson, I think the goal of this lesson is to replicate the behaviour of push using concat. In that case, my suggestion would be: \"Change the nonMutatingPush function so it uses concat to replicate the behaviour of push without altering the first and second arrays\".\nI think we need to be careful. The intended behavior is better. We don't want the users to concat a reference to the second array.\n! you need to assign (newItem) to a new variable and return it\nAs far as I can see the idea here is the user should create a function that behaves like , but it returns a new array instead of modifying the array it's called on. That function can be implemented as follows This replicates as closely as possible, so that if I in the same way as if I used push So, the main issue is that both the solution and the final test need updating. Also wording, should help guide users down the right path.\nIf we want users to learn a \"non mutating push\", I think its better that the solution not provide an avenue to mutate the original arrays. I think the current intended solution is fine but the wording describing it isn't quite accurate.\nI think it would be better to compare:\nIMHO, it is necessary either to change the expected solution or the wording of the task. For example: P.S.: It seems to me that it is better to change the expected solution (based on the previously described behavior of the push method)\nI wouldn't change the expected behavior.. If we change the expected behavior, then this is no longer a non-mutating function. We should modify the description.\nI agree with any of your solutions, but I did not understand - why would another solution cease to be a non-mutating function?\nIf you change the expected behavior, then if is an array, the output of this function can be used to mutate , as I explained above.\nThank you. I understand what you mean... - but then it looks like we are deliberately simplifying the task to meet the requirements. Maybe it's better to just replace the expected behavior with (for example)?\nI don't see how this would be a simplification. The current solution works fine. Not changing the solution wouldn't make the task simpler - it would make it identical to what it is right now."}
{"_id":"doc-en-freeCodeCamp-92f4ea1800a05fecd58324ad217e2a7a4d321c877761eefc7d60e5d5a4d58471","title":"","text":"We just need to describe the task more accurately.\nWe show that we can get this result with push: [1, 2, 3, [4, 5]], and then we ask to get [1, 2, 3, 4, 5] with concat?.. Well... - Ok. Thank you for your time.\nRight.... You highlighted exactly the [wrong] description that I want replaced. Using push like that mutates one array and allows for the mutation of the other. The current solution to the challenge prevents mutation of both. The description should reflect that fact. Changing the solution to permit mutation of one of the arguments misses the idea of making a more functional solution to using push.\nCan I work on this ?\nSure. We don't assign issues - we accept the first complete PR that addresses the issue. In ttis case, we are looking for someone to update the description of the challenge so that is clear that we want a non-mutating push.\nI've read through the full thread and submitted a PR that I think should satisfy most, if not all, concerns with the description."}
{"_id":"doc-en-freeCodeCamp-a54453137ce043c4859f912738d64b2a251afc29787d784d9339aa3cca219ee4","title":"","text":"The Project euler problem 250 has a format issue Confront with To fix this issue you will need to change this file so that the numbers are correctly formatted as exponents: (You can use the way ^ is written in the challenge as a guide to fix 1^1, 2^2, and 3^3) 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. An issue with the help wanted or first timers only label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. 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 have set up the project in my local machine and looking to contribute for open source is this still open can I work on it"}
{"_id":"doc-en-freeCodeCamp-f9cd58cb25280d2deb8301f0687764fd29dc1bec4c1fbfc7ba429a9d8e784782","title":"","text":"This part is still tripping people up Usually one piece or another gets lost: Maybe this is clearer Side note - I still don't love the fact that we say like a variable instead of like a string literal. I think that's confusing here. (I know, I know, the style guide hates \"s) No response All No response\nAgreed, it has the potential to be confusing. Can we reword to say: \"If is the string and ...\"\nI'm still not clear on the reason why string literals in inline code blocks are forbidden by the style guide since it makes the instructions less clear in this case. do you have some context?\nI don't remember the full reason, only that it was a decision made as part of our i18n efforts. We reference a discussion in but I can't for the life of me find where that discussion is."}
{"_id":"doc-en-freeCodeCamp-bbd93f8470b7d7ea5f9f55cabdaa328f863dae7eaeb118e691c7f506ed288615","title":"","text":"Currently on step number 5 there's a note that reads Note that when reassigning a variable that has already been declared, you do not use the let keyword. As it stands this note is incorrect and unnecessary. No code, just instructions re-wording. The note could be changed to: Note: You can only re-assign a variables that has been declared with Or we can simply remove it altogether instead. <img width=\"1217\" alt=\"Screen Shot 2024-05-02 at 10 31 38\" src=\"\"- Device: [Laptop] OS: [MacOS 12.7.4] Browser: [Chrome] Version: [124.0.6367.91] No response\nThe note is correct. I think you are interpertering it wrong? It is saying does not need to be used when re-assinging the variable with a new value. edit: It is not saying that you can use any kind of keyword like or\nI understand what's it's trying to convey, but it's written in a confusing way. Here's the text directly copied into ChatGPT for some additional context: <img width=\"820\" alt=\"Screen Shot 2024-05-02 at 11 01 54\" src=\"\"\nText refers to potential situation when both assignments are using , ie: Depending on where exactly both are used, this can result in . - - x = 10; There's no on this line. It's one of the cases when chat doesn't know what it's talking about.\nHi thank you for creating the issue. As Sem pointed out, we don't think the note should be updated to because the new version communicates different information from the original. I think the confusion came from the word \"declared\". The word isn't needed since \"reassigning\" already implies that the variable has been declared, so I'd propose changing the sentence a little: cc'ing for input, since you're much more experienced with this kind of change than I am\nThanks for the input your proposal addresses the issue I presented\nThat change works for me. Let's open it up for first timers This has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors."}
{"_id":"doc-en-freeCodeCamp-ac254695d37c5de9e3d6f455e65a6fdc02480cc088a6d2cdf28fba8746fc8530","title":"","text":"If you would like to contribute and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the js let programmer = \"Naomi\"; programmer = \"CamperChan\"; ` Happy coding"}
{"_id":"doc-en-freeCodeCamp-cbc54c7df1af71f1efe1bed30c8aacd1f8548663fda18389dd765770cf8d40cc","title":"","text":"The following test (user story) prevents my previously passing project from passing: Important: Notice I use instead of just I never claimed to be a UI expert Do we want to keep such a test? No response Unrelated No response\nMaybe you should update your project Honestly I think small tweaks are going to be okay - my tribute page fails because the image needs a height now.\nI am also happy with small tweaks, but we did (largely) want to keep the requirements exactly the same. The only change we agreed upon is to add requirements for tags.\nLooks like they accommodated for the tag in that test. Maybe we can just add it here too.\nalthough, I think it's good, that we moved on from the old test. tag is extremely useful in html, it has attribute that help developers use less needed css, which lead to better experience, . it should be accepted to use Edit: if you paste this code in it won't pass although there is a media query but in the html Edit: I changed the for easier testing"}
{"_id":"doc-en-freeCodeCamp-8e12d708f1d3f8f36c2cf176eb60bbdcfab77d3d5248c4869781f5275c5ebc7d","title":"","text":"Even though on macOS it would seem that Ctrl+Enter does not work & Cmd+Enter does; website still tells you to use Ctrl+Enter. I think this might end up being confusing for some - and should be fairly straightforward of a change. All coding pages You must use macOS for this issue. to any coding challenge your changes will see button underneath says \"Check your code (Ctrl + Enter)\" Ctrl + Enter will happen. Cmd + Enter behaviour will occur. It should tell the user correct shortcut (Cmd + Enter) instead of (Ctrl + Enter) depending on the platform. <img width=\"647\" alt=\"Screenshot 2022-06-09 at 16 52 28\" src=\"https://user-\"- Device: M1 MacBook Pro OS: macOS 12.0.1 Browser: Safari Version: 15.1 No response\nI would like to handle this issue as a first contribution. My proposal would be to use (). Use Ctrl + Enter as a fallback and define a special case for macOS cases. Alternatively we could use () however that is not widely supported as opposed to . As far as I can tell on mobile we don't show modifier keys on the button; so I'll preserve that behaviour. I can't change the labels on this issue - I don't think this is severe enough to be classified as a bug based on definition; my apologies regarding that.\nHey thanks for raising this issue and don't worry about the labels, they need to be handled by maintainers. What you've suggested does sound good to me, so if you're happy to take this on, that's awesome.\nI've created the PR however; I've updated non English translations as well in here to use dynamic values; however not really sure how to align it with the crowdin. Since updated translations should coincide with this change; any opinions on this?\nDo not worry, I think you are putting too much effort into it. Simply drop the changes to those files and as the bot mentioned, they will get updated eventually via our translation workflow. As for the bug itself: I am 100% sure at some point we introduced a regression, because (in addition to the implicit Cmd + Enter) was working since the inception of the code editor. do you happen to know if this was just an accident with the new editor?"}
{"_id":"doc-en-freeCodeCamp-7ac2908a8f05ecfc6049911c8a00ad2deed072b2cc68655edf00516d45664f72","title":"","text":"To be clear it should always work with regardless of the OS in addition to implicitly working with just like it was before.\nI can't check this myself, since I don't have a mac, but it should work. This is the code: and could you try and reproduce the issue?\nI've shot a short video of the behaviour I am seeing; if that helps.\nThat does help, yeah. It seems to be ignoring the command button entirely, which is odd. I can't investigate myself, but this will help anyone that has access to a Mac.\nThanks for the video I don't recall if ctrl+enter ever worked on mac - I may or may not have ever used it. I just hit buttons without looking I'm not sure if you are trying to show something specific with those code snippets - that's the code on main. Which results in the current behavior. Edit: I get it now - you were just showing the code and that it should be working. I thought you trying to show new changes or something. Here's the current behavior I see (all on mac) - there's some nuance... New RWD: Execute: only command+enter works on mac Submit: Enter alone works, so any key+enter works Legacy RWD, JS, etc: Execute: Only cmd+enter works Submit: Enter alone does not work - both ctrl+enter or command+enter do work Multiple choice Python video questions: Execute: Enter alone does not work - ctrl+enter and cmd+enter work Submit: Enter alone does not work - both ctrl+enter or command+enter do work Projects with URL inputs - e.g. front end libs cert project, or backend api challenges, etc: Execute: Enter alone works cause it's a form I suppose, which also means any key+enter works Submit: Enter alone does not work - both ctrl+enter or command+enter do work The last three groups there have the same submit modal, so the behavior is the same on all of them. What I see is that the submit modal, and the video question both allow [ctrl or cmd] +enter - we should see what those are doing. Looking into to it...\nK, I think I found a fix. ctrl+enter works when the hotkeys package/component is used. So crtl+enter actually does work on the legacy challenges when the instructions are focused."}
{"_id":"doc-en-freeCodeCamp-54d558a1c3cbba1a76fbc3181d8965f9e076c0a12ae00262c78ea4854f1135c1","title":"","text":"When the editor is focused, those hotkeys don't get used, the actions/hotkeys we add to the editor take over. I made ctrl+enter work when the editor is focused by changing that line 431 mentioned to this: That should work. There's a number of actions in that file that use the same hotkeys - lines 457 and 469 for example. There may be others. I think we should be safe to change all those. Do you mind playing with that a bit and updating the PR to make those changes.\nNice work, Tom. I thought CtrlCmd was \"Ctrl or Command\", but it must be Ctrl on Windows and Command on Mac :man_facepalming: I guess this has never worked properly.\nhappy to give it a look and update the PR. Thank you\nHere's an I had created sometime back when working on the . Apparently the logic goes like this - the first word is Windows and the second one is Mac button."}
{"_id":"doc-en-freeCodeCamp-6f94e51f2cae7eeacd58ec52d3e48386d1ac28d1f3dc70df28c945e388ee9a80","title":"","text":"Describe the bug 1) It appears a was accidentally left in the script. 2) A request to my/(a user's) page-data is returning a 404. To Reproduce Steps to reproduce the behavior: to DevTools log or in console, due to: File: Line 126 error in console as in picture below. Expected behavior No Errors, no logs. Screenshots ! Desktop (please complete the following information): OS: Windows 10 Browser: Chrome Version: 83.0.4103.97 Additional Info I believe the: 'progress updates processed where possible' Is useful, and should stay.\nI think it would be better to remove all the logs, since we can use the flash messages if we need to communicate information. Ideally, all errors should go to Sentry. This currently does happen for the server, but we haven't implemented it for the client, yet. Basically because there's still a bit too much noise (like the page- 404 in your screenshot).\nYep, git blame and me for missing it in the QA. Reference: A PR is welcome to remove this and any other rogue logs. This is an expected side-effect of us using Gatsby's routing to query and get the user profile available at . Essentially, when you hit , we first let Gatsby check in the static files if something is available at that path, if not we query the API to lookup there for a username. If both conditions fail, we would render an actual 404 page. But for this to work the status code 404 is sort of abused. Its hacky but there is no way around this to the best of my knowledge. Just to clarify, this should be left as is.\nany suggestions where to search? I am trying to search around, but there doesn't seem to be, or I am finding those in the challenges code maybe there aren't\nIt's a bit tricky, because we use console logs as part of the challenge code, but the place to look is in could you explain why 'progress updates processed where possible' should appear in the console?\nthere are a few, but they all seems needed where they are\nI don't know why, but it comes from file line 98\nthere are some s, s s, too. gets me: of which probably should not be there."}
{"_id":"doc-en-freeCodeCamp-ee157aecc4ff09adc0c9219489477b45863b3d1135a8980e2a87e8bf893a0c35","title":"","text":"I'd like to get input before we remove them, though. I think should eventually make it to Sentry and possibly should too.\ncould you explain why 'progress updates processed where possible' should appear in the console? , Sorry - my language was too strong. I meant to say: For no other reason than it is a debugging message. Re-thinking about it, I think it could be more useful being changed to , as that is how I interpret the message. After all, it is a component.\nThere's nothing to apologise for. So, my position is just that debugging messages are things that should be shown to developers, rather than users (if possible). Essentially because that information is intended to help find and fix bugs, which isn't something a user should be expected to do. In this case 'progress updates processed where possible' mostly just indicates that you've navigated to a challenge, so I don't think it's useful. seems worth showing, but only because we don't have access to this information with a remote error logger (Sentry in our case)."}
{"_id":"doc-en-freeCodeCamp-8f586eb3f95cf85eea75384224435e0ddac04a5b91e7c46bd7fc3b2e42bd95f0","title":"","text":"<!-- NOTE: If you want to become an author on freeCodeCamp, you can find everything here: --<!-- If you are reporting an issue with an article on our News publication, please follow this link to send an email to our editorial team --<!-- Add a link to the page with the problem. --<!-- Describe the problem and how to reproduce it. --<!-- A clear and concise description of how you want to update it. --<!-- If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box). --!\nHi ! Thank you for finding this typo. I have the first timers only label since this is an easy fix. For those interested in fixing this issue, here is the file you need to change. Proposed fix: The border-radius property accepts up to four values to round the top-left, top-right, bottom-right, and bottom-left corners. Please also read through our . When the file is fixed, please make a PR referencing this issue and it will be reviewed. Happy contributing!\nI'm going to start looking into this.\nThank you for fixing the issue. It was the first time for me on Github. I'm a total newbie in the webdev coding bootcamp."}
{"_id":"doc-en-freeCodeCamp-ab7a3a3a5cfb178bab6f55d27854b7d5c8a5f7ce14682f8aad0194e32b8022d8","title":"","text":"There is a difference in the font size and the margin between the text , on the home page () and the learn page (). Although you may not notice it on first glance but it disturbs the UI. The \"sign in and get started\" button on home page is also wider than the \"sign in to save your progress button\" on /learn page.\nHi Could you add some screenshots that demonstrate the problem you're describing?\nHere are two screenshots from the landing and the /learn tab, before you're logged in. ! ! There is a difference with the button width being stretched to fit the container in the landing page, but not on the /learn page. There is a minor difference in the margin right below the 'Welcome' Header between the two pages.\nI was talking about the change in margin between \"Welcome to \" and \"Learn to code.\" on the lading page and the /learn page , and the width of the yellow Button on the two pages , as you can see in the screenshots shared by\nThanks for clarifying, and I'll open this up for PRs.\nImplemented some changes. Please see screenshots <img width=\"1280\" alt=\"Screenshot 2020-01-19 at 09 59 13\" src=\"https://user-\"<img width=\"1280\" alt=\"Screenshot 2020-01-19 at 09 59 31\" src=\"https://user-\""}
{"_id":"doc-en-freeCodeCamp-72782e38ba9a4963f985e49d55a0b5930b1c69c7b6d7febbcff8c4e0fac5c0a7","title":"","text":"There are missing spaces between some words in: \"welcomeToBooleansfunction so that it will return trueinstead of falsewhen the run button is clicked.\"\nThere is a similar issue with \"Waypoint: Use Bracket Notation to Find the Nth Character in a String\" In the first paragraph and the third paragraph. As does \"Waypoint: Manipulate Arrays With unshift\" in both paragraphs."}
{"_id":"doc-en-freeCodeCamp-219ad931c641558f080435fd4a2d9a0472af24d07da7392b849dd0930a7cb560","title":"","text":"We got some feedback here about the spreadsheet project step 31 They mentioned that if you try to use an OR operator here then the hint does not tell you what's wrong. I think the easiest fix would be to just update the directions and hint text to explicitly mention the use of the AND operator. This has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the Happy coding 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\nHey Jessica, may I open a PR to fix this issue? Thank you!\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-5ebf2de007ae3a130e9cda1f2e7778f6c1cf3f66597a290abe7f12731bd6cedc","title":"","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:50.0) Gecko/ Firefox/50.0</code. Please describe how to reproduce this issue, and include links to screenshots if possible. There is inconsistent spelling in the instructions. Is it \"inline\" or \"in-line\"?\nthanks for the issue. They should all be ."}
{"_id":"doc-en-freeCodeCamp-72bb2682bd59e62633dd06b6811b4042dd43408796e6690030c5f58a63cd1459","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: Challenge is missing a period in its description. ! Add a Link to the page with the problem: Here is the file that needs to be edited:\nBtw, I think there is a typo in the description as well: should be\nLooks like those could both changed."}
{"_id":"doc-en-freeCodeCamp-a0576a87f4cf2a28a4895412e10465c1a7b265fb291212aa477a546c7e500330","title":"","text":"I suggest changing the phrase 'template interpolation' to 'template literals,' because are correctly referred to as template literals, which support string interpolation. ! Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response_\nit should be \"string interpolation\". Template literals are already mentioned a few words before, it would be extremely redundant. I'm opening this issue for first timers to make the change \"template interpolation\" -\"string interpolation\". This change needs to be done twice in this file: Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.\nSorry for the misunderstanding. I need to change the text from 'template interpolation' -'string interpolation'\nHi, I guess has raised his PR with the needed change. I haven't contributed before to any open source project. I thought this was an easy one to do to get started. Please tell any easy code or non-code contributions to be made. Happy to help.\nI am able to make the required change and happy to start open source contribution with hacktoberfest . Kindly assign this issue to me.\nWe typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labeled with or are open for contributions. Please make sure you read . We prioritize contributors following the instructions in our guide. Join us in or if you need help contributing - our community will be happy to assist you.\nThis pull request resolves the issue of incorrect terminology in the JavaScript curriculum where \"template interpolation\" was used. The correct term is \"string interpolation,\" as template literals support string interpolation. I have made the following changes: Replaced \"template interpolation\" with \"string interpolation\" in the two locations within the file. Fix :\nAfter reading the contributing guidelines, I now understand the mistake I made in my PR."}
{"_id":"doc-en-freeCodeCamp-6dab1c8f70b0733f57dab87ba65dc3cbbed275bd57cb66a91855d81188e2eff3","title":"","text":"This sentence seems to be confusing campers on the forum Let's go with this updated description here 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\nHi, I have created this PR as a first time contributor (no PRs merged yet) to this codebase. Hope the changes are up to expected requirements. Thanks!"}
{"_id":"doc-en-freeCodeCamp-f0db4dce4dd952d2d2f9af0cf838f045ef6f0a1b2b23899f21ff16856770aeed","title":"","text":"There is a typo in Step 156, the word is used to refer to the operator. Here is the typo it should be Can you change the lowercase that refers to the operator in the file, to uppercase , as well? to follow the docs of Mozilla If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first. Happy contributing.\nHello, I would like to work on this issue.\nhello,can i resolve the issue?"}
{"_id":"doc-en-freeCodeCamp-d045ccca1a1caa338b0bdde2b4aaa55e9b387fbf33dc28f8cfc0906d22f29c65","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 this forum topic: Affected page File: Your code Expected behavior As this challenge is about lazy matching this code should fail Maybe a way is to make sure that the character appear in the right place, there is a test that check if the character is used, so maybe we would need to have a test that check if or are used this in the screenshot checks only for , maybe we can add also the possibility to use as that is also lazy matching ! and just as we are there, removing the flag from the regex as it is not needed, see maybe also this can be fixed so that nor nor are included in the regex"}
{"_id":"doc-en-freeCodeCamp-a4fd84cdedd7c0a726d9d7322f9bb092836a629ff9c17e1443b105858258fbf4","title":"","text":"Describe the bug The PayPal sdk gets called by the local site, even when there are no keys specified in .env To Reproduce Steps to reproduce the behavior: to any page with a donation component the console a 400 error Expected behavior If the keys are missing, PayPal should not be contacted. Screenshots !\n/cc\nHello guys! Does this happen on page or somewhere else too? Can't recreate it anymore, happend only once. I'd like to help with that issue if you don't mind Also, I noticed PaypalButton has a typo -in props, example:\nit should happen if you hard refresh on donation page. (and on donation modal) That script loads the button. A solution would be to check for paypalClientId in the render of PaypalButton component and return PayPalButtonScriptLoader only if paypalClientId is truthy.\nPR is ready. Could you please take a look? Also about the Stripe issue. I'm not sure if it's expected/known but if I don't configure the key for stripe, the page isn't loading for me at all. <img width=\"1054\" alt=\"CleanShot 2020-05-11 at 02 59 29 src=\"https://user-\"\nYikes, that seems like it needs a fix as well. Thanks for catching that."}
{"_id":"doc-en-freeCodeCamp-e6e038ff0a61841b2e41238cd997543312ed0132abdcefc878a0c7c116ebff14","title":"","text":"[ ] Trigger Click Events with jQuery [ ] Change Text with Click Events [ ] Get JSON with the jQuery getJSON Method [ ] Convert JSON Data to HTML [ ] Render Images from Data Sources [ ] Prefilter JSON [ ] Get Geo-location Data\nWorking on it!"}
{"_id":"doc-en-freeCodeCamp-86a265e4f748cedf1699b2c4665bc32ebba55a52791f6af626530c662e40339f","title":"","text":"the code below should be accepted by the check for step 35 of the pyramid project as it is a valid attempt. However, currently it is not accepted unless the user deletes the extra space to the immediate left of the second semi-colon. less strict space checking in the for loop condition. No response N/A No response"}
{"_id":"doc-en-freeCodeCamp-0f05ca4f9ddcb641b310fe67c17a315ec22cdbb5ee1b07d92c5cbc55d41903ba","title":"","text":"Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. 4th paragraph reads: \"Use bracket notation to find the first character in a the firstLetterOfLastName variable.\" The \"a\" is not necessary"}
{"_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-83eca547f0d3e69a54239f5587b79bf7d0e0b7d58021b5936a170fa0b324dc7e","title":"","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: Usually, paragraphs are separated with an empty line but here it is not. Currently, both paragraphs are in one string with a separating the two paragraphs. For this challenge in the file, the second paragraph should be on its own string so the spacing is consistent with all the other challenges. !\nSame goes for this challenge as well:\nHumm, don't know why I did that. Yes, these need a proper line break.\nIs this how you fork? This is my first time.\nI would consult the . It's got a lot of helpful information. The things I can see that need to be changed are: the branch name (it needs to be in the form of so like would be good) and also the issue number should not be in the commit title. It should be in the commit body and say something like . Here's more information about ."}
{"_id":"doc-en-freeCodeCamp-b87dde3a56f81197e1059d70e737ae85907415127d77731fbaa77954d332ab33","title":"","text":"to your profile settings page the privacy setting to the top and click The privacy setting you changed will not have taken effect. From there, you can go back to the settings using the settings button, and the privacy setting will still show it as it was before you changed it. I believe this is due to using to navigate to the portfolio. The setting will have actually changed in the DB, but the effects won't show until you do a hard reload.\nI can fix this if it's decided to change it.\nAs far as I can see, the problem is that the user is only pulled from the server once. The server is getting updated correctly, but the redux store isn't being asked to mirror these changes.\nas there seems to be an issue with a redux reducer.\nI was speaking to earlier and he says:\nIs someone looking into this ( Otherwise I can take a crack at it tomorrow.\nGo for it - let me know if you want to team up on it."}
{"_id":"doc-en-freeCodeCamp-a6d770564aebdaa66b0c0b7af1b37ac95c515453c67a146896ab780c222c74a2","title":"","text":"I don't think this challenge is described correctly. The idea that a variable is only available to the element and it's children has nothing to do with cascading. It's a clear definition of scope. Cascading is the concept that if there are multiple of a thing, the last one wins, which is described in the previous challenge related to fallbacks. Just my 2cents for what it's worth, but if I had someone come in for an interview and tell me cascading was the idea that a variable could only be used by an element and it's children, I would consider that a wildly misunderstood concept.\nThanks for reporting this! While this challenge isn't intended to introduce the concepts of cascade and inheritance, it clearly does not use the terms correctly. I'll have a go at rewriting the challenge to show that CSS variables behave like ordinary properties in this respect.\nfor what it's worth, this was discussed a little bit in a previous issue that was never resolved - - perhaps it should be reworded since it has now come up multiple times."}
{"_id":"doc-en-freeCodeCamp-af2b8ede204467aa97ec53a159f9a7a2ce17e592bcc18c65a8a7405825da2ccf","title":"","text":"Describe the bug Using the search-Field and clicking \"See all results ...\" To Reproduce Steps to reproduce the behavior: to '' on 'Search Field' and enter s.th. I did \"Flutter\" and then I clicked \"See all results for Flutter\" error: \"404 Page not found\" I think the error is easy to fix: The automatic created result link after clicking has double \"news\"-part: if I manually remove one \"news\" as the result would be the correct one.\nThanks for the report! It seems it's a problem with redirection. redirects to and the link is to which redirects to cc:\nThank you for reporting this This was also a problem on /news. I deployed a quick fix and am working on PRs now. I noticed that we could change the URLs in the search related files from to This seems to get around the problematic redirect, at least for search results. Still an issue we need to investigate further for other use cases.\nsearch is still broken? I can't get anything to load for generic searches.\nwhat sort of generic searches are not loading for you? Things seem to be working on my end whether I search from .org/ or .news/.\nworking on my side on news and learn from multiple locations for the initial test case.\n!\nShould it say something like \"No results for for 'this is a generic search', please try a different query\"?\nThanks for the gif, I see what you mean now. The behavior should be a message that says \"No tutorials found\" and not to allow the search to complete. There's a PR for this on News , and I'll start working on the implementation in the main repo.\nI am going close this since the above prs address the issue. Feel free to reopen if you think this issue has been closed by mistake.\nHas the fix landed on production. I am able to reproduce the issue?\nhas not landed yet on learn. but you could see the fix on /news\nThe query string is passed on to the news application. URL is available on the GIF that I sent.\nwe deployed the updated theme to News, so you shouldn't be able to enter a long string there and hit the search results page. Once the fix to Learn is deployed you won't be able to pass long strings with no hits to News like in the GIF."}
{"_id":"doc-en-freeCodeCamp-cc23328e1e4d35c48ed696db706791cfad90d19685fd038d9d827bad2914eada","title":"","text":"Quick follow up, is there anything that is preventing us from deploying?\nsorry for the delay in deploying. We just got access to the client VM to clear out the old builds. We'll do that later today and get all these changes out.\nGreat, thanks for confirming. Apologies I have the keys to the VMs a couple days ago. I missed letting you know. I have also cleared the older builds. You should be able to simply run a build. Thanks.\nNo worries man. Thank you for adding our keys. We should have checked to see if we had access yet. We're just about to go in now and run a build.\nThis fix has been deployed. The problem in the gif above should no longer be possible on or"}
{"_id":"doc-en-freeCodeCamp-bf39724d2e827eab9ceffbecd550381e23bd8b12c0e70c766f99df73042caa43","title":"","text":"There are two links in docs. Following are the two links how to work on coding challenges. up freeCodeCamp locally I am also adding screenshot to show more clearly that which links are broken. ! so when we click on these links in README in docs it shows page not found\nNice catch! I will correct this.\ni have linked pr for this issue kindly merge it thanks\nWe will have to figure out a better way to handle links. We are currently using to host our documentation at This means we have to handle links in a way that they work on that page. I think a quick way to work around this would be to rename to which we render on the contribute page. Then we create a in which just has a notice similar to the Thoughts?"}
{"_id":"doc-en-freeCodeCamp-d074c5487b553d8354c5beb4e92f8824648773f6ed572b160658d9d3be6a6f70","title":"","text":"Thanks for noticing this, Sem. As this route has been deprecated for a while, we should be able to safely sunset this route - NOT have it in the new API.\nReopening it as we're migrating deprecated endpoints as discussed in todays API meeting"}
{"_id":"doc-en-freeCodeCamp-5307c8971d736c321032a51b48f9902d94f95b8ca261e0b7c6779249febdd172","title":"","text":"! Hi I have found this on my Learning Map... Hope this can help you all in solving bugs... :)\n! Note: it seems to appear only on the section of lessons that I have completed.\nThis was fixed in and can be closed.\nafter reloading the page, I still get this - has the fix not been pushed to the server yet?\nIt got pushed just there folks!"}
{"_id":"doc-en-freeCodeCamp-00a8696a25161a801af471fed373a732aad527129a6b6d1bc5f586e903b0be61","title":"","text":"Describe the bug Up and down arrow key don't work after typing JavaScript reserved words To Reproduce to a challenge in Basic JavaScript (Example: ) the following code: (or other JavaScript reserved words) in the second line up or down arrow key on the keyboard pointer can't move to the previous or the next line Expected behavior The pointer can move to the previous or the next line Desktop OS: Windows 10 Browser: Chrome Version: 83.0.4103.61\nYeah, I just tested it. It's reproducible.\nIt looks like it happens if there's a syntax error. Also it can be cleared by typing anything else. I reproduced it by clearing the editor and then typing At which point the cursor will not move up. However, if you press , everything starts working properly again.\nYeah... it's definitely not a big bug. Might cause minor annoyance though.\nAgreed. It's not urgent, but it's definitely not working quite right.\nI'm guessing it has to do with the changes we made to the editor in I think the arrow input is stuck inside a hidden suggest menu. I would need to look into it some more but here is a gif showing changing as I click the up and down arrow. I suspect this happens after triggering the menu and the arrow up/down input is supposed to be moving up and down inside the menu. ! The menu from the monaco editor playground ! Edit: It is the menu. You can pick an item from it. let down arrow Enter is replaced with (see screenshot above for the location of length in the menu)"}
{"_id":"doc-en-freeCodeCamp-c7bee19ff795c5f2929751c1fe609035834fecaccf1fde1093d0ac18c37e1326","title":"","text":"In step 28 of the date formatter project, the hint shows the solution, which is not hard to explain. This might not be ideal for learning, as a camper (especially a JS) beginner can go ahead and copy the solution from the hint without bothering to understand what the code does. ! N/A The solution should not be in the hint text because it can be described. We could go with something like this: If the text is too long, it is better to break the hint text and test into two. 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\nThe same text is in the description, it would make sense to change description to not give out answer at the start.\nBased on the activity I have seen on the forum, I think campers will struggle with connecting \"interpolate the , , , , and \" with the desired format we are asking from them. I think it would be best to show them the desired format in the description. something like this for the description\nSo we should leave the hint as is and modify the description text?\nfor the hint text we could go with this\nOk. Let's open it up for contribution then.\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 please use this for the updated description please use this for the updated hint text Happy coding"}
{"_id":"doc-en-freeCodeCamp-03b3b4fa06db8c93318a4d8f55d9c8eb4d369a66c84bbffbb74c991b2b35c676","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'm on the Regular Expressions: Check For Mixed Grouping of Characters. I was able to pass this checkpoint with a solution that doesn't meet the objectives of the assignment. I used the following code: With this code I match just “Roosevelt” which is only part of the name(s), yet I still pass the assignment. Add a Link to the page with the problem: With this code I match just “Roosevelt” which is only part of the name(s) we are supposed to match for this assignment, yet I still pass the assignment. Tell us about your browser and operating system: Browser Name: Chrome Browser Version: Version 79.0.3945.117 (Official Build) (64-bit) Operating System: Windows 10 pro If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):\nI think that the regex you've written should pass the test. The part is a capturing group, so the regex will match or . The as a quantifier will match the above 0 or 1 times. This means that your regex will capture as well as Unless, I'm mistaken, I hope this helps :)\nApologies... Actually, I've re-read the instructions. I think you may be onto something.\nYeah, the problem is that it matches the string \" Roosevelt\". A simple solution would be to add another test that makes sure it fails if you use, say, \"Frank Roosevelt\".\nWould like to have a crack at this\nGo ahead and create a PR.\nHad a go Please see"}
{"_id":"doc-en-freeCodeCamp-0aa659dca3b70c97a9d7525e33b4d20486f31ef187180cd6369e18ff25f0da2c","title":"","text":"If the user adds the new tag on the same line as the first tag then the test will fail. The hint will tell the user that they should have two tags, which they do. As soon as the new tag is moved to a new line then the test will pass. If we want to require that new tag be on a separate line then we should mention this in the instructions or give a hint that tells the user it must be on its own line. Otherwise we should update the test to stop checking for this. No response Confirmed in both Firefox and Chrome. No response\nThanks for opening this issue. This looks something that can be fixed by \"first time\" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: Changes to make: You will need to change this test: The regex needs to become . Explanation: the matches everything but line breaks, so the pattern with matches all the line up to the , in case of two meta tags on the same line, it matches both of them at once. Adding the in front of makes it a lazy matching, meaning it will match as little as possible while satisfying the pattern, and if the two meta tags are on the same line it will end the match at the first . Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing."}
{"_id":"doc-en-freeCodeCamp-0244e418dc4d5046d5e2938b2d9a86519d664f464739c0852982c697c1cdeb22","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. --in here should exist <code</codeelement: &lt;codesans-serif&lt;/code ! <!-- 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. --win11 Firefox Device: [e.g. iPhone6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.4] Browser: [e.g. chrome, safari] Version: [e.g. 22] <!-- Add any other context about the problem here. --I want to modify it myselfbut I don't know how to deal with it. I don't know how to find him\nHi thanks for raising this issue, but there's nothing to fix here. The reason is that sans-serif is not being used as a programming term here, it is referring to the class of fonts. Multiple different fonts, such as Arial and Helvetica, fall into this class.\nHi@ Verdana similarly referring to the class of fonts, but please note picture, Verdana is surrounded <codeVerdana </code! in here should keep consistent\nThanks, that's a good point. I think Verdana should simply be plain text for consistency.\nand The instruction to set the preferential font to is not a suggestion for a family of fonts. It is an instruction to use the code-word as the preferential font. It should remain within a element. Specifically, we are talking about family-names and generic-names : is not a generic-name font.\nIt's a bit of grey area, to be honest, but I feel like this is not really code. Reason being, it's just the name of specific font family called Verdana. It's not a keyword or part of any specific language, it just a string id that lets you get a via a rule.\nAm I missing something?"}
{"_id":"doc-en-freeCodeCamp-7e679e2308ddec37bf9a48a1b873513e9436993244a900250d69cec83f9f7a04","title":"","text":"The challenge expects Campers to use the code , if they put anything else, it will fail. js const gs = (s) =new __helpers.CSSHelp(document).getStyle(s); const style = gs('h1, h2') gs('h2, h1'); assert.include(style?.fontFamily, 'Verdana'); `\nand sans-serif both part of the actual css code !\nMy two cents, for what it's worth. I think Verdana should remain marked up as code since the instructions are specifically telling the user to use Verdana for the initial font. I've found other courses that have the font name marked up as code in the instructions as well. And it just seems that in general, whenever the instructions tell the user exactly what value to add, the value is marked up as code. And I also think that sans-serif should not be marked up as code since it is referring to a family of fonts and the tests will accept five different fonts for the fallback, so we aren't telling the user specifically what to use here. I'm guessing any confusion stems from the fact that one of the acceptable fall back fonts is sans-serif itself. Perhaps we could reword this a little? \"..., and use another web-safe font in the sans-serif family as a fallback.\"\nThank you all very muchI understand itsans-serif is a family, Verdana is a sans-serif family menber. I think the suggestion is very good. <br !\nLet's go with wording, I think that should be clearer than what we have.\nHow should I further locate where the file is !\nis the file you need. We're in the process of making it easier to search for individual steps, but for now you can search for the title (Step 17 in this case) within that folder. For instance\n&nbsp;thank you ---Original--- From: \"Oliver Date: Fri, Apr 8, 2022 19:10 PM To: Cc: Subject: Re: [freeCodeCamp/freeCodeCamp] in here should exist <code&gt;</code&gt;element (Issue ) is the file you need. We're in the process of making it easier to search for individual steps, but for now you can search for the title (Step 17 in this case) within that folder."}
{"_id":"doc-en-freeCodeCamp-6520ec2d8f5686c6248de628cab659d2664f4639190c1c1f1fbab3126c646b88","title":"","text":"For instance grep -r 'Step 17' — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID:"}
{"_id":"doc-en-freeCodeCamp-3d083c8a309bfc593040ed0554e875aafe490ea0d54262798bd417835aaaf9d3","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 challenge \"Testing Object for Properties\" passes with wrong code: Add a Link to the page with the problem: users find the old solutions, paste that in the editor, and then add a new property to the object... My proposal is to add a few more tests - even obscured if needed, to avoid these kind of solutions passing\nI created a PR to deal with this issue."}
{"_id":"doc-en-freeCodeCamp-fa0dd1af7040c4eaa2f6709f8b8c3e59222b55d77275348444ab208fbbd776a1","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 usage of the word \"argument\" ist unclear to me. The title of this challenge uses the word \"parameter\". Then the instructions state: \"If an arrow function has a single argument, the parentheses enclosing the argument may be omitted.\" But the following snippet cited from the instructions shows the parameter \"item\" without parentheses: The functions are never invoked with an argument in the examples. As I understand it the sentence should say: \"If an arrow function has a single parameter, the parentheses enclosing the parameter may be omitted.\" Add a Link to the page with the problem: or, Tell us about your browser and operating system: Browser Name: Browser Version: Operating System: If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):\nHello~! I agree that the verbiage is wrong here. should probably be replaced with in the examples and text, with the exception of the top line (which, at a quick glance, is the only correct use of ):\nThese are the ones that should be changed, I think. In fact, we could use instead.\nI like that approach. Think this could be opened up to first timers?\nI would go for: Just like a regular function, you can pass arguments into an arrow function. If an arrow function has a single parameter, the parentheses enclosing the parameter may be omitted. It is possible to pass more than one argument into an arrow function.\nSure, that works."}
{"_id":"doc-en-freeCodeCamp-6d0b624ac84c104fd3d86b8143b25380dfcf51e4253691a2db41c1f1d68ab5dc","title":"","text":"When writing Python code in the editor, it would can be a bit frustrating for campers to keep track of the indentation specially if the instructions are a bit wordy. Also, the tests would fail in case indentation is incorrect. It would be a good feature to provide assistance within the browser editor to maintain indentation. A good example is how VSCode provides markers: ! No response"}
{"_id":"doc-en-freeCodeCamp-2863d6451c4e4fbef04b632ac3293c310ef9f21e55bdaa16c966efc50a7b9626","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: For this challenge, the starting code in my editor contains the following lines: The challenge is Since the idea behind this challenge is the ability to combine conditions with the && operator, I would expect the starting code to instead read: 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.100 Operating System: MacOS Sierra If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):' <img width=\"1408\" alt=\"Screen Shot 2019-11-10 at 5 36 23 PM\" src=\"https://user-\"\nThe instructions tell you what to do regardless of the seed code. If the seed code was provided as you describe, it would not be much of a challenge to solve.\nI think the point of the exercise is to demonstrate the usage of the && operator, so even though it's easier with my suggestion, it's not trivial. If you'd rather not give that hint, though, there's no reason for the nested if statements in the seed code, and I was confused by them. The seed code should read:\nThe point of the exercise is two-fold. One is to teach the user how to use the operator. The other is to have the user figure how to achieve the same logic with the operator as without the operator using the nested if statements. I do not see any reason to change this challenge. I will let the other collaborators/mods give their opinions on this issue.\nI'm with on this one - I don't think the seed needs changing. I redid the challenge and found that the nested if statements were helpful. You can create the intermediate solution: if you're more comfortable with nested if statements and that will pass all but the first two tests. This allows you to confirm that you've got the logic right before refactoring it into a single conditional. The only thing I would consider changing is to since 'combine' slightly implies that the new statement is built out of the original two, which isn't really the case here."}
{"_id":"doc-en-freeCodeCamp-67a73f6dd52d75ef701f896bc6f2c553742d21f8814e38c0dba4c07e4b837dc1","title":"","text":"Doing that should make it less confusing without watering the task down.\nThanks I like your suggestion to change the wording to\nAny interest in creating a PR for that\nThank you for the link"}
{"_id":"doc-en-freeCodeCamp-84fa9c19a4f383a592614f14ca792bad289e6faa9f03a072000a865419880c60","title":"","text":"Affected page Your code The callback url is redacted. Expected behavior I expected this code to pass the tests. But it did not. System (please complete the following information): Device: [Laptop] OS: [Ubuntu 20.4] Browser: [Opera] Version: [77] Additional context The third test didn't pass. So, I ran FCC on my local computer and checked the tests on the page. The first regex test is as follows: The regex won't pass if is on a new line because matches all characters except for the new line. When I replaced with the tests passed. So I think we should change this test to the following: My reasoning is that the correctness of a solution should not depend on formatting. Especially when the formatting is not something very abnormal.\nHello there, Thank you, for taking the time to open this. In general, we need to find a better way of testing these challenges without using RegEx, as mentioned in As for this issue, a quick-fix could be as you mentioned, but, I might even just make the test to use the flag: An issue with the help wanted or first timers only label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the\nHello, Can I do this? I understand that I just need to change to this , right? I just didn't get this part: \"make the test to use the s flag\".\nHey . Thank you, for your interest in contributing. The issue with the current test RegEx is the does not match new lines. In JavaScript RegEx, there is an which allows to match new lines. Hope this clarifies\nYes, thank you I've another question, the only way to try these regex tests is by passing the url with the code as if you were someone trying to do the challenge, or does freeCodeCamp makes specific tests for this? Like tests to try the challenge test or something like that."}
{"_id":"doc-en-freeCodeCamp-0e5adb98e10223faf27ba272ef379d42ad9a97e47882574d270c7769dbe08864","title":"","text":"Unfortunately, we currently have nothing to help test the backend content - you will need to have the project and code, and build freeCodeCamp locally with the changes to test. Do remember, this section of the curriculum links all the code needed to pass the current tests.\nOK, I'll see if a can give it a try, then! Thank you :)\nHey so I tried it out and the test actually passed without needing to modify anything! I made a deploy in Heroku: https://aileen- Based on this for the challenge. I just modified some files in the repo to see that the first tests of the challenge pass (i.e. try the previous heroku url ) Then skipped some steps and go ahead to modify the part of code that alirezaghey said that wasn't passing the tests. I tried with both codes: the one provided by the and the one provided by alirezaghey and it worked just fine. The file with the code that is being tested is right , as you would see is the same code provided in this issue. Here's a screenshot of the results. <img width=\"858\" alt=\"Screen Shot 2021-06-24 at 7 24 31 PM\" src=\"https://user-\"Supposing I didn't miss anything, I would say that maybe it was a different problem that causes the regex to fail. I'll see if I can try it on Opera browser. I have this config: Device: [Laptop] OS: [Mac OS 10.14.6] Browser: [Chrome] Version: [91]\nHi Are you sure you haven't a false positive produced by the ? Neither of the regexes can differentiate between commented and uncommented code.\nYou're totally right, I completely forgot about that, sorry. I deleted the commented code and now the test is not passing. Tomorrow will be trying the fix both of you suggested. Thank you for your response!"}
{"_id":"doc-en-freeCodeCamp-3c7159f6f695b80fc71881448e11ed7bf0733c4223fd081fe2d40910fb2f95c1","title":"","text":"We have fixed this issue and it live on . Please go ahead and submit links to your solution and GitHub again and it should work now. If you see any 403 in the browser console that is fine and will clear itself. You can safely ignore them. Those are the past updates which will resolve as you submit valid solution URLs. Thanks for your patience with this fix. Original issue: Describe the bug When a backend project is submitted it does not send the solution or Github urls and is rejected, silently, by the server. <details<summaryOriginal issue details: </summaryTo Reproduce Steps to reproduce the behavior: to localhost:8000/learn/apis-and-microservices/apis-and-microservices-projects/exercise-tracker valid urls into Solution and Github Link \"I've completed this challenge\" \"Submit...\" at the next challenge to your public profile (with timeline public) that the project does not appear. Expected behavior Either the submission should succeed or the user should be informed that it has failed. </details\nI was wrong about the 'silently' part. On the .dev site you can see that there is, briefly, a message warning you that the server is not being updated !, but that gets wiped out when the new page loads.\nCan you re-confirm this. I just want to rule out our earlier outage, and that we need to update the template on boilerplate with the as a CORS allowed origin. I think a recent issue came up about this, can you help in digging through the issues on what it was and if it is related.\nI can reproduce this on the current master and on production.\nI can take a look at the example projects and boilerplates to make sure is allowed as an origin.\nYup, please test one of the projects and see if it works, which may mean we needing to do something fancy about these.\nI've checked a few projects and those that have CORS settings all have . I've tried explicitly allowing and disabling Helmet and CORS wherever possible, but still get the same error.\nOkay, need to investigate then.\nI think the forms may not be sending the URLs in the first place. Well, the server is complaining because it isn't getting them.\nHi everyone! I've been facing this for about a week or so. Tested yesterday and today (just now) and it's still the same."}
{"_id":"doc-en-freeCodeCamp-1acbad7b1ee323d2e5eae221995bef5727dd9d16463b644a76e5ec58c3eb44ba","title":"","text":"For me it's at submitting the Issue Tracker project. Tests pass but after clicking Submit and go to next project, the request to fails with status 403, body is just 'Forbidden' and payload has only . For the full request output (headers, etc) see Best.\nyou were correct. Contributors, The forms are not sending the links to the API and the validation checks on the API reject the calls as 403 I have created a PR which will send a json response to make this less cryptic on the XHR response. Doesn't fix the issue, but better for debugging. Now, coming to the client: need to look into the redux wiring and understand why its not sending out the links to the API as it should. need to fix the learn (possibly in the layout) or somewhere else to show the messages received from API as Flash. The later can some as a separate pull-request.\nwe are on it.\nI am still experiencing this issue when trying to submit my projects. Would you like for me to open a new issue? Edit: Here are some pics of my console for accessing site, going to current challenge, and then submitting the challenge: ! !\nHi Kelsie, Thanks for reporting. Yes, please open a fresh issue."}
{"_id":"doc-en-freeCodeCamp-5abec4560661c486f4dd3a050e89f45d6c0ebc5ce38f2df86257e86903d4e7f7","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 --After writing \"use strict\" at the top of the editor, the warning icon appears to the left. When the cursor hovers over it, the text bubble that describes the issue is covered by the navbar making it unreadable. <!-- Describe your workspace in which you are having issues--Browser Name, Version: Google Chrome Version 61.0.3163.100 (Official Build) (64-bit) Operating System: mac OS Sierra version 10.12.6 Mobile, Desktop, or Tablet: Laptop <!-- If relevant, paste all of your challenge code in here --<!-- Add a screenshot of your issue --! <img width=\"1440\" alt=\"screen shot 2017-10-21 at 12 52 09 am\" src=\"https://user-\"\nConfirmed this on Firefox 56.0 and Chrome 61.0 !\nFixed. Thanks for this issue; I needed a good hacktoberfest PR\nNo problem!"}
{"_id":"doc-en-freeCodeCamp-8e65f225c1a5cd51ab405d9298c02ec8e9590c3bfa58ebf801795d278c129122","title":"","text":"There is a typo at the following step: It should present the text: Device: Laptop OS: Windows 11 Browser: Brave Version: 1."}
{"_id":"doc-en-freeCodeCamp-1e77a6e203001a472bfd77222693cc2ef2cf9a8ad923754e258e674d994cbe86","title":"","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nmethods are case sensitive. should be is a great place for questions like this\nthanks for the issue but if you get stuck or have questions with a challenge in the future, please first ask questions to the . What has suggested is correct. Happy coding!\nI've tried it several times, making sure code was acurate... there must be another problem\nSorry about that but no one was answering me in the help room\nno worries. Yeah, sometimes the Help Rooms are pretty busy and getting help is difficult. Please be patient. There are many people in there that are willing to help. You can always tag me there and I get help you out when I can"}
{"_id":"doc-en-freeCodeCamp-67bc9ddcb45b6f8fff60e8f937d105b61c51958d391e0d7db43606afd3f9e407","title":"","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36 OPR/37.0.2178.43</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nIssues are for reporting bugs or other problems with the site. Please consult the for help with writing code.\nthis is not issue. Your code just don't have any tags.\nThanks for reporting this. GitHub Issues are for reporting bugs on the website only. Please consult the for any assistance to Coding. Happy Coding!"}
{"_id":"doc-en-freeCodeCamp-1900eb6c754a31f7f4a4737a49530c75b5d45ee9dc1abb6ba52245f2c91bd944","title":"","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.87 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nthe instructions are correct. You'll need to return \"Huge\" whenever . If you get stuck with a challenge, please ask questions to the . Happy coding!"}
{"_id":"doc-en-freeCodeCamp-46252f748a1ee337ca0bfe8f561062aa4e734f5aa082d50bca4cbabb28bed115","title":"","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.152 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nYes. They are, but that's not issue to be logged under this repo :wink: ! Thanks for reporting this. GitHub Issues are for reporting bugs on the website only. Please consult the for any assistance to Coding. Happy Coding!"}
{"_id":"doc-en-freeCodeCamp-0d91d9a688ec2c824aa2ae7c83be116191c55555b458674d36ebed98534a37bb","title":"","text":"Challenge - This challenge says that we must find campsite city on the list, but when I open link, there is not any list of campsites. It redirects to camperbot page, which redirects to gitter\nThe wiki URL was changed for the list of campsites. To contributor: Change this line: New link: Please, check our and if you need any assistance reach out to the .\nHi, first timer here. I'll fix in the next hours. Cheers!\nHey Bob, mind having a look at any of the open issues? Looking forward to your contributions."}
{"_id":"doc-en-freeCodeCamp-d4d29efc443dfc7f043ee106efa5d39e595d3d009c39ddc8866897e4657c82e8","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 --The test: Use the ++ operator fails when the pre-increment version of the \"++\" operator is used (i.e. \"++myVar;\") rather than the post-increment version. Nothing in the description of the task precludes the pre-increment version being correct. <!-- Describe your workspace in which you are having issues--- Browser Name, Version: various Operating System: various Mobile, Desktop, or Tablet: multiple <!-- Add a screenshot of your issue --!\nthanks for the issue. Because we're targeting beginner coders, we wanted the challenges to be simple enough to teach a concept but not overwhelm learners with other details. Same goes for . cc/ worth accepting this prefix operation?\nI remember this was and more times in the chat, we could add separate challenges for pre/post increments/decrements. But this is going to be confusing for beginners. Maybe we could relax the tests to allow but not change the test case message. So advanced campers who are attempting these as in this case can pass the challenge and beginners are not overwhelmed as well.\nI agree on just accepting the answer for flexibility but not change the test messages. I think editing to the following will work. I'm not sure about escaping the parentheses but whoever takes this will have to check this. The code will break for anyways so I think the above should be okay. There is a similar case in so someone taking this can easily do the other\nWon't the above code pass with just ? Since both sections are optional, that will match just . Better to do:\ngood point. I was being careless Thanks!\nThanks ya’ll! I couldn’t have asked for a better outcome. Having poked your backend with alternate ‘correct' solutions to prior challenges and been impressed with your robust handling of them this situation stuck out a bit. And I was hoping to contribute to the polish of your beautiful project. I appreciate the peak behind the curtain. It confirmed that the modification only required a simple regex edit and that ya’ll really are a copacetic group. Kudos all around!"}
{"_id":"doc-en-freeCodeCamp-5b8ceb4f2f55569f5f29374ca3115f46b54306c309738339afca30a0958efd73","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 --Convert JSON Data to HTML <!-- Describe below when the issue happens and how to reproduce it --Can't use or alert to show my results this problem with all challenges. <!-- Describe your workspace in which you are having issues--- Browser Name, Version: Chrome, Version 50.0.2661.94 m (64-bit) Operating System: Windows 10 64-bit Mobile, Desktop, or Tablet: Desktop <!-- Add a screenshot of your issue --!\nFirst of all your code is incorrect. Hit the and just adding the below at its correct place: ! Closing. Please consult the for any assistance to Coding. Happy Coding!"}
{"_id":"doc-en-freeCodeCamp-a0a9fc698f9923390eb0571c35189ac9dc74365618910e19ad1760f2c99ae288","title":"","text":"Hello everyone, When a new challenge is launched, the focus is not on the code window. User has to manually click into the code window to be able to write. Is it possible to have a keyboard shortcut to focus on the code window, just like we have a keyboard shotcut (Ctrl + Enter) to submit our solution and to launch the next challenge? It feels annoying sometimes to use mouse just to get focus when all the actions are happening via keyboard. Thanks in advance. Prasoon\nWhat do you say?\nI think that idea is great to me!\nHow about <kbdCtrl/Cmd</kbd+ <kbdShift</kbd+ <kbdE</kbd?\nAnyone interested in working on this, check these files:\nWhile I'm theory this can be done, there's an on-going issue with the code mirror cursor bugging out. The editor does auto focus on page loads but there's a bug that prevents round. There are a few issues open around this that would still be open.\nHi, I would like to work on this if you guys are alright with that.\nGo ahead, help wanted issues are open to all. Please, check our ."}
{"_id":"doc-en-freeCodeCamp-489d275d36054f460b848ecd7ef20914f7e10f9e06bd2f1da6185e2cd87a6814","title":"","text":"Challenge has a minor typo. Step 8 reads \"[...] if you don't haven't built any websites before [...]\" when it should simply read \"[...] if you haven't built any websites before [...]\". Additionally, the code styling from step 12 appears to be bleeding over into steps 13 - 16, so the text for those steps is improperly styled. !"}
{"_id":"doc-en-freeCodeCamp-64dc21208e0ea45feec094feacc5a65663a2488fa95e1ab6cfddd75e605b4a92","title":"","text":"On Settings page, the empty space between the \"Certifications\" and \"Legacy Certifications\" seems to be missing. <img width=\"840\" alt=\"Screenshot 2024-03-12 at 12 04 47\" src=\"\"We could add a to space them out a little. The Spacer should go in between line 421 and 422."}
{"_id":"doc-en-freeCodeCamp-c325038c921c166167eb02d5c2c076ddb7fe60dfb3200a1cbcc07c71f77b3711","title":"","text":"In step , currently, the instruction says: The at the beginning of the other commands at the bottom stands for \"meta\". It's a key that doesn't exist on most keyboards. If you're on OSX it means press then then the letter. If you are on another system, press then the letter. Use the exit command to get back to the terminal. Instead of this, the instruction should be as follows: The at the beginning of the other commands at the bottom stands for \"meta\". It's a key that doesn't exist on most keyboards. If you're on OSX it means press then the letter. If you are on another system, press then the letter. Use the exit command to get back to the terminal. NOTE: There's an extra then in the third sentence i.e. If you're on OSX it means press then the letter. In step , currently, the instruction says: That construction team must be working hard Open the file again to continue building. Instead of this, the instruction should be as follows: That construction team must be working hard . Open the file again to continue building. NOTE: There's a missing full stop ( ) after within the first sentence. In step , the instruction should be as follows: The at the beginning of the other commands at the bottom stands for \"meta\". It's a key that doesn't exist on most keyboards. If you're on OSX it means press then the letter. If you are on another system, press then the letter. Use the exit command to get back to the terminal. In step , the instruction should be as follows: That construction team must be working hard . Open the file again to continue building. <img width=\"707\" alt=\"image\" src=\"https://user-\"<img width=\"706\" alt=\"image\" src=\"https://user-\"- Device: Laptop OS: macOS 13.0.1 Browser: Chrome Version: 107.0.5304.110"}
{"_id":"doc-en-freeCodeCamp-82667795931f7b2612de039ff1d1d746a2bd03504b84276afe17aff1e6c29b21","title":"","text":"It says that plot 1 should have an x label of Month, but it's the second plot that is monthly. It should say that plot 2 should have that xlabel. It should say that plot 2 should have an xlabel of Years It's testing correctly, so it should be an issue only with the assert message ! Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response\nsame thing for the ylabel in plot 2 actually, it says plot 1 there too\nHello, It seems that same thing is for the \"testboxplot_titles\".\nI am opening this for contribution. The PR has to be done on the boilerplate:"}
{"_id":"doc-en-freeCodeCamp-59ca6f224ec893eb5c9e2cac709ae71dd3b378a853b8f8ed47f34db6647dd267","title":"","text":"Sometimes when testing the Scientific Computing with Python projects the unittest response is \"The diff is x character long. Set maxDiff to None to view it\" (or something similar) I propose we set that maxDiff to none in the tests in advance\nTo expand on this, the boilerplate projects can be found in the following 5 repositories: (see below for this one) Each of these has a file which contains the tests. From what I can tell, adding between these two lines would resolve this. The arithmetic formatter uses a different testing package - do we know if this one is having the same error?\nHi. I would like to work on this. But I wasn't able to find instructions on setting up the code?\nArithmetic formatter can have part of the output truncated. Using in will always give full output.\nI vote to do that change to Arithmetic Formatter then\ndid you do all the projects? or there is something missing?\nonly left is Arithmetic Formatter\nOk, let's see if I can do it\nFor the Arithmetic Formatter, the tests say\nI seems I am not managing to figure out how to make the change to pytest in the file, I probalby need to delve deeper in the pytest documentation\nChanging to in the file should do that.\nyes, it does! and now it says lots more I don't know if maybe now there is too much?\nIt can be a bit overwhelming for somebody not used to it, but that can be said about version without as well."}
{"_id":"doc-en-freeCodeCamp-ee90e34dd48c9238c86500826dfeee57088276c313289d40e50590bfa8448518","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: -- Expected to see Clothing withdrawal transactions (-25.55) on output but only seeing the 'transfer from food $50'. Transfer method passes but the food transfer of 50 but it is 0. <!-- Add a clear and concise description of what you expected to happen. --<!-- If applicable, add screenshots to help explain your problem. you can drag and drop, png, jpg, gif, etc. in this box. --<!-- Please complete the following information. --- Device: PC Desktop OS: Windows 10 Browser: Firefox Version: 93.0 <!-- Add any other context about the problem here. --I've since updated my transfer method to use the withdrawal and deposit functions to accomplish the task correctly. It seems the Transfer method test case needs a bit of an upgrade to make sure withdrawals are working.\nThe test for transfer function is not checking if the amount is deducted or , But only checks for the ledger entries. Adding two additional tests for deduction and addition will fix this issue.\nI tossed up a PR for this: I two asserts to the existing test."}
{"_id":"doc-en-freeCodeCamp-612ece350b666dd3046d2a7a3d483f5e9c076314fdbcba72849481d673682d1e","title":"","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nyou need a closing brace after the quoted class.\nthanx"}
{"_id":"doc-en-freeCodeCamp-a645685b48e5309fb800426194b42c5c4929980c90836e094ae098c4cf916dde","title":"","text":"Describe the bug PR builds for freeCodeCamp / freeCodeCamp are failing in Travis CI with the following: To Reproduce a minor PR change build in Travis CI (ie: https://travis-) Expected behavior PR should pass all the builds to allow QAs to merge PRs to repo. Screenshots ! Additional context ref:jsdom/jsdom\nCorrect me if I'm wrong but '' is asking for: If this file was missing would that not trip something?\nDid you mean this file: ? I believe all this is unused completely. And some of the files around that as well. If you are investigating, I recommend you look The challenge-markdown-parser is something worth looking at as well. It's in the tools."}
{"_id":"doc-en-freeCodeCamp-a9a20e6fb4828abe2d97db8f2a0dbd64d972923038d3879afd3152d7f904ea02","title":"","text":"The description here is missing backticks for the number zero. Here is the new updated description. This has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the Here is the correct file that needs to be updated. Note: Even though the file says step 62 instead of step 63 that is on the site, this is still the correct file that needs updating. We recently made changes to the ordering and those changes haven't shown up yet on the live site. Happy coding see explanation above see explanation above No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response\nStep 145 has the same issue here Here is the file that needs to be updated here is the correct use of backticks for the number zero in the last sentence here"}
{"_id":"doc-en-freeCodeCamp-117fe4b7315f176f1bfba591395b104213f37a4fd6bec94f05c14e3b5f3435c2","title":"","text":"On the settings page, you can change your username. Any time you stop typing, it reads from the database to see if the username is available - we could change it so that it only makes a query when the user is ready. So instead of when they stop typing, we just let them choose the name they want, then when they click save we check if it's available. Not sure how big of a deal this is, I'm guessing users don't change their username often. Every little bit helps?\nI've always wondered about this one. Definitely agree that we shouldn't hit the DB until the camper tries to submit.\nI think we can go with the current implementation but wait for a meaningful pause to make sure the user is intending to submit the new username for validity check."}
{"_id":"doc-en-freeCodeCamp-50eace3c7a4b77492b66c122f98e16f7063e000a1a304a4e48ef5cb5f539e174","title":"","text":"I the \"thumbs-up\" icon to the \"Info\" button and I still passed the challenge. I don't know if this was intended to help. Cheers! :D Challenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/601.2.7 (KHTML, like Gecko) Version/9.0.1 Safari/601.2.7</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nThanks for the report. I've put in a PR that will check what the parent element of your icon is.\nThanks for taking the time to fix it! :D Cheers!"}
{"_id":"doc-en-freeCodeCamp-d481145130cf6f8685e1647a805c996d9ce04ec1a543b64a9f6d20f692b36b69","title":"","text":"I suspect there is some text missing from this (it makes no sense): \"We can do this by replacing the . part of our regular expression with the current regular expression with the word and.\" My suggested verbiage would be: \"We can do this by replacing the . in our regular expression with the string we wish to match (the word 'and').\" Secondly, let me suggest \"g means that we want to search the entire string for this pattern instead of just the first match.\" should be reworded to \"g stands for 'global' and means that we want to search the entire string for this pattern instead of just the first match.\" This will be a great aid to students in remembering the parameter.\nLikewise, in \"Waypoint: Find Numbers with Regular Expressions\" it should be mentioned that represents a digit. The proper association goes a long way in retention of new concepts and ideas."}
{"_id":"doc-en-freeCodeCamp-9e801d56d1a8ea4e1a84ea13cdb42add40d04c45136938d9baa555b8c3df2d78","title":"","text":"Thanks for reporting. I created a PR to resolve the issue. Once it gets reviewed/merged, a user will be able to put the properties in any order (as it should be)."}
{"_id":"doc-en-freeCodeCamp-fdb53f6ec45f23ed4dce13d0eb2c4cdd951c27ca4fb7e77fa30cbb6acf769066","title":"","text":"We are using in the tests of Table component. does not guarantee that the element has the correct role, and this attribute should be the last resort when querying an HTML. We should use the method instead. Remove from the tests Replace with\n/attempt"}
{"_id":"doc-en-freeCodeCamp-9eb03d1a8d4349cb16d0414104e813f5bdaee15b737ed265ed12deb8273ddf54","title":"","text":"Lesson asks you to, \"declare a regex variable. Assign it a regular expression that matches a number (including decimal numbers) followed by a or / operator followed by another number,\" but will accept regex' from users that don't satisfy this criteria (examples /d/ and /5/, matching anything with just a number, and anything with a 5 in it). Related issue to address test being too strict. Opened from forum post: Lesson should pass when Regex matches against a number, followed by a or / operator, followed by another number, but matches any number. Regex's that pass but should not (likely not limited to): /5/ /d/ // 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\nIt looks like the last test to could be updated to include a few more assertions like this js assert.isTrue(highPrecedence(\"53\")); assert.isFalse(highPrecedence(\"5\")); assert.isTrue(highPrecedence(\"10/2\")); assert.isFalse(highPrecedence(\"\")); But also, looking at this challenge again, I think it could be simplified. At this point, we should only be testing for the final result and allow campers to solve it however they want to. Here is my proposed update js assert.isBoolean(highPrecedence(\"122\")); js assert.isTrue(highPrecedence(\"53\")); assert.isFalse(highPrecedence(\"5\")); assert.isTrue(highPrecedence(\"10/2\")); assert.isFalse(highPrecedence(\"\")); I'll open this up for discussion so the other members can chime in with thoughts.\nI see this as the only test for the regular expression itself: Your variable should be a regular expression. does this issue require the addition of more tests? and if so, should there be seperate tests for each regex that produces an unexpected behavior like /5/ and /d/ or just one test that ensures the regex conforms to what was asked for (includes the two numbers, * symbol, / symbol, and 3 capture groups)?"}
{"_id":"doc-en-freeCodeCamp-1f037139b773ac5bcf82cd1f6b01fbeaf52d1c3e2f91f97a773ed133e49a2c87","title":"","text":"The test you mentioned here only checks that the a regex variable was created and that some sort of regex is being used Currently this test is checking for the correct result js assert.strictEqual(highPrecedence(\"53\"), true); but it right now allows for multiple incorrect answers My proposal is to rewrite the lesson to allow for more correct answers and ensure that incorrect answers don't pass. Right now, you have to create a regex variable and you have to return But there are dozens of correct answers and this should be rewritten to allow for that. So you can see my note here for my proposed changes The thing we want to be carefully about is not using regex tests to check for this. Because that is what is happening for the other lessons and it is difficult to maintain and only allows for a specific answer. So that is why this is marked as open for discussion\nOpening this up for contribution - a PR which resolves this will follow Jessica's updated approach in to test the function result, regardless of the function implementation."}
{"_id":"doc-en-freeCodeCamp-a2ea0e1ba2891a7f05a03c300401ec65cb487d84ec1321fbf0ffe9af9c920581","title":"","text":"Describe the bug The completion model buttons are not correctly aligned. To Reproduce Steps to reproduce the behavior: to out. to the challenge run tests error Screenshots ! This is only on the development server, probably created by the css changes introduced by the landing page redesign.\nI am able to confirm this bug. Looking at the elements: The Go To Next Challenge button has a left margin of 5px. ! The Download My Solution button has a top margin of 5px. !"}
{"_id":"doc-en-freeCodeCamp-8be2c1921e7606ff36040a3eaa6c8e52815ba7ac4422f717f7a2a983f93ce0e3","title":"","text":"Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. s - captures much more than spaces as the lesson implies, a better description that talks about what characters white space, as the title hints at, includes should be used.\nThanks for pointing this out. I agree, feel free to for this."}
{"_id":"doc-en-freeCodeCamp-9f496ddfa006515f5d5a402fc79db835bc1160c82255eb33b451f0ae081432b3","title":"","text":"Describe your problem: Paragraph breaks in challenge descriptions that are present in production are missing in the master branch. The blocks of text that are paragraphs in production are only separated by single newline characters in the source markdown (on the master branch). This is not enough to push them into paragraphs - they need to be separated by an entire empty line. Add a Link to the page with the problem: The problem is ubiquitous, but a good example is the which looks like this on live: ! and master: ! From , live: ! and master: !\nI don't think this problem can be solved by changing the parser, since it's behaving correctly when given blocks of text are separated by an empty line. The markdown itself will need changing, but it isn't as simple as globally replacing -since that will mess up any code blocks and any embedded html. However, as long as it's restricted to text, it should be safe. Edit: 'safe' assuming the challenge was well formatted in the first case. The Project Euler challenges are a bit messy and will need dealing with separately.\nThis used to not be a problem. Something has changed recently.\nAny idea when it was working? I couldn't find any obvious changes in the parser or in the challenges, and the first challenge has (probably) been wrong since .\nTurns out I wasn't looking hard enough. My PR, caused it, so I'll just revert that if I can't come up with a better solution."}
{"_id":"doc-en-freeCodeCamp-7303d9f455eb723c832d87dcbbc792d397546e3e6668711d5d71be2aa68769fb","title":"","text":"Under the section, add the following line as the first item:\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."}
{"_id":"doc-en-freeCodeCamp-f94a3c8ed35e835ea8723b2dcb546d5acdc90c2ce89480c529f7dd7b8c4787ed","title":"","text":"We had camper that was able to pass the test for step 44 of the pyramid project. However, they created an infinite loop with recursion because of this code here the initial starting code does make it seem like you are supposed to write your code inside the function Here are the current editiable regions but it should be changed to this to make it clearer for beginners where to write their code 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\nCan you please tell me where the file is in the repo?"}
{"_id":"doc-en-freeCodeCamp-a49e0ea1334d5451e6c026c1e0b60783d534ffc09b556bae1c5a9db215c08a0a","title":"","text":"One of the tests for that bonfire is : , which is supposed to give : . And another test is the same bonfire is : , which is supposed to give : . This doesn't make sense. If it can be inferred, based on the difference being one month apart, that it's the next year, for the second case, then it should also be possible for the first case too. March and May are one month apart, so the output should be just like the second case.\nWe're a little backlogged right now so if you can submit a PR to clean this up it would be much appreciated."}
{"_id":"doc-en-freeCodeCamp-6df89afc3b31918f44946573158927720006c6d415da0094c076f449b290f92f","title":"","text":"Under Tests section text and textString do not match properly. If you only forget ' ; ' it still awaits for ' % ' We need a separate test for ' ; ' check or fix the text like ' Do not forget % or ; '\nThe can be made optional in the regex instead. Leaving the off the end of the line does not affect the code. The test is trying to get the user to implement a \"best practice\", but all we really care about is the code written is valid and accomplishes the task. Are you interested in creating a PR to make the at he end of the line optional?\nWhile we are at it, can we strip the code of whitespace? I much prefer looking at regex without the everywhere.\nI think that is fine. FYI - There are a few helper functions available that can be used in the testString by using . For example, you could use it in the referenced in this issue like:"}
{"_id":"doc-en-freeCodeCamp-44f7d7056297d6c6fd85f569c82d06064a2bf0bdeab1a8836a45e78aee8d5566","title":"","text":"The instruction are not clearing, it take times to know what it is saying The heading should read <img width=\"832\" alt=\"Screenshot 2024-02-05 at 21 30 18\" src=\"\"- Device: Laptop OS: Mac Browser: Chrome No response\nIt looks like the steps have been updated on the main branch but these changes are not live on the site. So the step you are referring will be step 110 here.\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-e07f64e3c13ff7a758aec7fd9dd34f389320acdd29ffb08ba76ac905e6494c66","title":"","text":"When I want to add my x account to my profile the format of the link must be but the domain nowadays is and when I add it with x instead of twitter it shows me an error ! to the settings of your profile the Your Internet Presence section to add/change the Twitter account link It should allow both domains to be entered not only ! Device: [Desktop] OS: [Ubuntu 22.04] Browser: [Firefox v128.0 - 64bit] If the context is not enough for the issue reply to this issue and mention my username\n! Huh?? That's me too!!!\nHello, I am new to contributing so please inform me if I am doing anything wrong. The Line254 effects social link validation. could be changed to X.com for a quick patch although moderators may want to redefine all twitter references to x. Line239\nHey Yes, I think the same but I think it should not be changed to x.com we have to change the value to array instead of string like this: then use a conditional statement to be sure the entered data from a user includes one of these two."}
{"_id":"doc-en-freeCodeCamp-6cd696be726f0144a1505a4e4cd786750479e095cc6d7fd39abf300ea2eb9fa9","title":"","text":"In module, currently, the instruction says: Write an directive that goes through a list: and assigns each variable to a class, where the part changes for each item. Each class should set the the respective color. In order to avoid any sort of ambiguity and to make instructions more clear, I think the instructions should be as follows: Write an directive that goes through a list: and assigns each variable to a class, where the part changes for each item to the respective color. Each class should set the to the respective color as well. In module, the instructions should be as follows: Write an directive that goes through a list: and assigns each variable to a class, where the part changes for each item to the respective color. Each class should set the to the respective color as well. <img width=\"521\" alt=\"image\" src=\"\"- Device: Laptop OS: macOS 13.0.1 Browser: Chrome Version: 107.0.5304.110"}
{"_id":"doc-en-freeCodeCamp-f2254a25c7d53e14eea3f959b6b25ca3d14b1cb5cdf4213ac81484733d317002","title":"","text":"Describe your problem and how to reproduce it: Declaring a loop using as the declaration to solve the challenge does not pass one test. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: 80 Operating System: Windows 10 Pointed out in this forum topic:"}
{"_id":"doc-en-freeCodeCamp-f28f39f0f36485e4d89da3957a19189b0b63f2b6fbeeaf1aafe8b2fdcad5794e","title":"","text":"The test is expecting to use 49 in the slice. Which seems like could have been an error….It should be 50 The test is expecting to use 49 in the slice. Which seems like could have been an error….It should be 50 No response Device: [Laptop] OS: [Windows 10] Browser: [ Chrome] No response\nYes, you are correct. The test is incorrect. I will go ahead and open this up for contribution for the community. Please read through the guidelines first. We do not assign issues. If you are interested in working on this, then work on the issue and create a PR. Several changes need to be made Here is the first file that needs to be updated For step , you will need to update these two tests here to use the correct value of 50 for the slice method. You will also need to update the seed code for steps 28 and 29. Remember that step 29 also has the complete solution which needs to be updated as well Happy coding"}
{"_id":"doc-en-freeCodeCamp-ad4b6ed4d228ba01e2dd57bce800f4e33b337f6b02ee53a8af1b5412713dc458","title":"","text":"The following classes in are unused and should be removed: .help-modal .help-modal-heading .btn-lgRemove the above classes from Test and confirm that the modal displays properly after the changes"}
{"_id":"doc-en-freeCodeCamp-628fc2dba23c84ab456be42f376d663156f0279b9a115e789f2a3778e37218ac","title":"","text":"Describe your problem and how to reproduce it: Anchor links such is not working properly in several languages. For sure is not working in: Russian, Spanish, Chinese languages. 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): !\nThese 3/4 PRs (exlude one - which I PR'd to my own forked-repo) may close this issue. Please review them."}
{"_id":"doc-en-freeCodeCamp-eeedeb2cecde96220ee1197bd11d781b3d19b6807e1c41cd1e85b931108f1538","title":"","text":"The following code passes all the challenge's tests, but it is incorrect (it fails to find if is the last element of The code above should not pass the challenge. ! Device: Macbook Pro OS: 10.13.6 Browser: Firefox Version: 97.0.1\nChecking against the solution on the forum, it appears that should return . We could add a test to the challenge that checks this, which would resolve this issue.\nYes, that should be all it takes to resolve this issue.\nI'm going to go ahead and open this up for first time contributors. A PR to resolve this issue will: Add a test to that asserts returns . If you are interested in working on this issue, we recommend starting with our , and you are welcome to join our if you have any questions.\ncan I do the code in python ?\nNo. Our challenges run on Javascript. In this case, you don't need to write a new impl of the algorithm or anything. You just need to add an additional test case that matches the one given above.\nSure, unless wants to take this, I will"}
{"_id":"doc-en-freeCodeCamp-6f5a87566b3e035a8fd1ef42f4d47cd8e410434012079a1ccb06581bed425ef0","title":"","text":"Describe your problem and how to reproduce it: Clicking on any of the case study links under the developer ethics guide in ~any language~ will all lead to the Software Engineering Ethics Research Institute (SEERI) homepage. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: Operating System: Mac OS If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! It seems as if the Ethical Cases tab on their website is the was probably where the case studies used to live but has since been replaced by an empty template. I can hop onto this issue if y'all have ideas on how to proceed - find new case studies or get rid of these links?\nI'd say google the links, maybe they've moved to a new place. If you cannot find anything, I think we would need new links but also some discussion on the issue before we change links to new studies. Go ahead and take this up if you want\ni am a first timer contributor i would like to fix this if you can just show where to begin\nWe'd absolutely welcome you help on this issue but we're waiting for a reply from . In the meantime, have a look and check for issues which do not already have a PR made. Also make sure you read out contributor's documents properly in the /docs directory.\nOkay, I will look into this!\nIt seems that the case studies are no longer on the site, but I've found a list of similar case studies at another . Also, the first link on the page also seems as if it's supposed to lead to an ethics code, but that has\nIf the new links look fine to you, go ahead and make different PRs for each language and replace the links\nEnglish links are in the pull request below, but if approved, translations will be needed!\nWe are no longer excepting translations for the existing curriculum, so don't worry about creating PRs for the other languages."}
{"_id":"doc-en-freeCodeCamp-40df9809fc0468643918d9744b70093112efa3192836d3e002dabc26b3b60b60","title":"","text":"There is a typo in step 87 of Building a Cipher: Fix the typo in the following file:\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.\nIs someone working on this issue? If not, I want to work on it.\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-eaca1533f19a98ad82ed855ef99fa46b98d2c3fcf673c7029fe4c759a04a66bb","title":"","text":"in the document, the instruction header says this: because how the following instruction looks I agree with the camper suggestion, in the original issue Can we clear the empty line in the code block, it's annoying me here is the file here is the original issue\nhiii, Please accept the pull request\nHello Please is this still open? And how can I work on it?"}
{"_id":"doc-en-freeCodeCamp-94d9f21cd5334fcead9b679223d6d9162f46260924d3d1ebb0dada0468d97938","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: Bug - Test for below code fails with error: checkSign should use multiple conditional operators. Screenshot -1: ! Screenshot - 2: ! How to reproduce It. Instead of Error: “checkSign should use multiple conditional operators.” Error should be: Using multiple ternary operators in statement-if-true part of ternary operator is not best practice. (Increasing clarity of error message) Add a Link to the page with the problem: Link to ; Link to reporting bug on forum:\nI agree that some tweaking makes sense. I'd would help if we can capture the fact that the test fails if a) you aren't using a multiple ternary or b) the ternary isn't in the expected format.\nI do not think this is what the challenge asks for: This is the code from the docs: What you have constructed is: I agree, you have accomplished_ the task. However, the expected implemented logic is of the form: So, perhaps we should change the challenge instructions to be more specific as to the format...\nSir, please note: this repository is of . Thank You for your reply.\n, haha. Yes, I am well aware. I linked to the Mozilla documentation to retrieve an example of Multiple Conditional Ternary Operators. My point is still entirely valid.\n` Please try the above code in this . Please check what is required to pass the challenge.\n, I have, and I understand exactly why this issue was created. I am pointing out that the format of your solution is not what is expected, which is clearly seen in the example given in the lesson: I agree, you have accomplished the task. However, the expected implemented logic is of the form: Your solution does not contain logic.\nSir the condition to win the challenge is: Use multiple conditional operators in the checkSign function to check if a number is positive, negative or zero. The function should return \"positive\", \"negative\" or \"zero\". We should Use Multiple Conditional (Ternary) Operators.\nPerhaps the error message should be \"... multiple conditional operators in the recommended format.\""}
{"_id":"doc-en-freeCodeCamp-cc76ccc8103b659eaf83cfb6a69434b86dfbc56e063a18e1e4c295abe52e40af","title":"","text":"And perhaps adding a note along the lines of \"It's is a best practice to format the multiple conditional operators so that each condition is on a separate line, as shown in the example, for readability.\"\n\"It's is a best practice to format the multiple conditional operators so that each condition is on a separate line, as shown in the example, for readability.\" I would be for adding a note similar.\nClosed? Was an update to the description merged?\nIt is not possible to implement if/else if/else logic using ternary Operator. But the task can be accomplished. No, the expected implemented logic is of the form:\nExpected solution (one of 6, very similar to your final answer): If-else version A ternary, or multiple ternary, always can be written with if-else. The challenge and the description is accurate. We just want to add a clarifying comment or two to emphasize the best practice formatting for readability.\nNevermind.\nIt looks to me like adding clarifying comments is the best solution. So, let's leave this open until a PR gets merged.\nI'd like to jump on this, if possible. I'm a first-timer but really excited to learn!\nGo for it, This should be a good issue for a first-timer. I recommend taking a look at the , and if you get stuck ask away in the"}
{"_id":"doc-en-freeCodeCamp-bb82d9d27a0dc587c53612da50417fc02b084ac91704db22fcc1c202cf8be3d4","title":"","text":"Clicking on link in the code preview (for example on \"The Garfield Files\") opens up web page with all three modules again (Coding Challenge, Code field, Code preview). ! ! I don't know, if this is challenge specific.  Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Firefox Browser Version: Firefox for Linux Mint 1.0 Operating System: Linux Mint 18.3\nThis is due to how the rendering engine for our curriculum works. If you try this on a stand alone webpage, it won't happen.\nThank you for the explanation May I ask, how I could open it on a stand alone web page? Could we maybe improve the issue, by inserting a dead link instead of leaving it empty?\nWhen I say stand alone web page I mean the you copy the html part out from the FCC paste it in another new file on you PC and run. What we can do is make a PR so that the href contains and not , that fixes it\nThat is a valuable piece of information, thank you! I will create the PR immediately."}
{"_id":"doc-en-freeCodeCamp-220e40ba549ed779486f97098dd9f430deb0fe959e14a19c0809cbf96a6661ef","title":"","text":"If I click on a link to a certificate from my settings page, it opens in the same tab. If I click on one from the timeline on my portfolio, it opens in a new tab. We could probably make this consistent. I believe I made the timeline links open in a new tab because there's no nav on the cert pages, so the only way to get back to the site is with the browsers back button. I believe I have also heard an argument that they should open in the same tab so I'm not sure what the better way to go is.\nsir.. i would like to solve this i contribute??\nplease go ahead . No assignment is necessary as described in our . The first comprehensive PR will be considered for review.\nSo should it open in a new tab or in the same tab? what should happen?\nsame question as shold happen??\nI will double check with the dev team and get back to you.\nMy vote was to open them in a new tab - like I said, there's no nav on the certs so you have to use the browsers back button to get back to the website.\nI agree\nI was told, \"If the user donates on the certificate, the redux store will not be updated on the other tab and would need a refresh\". So, I think that for now, we should open them in the current tab - unless someone has a better solution to that.\nCould you clarify this? If the user donates on the certificate opened on a new tab, the redux store will not be opened on the original (settings) tab? This does not sound much like a problem. In fact, I would have said that is expected behaviour, from past experience.\nSo If a user donates on their certificate the store on that tab gets updated (isDonating: true). When the user goes back to the previous tab to work on the challenges, she will see the donation modal. (unless refresh). Solutions: 1) keep a navigation on the certs and keep them in the same tab 2) open certs in new tab but sync state across tabs, Might find this one helpful.\nWhat is the chosen path to solve this issue? Or am I missing something?\nWe have not come to an agreement regarding the way to move forward yet. The options are listed . Once we reach an agreement, we should make the experience consistent across the app."}
{"_id":"doc-en-freeCodeCamp-de364aec5dc27b59805aee034aeee07ce8dc32d1ccada87fa85e25c854fd4de2","title":"","text":"In the Responsive Web Design challenge there are these sentences As I don't think these colors are keywords, I propose to remove the backticks for translation purposes\nBit of a weird one, tbh. Those all are html color codes, but they're really just being used as names for colors. Anyways, it seems reasonable to stop using them as keywords, honestly.\nI mean in this specific use case, considering also the table in the description with the hsl codes does not have the colors in backticks. And ok there are the name of the classes, but better needing to do something like \" (ciano)\" than keeping the colors untranslatable everywhere else imo\nSure, I agree that they shouldn't be keywords. I was just speculating as to why they're currently keywords."}
{"_id":"doc-en-freeCodeCamp-13115dde48133a0be7a9260508bc4f41061ddd722d5162fd4e829e12c1c83faa","title":"","text":"Some users are encountering the error in the linked video. See the forum for more discussion. All Console error messages should clear so users can run code No response various No response\nIf I revert the change from it seems to fix it.\nI am also facing this issue while doing javascript datastructures and algorithms course. The console errors are stuck and the solution is to refresh the page everysingle time.\nI also face this issue while doing a JavaScript data structures and algorithms course. The console errors are stuck and the solution is to refresh the page every single time.\nThanks for tracking that down, it was defintiely the culprit."}
{"_id":"doc-en-freeCodeCamp-5476562a5ed808f2dee75e7687e0e43e986133dcee9e484680eab989bf6055d9","title":"","text":"In the multi-file editor, if the preview pane is toggled off and then on again, any output in the console will be cleared. Granted, the user can always check their code again to get the console output back. But I'm assuming this is not intended behavior? Any page using the multi-file editor the Survey Form in the new RWD the Console button so it is showing below the preview. the tests. the Preview button to hide the preview. the Preview button again to show the preview. that the console output resets. Console output should not reset if the preview pane is toggled off/on. No response N/A No response\nHere is what I tried, so anyone in the future save time: Changing lowerJaw to JSX didn't help. TabPane change display to , but React doesn't care and preserve the state. if you turn to JSX, so react preserve the state, it won't render at all. monaco wants it to be an element. I don't know if this helps, but I personally think if become JSX, then React can do its thing and preserve the state. I have no idea how to make monaco accept JSX instead of Element, so I am going to stop there, maybe someone else the same issue. Here is the file with the issue Here is the react-wrapper for the monaco, maybe it does have a way to do it\nI have looked it more up And I don't think, it is possible to inject JSX element inside the editor. I am maybe wrong, but the easiest solution, is to have the editor in instruction and lowerjaw in different tab, is that possible?\nI think the console output is not related to the editor per say. We just need to investigate output, consoleOutputSelector, and consoleOut state in redux store and see at what point it gets reset."}
{"_id":"doc-en-freeCodeCamp-2f9437f65bcae6241284d9e26b1930982ab3a59b476372c8faa848f9c8ad03fe","title":"","text":"In step 53 of the Building a Cafe Menu project: Adding by mistake three p elements inside a single article element (instead of three different article elements), I received an unhelpful hint message. Code: Hint: I think that the hint should say something like: You should add three new article elements.\nI don't think this hint is necessary wrong or needs to change - there's a test that makes sure there's no spaces between the elements. It fails and gives that message. It just gives the message for the first test that fails. The idea then would be to use the hint to try and solve the step. If you remove the spaces, as the hint suggests, you will pass the step. Although, because I did not add the three new elements, it should not have passed. I think we should just add another hint and test, probably near the top of the tests - maybe the first test, that checks that three new article elements were and we can use the suggestion as the hint. Then, that would be the first test to fail, and you would get the hint about the number of article elements.\n<section<h2Desserts</h2<article class=\"item\"<p class=\"dessert\"Donut</p<p class=\"price\"1.50</p<p class=\"dessert\"Cherry Pie</p<p class=\"price\"2.75</p<p class=\"dessert\"Cheesecake</p<p class=\"price\"3.00</p<p class=\"dessert\"Cinnamon Roll</p<p class=\"price\"2.50</p</article</section"}
{"_id":"doc-en-freeCodeCamp-291ca661826a9da9cbca2f379a52e09946bde1e700ec7bcac8d97d11162ddcad","title":"","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. content: \"\"; // when you addany extra space outside the empty string will not pass this challenge. Can't you add any whitespace?\nI believe this is by intention, rather than being a bug. You can, but you would do so using a few different means such as margin, padding, or positioning depending on the situation and what you are trying to accomplish. The content attribute of the :before and :after attributes would not interpret arbitrary white space in the way I believe you are asking.\nI see what you mean, the tests are too strict. I could fix this if a moderator approves that the tests need to be changed.\nWe just launched the new curriculum and learning platform. Please take a look at it: Do you still think this challenge is confusing or overly hard? If so, we would welcome improvements to this challenge.\nI will look into the tests tomorrow.\nYou're the man. Thanks! Please keep us posted\nI will prepared this and a couple of others for first timers. If the issue is not taken in a couple of days, I will come back and fix them. Let me know if you want me to fix them immediately The location of the test that needs to be changed: the new line should be: \"testString\": \"assert((/.heart:befores?{[sS]content:s?\"\"s?;/gi), 'The <codecontent</codeof the <codeheart:before</codeselector should be an empty string.');\"\nFYI on the issues page it encourages fist timers to search for the \"good first issue\" label which does not exist. It should say \"first timers welcome\" !\nDoes the issue still exist if not then I would like to work on it?\nsorry for the late response. Yes it is open.\ncould you link me to the page where you're seeing this?  Then I can update it.\nIt is on the issues page when I sign in with my moderator account.\nplease review my PR regarding this issue."}
{"_id":"doc-en-freeCodeCamp-b23e825ed9486338c998037fc6a7d7236cccb2a1ce06835ebf77ba9fa7634e73","title":"","text":"OK - thanks for letting me know - I still can't see it for some reason so you would be a better person to QA this."}
{"_id":"doc-en-freeCodeCamp-b0759a062268ee5ad457161321ccbea87050803051760e7daf1a31c6c2590aa8","title":"","text":"for step 38 here: the new user needs to set up an SSH key to push to github. the key is given by C9, but it's not clear to me how to add it to github, a simple copy /paste to my SSH keys in my account isn't working. This should be clarified for new users of c9. Not sure if it's needed for every c9 workspace or just once, but I guess github is seeing c9 as a new computer?\nHere is a set of instructions that worked for me: In the bottom left of your C9 dashboard is a section called “Add-on Services”. Click “activate” next to the “GitHub” icon (if you haven’t already). When the pop up appears, tell it to allow access to your account. This should complete the link between GitHub account and your C9 account. While still on the dashboard, look to the right under “Account Settings” for the link “Show your SSH key”. Click on it, and copy the value which appears. Go to the GitHub SSH settings page, and click “Add SSH Key” Enter the title “C9″, paste the SSH Key into the “Key” box, and click “Add Key”.\nExcellent. Thank you for pointing this out. I'll add this."}
{"_id":"doc-en-freeCodeCamp-347b387dd3cbd94eba5ac8e8127cb49c8c53237abf54085c43a65d878b44acae","title":"","text":"The description does not specify to preserve the title case of the word replaced. Although the tests somehow expect the title case to be preserved if the word is getting replaced. We should either: A. change the test B. Add a note in the description about this quirk."}
{"_id":"doc-en-freeCodeCamp-a51a266b0ff1cbc591f5933105b3525730bec7e2e07f9abdac24f2a2c0c70635","title":"","text":"It would be really helpful for each bonfire solution on a user's profile to include a link to the original exercise, esp. for non-FCC users.\nGreat point. I'm doing so. Thanks!"}
{"_id":"doc-en-freeCodeCamp-960da73a0221fb8a3bea40e36acec97675fff8fa15d260f2ce95f1dc3f68c12e","title":"","text":"In the ux-improvements branch: Looks like this is an issue with the seed data here:\nThanks! I've fixed the copy for all of these waypoints.\nNo problem. You may already know this, but it's still showing the Mongo video..."}
{"_id":"doc-en-freeCodeCamp-54b85bde8e5a5af5df0206257682ad180f4b5758e3b7ce6ca6e13556fdb9d061","title":"","text":"[x] Build a JavaScript Calculator [x] Build a Pomodoro Clock [x] Build a Tic Tac Toe Game [x] Build a Simon Game\nWorking on this one"}
{"_id":"doc-en-freeCodeCamp-cabf7fb5647a9d134e43716dd37d1780cfa50695a88815617aab6ecc796eaa98","title":"","text":"<img width=\"993\" alt=\"screen shot 2015-10-23 at 3 08 25 pm\" src=\"\"in this challenge you are supposed to change the first line: h2 class=\"red-text\"CatPhotoApp</h2into.... this next line. h2 class=\"red-text text-center\"CatPhotoApp</h2however if you just put in h2 class=\"text-center\"CatPhotoApp</h2it sends you through and says you're awesome and stuff, however you lose the red text in the process. I'm new to FreeCodeCamp and I know this isn't a huge issue, I just wanted to contribute."}
{"_id":"doc-en-freeCodeCamp-e98397bf78b8e421f013b3bd4d46b80049045184e2b8600c56e99aa94f5366b6","title":"","text":"<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Link in the readme does not link to a valid url. ! Browser Name: Browser Version: Operating System:\nThis link needs to be updated with the correct & valid URL."}
{"_id":"doc-en-freeCodeCamp-c3525ea24dcd85555687dae959c213d577b7e8cd83d73bde9c4a0885a45d5ef9","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 challenges prior to this method use the match() method to determine regex tests, in this there is a sudden use of the test method. There should be a small description to be provided to the user so that he/she can understand the difference between the two, also the challenge requires the use of the test method in place of match, so a beginner might be replacing the test with match only to be thrown with an error. Alternatively, the guide can provide the description necessary. I can open a PR and do the modifications. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Not Browser Specific Browser Version: Not Browser Specific Operating System: Not OS Specific If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): <img width=\"1160\" alt=\"screenshot 2019-02-08 at 1 32 33 am\" src=\"https://user-\"<img width=\"623\" alt=\"screenshot 2019-02-08 at 1 32 47 am\" src=\"https://user-\"\nReally that requirement is just to make sure you don't change any line besides the one that says .\nYes but then again, in the next challenge, a user maybe inclined to try the test method as well. Causes a bit of ambiguity.\nI specifically remember being confused by '.test()' because FCC just threw it in there without an explanation, so I think 's concerns are valid.\nOn checking through some stack overflow, i have observed that method will return a boolean true or false on whether a regex matches a string or not, whereas a method will return the matching strings or a . So it would be worthwhile to add a note to explain the use of test in contrast to match in this particular challenge. any thoughts ?\nThe first challenge in the Regular Expressions section introduces the method, so they've definitely had a chance to learn about it. That said, the instructions do talk about while the tests require you to use , so it is a little muddled."}
{"_id":"doc-en-freeCodeCamp-4deb5ce4a50fdb99a66d9395fd5772fae40489ab9a08a67af4e8d734250fbc56","title":"","text":"It wouldn't hurt to remind someone that exists, so I think using it as part of the challenge is perfectly fine. In light of that, all I would change is the description. If you're still interested in working on this, I'd recommend modifying the description (the examples in particular) to use .\nI have never modified a challenge before, but I have been looking into it and would love to try to help out. I am working on it right now, if that's alright."}
{"_id":"doc-en-freeCodeCamp-e075a73add22485ccc7128fe2ffddba2b23e5d4f726610a3cc5c85d5fe7f1730","title":"","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.99 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: There's a typo in the top comment. Instead of reading \"Let's create an object with a two functions.\" it should read \"Let's create an object with two functions.\""}
{"_id":"doc-en-freeCodeCamp-1db05da6a6e06c6288acd0e21900060bfabd742928c23069949fbdd6262e1fd0","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 --going to step 2/2, the last 3 paragraphs of step 1/2 are still displayed I click \"Go to my previous step\", the same 3 paragraphs are displayed twice, with different font <!-- Describe your workspace in which you are having issues--Browser Name, Version: Chrome 60.0.3112.90 Operating System: Windows NT 10.0; Win64; x64 Mobile, Desktop, or Tablet: Desktop <!-- If relevant, paste all of your challenge code in here --<!-- Add a screenshot of your issue --\nCan I give it a try?\nConfirmed. Go ye forth"}
{"_id":"doc-en-freeCodeCamp-fd33809949480f81950da7b78b16ff7dcce25406cac57bcec913ef4c0d3f7984","title":"","text":"Describe your problem and how to reproduce it: During a challenge, testing various methods of completing them, I’ve noticed one of the coding questions seems to be a little too easy to pass and I believe it could be fixed with a simple additional test. consider this code This code will pass all the tests provided, even though, when the target is changed to for example “sage” it returns I think a test should be with some incorrect middle letters such as testing if each individual letter is correct. Let me know what you think or if I’m being silly! Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Google Chrome Browser Version: Version 84.0.4147.89 (Official Build) (64-bit) Operating System: Windows 10 Pro\nI concur you have found an edge case missed by the current tests. Go ahead and create a PR.\nWill do. This is exciting!"}
{"_id":"doc-en-freeCodeCamp-37a64e2288ca916ba2918ec4345c1a80dd829600e410bd4502fbd7309ca1f75d","title":"","text":"Describe your problem and how to reproduce it: While working on the Sudoku solver project, one scenario came up that wasn't clear to me how to handle. The scenario is what do you do, if I ask to check a value of a cell with an existing value? For my project, I chose to return a conflict with the row, column, and region. However, I checked what the example app returns. The results it returns are logically inconsistent, which tells me this use case is undefined. For the example app: https://sudoku- coordinate enter C3, for value enter 2 (the existing value), click Check Placement returns value to 9, App returns value to 1, App returns These response are not logically consistent. For the first one, it appears to be checking against all of the existing values in the puzzle. For the second and third cases, it appears to be checking after replacing the value. I would expect this use case to be defined as either, it's a conflict, because there is an existing value at that cell or to replace the value in that cell and then check if it is valid or not and return the appropriate results. Add a Link to the page with the problem: ://sudoku- Tell us about your browser and operating system: Browser Name: Google Chrome Browser Version: 87.0.4280.67 (Official Build) (x86_64) Operating System: macOS Mojave 10.14.6\nYes, seems odd that you can place a value over an existing spot and it can return as valid Seems like this should be the response Or something along those lines\nI do agree that this should be handled as a valid placement (given that the number is already present in that cell). Unless there is objection/disagreement, I'd be willing to open this up for contribution.\nI also vote to make it behave as if it replaces the cell before checking validity. Or something along those lines. I have opened this up for contributions."}
{"_id":"doc-en-freeCodeCamp-6589f7050077b5714621d6319e269e5558bbf7e21ac6e3e51637dce3fb286bac","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 instructions, is an invalid css property. It should be . Alternatively, we could remove the code quotes and replace it with bottom margin. ! <!-- Please complete the following information. --- Device: Laptop OS: Windows 10 Browser: firefox Version: 98.0.1 (64-bit) <!-- Add any other context about the problem here. --\nThank you, for taking the time to open this. For simplicity, let us go with \"\". I have opened this up to first-timers only. An issue with the help wanted or first timers only label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the\nI would like to contribute Apologies for the redundant question here"}
{"_id":"doc-en-freeCodeCamp-2a1f7073d5c68b5170edb7627865f6e4d1edfe7a938a4bfbabb6b9330e639a89","title":"","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; WOW64) 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. Text for objective two says \"Use rgb to give your body element the background-color of black. For example body { color: rgb(0, 0, 0); }.\" There should be \"background-\" in front of the \"color\" in the example.\nFixed with"}
{"_id":"doc-en-freeCodeCamp-995285729f4341486dd1043bc611f3de54452402ea41e39b861a6c1efcb3a62e","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 description of the problem and the solution that passes are not the same. The code that passes this section would give you the wrong answer to the instructions. write the proper code for the instructions and it will not pass. try it. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: CHROME Browser Version: Version 71.0.3578.98 Operating System: OSX If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):\nCan you be more specific? For example, what code passes the challenge which you think goes against the instructions?\nI just came up with this solution based on the instructions and passed the test cases. ! After thinking about it more I can see how the instructions might be misleading. The following code pushes the number 10 to myArray, and i will be equal to 11 when the code finishes running, but the array equals [5, 6, 7, 8, 9, 10]. It might be less confusing if the instructions said \"Change the loop in the code to a loop so that the loop will push only the number 10 to , and will be equal to when your code finishes running. !\nthe first pic is the way i tried it first and it wouldn't pass. i got it to pass changing the while: } while (i < 5); that should not have passed. i also had a few connection issues with that one. like i clicked on run test and the page would lockup. i would close my browser, reopen it, go to your page, click on curriculum, and it gave me a 404 error message a few times. Have a great day! Jeremiah Kalb\nThe code should definitely pass the tests, because you just need the loop to iterate one time. So, the while loop condition should evaluate to in the first iteration (which it does with that code). If you start with the original seeded code, is and not , so it is not going to add other numbers anyway."}
{"_id":"doc-en-freeCodeCamp-6cd53b018b7434472b860a448d19e0e9fb43f3b085bcbbc1f70d290ff81d139f","title":"","text":"That being said, the wording change you suggest might not be a bad idea. Would you be interested in creating a PR for this change you suggest?\nI would love to do that.\nHow's your PR coming along?\nI'm pretty sure I finished with it. Is there anything else I need to do with it? The correct PR is\nthis how i got mine to pass // Setup const myArray = []; let i = 10; // Only change code below this line do { (i); i++; } while (1 < 0);"}
{"_id":"doc-en-freeCodeCamp-c3c33c865c0ed183dd0f7f9a97ae5fbb9840f175283f0764f3f670256432c372","title":"","text":"Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. Example: if (1 == 2) { //should be === return(true); } else { return(false); } Let's use if and else statements to make a coin-flip game. Create an if-else statement to return heads if the flip var is zero and to return tails if it's not."}
{"_id":"doc-en-freeCodeCamp-9b894ac82affed305ddb6414ac684501d1274fea78774bb1571aa80b676c0730","title":"","text":"! !\nIt is always best if you post an actual link to the challenge also. Thank you.\nHere is the URL. Babar Khan\nI would love to fix that issue, could I?\nSure. You will need to setup and test your changes locally.\nHow to setup ?\nStart by taking a look at . If you have further questions or run into any problems, check out our . You can post your questions there and someone will get back with you.\nThank you all for reporting and helping to resolve this issue.\nBabar Khan"}