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


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.
I 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.
I'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
Also 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
This 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
Also, 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.
I 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
6 and 3.
I vote for example 6 in single notes and example 3 in multiple notes.
I think it is settled then.


6 and 3. What do you think?
Agreed, with you all. Thanks. Please proceed with pull requests.
I would like to work on this. Is there a way to assign my name under the assignee? I am not able to do so
Hi 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.
The 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.
I found more cases for single note. Perhaps you can update the list Case 1: Case 2: Case 3: Case 4:
Are you going ahead with a PR to put it somewhere into the docs?
Are you converting them to the suggested style And have you come across many multi-notes?
In 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?
yes i am following the example 6 for single note (as voted) Have not come across multiple notes yet. Will re-check.
Good 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.


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.
I 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?
That 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.
I 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.
I 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.
that 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.


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.
I 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.
The search indexes have not been updated in over 12 months, so that could be part of this problem.
I 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.
So 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
I 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?
A PR to describe this in the guide? Sure


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
Page 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.
I would like to work on this issue. Please assign this issue to me .
We 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.


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
Yes, 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."
I am fine with the suggestion. You could use as the example. What do you think
Agreed I'm going to add the help wanted label.


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.


<!-- 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):**
I 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.
Can I take this issue?
If 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.
Sure! I'm still very new and inexperienced so I leave it to your more capable hands! 8D
I have started course and in my Glitch app there is no file, also putting console log in is also not working
You need to use the boilerplate project mentioned in the introduction challenge.


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...
I think this should be to the Hint: "Use the new Glitch link for this episode" See this forum posts:


<!-- 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-"
The 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.
Found 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".


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.
I've opened a pull request to fix these tests. Luckily, this "input-number-value problem" only afflicted this particular challenge.
thanks for explaining and for fixing :+1:
anytime :smiley:
Hi guys, thanks for taking the time to report and fix, we will get this reviewed soon. Happy contributing!
Hi, 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.
it 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) }


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.
Thanks 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.


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


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
To 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?
To 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.
That 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.
Update: 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.
I 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.
Other than the Feature Preview, everything is bog-standard. I will try to disable FP.


Disabled Feature Preview Rebased fork against upstream <details<summaryNew Client Error (similar, but different)</summary</details
If 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.
Fork? That could be relevant. Could you drop the Gitpod link that you're using here.
I 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:
All 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.
Quick 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?
I 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...
Hmm, 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. :(
I've one idea left to try, that's updating my own fork and seeing if I can repro. I'll have a go tomorrow.
This 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.


If there is anything in particular I need to work on, then I will take you up on this. Thanks
Just 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.
Worst case you would need to delete and recreate your fork and PRs, which is going to be a pain.
Strangely, his fork doesn't work locally also.
After 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?
Well, 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.
Sorry 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.
Hey 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.
Thanks for confirming the issue!


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.


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.
These all sound like reasonable changes. Go ahead and get a PR going for it.
I'll get started on it.


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
Hi 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.
Hey 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
Hi 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.


"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.


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
This 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.
I'm limiting comments in this issue to reduce noise. If you're interested in contributing, everything you need is provided in the thread.


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
I think this is more of a note for advanced campers, similar to mentioning that the tests might not work with a framework like Vue.
Yes 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?
It likely wouldn't - though I also haven't seen much mention of beginners who do have confusion.
I 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)
Thanks for opening this issue. This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: 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.


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.


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
I want to contribute towards this issue. Can you assign this issue to me.
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


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.
Hello! I tested this issue, and I was able to claim the certifications without completing the projects.
could you check if you can see the certification after claiming it? I'm just wondering if this is purely a client-side issue.
I am able to see the four certificates I could claim, yes.
Thanks 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.
Yes We Can Claim Python Certification Without submitting the Projects.
that's really serious


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.
I'm a new contributor but I'd like to help out on this.
I 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
Ah, interesting. This does seem to work locally but not on .dev for some reason.
This 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.


