|
|
{:,:} |
|
|
{:,:} |
|
|
{:,:} |
|
|
{:,:Remove all values (last argument(s)) from an array (first argument) and return as a new array.\last argument(s) and \) seem confusing. Can you please ellaborate further?\nHere's another way of saying it: You will be provided with an array (the first argument in the function) and one or more values (the remaining arguments in the function) that must be removed from that array. If you look at the current tests, the arguments are similar: 1 array and 2 values. The instructions are asking you to remove as many values as are provided, but you will pass the tests if you only account for two (this will most likely be updated in the future). Does that help?\nIn the more information section we should mention about the object of JavaScript, and also perhaps link to the MDN page of it.\nSee updated copy: and pull request"} |
|
|
{"_id":"q-en-freeCodeCamp-26a3127407cc9ceefd27002d57ad8b83484ba1ff8665d078434031c6cd1c3729","text":"Seeing this in production here: solution: Use and/or check for user existence and end early. cc:"} |
|
|
{"_id":"q-en-freeCodeCamp-9c22f1ffb98d4c73f911e606ab0df8e07c0e1f12ecaa7c57f5c679ca0643020b","text":"Typo on the first test \"your text field have the property of being required\". Also, the second test passes even if the placeholder text field is empty.\nThanks for the report, the copy has been updated."} |
|
|
{"_id":"q-en-freeCodeCamp-1018c09c75f47a29b8a61111d9ec35e0ed0194be7c3da8ad1050b2ae0ac7a50a","text":"Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. What I see: You can apply a class to an HTML element like this: <h2 class=\"blue-text\"CatPhotoApp<h2What I expected to see: You can apply a class to an HTML element like this: <h2 class=\"blue-text\"CatPhotoApp</h2\nMarkdown's getting in the way, see screenshot. ! |
|
|
_idq-en-freeCodeCamp-234245602436879a1774b3132a430122f0c415f762d64dff829b3ead1b3dde17textChallenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. Step : \ incorrectly to this url: It should link to: Unless that misdirection is meant to be tricky for the student ;)\nThis is a duplicate of\nKind of. This one is referring to a different page (challenge/zipline), but I did notice that all of the Ziplines have the same bug.\nThis was fixed ages ago, right? Please close.\nThis isn't actually fixed. The erroneous link still exists in these ziplines: Maybe it's not an issue because we'll be switching over to the content at soon? But I thought you should know that the issue hasn't actually been fixed yet. Actually, the only reason that it isn't an issue on the beta site is that none of the ziplines seem to link directly to the jquery json page.\nThis was fixed in prior to the branch being available through Now they seem to have changed how the ziplines look, so it wouldn't be an issue regardless. Since all changes seem to happen on the branch before ending up in production, issues that are fixed in should probably be considered fixed, even though it might be better to merge small fixes like this into production at a quicker rate than what is the current reality.\nThanks for the explanation! That makes sense. I'm not privy to staging, so I didn't realize it had been fixed there. |
|
|
_idq-en-freeCodeCamp-0b2cd09e6d67a6c9e98135863e0917a65e74bd5f3858de9f43513ced82ba4614textIn this lesson: In the second requirement the is included in the code tag markup which indicates it should be part of the href. It's minor but wrong and confusing for people new to html."} |
|
|
{"_id":"q-en-freeCodeCamp-26e9843ce77656b9418b6db7e7ef5d449dcefc989f1ec507c7ff3f89d815b7da","text":"One of the instructions has the following: start this tutorial by running npm install how-to-npm it says to run the npm tutorial by typing 'npm install how-to-npm but you are actually supposed to just type 'how-to-npm' |
|
|
_idq-en-freeCodeCamp-6254ed199e52baac6e46ec24eb6e23b68c95b5bdf886cd14059ed0b9e445e1eetextChallenge has an issue. In JavaScript whole numbers (called integers) can be easily used to preform mathematical functions <-- Let's try a few of the most commonly used ones now <-- We use - for subtraction <---\nmerged to"} |
|
|
{"_id":"q-en-freeCodeCamp-6addc42d72e8d06e0fa803c64940a9e980139486935b74f92616ee2668763172","text":"! Same with the other waypoints that ask for a hex code that includes alpha chars.\nGreen worked fine.. blue has case issue."} |
|
|
{"_id":"q-en-freeCodeCamp-c8748fb20a987fdd81467115f5ae6621da1a03873545a3880fbd431d465aeff9","text":"Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. \"Another type of JavaScript loop is called a \"while loop\" because it runs \"while\" something is true, and stops once that something is no longer true.\" Should probably read as: \"Another type of JavaScript loop is called a \"while loop\", because it runs \"while\" something is true and stops once that something is no longer true.\" Commas separate complete sentences, or act as a pause."} |
|
|
{"_id":"q-en-freeCodeCamp-8463964a8b948c8a1022fb2ac37944965aff41b27bb4a50d0cb0b1377e4fa78e","text":"In waypoint description there is a word with missing letter \"r\" and wrong letter - \"a\" instead \"e\" . I don't know English well, therefore this typo a slightly confused me:) ! |
|
|
_idq-en-freeCodeCamp-09ced1f9665b0fae87151a85dae26151262c2f4e2a9f7c56accd249f1853c841textChallenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. There seems to be a conflict between the last paragraph above the \ button, and the first test-item below the \ buttons (see screenshot, below). It is not clear if the <div class=\'s should go inside the <div class=\"col-xs-6\"'s, or vice versa. If I were to follow ALL the directions to the letter, I'd have two <div class=\"col-xs-6\"'s nested inside each of two <div class=\'s, each of which is inside an outer <div class=\"col-xs-6\". I think this is just a text-editing problem, because my code passes when I did what I expected the waypoint to be looking for: an empty <div class=\"well\"inside each of the previously-placed <div class=\"col-xs-6\"'s; this is included in the screenshot, as well. Also, I am fairly the text is missing a \, where I've sloppily drawn it in on my screenshot. !\nI ran into this also. The challenge validates when you follow the instructions in the explanatory text. It does not validate when you only follow the instructions in the checkpoints."} |
|
|
{"_id":"q-en-freeCodeCamp-b629a954d269acc2047034dad567acbeae8515bbb189fc31baf3f80796e436c9","text":"Challenge has an issue. This is backwards and should read: \"Add two div elements inside your \"col-xs-6\" elements both with the class \"well\" - or something similar. !"} |
|
|
{"_id":"q-en-freeCodeCamp-ba0ba15d35fa47719bd6f2bad5215bf5e72d2c4a30a225f673c846913a02a83b","text":"Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. step 9 says Install how-to-npm with this command: npm install -g git-it. it looks like we are installing something called git-it instead of how-to-npm. As before, if I am incorrect please disregard this issue and just close. Just trying to do what I can for you guys. Love this site!\nHey thanks for posting an issue! It looks like you are right! I believe the step should say\nThat's what it looked like to me to. It seems that the command was copied from the next page when you do actually have to install how-to-npm. Btw, now that I have done a lot of the free code camp challenges, how would I go about starting to contribute to the project? I would love to help out with the code or issues or anything really.\nAwesome! Just jump right in :smile:! Maybe start with putting in a pull request for this issue? Feel free to ping me in gitter if you want to chat about this further (so as to not pollute this issue with conversation)\nDear camper, your issue is related to: Please see .\nI checked when I was creating the pull request to fix this issue and it seems that the how-to-npm part of it is already fixed. |
|
|
_idq-en-freeCodeCamp-8be2c1921e7606ff36040a3eaa6c8e52815ba7ac4422f717f7a2a983f93ce0e3textChallenge 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. |
|
|
_idq-en-freeCodeCamp-34459355e0f52092ca0e71cb588135e27f9bac982b6e32302fec084ccf794629textOn \#left-well\color\blue\ Shouldn't it just be color of blue instead of background color of blue?\nthank you for pointing this out!!"} |
|
|
{"_id":"q-en-freeCodeCamp-51839f2828bd5b9c1c7e92133c551a284eccb660ecf9a249b12919bad8208143","text":"! Challenge has an issue. User Agent is: <codeMozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nThis challenge is asking to you wrap the existing tag that is right below the , not create a new one at the bottom. The test expects to find your up there with the original , so adding it down at the bottom causes the test to fail. However, this is the third time in a week or so that I've seen this same issue reported, so I propose adding some clarifying language to the waypoint that lets the user know they should not be moving existing tag, only wrapping it.\nIt worked. Indeed the language should be more clarifying.\nGreat, just reading your your response. Unsure if you have clarifying language yet but I have run into the same of two days ago, 10/21...\nThe change has been pulled into the staging branch but hasn't been pushed into the production code yet. It shouldn't be too long before it is. |
|
|
_idq-en-freeCodeCamp-74694663abf147e7e82b45c8dd0e3c2b7c94debd5506871068314a30fb6f73aetextChallenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; WOW64; rv:41.0) Gecko/ Firefox/41.0</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: Issue: Properties box says: \tails\ Test success statement: \bark\ Test succeeds on deleting bark property, not tails.\nI noticed that too ! |
|
|
_idq-en-freeCodeCamp-38335cf883a58588fb3aaaf627ee19e76729df427798aa4f4126329fbf655285textShould be \ I would fix it but I'm not sure where this file is located. !\nclosed. Fixed with"} |
|
|
{"_id":"q-en-freeCodeCamp-5683e78bf7bba8e0ae6cb448138bb13344ba877a5de561aebb03c97d2436f205","text":"[x] Trigger Click Events with jQuery [x] Change Text with Click Events [x] Get JSON with the jQuery getJSON Method [x] Convert JSON Data to HTML [x] Render Images from Data Sources [x] Prefilter JSON [x] Get Geo-location Data\nTrabajando en esta"} |
|
|
{"_id":"q-en-freeCodeCamp-5248a4d319c25277965ac0979b6acd34fdc6ea52ba87c7513f98339191c884fc","text":"Challenge [Bonfire: Validate US Telephone Numbers] Apparently the test case \"telephoneCheck(\"555-555-5555\") should return true.\" runs twice."} |
|
|
{"_id":"q-en-freeCodeCamp-f2bc12afc5447a4f42dfd972b24f1d74d4fdca7e4eb82ab5cee30e7e33d7de2d","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: This is a very minor issue, almost trivial, but this Waypoint initializes the editor with an unnecessary space right under . The space can be found if you look back at the code It should be instead of .\nEasy enough. I'll grab this one.\nSo maybe I'm doing something wrong but I just fetched the latest from \"staging\" and there is no space between the quotation marks in the latest version. This appears to have already been corrected.\nHmmm, I'm not sure why you're not seeing it on your end. I still see it on github and in the most recent staging I just pulled down.\nMy mistake, I hadn't pushed to my forked repo and I guess that was keeping the latest fetched files from showing. Should be fixed with |
|
|
_idq-en-freeCodeCamp-26ab1d47556a33594d28174bfb43f745079396f7072c6f64546826f591095400textand have text in code tags within a blockquote already. The code tagged strings need to be removed. You can see them because they are highlighted again within the code block. Access MultiDimensional Arrays with Indexes: ! Understand String Immutability: !\nAgreed, these just just be in the block quote. |
|
|
_idq-en-freeCodeCamp-40f4b91c41dcba535750f759c0bb8b898b631e3a74013c0972ed46aef11af3f1text[x] Learn D3 Challenges\nwhat should we do with these ones? I guess they are not finished, so there's no point in translating that one line, or am I wrong?"} |
|
|
{"_id":"q-en-freeCodeCamp-9934050814375f1bba1a4233e9bcdf79eb7b2bd74f545dd769c3f49306f9d3e2","text":"[ ] JavaScript Lingo: MDN and Documentation [ ] JavaScript Lingo: Value Types [ ] JavaScript Lingo: Variables & camelCase [ ] JavaScript Lingo: Arrays & Objects [ ] JavaScript Lingo: Finding and Indexing Data in Arays [ ] JavaScript Lingo: Manipulating Data [ ] JavaScript Lingo: Math [ ] JavaScript Lingo: Loops [ ] JavaScript Lingo: Regular Expressions\nWorking on this one"} |
|
|
{"_id":"q-en-freeCodeCamp-0db7f9640729f6ed059bec883a70a1a1556e2e838907b749830feb8afce303e4","text":"Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.124 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:\nIf you scroll down on the left section of the page below the Run Tests button you can see the results of the tests for your code. In this instance, the test fails because you have a capitalization error. For help with writing code, please consult the . Issues are for reporting bugs with the challenges or website. Happy coding!\nthanks for help :) i have found the error it was on the coding i was placing another anchor tag while i supposed to use the existing one thank you :+1:\nthanks for the help diagnosing the issue! Closing this issue as it looks like the issue has been resolved. Happy coding!"} |
|
|
{"_id":"q-en-freeCodeCamp-f535349981fb401a764fc6ee4708a6d272eed75f4ab42f7fff2ffc5bea95bacf","text":"My challenge is makes sure all p elements have closing tag\nThanks for reporting this. But your code is incorrect. GitHub Issues are for reporting bugs on the website only. Please use the for getting challenge related help. Happy Coding."} |
|
|
{"_id":"q-en-freeCodeCamp-1b8336b11f6a1c9e8d15f9e8fb2ec9f30499c6c7101d2aa2039600fa29b329b7","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.81 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. I feel like while the above code works it simply fails to communicate the purpose of the exercise by delivering a visible change in the resulting page at the right side of the screen. For comparison's sake, this is how it looks like when the code is executed in JSFiddle Given that the page display is narrow, my proposal is to change the required positioning entirely, so that the student will be able to see more clearly the results of the absolute positioning.\nHi - thanks for pointing this out. Yeah, the narrow output screen unfortunately doesn't show the change at all. We could change the requirements to use to make it more obvious. You titled the issue \"Replace the example...\" though, so if you had ideas to re-work this even more, let us know your thoughts!"} |
|
|
{"_id":"q-en-freeCodeCamp-3b63a174690ac07405c9d3f8645d7bf556ecfd0755bc6bc0f2de8f343c61f514","text":"According to Google Analytics, the is way too hard, and is taking campers an average of 6 minutes and 35 seconds to finish (if they finish - a lot of them seem to give up). According to this table, campers spend more time on it than they do on the algorithm challenges. ! We need to either reword this or simplify the challenge so it can be completed in closer to 3 minutes. Otherwise, we should move it back to the algorithm section.\nThis challenge does have a large amount of constant strings which could cause users to take a longer time than a typical challenge. Maybe we could provide an array of the responses in the seed code. Make the seed code: This could help in two ways. The first is the users can save time by not having to type out each response. The second is this approach could minimize errors from typos in the response phrases (i.e. Hole-in-one! vs. Hole in one!). We could remove the number of different responses. Maybe remove Eagle and Double Bogey.\nyes - that is a great suggestion. I think leaving all the names is fine but we should pre-populate the array with the names. Since this was your suggestion, would you be interested in tackling this and submitting a PR?\nYes, I would like to tackle this and submit a PR.\nThe Golf Code challenge did take me longer that the other challenges. I did not initially realize that golfScore() had BOTH strokes and par as parameters. With the other IF ELSE challenges we were only dealing with one argument to pass into the IF ELSE condition. I found myself in that \"flow\" and completely overlooked that two parameters were available to work with in the IF ELSE condition. I also found myself looking at the Strokes/Par table thinking, \"How will IF( <= par-2) work?\" After a little head scratching, I realized the values under the Strokes column were what you were supposed to compare Strokes to (i.e. IF (strokes <= par-2)). Hopefully, this feedback is helpful. I think the confusion is coming from the wording of the challenge and suddenly going from using one passed in parameter to two in your IF ELSE condition.\nAwesome. has a PR open already. Could you take a look at that first and let me know what you think of his proposed changes?\nI agree with MiloATH's proposed changes. Would definitely reduce the potential for typos when working the problem. As a side note, feel free to let me know if I am breaking any GitHub etiquette at any point. Zero experience providing input on collaborative projects. Looking for to learning and have really enjoyed FreeCodeCamp thus far. You guys and gals are doing awesome work. :)\nSure - we will let you know in a polite way if you break GitHub etiquette. Thanks for being receptive to feedback :) |
|
|
_idq-en-freeCodeCamp-37c39f6c4a469140feb93a624038f9c5e9ff34e5e4a281aa28c9f330a77f0b21text<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Tests are not passing with correct code. Curiously, the \ test is passing, but none of the others. DOM elements are rendering correctly with appropriate inline style. Browser Name: Chrome Browser Version: 68 Operating System: Chrome OS !\nit passed for me on firefox and chrome with the code in the picture - were you able to get it to pass?\nOddly enough, no. I find it very strange that I can get the fifth test to pass, but none of the others, no matter what I do.\nyea, im not sure - did you try resetting the code and doing it again? is there any errors in the console? Try another browser maybe\nYes to reset, no to errors. If it's a browser problem, that's an issue for people using Chromebooks like myself.\nI got the same scenario as . Only the fifth test is passing. Browser Name: Chrome Browser Version: Version 71.0.3578.98 (Official Build) (64-bit) Operating System: MacOS Mojave Version 10.14.2 I tried completing the challenge in Firefox and it passed. Similar users are having problems:\ndoes not work on Chromium - Version 75.0.3770.100 (Official Build) Arch Linux (64-bit) works on Firefox 67.0.3\nmy browser: Versione 77.0.3865.120 (Build ufficiale) (a 32 bit) on Windows 10 Home v1803 no test passes with callback\nPretty sure the problem is similiar to the problem on\nYep looks like yet another zoom bug with Chrome. We can check the inline styles set instead for the test. I will make a PR. |
|
|
_idq-en-freeCodeCamp-3aa0738c73a98966c6ec81758d81218e55f1f56bfe17649aced191faba61b805textfrom its english version at from its english version at from its english version at from its english version at from its english version at from its english version at When you make a PR for this particular issue, do not tag it with instead just reference it with\nHey ! How could I claim so we don't double work? Thanks\nHi ! Actually we just merge in the first PR for open issues. And your comment on this thread is enough. So, its yours. Happy translating.\nI just open a PR for\nthanks a lot that was fast! Would you be interested in translating these in future as well? If yes, please keep a watch on this thread. We will be updating on the progress often Happy contributing.\nDone translating ! My PR is available at ! Thanks for all you do, freeCodeCamp\nI have sent a translation proposal for /docs/how-to-work-on-guide- PR Hope it will help!\nThere is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with\nHello, I'm starting to help on the translation of the document /how-to-set-up-freecodecamp-\nWorking on /docs/spanish/how-to-work-on-guide-\nHello, I've improved the file\nHello, Improving docs/spanish/how-to-catch-outgoing-emails-\nHi, I'm improving docs/spanish/how-to-work-on-coding-\nHi, can I help with /docs/spanish/how-to-setup-freecodecamp-\nSorry, I opened a bad PR regarding but already closed it. I found there was still an English part to be translated\nHi! Is there any remaining documentation where I can help translate?\nyou can improve or fix redaction and spelling errors.\nHi there, It would be good if at the top are checked so we can see what is left to be translated. Thanks\nWhere I can start helping?\nsorry to put it in this issue, but is there any way somebody could help with the pull requests? I mean, there are 5K+ opened already, people are sending them in troves, and I suspect a lot of them are a total crap (Like ) . I guess you opened a Pandora Box with your articule about HacktoberFest.\nHey all, not a translation, but fixes for the language bar of HTML links on the README file for Spanish, and markdown links to the How To guides that everyone has been translating. . or anyone else looking to do translations in Spanish, you could make a copy of the 2 style guides to translate into Spanish from the English version in the doc folder. It looks like those weren't in to the Spanish folder originally or included on this issue. Just leave the title the same, but put it in the Spanish folder\nHola! to all. I believe we should have guidelines for Spanish translations, which include what treatment (formal or informal) to use when referring to actions or the user. For example, Agregue (formal) or Agrega (informal). - I don't know if this kind of things are found in other languages. In the last articles I've read I've seen a mix between formal and informal, and I think we should standardize (I have done it with some articles). I propose to always use informal. Another thing that could be specified in the guidelines is: Challenges translations. Should they be translated? Referrals to types and attributes (which need to be in English for proper coding). For example, type \ not type \. If there is a guideline already, please let me know, if not, I would be happy to start one (just let me know where to put it). Hey I would like to know your thoughts about this. Thanks to you all and happy coding!\nI agree that we should standardize around informal. I agree with you that we should look out for words like \ that have been accidentally translated during our automated translation process.\nHi all I'm not sure if this is the right issue to discuss this, or if I should open a new one. I'm happy to open a new one if that makes things easier to track. I'll keep it here for the moment. What do people think about translating \"array\" as \"arreglo\"? I think this is a big mistake that has been repeated since somebody made that bad translation many years ago. As any Spanish speaker know, \"arreglo\" means \"repair\" (), and it makes any programming related text even harder to understand. This is especially true for programming texts because it's full of abstract nouns and things that are not easy to represent in a tangible way. I learned to code in English (mainly FCC and Coursera), and after a while, I stumbled upon a programming text written in Spanish. I couldn't understand what it was talking about until I found out that \"arreglo\" was the (really bad) translation of \"array\". Then I could read the text as if I was reading an encoded message that had to be deciphered. I propose that the Spanish version of FreeCodeCamp doesn't carry on with that translation, which is just based on the similarity of the spelling but has nothing to do with the meaning of the words. I think the right term in Spanish is \. According to the : Which basically means: \ They also share all the phonems in \, with the adittion of /r/ (rolling r) and /t/ in \. I'm open to other candidates, but please, let's take \ out of the Spanish version. The word \ has been used in Spanish texts before and even though it's not a Spanish word, I think it's still better than a word that exists with a different meaning. And to be honest, anyone learning how to code will have to become familiar with certain English terms like \, \, \, \, etc. [1]: [2]:\nHello guy, I vote for yes, let’s do the change and I think will create a huge impact around of the world! Please let me know if you have more question questions or concerns. Andres Haro Cell: (619) 534-3190\nThanks - I agree that these machine translations need improvement. I encourage you to dig in and start fixing them. Be sure to join if you need help getting set up\nThere is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with\nThanks for working on the translations for the \. Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs. |
|
|
_idq-en-freeCodeCamp-35d602ee7ccda20fb5414057a65c66f318a288913d14a6e9aa6b26950a449373textfrom its english version at from its english version at from its english version at from its english version at from its english version at from its english version at \nPlease, review\n[x] [x] /docs/russian/how-to-work-on-coding- [] ()\nFixes the html links in the top language bar for all language README docs. Not a translation, but just link fixes. Once the Russian README files get merged, we can add the markdown style for links to all the articles in Russian too!\nstarted to review PRs. ping me if more help needed reviewed and requested changed at LGTM from native russian speaker view LGTM Resolve conflict is needed\nHi, guys! Please review my PR\nThanks for working on the translations for the \. Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs. |
|
|
_idq-en-freeCodeCamp-2e3d81e54fa9b6987665cc5241947f205be6b7c98e01850f679bdf10975bb825text<!-- 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: Link to the guide on the challenge Data Visualization: Data Visualization with D3: Use the and Functions to Find Minimum and Maximum Values in a Dataset is pointing to the wrong place Incidentally, the challenge page uses the d3-max and d3-min in the url while the guide page uses and Add a Link to the page with the problem: Get a Hint button brings the camper to which is 404 - Page not found Correct link is Tell us about your browser and operating system: Browser Name: Mozilla Firefox for Ubuntu canonical - 1.0 Browser Version: 62.0.3 Operating System: Ubuntu 18.04 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):\n/ If you can guide me to where this file might be located. I can check....\nSolution <body<scriptconst positionData = [[1, 7, -4],[6, 3, 8],[2, 9, 3]] // Add your code below this line const maxX = (positionData, (d) =d[2]); const output = maxX ; // Change this line // Add your code above this line (\) .append(\) .text(output) </script</body |
|
|
_idq-en-freeCodeCamp-5710c410b2fdda6888e754827143ecaed3ace3caec9a3a99f3ea92c115376c5ctext<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: The formatting of the header-tag page in the guide is wrong. I checked the codebase and there are missing back-ticks for some of the html tags in the markdown page. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: Version 70.0.3538.102 (Official Build) (64-bit) Operating System: MacOS 10.14.1 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! |
|
|
_idq-en-freeCodeCamp-4754794ccf58ff1613bd93d681d3308b3c0263d943bc15d445e8d03ffc42db0ftext<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: While working inside the coding challenge \, I found out that while the challenge works fine if you declare a local 'var' variable inside the function 'myLocalScope' and then deleting the log out at the end. as usual. But, initially accidentally I wasn't paying attention and declared the 'myVar' outside of the function scope just below its call, and the challenge validated it as correct and completed the test. Not being a complete beginner I was able to recognize the problem, but I am aware most beginners maybe stumble upon this problem and accidentally may learn the wrong thing or may NOT learn this properly. The test looks out for global variables as variables not being declared by any 'var' keyword but it misses out variable declarations outside of the scope of the function but using the 'var' keyword, which are also global variables and shouldn't be validated. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Safari Browser Version: 12.0.2 (.3.4)(Latest) Operating System: MacOS Mojave 10.14.2 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): <img width=\ alt=\ src=\<img width=\ alt=\ src=\\nI have opened a PR, which modifies the test case for checking if the variable is a local scope of the function. Did a regex test\nHopefully this fixes the issue. Even though I think it was already throwing an error if we declare a global variable (by not using var keyword) But the bug came when we used the var keyword. |
|
|
_idq-en-freeCodeCamp-43fb7bc3a881211900f2c5b48150524525879dcb0bfab85efaa54c0d39423a84textExpected behavior Please see attached screenshot for more details. Basically: [x] \ should be \ [x] We should get rid of the outbound link icons [ ] The footer should always go below the tallest element. Currently on the Guide, it seems to go under the least tall element. Screenshots <img width=\ alt=\ src=\\nSide note (perhaps a separate issue): the footer on the page is difficult to get to due to the loading of content on a scroll down. So you have to keep scrolling and keep loading content until there's no more to load to reach the footer. I suppose there would be a similar issue on the forum or anywhere else that uses the loading on a scroll.\nI'll give it a try.\nI have fixed the first two issues but couldn't quite reproduce the third one either in Chrome or Firefox(In Windows 10). cc - !\nThere is a UX trade off for doing that for implementing the third one. In order for the footer to go under the tallest element, both elements should have the height of 100% (no-scroll). In that case, when user clicks on a side nav that is taller than the content, the page should either go to the top to show the top of the content (loses the location of the scroll), or keep its scroll which means the user will scroll up and down just to change the tabs. here is a demo: ! with no footer, our layout would have behaved similar to the default Gatsby sidebar example. With the footer, the optimal solution would be to add some javascript and have a floating sidebar that stops at the footer. We could also have a fixed sidebar that the footer would overlap at the end of the page. imho, the current setup does the job, but please let me know which solution you would like me to explore.\nHi I agree with I think the key here is to use the site as an end user, and then decide on the tradeoff. I agree that the current sidebar is far better UX for the user, who are more likely browsing through an article and have it in view rather than have them scroll a long way to switch to the next topic of their interest. That will definitely increase a session time and reduce bounce rate.\nThat is fine. People will scroll. I think you all are dramatically overestimating the inconvenience of scrolling. On mobile, this will all be a single column layout anyway. This is what people thought was the optimal solution back in the 1990s. In practice, it's confusing to users. Users would much rather scroll up and down a page then have to move their mouse around to different \ and scroll up and down within those in a more confined space. Just look at this page here on GitHub. The footer is always at the bottom of the tallest column, which in this case is the middle one. If I want to see who this issue is assigned to, yes - I have to scroll back up to the top of the page. That's no big deal - it takes less than a second. We should use a similar approach with footers everywhere on freeCodeCamp. Separate horizontal scrolling portions are bad enough, and I'd like to move away from them - let alone separate vertical portions. Here's an example of how having separate scrolling areas is hurting usability on learn: <img width=\"1415\" alt=\"learnbasichtmlandhtml5fillintheblankwithplaceholdertextfreecodecamporg\" src=\"https://user-\"A new user might not even realize that there are buttons and tests underneath the \"run test\" button. The footer should always be at the bottom of whichever column is tallest, and we should not have independently scrolling columns. At some point in the past year or two, the independently scrolling columns were introduced. could you start working on a version that puts the footer at the bottom of the tallest column?\nI strongly recommend testing the app as user would to derive the best UX for our app's use case. For the Guide, I think the tallest element principle does not work in practice, you can test that locally yourself, it's just weird to scroll through whitespace vs content. People will scroll through content, not whitespace? For Learn I had given my feedback in a comment here: But, we quickly realized that the tallest element won't work either. Here is what we should do though is to use the buttons as a fixed component on learn. This gives us the ability to scroll the \ as much as we want, while keeping the most used component buttons in our case in view. ! Also, I would like to bring light to the fact that several feedback (fairly frustrated) threads that we have had here on GitHub and forum is the ability to use the challenge map about scrolling. It works when you are casually browsing, not when you are looking for something specific. But that's a different problem unrelated to this thread. Anyways, let's start working on a version that does put the footer at the bottom of the tallest element and do a A/B test.\nI will make a MVP and have you test it ASAP. Here is how Khan academy does it when the scroll meets the footer. Notice the shadow indicating that side nav is continuing and scrollable <img width=\ alt=\ src=\.\nPlease let me know if you wanna move forward with this design, and if you want the user to go to the top of the page after clicking the side nav or not so I could adjust it accordingly.\nPlease take a look at this document: Also consider this: very few people are actively looking for the footer. And if they are, they're just going to swipe down really fast and get there immediately, regardless of how tall the page is. The main purpose of the footer is SEO and for the 0.001% of people who are actively looking for it. (how many times a day do you find yourself trying to scroll down to content in a footer?) The Guide's sidebar is only 109 entries tall. It's not going to be that much space. If they have one of the bigger categories expanded, yes, it could be more. But I don't think the footer is important enough to warp the experience of the guide.\nA good example of how to handle a documentation page with expandable side menu items, and a footer, without extra scrolling is the MDN: When you expand the menu items on the left, the footer just gets pushed further down the page.\nwith these changes, this issue will back Or am I missing something?\nso I think wants the page scroll to go to zero only when a node with no children is clicked on the side nav. I cannot think of a way that I could implemented it without recording and resetting the scroll with JS, so if anything comes to your mind, let me know.\nNodes with children also have articles.\nvery good point, so we would be reverting to the bug, then. if the height of both elements are set to 100% our footer would be pushed down when an element is expanded; however, in the mozilla doc, Nodes with children do not have articles. So users can click on an end node on the side nav and then it page goes to the top. in our case, if a user wants to visit for example . She would be scrolling the whole side nav 3 times. If we really need to go in that direction, the other option would be not take the users to the top of the page regardless of where they click on the nav. but when they reach their destination in the sidenav tree, they will have to scroll up to see the article's beginning.\nHi IMHO, and all honesty I really do not care about the footer. Meaning we are on the same page about its priority. The idea is the best usability of the site itself. I am not advocating that we should not make it so that people do not have to scroll. All I am interested in is making the UX intuitive and not painful from a user's viewpoint. I completely agree on your well researched thoughts about scrolling. But I keep re-iterating to test the site ourselves in A/B strategy and see what works best for us. In my tests, I found it weird and awkward to scroll when I am working through challenges, or looking through guide articles (not casually browsing like on a news site). So, from my tests: On the guide, the footer should be below the content element (the right guide article itself). The content element will expand in height depending on its content. This will keep the footer out of the view at all times. That is The footer can be hidden out of view under the viewport. Your MDN example, does something same. At all times, the content block is on the top of the footer. On the learn, I think we should get rid of the internal scrolls. But this also means, we should keep three things always in view: editor (labeled 2 on my screenshot) buttons preview panel (labeled 4 on my screenshot) These are the most interacted elements on the learn app. Only the instructions (without the buttons, will scroll) The footer can be hidden out of view under the viewport.\nMaybe for the challenges and guide page we could make a smaller footer similar to the one github uses.\n!\nRe-opening. GitHub closed it automatically. This issue will be taken care of in repeated iterations.\nI believe the decision is to make the sidebar more concise so there would not be a need to scroll. Although displaying the sibling nav items were discussed, I think it would be best to move forward with something similar to the following convention where only children and parent nodes are in the sidebar. !\nYes, let's get a variation that you propose in, and test it out.\nI have a couple of suggestions on the footer: I feel the links are too cramped and need a little more padding between them Headings can be simplified There should be substantial space between the block of text on the left and the links At the end, it could look somewhat like this: !\nI really like your design, it definitely looks better than the current one. Here are a couple of considerations. The logo looks great, but it makes the footer area taller. As a general rule we would like to save as much screen real state as possible. To be accessible we need a way other than color to establish visual hierarchy between headings and footer items. I encourage you to take screenshot of both the current version and your design so we could compare their sizes and their white space allocation better. After that let's have a pr and merge the changes.\nAlso I don't think you're allowed to change the colour of logo according to https://design-style-\nlet us address side-nav related suggestions and improvement in the above-referenced issue so it does not get confused with the footer.\nHere are the screenshots for screenshots for comparison. ! ! !\nwould you be interested in making the footer titles more concise as suggested?\nI always have this message always poping up when i run my code \ i have done all i could but cannot detect any fault in my code. this stopped my html from running further. I gave an inline style with white as color yet the problem continued. I just don't know what to do again"} |
|
|
{"_id":"q-en-freeCodeCamp-21fdeec119466902507f4ec25f6806cbbd736ccc1b61d212e0b212c790ea10af","text":"Donate modal is rendered/animated twice when invoked\nSteps to reproduce. Complete at least 9 challenges. See modal once per session.\nalternatively, change this line to true and get the modal after completion of each challenge.\nJust in case someone tackle this before I get back to it. it seems like the app gets updated after the donate modal is up. so that might be causing the flashing. redux devtools actions order: <img width=\"338\" alt=\"screen shot 2019-02-22 at 6 46 38 pm\" src=\"https://user-\"devtoolds error: <img width=\"642\" alt=\"screen shot 2019-02-23 at 12 19 40 pm\" src=\"https://user-\"and here is where the modal is being called:"} |
|
|
{"_id":"q-en-freeCodeCamp-628fc2dba23c84ab456be42f376d663156f0279b9a115e789f2a3778e37218ac","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. |
|
|
_idq-en-freeCodeCamp-047973231a5cc72b4c98efbbfae0aff36e7362b3c9fd5cfbbfb4781a40a84198textDescribe your problem and how to reproduce it: Link to \ is different from English version. Portuguese version is redirecting to \. English version is redirecting to \. Add a Link to the page with the problem: English version Portuguese version Tell us about your browser and operating system: Browser Name: FireFox Browser Version: 68.0 Operating System: Windows 10 Professional |
|
|
_idq-en-freeCodeCamp-d84f5adeb12fb5309bed3fecf1b606447cb00166c6a82002af8ed73fa09d63ddtextChallenge: Video: The code is supposed to create a two-column layout but there is a typo. Video has: Should be: It would be nice to have the video fixed if possible.\nI would like to help but I need some more information like the download link for the video to edit it and overwrite columns on colums.\nIs it possible to get this video updated?\nthis still needs to be fixed, if possible. |
|
|
_idq-en-freeCodeCamp-703da7cdca94e3e9ab65d44a7c99361c9b871adaa7bc3709149e10fbf1f30dd6textFront end project pages have no margin and hug the window: <img width=\ alt=\ src=\All other pages have a margin I believe: <img width=\ alt=\ src=\I can fix this one\nfrom the screenshots. does adding a padding that way causes a horizontal scroll?\nNo, I'm pretty sure that's just my firefox being goofy again - that screenshot is from .dev and it shows this at the bottom on my firefox... <img width=\ alt=\ src=\causing the horizontal scroll bar to appear, but it's fine on chrome.\nThat should get fixed by , unless there's some other stuff overflowing. It just needs\nThinking about it: do you want to make that change in your PR as well, That way you can see if there are any other problems.\nLooks like it might not be my firefox - I found that when signed in, it displays the button in the picture above - but when not signed in, the button says \ So it's not the margin causing the scrollbar.\nlooks like that property does fix the scrollbar issue - <img width=\"292\" alt=\"Screen Shot 2019-08-23 at 8 23 25 AM\" src=\"https://user-\"but it's strange that the button displays different text based on authentication |
|
|
_idq-en-freeCodeCamp-d3f260ddb9ee7fb54e7dd7b7b61ee149a32a2cb18d536f3518a9a61378872b83textI did not see anyone raising this issue, but I don't think the background of the preview in default or night mode should be anything other than white unless the coding exercise specifically changes the background to something else. The preview should be exactly what you would see in a browser. In almost all the challenges, the background would be white. !\nI share your concerns The reason we changed the color of the display is that a white display is discomforting to the eye on night mode when everything else is dark. so we injected some styles to harmonize the view in general. That convention was carried over to light mode.\nIt might be better to default to white in light mode, same as the editor. As for night mode, some of the css challenges might need some changes to look reasonable in both modes. For instance, in night mode, looks like this: ! If we change the seed code to it would become ! It would have to be case-by-case, though.\nThat is a very good point. I will defer this to\nLogically, I have to agree with - displaying anything other than what the code in the editor would produce might confuse campers. But it is a little rough on the eyes to have the white background on night mode. And the current theme looks a lot better - so it's a tough call. I scrolled through a number of challenges, and there's quite a few that don't look right with the blue background. So there might be a decent amount of work to go through and fix all of them.\nI really like the new theme, but a preview should be a true preview. We want to make this like the real world. Developers working in some kind of night mode on their favorite local editors, still expect to check the \ result of the code they have written on a browser or in a preview mode in their local editors. The night mode should only apply to the editor or the non-preview part of the FCC site. Anything else is just not realistic.\nThe preview should be white.\nI agree with everyone here on this thread. The preview should remain white. Note that soon the preview won't always be there on the right side \"brightening up\" the user interface and ruining people's night mode experience. Soon we will have a single column layout where you the preview only shows up when you click a button to show it, or it loads in a separate tab. - could you update the styling on this so that the preview area is unaffected by our styling?\nDefinitely. |
|
|
_idq-en-freeCodeCamp-4e32b4aa53c0c39e8c176aae90836e946bbc9e46c6898b5f9216b8b1522f24fetextIs there a reason the certifications have an apparent margin above them? ! It's bigger with a taller viewport. Seems like there should be no margin there."} |
|
|
{"_id":"q-en-freeCodeCamp-5e5ba63eb6171f205e0cd48090b59b21276c34252b08812900ee182be92990ef","text":"<img width=\"616\" alt=\"Screen Shot 2019-10-01 at 3 26 24 PM\" src=\"https://user-\"This is a picture of my own private profile locally, seems like it should say something like \"You have not made your profile public\" instead of \"mot01 has not made their profile public\" And as I'm typing this, I'm wondering if a profile should render completely if it's theirs, even if it's not public - there's no way for a user to see what their profile would look like if they don't have it public.\nThat does look better. The next sentence should be something like \"You need to change your privacy settings in order for other people to view your profile\". So, they should be able to preview their public profile, basically? Sounds good. If going that route, it would be good to emphasise (even more than currently) that their preview is not public. It wouldn't be good if people went to their preview, saw that it looked right and didn't notice that they were the only people that could see it.\nYes to this, please open a PR. It seems to have been an oversight. I think it's fair to leave the warning on their own pages while showing this page in that case, which means we may need to update the copy for them.\nCan you clarify what you want here I'm not sure I understand - do we want to keep the page how it is, and just change the two sentences? Or do we want to display their private profile for them?\nYes. Sorry about being vague last time. I thought about this a little more and I think we should show the users their own profile only when they are signed in. Here is what we should achieve at the end of the day: profiles which are public are visible by default. settings button is only available if the user is on their own profile page. who are not signed in and are visiting profiles which are not public and are not their own are shown the current notice and warnings: ! who are signed in and are visiting their own private profiles are shown the same notice as the above screenshot in point 3 with the verbiage stating \"You\" and the settings button available. The rest of the their profile is visible as a preview.\nSo, there'd be a button on their private profile labelled 'Preview profile' and a label 'preview how your profile would look if you made it public'. Clicking that would take them to, say, which shows the preview (and a notice saying that it's currently private). Something like that?\nNope, we do not need a new route. Their profiles can be rendered just below the notice like so: ! Here is the copy: You have not made your profile public. You need to change your privacy setting in order for your profile to be seen by others. This is a preview of how your profile will look when made public."} |
|
|
{"_id":"q-en-freeCodeCamp-a3634e7457c9bdaf867d6baf35042d84308c7b4bb127642bb64333d94ea57729","text":"Is there any reason not to put the real and in ? I reflexively put in a dummy key when I set this up, but now that I revisit this, that seems like a mistake.\nYes, actually it broke the .dev build unsurprisingly , I think noticed it and reported in the team chat. My bad for not catching this previously. The real fix is to ignore and move ahead when the keys are not available are default. We do this with google application credentials.\nOh, I assume it broke the build because .dev isn't using I didn't think of that... So, we should implement the fix and add the public keys to , right?\nI was thinking something more along the lines of (example from api-server): I would try to avoid hundreds of contributors hitting the indexes locally. Ideally people should get their own keys. While the key and index is public, it's still not recommended to hit it?\nAs for the production keys, it's actually fine because the build should fail. I have since the keys in the build pipeline.\nOne thing: if we don't want contributors spamming search (fair enough!) I think there should be some docs that let people know what's what. Either that search isn't available in development or the steps they need to take to make it work.\nI agree. We should add some docs on getting keys, or perhaps creating a test index and sharing that instead |
|
|
_idq-en-freeCodeCamp-6ec8e735d85c760ded6043928d47078eb9725564268f3a009878b9599a8f4e71textThe font size for the CTA could use similar breakpoints for the h1, h2. and set to 1.2 - 1.3 rem !\nI'd like to work on this.\ncan i?\nWhere is this button?"} |
|
|
{"_id":"q-en-freeCodeCamp-a47984b70ae1ef6bb7963849482a42e0b10827f8e615a2a12ffad81d716028aa","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 feel like the description for the code in the is a little confusing and can be further cliarified. For example, the description is this: \"... Like strings, arrays use <dfnzero-based</dfnindexing, so the first element in an array is element <code0</code.\" <strongExample</strongTo be a little more clear and following the index concept, this could possibly be explained like this: \"... Like strings, arrays use <dfnzero-based</dfnindexing, so the first element in an array is element at index <code0</code.\""} |
|
|
{"_id":"q-en-freeCodeCamp-80f94e17a1b35a6b837d3aa2c3660f1b62a4eb1a6fa42a9f3797e1c6797105e4","text":"Link to the challenge: Adding a global flag to the regular expression has the test fail for the first two assertions. This can be confusing considering also how the challenge is introduced, since the code snippet explaining the concept shows the global flag being used. Update the code snippet introducing the challenge: However, since the global flag should not affect the outcome of the test (to what I can ascertain), a better suggestion would be to update the test itself, to account for its presence.\nThanks for the detailed report! I think it would make sense to do both. The isn't necessary, so it should not be there and it's not wrong, so we should not reject it.\nIt might be better to remove the global flag from the challenge example unless we also explain how and give some info on . I think in order to really know if we should fail the test when using the global flag we would have to consider how the code is supposed to run. Are we \"emulating\" that each is being run in isolation or are they executed one after the other.\nAgreed. This challenge focuses on teaching the user about groups - the use of over seem incidental to me, as does the presence of the flag. Also, the challenge asks you to make sure so it's only asking you to use against once.\nBut it is when the test is called multiple times on the same regex. Isn't this kind of the same as when users use global variables which end up causing the user's code to fail for all tests except the first because the the global variable does not get reset each time?\nI'm dumb - I'd completely failed to realise it's being run twice, once in the user's code and again in the tests. You're quite right and PR fixes that.\nChallenge: Fails with: Passes with:\nThe example/seed code moves to 14. I guess one easy option would be to change the example string to something like \"Fun with regular expressions!\", that should let all the tests pass and accept the global flag. The problem is if the camper uses a different string to test the regex it may fail. So we might just have to reset before running the tests.\nI assumed it would be the exact same fix as what Tom did:\nyep, that's what I concluded. I think we can apply Tom's fix in , rather than modifying the tests. Either works, but that should be more concise."} |
|
|
{"_id":"q-en-freeCodeCamp-c47543fc51d18a3d7734d6797bc769089d5454982064c1eac1ead98445d6a4c8","text":"<img width=\"1396\" alt=\"Notifications_Twitter\" src=\"https://user-\""} |
|
|
{"_id":"q-en-freeCodeCamp-b3bd7c113638daf26d244cecc70c40398c0a3ea12f79340120cda0bc8233dfcc","text":"<img width=\"682\" alt=\"Screen Shot 2020-02-03 at 7 30 48 PM\" src=\"https://user-\"For some reason, the font changes halfway down this introduction. . I don't see the problem at first glance. Probably just a spacing issue or something.\nHi . It looks like the problem caused by HTML tags in the text. I removed them and it looks better. Please check PR. |
|
|
_idq-en-freeCodeCamp-765301370e63f4832d1d47e48b2557c95545d8eceeb076cd9a76b0a859f9bc87textDescribe your problem and how to reproduce it: Go to: Look for: Test outputs in the bottom-left corner Duplicated test output: Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: 79 Operating System: Mac OS 10.13.6 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !\nThe same duplicated test output exist in the following Challenge: Go to: Look for: Test outputs in the bottom-left corner Duplicated test output: The Presentational component should render an h2, input, button, and ul elements. !\nYou are correct, the 2nd test should actually state: The <codePresentational</codecomponent should render to the page.\nTaking this up. |
|
|
_idq-en-freeCodeCamp-8f7af731ddc0bfc8bfc290f654e6aed8353eab038e23c77c7a75fab865e1c96dtextDescribe your problem and how to reproduce it: As discussed at exhaustive length , the username requirements don't technically preclude the username \"007\". The requirement \"Usernames should begin with a letter\" should be . Add a Link to the page with the problem: Low-hanging fruit for a new contributor."} |
|
|
{"_id":"q-en-freeCodeCamp-02b74d0594bfc650808e92d61875b5394314933d5ba5416ccdb9c5a39ce76523","text":"The logs for are quite verbose for some reason, making checking CI failures etc very difficult. Currently is logging all the solution, code etc for challenges? We need to avoid this."} |
|
|
{"_id":"q-en-freeCodeCamp-b1bd535d384f3fd2b5c8e4b3feeebe975ef1e5dcb71172ab73093104d9ef2513","text":"When navigating to and selecting a monthly donation, the text below says \"Confirm your donation of X / month with PayPal\" This text is coming from: There is logic elsewhere in this file that handles the different frequencies, it seems like this logic is needed here as well.\nCan I try this?"} |
|
|
{"_id":"q-en-freeCodeCamp-f2254a25c7d53e14eea3f959b6b25ca3d14b1cb5cdf4213ac81484733d317002","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":"q-en-freeCodeCamp-d52327b4cfbf30ee5099dac883f2c91fdf520b7683d1985e37a4f44687bcf5f3","text":"<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --This is a problem I found in the \"Applied Visual Design: Set the font-size for Multiple Heading Elements\".Even though the styling of headers in this challenge may be correct,the console gives an error stating that \"h6\" is not properly styled. I figured this may be due to the minimum-font-size issue of the browsers usually set to 15 or 16px(In Google Chrome and Firefox). Just wondered if we can put a note on the left pane where the question is present. Link Browser Name: Google Chrome Browser Version: 80.0.3987.116 Operating System: Linux\nYes, I believe this has come up before. I would rather see the use regex I think.\nBut this issue comes up every now and then in the forum. How is it possible for a beginner to use regex in this challenge ocnsidering that they may be only a few days into the course\nI meant to use regex to test that users entered \"14px\". Not that users should use regex at all. Right now the test is checking the value of the as it is rendered by the browser. If we check the input from the user, it wouldn't matter what size the browser gave the element.\nI am new to Open Source Contributions,can you guide me on fixing this issue?\nI would recommend following the . After that you need to fix the file I linked above and make a pull request. You can also reach out to us in our\nHi How would you target the element inside the tag, as it's inside HTML?\nI don't understand. You want to check the CSS of the . Right?\nThe first part, , isolates the styles for the class. Then you can more easily find if the correct styles are in there.\nThanks It was the variable that I was missing |
|
|
_idq-en-freeCodeCamp-bee7ec1b032d2dfcb62426de66e3f35e3363464af961eeef9fbf4a8cb514ce4btextIs your feature request related to a problem? Please describe. I noticed that there is a difference between the headers in and . Describe the solution you'd like Everything else is consistent except for the header. A solution would be to have it consistent throughout. Have it display \"Learn to code at home\" in both links. On the second line. Additional context Add any other context or screenshots about the feature request here. <img width=\"1095\" alt=\"without home\" src=\"https://user-\"<img width=\"1093\" alt=\"with home\" src=\"https://user-\""} |
|
|
{"_id":"q-en-freeCodeCamp-e21ed7c358848b5468adf4419cc15a550e3a3ee418d6c22d206fb6c3bf66846a","text":"Is your feature request related to a problem? Please describe. The activities count on the search bar in both /learn, and /news is different than /forum. Describe the solution you'd like A clear and concise description of what you want to happen. Fix the count on activities. Additional context Add any other context or screenshots about the feature request here. <img width=\ alt=\ src=\<img width=\ alt=\ src=\ |
|
|
_idq-en-freeCodeCamp-a4f6f557c105c1599a9a1845c4d1e414c21af6e05ee809ec2375218c0805faf1textDescribe your problem and how to reproduce it: Not Major: The sentence grammar should read: What type of HTTP request is usually used to access a website? Currently reads: What type of HTTP is request is usually used to access a website? Add a Link to the page with the problem: |
|
|
_idq-en-freeCodeCamp-9849198a19e1750b2d9a15457eb15b3b6664e7868d5a06613b99d364d34ce4ddtextIn the challenge, the following line tells users to use and , but the tests do not force the user to use and . Since this is an algorithm challenge, I believe we should let the users write the code any way that solves the problem. My suggestion is to change the line's text to the following: Any thoughts?\nI'll try to solve problem\nBefore creating a PR, let's wait for feedback from at least one of the users I tagged.\nsure, that sounds like a good idea, especially since we're not testing for those methods.\nI think this sounds like a good improvement\nok\nGo for it.\nNice, I'm thinking use on the testString, but I first want to know what's the asset version used on this repository. If you want that I use other way, please tell me. I also want to learn more about JavaScript\nOr use keyword?\nHello , There should be no need for either of those. The idea is to change the wording of this line of text: Use the array methods slice and splice to copy each element of the first array into the second array, in order. To this: There is no need to change the tests, as they do not check for the or methods.\nThanks. It's very much easy!"} |
|
|
{"_id":"q-en-freeCodeCamp-34d40b847a42fb178cf7cd4aa673498a42a6a35e080cccc9a63cbe491cc2d131","text":"I think the description of the checkfunds method () is faulty. ! It should be: \"A method that accepts an amount as an argument. It returns if the amount is greater than the balance of the budget category and returns otherwise. This method should be used by both the method and method.\" This is more logical, makes the code simpler and actually works with the tests. Browser Version: Firefox 79 on Ubuntu Linux Operating System: Ubuntu 20.04 LTS\nthis is genuinely a mistake as how can the amount which needs to be withdrawn be more than the balance in the ledger. amount can only be withdrawn if it is less than the balance in ledger. however there can be a probability that a part of that amount can be deducted from balance but the challenge stated nothing for the same. also the test module asked for a False return value which i think is wrong here in the challenge. !\nHello! Has any resolution to this been implemented? Im not entirely sure what to do about submitting this project because this error still exists. Any help is greatly appreciated!\nI don't think so, hasn't changed. It doesn't matter though, design the project as if it was modified the way I suggested and it'll be fine.\nThank you, for opening this. For anyone reading, before a fix: Change this: To this in the file: Can I get a sanity check here? What needs to change on the fCC repl account? I am opening this up to first-timers only Here is the repo: The README description makes sense, but the tests do not, in my opinion. So, the README does not need to change.\nThanks for your patience and for catching this Also, thanks for @ mentioning me, Sorry I didn't see this sooner. My first thought is that we don't need to change the test, but just the README like suggested. It seems like is supposed to be used by the other methods to make sure that there's a sufficient balance before calling or . So in the current test: It makes sense that the first condition is false and the second is true -- you shouldn't be able to buy 10. It's just that the current instructions in the README doesn't reflect that. is that what you were thinking for the method? Also, to answer your question once we decide what to do here and fix things in the boilerplate repo, someone on the team can sign into and mirror those changes.\nThanks for that. I was thinking about the use of the method in an odd way.\nI'm willing to work on this one if it's agreed that the README needs to be changed instead of the test.\nThanks, for your eagerness and patience. I was a bit quick with approving the change to be made. So, right now, I suggest you leave your current PR open as is. Once we come to a consensus here, we will be sure to let you know which changes (if any) to make on your PR.\nno problem. I think it could work the other way around, we would just need to change the description a bit more and maybe change the method name to something like . I heard back from and he agrees that changing the README makes the most sense. The wording that suggested sounds good to me.\nJust mirrored the changes from PR in the project: Thanks again everyone for your suggestions, reviews, and for this fix."} |
|
|
{"_id":"q-en-freeCodeCamp-3cce77ab4ca41e2190e1e250a3cbe625c9e96afd86fb2245df4ca0e3528c2dc0","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 exercise, one of the condition is \"The globalTitle variable should not change.\" but it returns an error if you modified the var (for debugging) at the top, even if your function doesn't mutate it. The verification should be that the initial globalTitle variable is the same as the final one, instead of simply looking to match it to a string. Add a Link to the page with the problem:\nHello there, Ideally, I agree, the tests would be robust enough to account for something like this. However, there is usually a reason for the comments, and users should not expect their code to pass, if they ignore this. If others agree to change this, I would not be opposed to the first test being removed. I cannot see it being used in any meaningful way in the seed.\nI would argue that, as this lesson comes after the section, users should be somewhat comfortable with using . Changing a global variable's hard-coded value seems like a less practical debugging method than logging a function call with the argument value to debug. Additionally, as mentioned, the is present to indicate which portions of the seed code should not be modified.\nfor debugging purposes, instead of changing a variable you are told to not change you should change the function call, wiritng there but, yeah, it's a thing that trips many up. But dealing with small details is also something that should be learned\nI believe the original purpose of the global variable was to actually pass a variable with a known value () to the function and validate that the function does not mutate it. However, the tests do not even check for this case. Such a test would look like: As states, the user should be writing their own calls to the function to test it, instead of changing the global variable. One way to possibly handle this, would be to remove the global variable declaration and use something similar as I mentioned above: I would argue, this kind of test should be to all the functional programming challenges, since this is one of the main concepts to learn.\nI can go ahead and submit a PR if we'd like to go this route.\ncan a string even be mutated in that way? shouldn't strings be immutable and so that is not possible in any case? the test should be to make sure the user reference function parameter instead of a global variable even if the global variable is present, I think To see if passed in argument is not mutated should be a thing to check with arrays and objects, as those are mutable\nyou are correct that strings are immutable, but it is possible to reassign the value of the variable within the function (which is bad practise, thus the reason for the test I believe).\nI mean if the global variable is removed from the editor you can't change a global string by operating on function parameter, right?\nCorrect - if we remove the global variable entirely, then it cannot be modified. If we leave it, it can only be modified by assigning the value to that variable name within the function. However, in general it is bad practise to modify the values of a function's arguments directly - with strings, it is less harmful than it is with arrays, but I believe that was the intent behind this particular test case. !\nI should not have used the word \. Looking at the challenge again, I think it would be fine to remove the global variable all together as it is not used in any other test (except the first). So, my suggestion is to remove the declaration and remove the first test, unless someone else can find a good reason to keep them.\nI have some errands to run, but can submit a PR later this evening. If anyone else would like to tackle this before then, let me know and I'll gladly step back and give you the opportunity!\nI would like to work on this issue, if that's okay with you .\nBy all means, go ahead! As a note, issues labelled with the \ tag (like this one) don't require permission before submitting a PR - I only made my earlier comment to ensure my interest didn't deter other contributors. Feel free to let me know if you have any questions! |
|
|
_idq-en-freeCodeCamp-a2ea0e1ba2891a7f05a03c300401ec65cb487d84ec1321fbf0ffe9af9c920581textDescribe 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. ! |
|
|
_idq-en-freeCodeCamp-5b90cc9d7a27398c8b954adcb04ae23be21527db5d36c597765fc30966c9fe9dtextIf there is no name set in the settings, doesn't matter if name is public or private, instead of falling back to username, it gives an error and certificate is not shown\nI assume the best UX is for a note to appear, if the Camper tries to set to public, without having first set to something.\nthe error appears also if name is not set and set to private - certificate does not appear saying that one has to put a name (I'm adding this on top message too)\nPicture !\nThe objective here then is to show the username on the certification if the name is not set ? Maybe some message then must warn the camper that his username will be shown on the certification instead of his real name (I am not sure though that a certification given to a weird username would be ok)\nalready if the name is private the username is shown, this issue appears if the name is not set\nApologies if this has nothing to do with you, but I vaguely remember you being involved in the discussion I cannot find: Was there any conclusion as to disabling the certification until a Camper has set their name, and made it public?\nSorry for the late response here - The only thing that comes to mind is\nEither we would need to remove having usernames as a fallback , or having a public name requirements when displaying certs. I now it might be inconvenient, but I vote for removing the fallback for simplicity and keeping the public name as a requirement.\nDiscussing in issue triage meeting. a camper sets the to a non-empty string and , the certificate renders with the . .When a camper sets the to an empty string and either or , the certificate does not render and redirects to with a flash message. We should update the behaviour of to mirror the behaviour of , and avoid using the username field as a fallback entirely.\nHello Is this issue solved ? |
|
|
_idq-en-freeCodeCamp-4bafc34f9f0eedc57ae03f155d05551de54638bd575964bff05cfd1bf97a20d5textDescribe your problem and how to reproduce it: SVG image in the challenge description is affected by SVG logo in navbar. They share some element s, what results in malformed image in description. Changing s to make them not overlap should deal with the issue. The simplest way seems to be, to change one of the images (probably one in the challenge), for example by adding unique prefix to s. That wouldn't eliminate completely the chance for some other conflict in future, but that's probably not something to worry about much. Add a Link to the page with the problem: If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): Current look ! Proper image ! |
|
|
_idq-en-freeCodeCamp-c5c4893455ff5ea7df8394ecf9cbb58b041ea01924e3ebd7c8d199bf05fc3614text<!-- NOTE: If you want to become an author on freeCodeCamp, you can find everything here: --The sidebar text on \ says \ The attribute cannot be an inline element. Change it to: \ or \. !\nHey good spot there I'll sort this"} |
|
|
{"_id":"q-en-freeCodeCamp-0399dd0ba18266ed224d19a48bc2b6f5d890749622a7b494bd3d81b7b9fe284d","text":"If I am signed in as a user while on and log out, I am redirected to the english home page. redirects to the chinese page.\nwrong endpoint in server code? Thats what I would assume, but am not sure how to locate where the correct endpoint would be placed in the code.\nHere is the endpoint: and most likely the issue is with the redirect \"predictor\" utility: However we would want to confirm the cause before we open this up for contributions.\nyes, that's the issue. To fix it we can grab the from and combine that with to get the desired redirect.\nShould that be done in the getRedirectParams function or should the path be put together from the data set returned by getRedirectParams in\nYou need to construct the URL from the values you get from the as a consumer of the function and not change its existing behavior. In simple terms the change is required within the endpoint handler.\nThat makes sense.\nI got the codebase installed locally is there a way to run just\nNot sure what you mean by running only one file? The API server is an express based application (Loopback 3). You need to start up at least the api-server app. If you want to do that, you should be able to do that by navigating to directory and using the run-script commands in its\nI'm trying to figure out what gets passed in pathPrefix, from getRedirectParams, when one signs out from the Spanish page. But when running the site locally, switching to Espanol leads to a \"This site can't be reached\npm run develop\close to prod\} |
|
|
{:,:} |
|
|
{:,:first time\} |
|
|
{:,:} |
|
|
{:,:} |
|
|
{:,:} |
|
|
{:,:} |
|
|
{:,:Check your code (Ctrl + Enter)\647\Screenshot 2022-06-09 at 16 52 28\https://user-\Ctrl or Command\} |
|
|
{:,:} |
|
|
{:,:} |
|
|
{:,:} |
|
|
{:,:} |
|
|
{:,:first-time\} |
|
|
{:,:message\Hello json\} |
|
|
{:,:} |
|
|
{:,:} |
|
|
{:,:} |
|
|
{:,:521\image\\} |
|
|
{:,:1429\image\\} |
|
|
{:,:} |
|
|
{:,:first-time\} |
|
|
{:,:} |
|
|
{:,:521\Screenshot 2023-12-18 at 13 58 26\\scripts\} |
|
|
{:,:} |
|
|
{:,:} |
|
|
{:,:Playwright-Gitpod Setup\How to add Playwright\How to add Playwright tests\Playwright-Gitpod Setup\} |
|
|
{:,:findIndex is an array method that lets find the index of the first element in an array that satisfies a given testing function.\lets find\lets you find\lets you find\lets find\} |
|
|
{:,:845\image\\} |
|
|
{:,:This\is\a\sentence\ \This is a sentence\} |
|
|
{:,:any field\id\} |
|
|
{:,:Certifications\Legacy Certifications\840\Screenshot 2024-03-12 at 12 04 47\\} |
|
|
{:,:all of those\} |
|
|
{:,:} |
|
|
{:,:} |
|
|
{:,:} |
|
|
{:,:} |
|
|
{:,:} |
|
|
{:,:too old\} |
|
|
{:,: rows[2] assignment\rows[ - 1]\rows[2]\rows[2]\rows[ - 1]\} |
|
|
{:,: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,\53\5\10/2\\122\53\5\10/2\\53\} |
|
|
{:,:} |
|
|
{:,:} |
|
|
{:,:} |
|
|
{:,:} |
|
|
{:,:767\Screenshot 2024-06-17 at 5 39 59 PM\\} |
|
|
{:,:first-time\} |
|
|
{:,:Tag omission\} |
|
|
{:,:} |
|
|
{:,:add a fillStyle property to the ctx object\set the fillStyle property of the ctx object\} |
|
|
{:,:an checkbox input\a checkbox input\} |
|
|
|