<!-- 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) !
Similar to
I am having the same issue with my Full Stack Certificate
Mine as well. Has this been addressed?
Same here - The issued date shows the current date and not the date on which it was originally issued -
Related
Have the same problem: the date of Full Stack Certificate is always a current date.
If 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.
optimally, 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.
My full stack certification also updates with the current date not the claimed date.
The 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.
This is an ongoing issue, please use the reactions instead to assert "me too". Potential approach for fixes: and
Also 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:
The 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!
Ok thenks On May 5, 2020 11:04, "Oliver Eyton-Williams" <:


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. --
the function should return (newItem). You put the newItem in an array literal, due to which the test is failing.
I 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?
it 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)
The 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 "
Yeah makes sense to me.


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".
I 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.
! you need to assign (newItem) to a new variable and return it
As 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.
If 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.
I think it would be better to compare:
IMHO, 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)
I 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.
I agree with any of your solutions, but I did not understand - why would another solution cease to be a non-mutating function?
If you change the expected behavior, then if is an array, the output of this function can be used to mutate , as I explained above.
Thank 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)?
I 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.


We just need to describe the task more accurately.
We 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.
Right.... 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.
Can I work on this ?
Sure. 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.
I've read through the full thread and submitted a PR that I think should satisfy most, if not all, concerns with the description.


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.
I 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


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
Agreed, it has the potential to be confusing. Can we reword to say: "If is the string and ..."
I'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?
I 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.


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
The 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
I 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=""
Text 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.
Hi 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
Thanks for the input your proposal addresses the issue I presented
That change works for me. Let's open it up for first timers This has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors.


If you would like to contribute and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the js let programmer = "Naomi"; programmer = "CamperChan"; ` Happy coding


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
Maybe 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.
I 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.
Looks like they accommodated for the tag in that test. Maybe we can just add it here too.
although, 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


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
I 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.
Hey 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.
I'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?
Do 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?


To be clear it should always work with regardless of the OS in addition to implicitly working with just like it was before.
I 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?
I've shot a short video of the behaviour I am seeing; if that helps.
That 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.
Thanks 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...
K, 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.


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.
Nice 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.
happy to give it a look and update the PR. Thank you
Here'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.


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.
I 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).
Yep, 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.
any 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
It'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?
there are a few, but they all seems needed where they are
I don't know why, but it comes from file line 98
there are some s, s s, too. gets me: of which probably should not be there.


I'd like to get input before we remove them, though. I think should eventually make it to Sentry and possibly should too.
could 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.
There'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).


<!-- 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). --!
Hi ! 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!
I'm going to start looking into this.
Thank you for fixing the issue. It was the first time for me on Github. I'm a total newbie in the webdev coding bootcamp.


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.
Hi Could you add some screenshots that demonstrate the problem you're describing?
Here 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.
I 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
Thanks for clarifying, and I'll open this up for PRs.
Implemented 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-"


There are missing spaces between some words in: "welcomeToBooleansfunction so that it will return trueinstead of falsewhen the run button is clicked."
There 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.


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
Hey Jessica, may I open a PR to fix this issue? Thank you!
We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labelled with or are open for contributions. Please make sure you read . We prioritize contributors following the instructions in our guide. Join us in or if you need help contributing - our community will be happy to assist you.


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"?
thanks for the issue. They should all be .


<!-- 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:
Btw, I think there is a typo in the description as well: should be
Looks like those could both changed.


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_
it 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.
Sorry for the misunderstanding. I need to change the text from 'template interpolation' -'string interpolation'
Hi, 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.
I am able to make the required change and happy to start open source contribution with hacktoberfest . Kindly assign this issue to me.
We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labeled with or are open for contributions. Please make sure you read . We prioritize contributors following the instructions in our guide. Join us in or if you need help contributing - our community will be happy to assist you.
This 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 :
After reading the contributing guidelines, I now understand the mistake I made in my PR.


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
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
Hi, 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!


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.
Hello, I would like to work on this issue.
hello,can i resolve the issue?


<!-- 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


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 !
/cc
Hello 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:
it 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.
PR 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-"
Yikes, that seems like it needs a fix as well. Thanks for catching that.


[ ] 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
Working on it!


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


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


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): !


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. !
Same goes for this challenge as well:
Humm, don't know why I did that. Yes, these need a proper line break.
Is this how you fork? This is my first time.
I 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 .


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.
I can fix this if it's decided to change it.
As 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.
as there seems to be an issue with a redux reducer.
I was speaking to earlier and he says:
Is someone looking into this ( Otherwise I can take a crack at it tomorrow.
Go for it - let me know if you want to team up on it.


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.
Thanks 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.
for 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.


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.
Thanks for the report! It seems it's a problem with redirection. redirects to and the link is to which redirects to cc:
Thank 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.
search is still broken? I can't get anything to load for generic searches.
what sort of generic searches are not loading for you? Things seem to be working on my end whether I search from .org/ or .news/.
working on my side on news and learn from multiple locations for the initial test case.
!
Should it say something like "No results for for 'this is a generic search', please try a different query"?
Thanks 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.
I 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.
Has the fix landed on production. I am able to reproduce the issue?
has not landed yet on learn. but you could see the fix on /news
The query string is passed on to the news application. URL is available on the GIF that I sent.
we 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.


Quick follow up, is there anything that is preventing us from deploying?
sorry 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.
Great, 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.
No 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.
This fix has been deployed. The problem in the gif above should no longer be possible on or


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
Nice catch! I will correct this.
i have linked pr for this issue kindly merge it thanks
We 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?


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.
Reopening it as we're migrating deprecated endpoints as discussed in todays API meeting


! Hi I have found this on my Learning Map... Hope this can help you all in solving bugs... :)
! Note: it seems to appear only on the section of lessons that I have completed.
This was fixed in and can be closed.
after reloading the page, I still get this - has the fix not been pushed to the server yet?
It got pushed just there folks!


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
Yeah, I just tested it. It's reproducible.
It 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.
Yeah... it's definitely not a big bug. Might cause minor annoyance though.
Agreed. It's not urgent, but it's definitely not working quite right.
I'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)


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
The same text is in the description, it would make sense to change description to not give out answer at the start.
Based 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
So we should leave the hint as is and modify the description text?
for the hint text we could go with this
Ok. Let's open it up for contribution then.
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 please use this for the updated description please use this for the updated hint text Happy coding


<!-- 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):
I 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 :)
Apologies... Actually, I've re-read the instructions. I think you may be onto something.
Yeah, 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".
Would like to have a crack at this
Go ahead and create a PR.
Had a go Please see


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
Thanks 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.


<!-- 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: <codesans-serif</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
Hi 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.
Hi@ Verdana similarly referring to the class of fonts, but please note picture, Verdana is surrounded <codeVerdana </code! in here should keep consistent
Thanks, that's a good point. I think Verdana should simply be plain text for consistency.
and 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.
It'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.
Am I missing something?


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'); `
and sans-serif both part of the actual css code !
My 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."
Thank 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 !
Let's go with wording, I think that should be clearer than what we have.
How should I further locate where the file is !
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. For instance
 thank you ---Original--- From: "Oliver Date: Fri, Apr 8, 2022 19:10 PM To: Cc: Subject: Re: [freeCodeCamp/freeCodeCamp] in here should exist 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.


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:


<!-- 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
I created a PR to deal with this issue.


<!-- 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):
Hello~! 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 ):
These are the ones that should be changed, I think. In fact, we could use instead.
I like that approach. Think this could be opened up to first timers?
I 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.
Sure, that works.


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


<!-- 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-"
The 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.
I 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:
The 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.
I'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.


Doing that should make it less confusing without watering the task down.
Thanks I like your suggestion to change the wording to
Any interest in creating a PR for that
Thank you for the link


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.
Hello 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
Hello, 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".
Hey . 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
Yes, 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.


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.
OK, I'll see if a can give it a try, then! Thank you :)
Hey 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]
Hi Are you sure you haven't a false positive produced by the ? Neither of the regexes can differentiate between commented and uncommented code.
You'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!


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
I 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.
Can 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.
I can reproduce this on the current master and on production.
I can take a look at the example projects and boilerplates to make sure is allowed as an origin.
Yup, please test one of the projects and see if it works, which may mean we needing to do something fancy about these.
I'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.
Okay, need to investigate then.
I think the forms may not be sending the URLs in the first place. Well, the server is complaining because it isn't getting them.
Hi everyone! I've been facing this for about a week or so. Tested yesterday and today (just now) and it's still the same.


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.
you 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.
we are on it.
I 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: ! !
Hi Kelsie, Thanks for reporting. Yes, please open a fresh issue.


<!-- 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-"
Confirmed this on Firefox 56.0 and Chrome 61.0 !
Fixed. Thanks for this issue; I needed a good hacktoberfest PR
No problem!


There is a typo at the following step: It should present the text: Device: Laptop OS: Windows 11 Browser: Brave Version: 1.


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:
methods are case sensitive. should be is a great place for questions like this
thanks 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!
I've tried it several times, making sure code was acurate... there must be another problem
Sorry about that but no one was answering me in the help room
no 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


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:
Issues are for reporting bugs or other problems with the site. Please consult the for help with writing code.
this is not issue. Your code just don't have any tags.
Thanks for reporting this. GitHub Issues are for reporting bugs on the website only. Please consult the for any assistance to Coding. Happy Coding!