Question: font-size: 20px; text-align: right; margin-right: 100px; <del> color: #fff; </del> <ins> color: var(--gray-00); } .certification-namespace .issue-date strong { color: var(--gray-00); </ins> } .certification-namespace .information {

When in a challenge, any of modals that popup (completion, ask for help, etc..), have a little close button at the top right that has recently become very hard to see... !
Also, when you hover over it, it gets obscured by the hover effect: !
Seems like there's an opacity issue... <img width="698" alt="Screen Shot 2019-11-26 at 8 11 42 AM" src="https://user-"Removing that 1% opacity makes it look like it did before, but I can't pinpoint where it's coming from in the code.
Production or local?
The hover effect is visible in production and they are also a little hard to see.
please investigate.
table for reference...
Thanks for the confirmation. The latest master is now (as of this comment) live on .dev, if you want to confirm this issue is fixed. If yes, I will proceed with the deployment to .org
I have pushed further to production and can confirm that the issue is reproducible on both staging and production applications.
I have bumped this to crit path.

Please see below. The text has been shifted around a bit in some aspect ratios. We need to ensure that the text on certifications looks right on all screen sizes: <img width="1149" alt="5freeCodeCamporgonTwitterWearetakingfreeCodeCampdownsowecandeploysomemajorchangesWewillbebacksoonInthemeantimeourYouTubeisupandithas1000codingtutorialsonPythonSQLDataScience_andMachine_Lea" src="https://user-"
Can I get steps to reproduce? I can't see this on my dev build with any screen size.
I can't reproduce this either. Although on one load of the above cert, I did get the date with a dark font color... <img width="877" alt="Screen Shot 2019-10-18 at 7 20 31 AM" src="https://user-"But I couldn't reproduce this a second time. Seems like maybe some of the intended css isn't getting applied intermittently or something.
hmm. it seems like a theme related issue. all colors in the certificate should come from :root {} in the
Since we're dealing with formatting and whitespace of certificates here, should we not center this to the page? !
Is it not already centered I'm not sure what you are referring to. So I think I figured out how to reproduce my issue. The date gets the dark font when you open a cert in a new tab or go to the URL through the address bar. But gets the correct font when you just open the cert in the current tab from the portfolio page. Can anyone else check this?
I’m referring to vertical centring. See the white gap between the end of the certificate and where the browser ends
I put in a pull request to center the certificates vertically on large screens. I can't reproduce your font color issue. New tab and navigating with URL both show the correct font color for me. I also can't reproduce the font offset in the first screenshot. So I don't think there is anything else that can be done on this issue unless someone can reproduce these.
I am not very sure as well, could be some specific device or viewport size. Will check with the OP to test this. Thanks for the PR.

The problems that pointed out: were not addressed in , so this should not have been closed.
Can anyone else reproduce that? or Quincy's issue? I can still reproduce mine on production, but not locally. Perhaps it has worked itself out on master.
I will have a build pushed to dev within the hour. Would you like your user record there for testing?
Sure
Okay let's do a before and after, I am have your user record to .dev, and will let you know again on this thread when I have pushed a build.
I can reproduce it on production. I haven't had chance to do locally, but my guess is you'll need to build the client to see it.
The changes have now landed in production as well. Can you check?
it's something to do with client-only routes. If you build the client and then use to serve it, you see the problem Tom found. For some reason you get a 404 for the cert route and it loads, but the gets and so the certificate renders incorrectly. Everything works as expected when using .
Hello - This may help debug the issue. I do not have this issue when viewing the certificate from my profile page - after clicking the "View Full Stack Certification" button. <img width="1377" alt="Screen Shot 2019-11-21 at 9 27 44 AM" src="https://user-"I do have this issue when viewing the certificate while visiting the url directly. <img width="1372" alt="Screen Shot 2019-11-21 at 9 31 17 AM" src="https://user-"
i think some general theme based color styles are over writing that element styles, in this case if this case if we make the styles more specific, and apply to it should work. !
It's not just the fonts. The page sizing is also getting messed up when visiting from an external link. If you come from somewhere other than fCC, you'll see scrollbars.
I could not reproduce this on mac and chrome 78.0.3904.108. could you give tell me about the browser and operating system you are using.
See scrollbar to the right when I open it externally ! None if opened directly from fCC ! Also, notice whitespace is different
Alright, since we've the donation request, this issue has been rendered moot


Question:
"Bonus User Story: As a user, I can see an icon depending on the temperature..", "Bonus User Story: As a user, I see a different background image depending on the temperature (e.g. snowy mountain, hot desert).", "Bonus User Story: As a user, I can push a button to toggle between Fahrenheit and Celsius.",  "Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON() to consume APIs.",   "Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON() to consume APIs.",  "When you are finished, click the "I've completed this challenge" button and include a link to your CodePen. If you pair programmed, you should also include the Free Code Camp username of your pair.", "If you'd like immediate feedback on your project, click this button and paste in a link to your CodePen project. Otherwise, we'll review it before you start your nonprofit projects.

Click here then add your link to your tweet's text" ],

Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. Step : "Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON() to consume APIs." incorrectly to this url: It should link to: Unless that misdirection is meant to be tricky for the student ;)
This is a duplicate of
Kind of. This one is referring to a different page (challenge/zipline), but I did notice that all of the Ziplines have the same bug.
This was fixed ages ago, right? Please close.
This isn't actually fixed. The erroneous link still exists in these ziplines: Maybe it's not an issue because we'll be switching over to the content at soon? But I thought you should know that the issue hasn't actually been fixed yet. Actually, the only reason that it isn't an issue on the beta site is that none of the ziplines seem to link directly to the jquery json page.
This was fixed in prior to the branch being available through Now they seem to have changed how the ziplines look, so it wouldn't be an issue regardless. Since all changes seem to happen on the branch before ending up in production, issues that are fixed in should probably be considered fixed, even though it might be better to merge small fixes like this into production at a quicker rate than what is the current reality.
Thanks for the explanation! That makes sense. I'm not privy to staging, so I didn't realize it had been fixed there.


Question: --- id: 56bbb991ad1ed5201cd392cd <del> title: Manipulate Arrays With shift() </del> <ins> title: Manipulate Arrays With shift Method </ins> challengeType: 1 videoUrl: 'https://scrimba.com/c/cRbVETW' forumTopicId: 18238

Describe the bug Having special character in the slug, title, or heading of the challenges lead to broken structure as shown in the image below. Originally reported by ! These challenges are the translation of these. ! Although we can not add them in the Arabic translation, this is a fix to the side effect, because Arabic isn't the only RTL language with translation efforts. I think it's better to not include special characters in the heading, if they aren't wrapped in spaced, example 'the Logical And Operator &&'. So I suggest two solutions: Delete special character, if they aren't wrapped around spaces, like change "push()" to "push". Add code block around functions and methods, to be something like .
Would it be acceptable to spell these out a little more? Instead of We could do Not only do we get rid of the special characters but it possibly makes it a little clearer for people listening to the page.
In translation, that's perfectly fine . Good call.


Question: const propTypes = { children: PropTypes.any, external: PropTypes.bool, <ins> sameTab: PropTypes.bool, </ins> to: PropTypes.string.isRequired }; <del> const Link = ({ children, to, external, ...other }) => { </del> <ins> const Link = ({ children, to, external, sameTab, ...other }) => { </ins> if (!external && /^/(?!/)/.test(to)) { return ( <GatsbyLink to={to} {...other}> {children} </GatsbyLink> ); <ins> } else if (sameTab && external) { return ( <a href={to} {...other}> {children} </a> ); </ins> } return (

The top nav items on the forum and news does not open in a new tab. We would like the same functionality on learn for consistency.
Do we want all external links to navigate without opening a tab? A quick search suggests that all the links in the footer open new tabs, as do a couple in . I think it's better UX to leave tab opening to the user, but I thought I'd check.
If you decide to go ahead with this, I'd like to have a go at this
I think we want this to remain as is except for the navigation links up top on the navbar, which are the most used links on the platform. This is to make it consistent with the behaviour on forum and news. can you proceed and make the changes. This will likely affect some of the routing. I would like to test this before working on the client app for chinese curriculum.


Question: } #learn-app-wrapper { <del> margin: 0 2em; position: absolute; width: 100%; right: -1.4em; padding: 5px 10px 5px 10px; </del> <ins> overflow-x:hidden; </ins> } @media screen, (max-width: 767px) {

!
I think 'settings ' is better UI, clearer and more obvious for users. Also think 'home' would be better than clicking freeCodeCamp word and icon which doesn't actually look like a button.
I agree. We should have both: a user photo and settings link - both of which will point to the settings. Is this something you'd be interested in helping us implement?
I'd be happy to but I've got a bunch on at the moment so might be a few weeks before I get a chance to look at it. I've it to my to-do list but in the meantime anyone else can pick it up. I'll add a comment if I start working on it.
I would appreciate it if someone told me what I should do and the progress of this issue.
Are you still interested in helping tackle this issue? I think we could add both a "home" button (which would take them to the "welcome page" to the navigation, and a "settings" link to the left of their photo (both the photo and the "settings" link would redirect them to /settings).
see my email - however for this issue I think I saw something being done in another PR which has changed the navs - www, learn and settings are all now different
Yes - we're trying to make the navigation universal across different services. We will add the settings button to the nav when we do so.
Hey there, is this issue still up for grabs? Also, are the requirements still as defined in It seems like it might have changed a bit from reading the conversation above. Thanks!
pointed out to me that we have a number of different navigations. I was wondering if you would be interested in a complete nav redesign to make it more comprehensive and more user friendly?
What is the current of this issue? Can I be of any help?
Thanks for your patience. We want to build a universal navigation component that exists on every page - including the Guide and Learn. Rather than add a ton of buttons up top, we want to add a footer that has links to all the various pages currently linked from The main problem with having a footer is that the curriculum view has 3 independently scrolling elements. Would you be interested in taking a crack at designing this? And We would welcome your help as well if you're interested in collaborating on this.

I made a quick pen at one point that I thought might be a good design to implement or build on... - basically just took all the parts we have on various pages and put them together.
Here's a list of what we might want in a footer.
I suggest finalizing the links that we need to include in the footer and then start working on the footer component. here is a link to bootstrap official sticky footer template: for large number of links, It is the industry standard to group the links for the footer. so we probably need to think of that. here are some examples: khanacademy: <img width="1234" alt="screen shot 2018-12-26 at 7 07 05 pm" src="https://user-"Udacity: <img width="1216" alt="screen shot 2018-12-26 at 7 07 43 pm" src="https://user-"EDX: <img width="1192" alt="screen shot 2018-12-26 at 7 08 12 pm" src="https://user-"Slack: <img width="1304" alt="screen shot 2018-12-26 at 6 59 48 pm" src="https://user-"
Any ideas for resolving the 3 scroller issue Qunicy mentioned? I think if we had only one scroller, the user had to scroll to the bottom of the page anyway to get the footer. Right now, i get a pretty similar behavior. when I have my cursor on a scrolling component and scroll to the end I am able to go where the footer component would be. So I don't think it is a major issue because the behavior is similar.
I like the simplicity of Khan Academy's footer, with it's mission statement and call to action on the side: freeCodeCamp is a donor-supported tax-exempt 501(c)(3) nonprofit organization (United States Federal Tax Identification Number: 82-) Our mission: to help people learn to code for free. We accomplish this by creating thousands of videos, articles, and interactive coding lessons - all freely available to the public. We also have thousands of freeCodeCamp study groups around the world. Donations to freeCodeCamp go toward our education initiatives, and help pay for servers, services, and staff. You can .

Columns: Our Nonprofit Our Community Our Learning Resources
Here is a quick pen. any thoughts?
This looks great! Very nice clean design, good use of whitespace, and good responsivity.
I have a working footer, and as Qunicy mentioned it does affect the user experience when placed under three scrolling divs. here are some solutions. the separating the columns separating the three panels so campers have something to grab onto to scroll the whole page rather than individual panels; a an expandable fixed bar at the bottom. a sticky expandable small footer at the bottom. removing the footer on this page. Let me know about your feedback so I could proceed with finalizing the footer. Thanks P.S there are other issues with the UI's grid system and markdown that affects the footer implementation. I addressed them in a separate issue.
There's already a lot going on in this area. More scroll bars seems like clutter and possible confusion... I like the expandable option(s) or... the footer within the lesson panel?
Thanks that is definitely an option. we should see how it would like in action. I also like the small expandable option. so if it does get in the way of the user, at least it is a small distraction. I included a gif of the current state of the footer in different screens. let me know what you think. btw, how does the style and the color look? !
Looks good, I was thinking more of a green background to match the nav, but the gray and green buttons look good... might want to get Quincy's opinion there. And actually, that looks pretty good just putting it at the bottom of the other panels... the scrollbar is hidden until you scroll down - I suppose it might be different on other browsers. It could maybe use some white space or something to separate it from the lesson panels a little. But overall, it looks real good - nice job!
I want to be an active participant in designing the footer but as you know I am presently inactive in the community. Fortunately, I landed here while I was looking at the issues. I want to share some ideas on this. Amazing work there . I am a big fan of GitHub's footer! We should do something similar. We should put the full footer only on the main homepage.

Few primary links may be put on the authorized user's welcome page. Some screenshots will clear the design I have in mind. ! ! ! ! And I am totally against putting footer on the platform. Before making any UI change we should ask ourselves "As a camper will it improve my learning experience?". Putting footer on platform will not. Presently, we have a lot of scrollbars and buttons on learn platform and putting footer there will conjust things up more. So, no footer on is the way we should be going :)
thanks for the valuable input. That is the industry standard to implement footers. So ideally the footer component will receive some props depending on the page that the user is visiting and output a custom footer. Let's wait for output to see which direction he would like us to pursue.
Nice design of the footer. I was wondering if for the social media part(FB, twitter, medium, Youtube etc.) we could change it to logos.
That looks solid! Rather than simplify the footer as GitHub has done, I propose we keep it the same everywhere so people don't have to adapt to the fact that the footer changes from page to page. We want to keep our navigation up top the same on every page, too. Regarding having the footer on Learn - we do eventually want to do this, but we need to figure out how. As pointed out, with the current multi-pain scrolling, having a footer would be a pain. Let's worry about that later, and focus instead on creating a common component we can use on all the non-learn pages. Since you've already got a working design of the footer, are you interested in tackling this?


Question: const res = await fetch('https://pokeapi-proxy.freecodecamp.rocks/api/pokemon/pikachu'); // Fetch from proxy to simulate network delay if (res.ok) { <del> await new Promise(resolve => setTimeout(resolve, 50)); // Brief additional delay to allow UI to update </del> <ins> await new Promise(resolve => setTimeout(resolve, 1000)); // Additional delay to allow UI to update </ins> const sprite = document.getElementById('sprite'); assert.isTrue(sprite.src.endsWith('sprites/pokemon/25.png'));

When testing one camper's code it fails some tests unless I increase all the delays to 1000ms, I tested with 500ms but that was not enough. I also saw the example project fail a test but it does pass more consistently (my guess is it is just faster with fewer async functions). To be on the safe side we should have a longer delay. I know 1000ms is a lot but better safe than sorry. Tests: Valid code should not fail because of "timing" issues. No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] Forum:
As this is a bug with a certificate project I the showstopper label.


Question: # --description-- <del> To elaborate a question using `there is` you just need to change the order of the verb to be, like so: </del> <ins> To elaborate a question using `there is` you just need to change the order of the verb `to be`, like so: </ins> `There is an ATM nearby` -> `Is there an ATM nearby?`

needs to be wrapped in backticks ( ``) in the first sentence needs to be wrapped in backticks. Here also needs to be wrapped in backticks. This looks like something that can be fixed by "first-time" code contributors to this repository. The files you should look at to work on a fix are the 3 linked 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.


Question: If the user rolls three of one number, and two of another number, this is called a full house. Declare a `detectFullHouse` function that accepts a single argument. The function will be passed the `diceValuesArr` array when called. <del> Your `detectFullHouse` function should check if the user has rolled three of one number and two of another number. If so, it should update the third radio button to display a score of `25`, with the correct attributes. If not, it should update the last radio button to display a score of 0, with the correct attributes. </del> <ins> Your `detectFullHouse` function should check if the user has rolled three of one number and two of another number. If so, it should update the third radio button to display a score of `25`, with the correct attributes. Regardless, it should always update the last radio button to display a score of 0, with the correct attributes. </ins> Don't forget to call your new function when the dice are rolled.

in step 13 of the dice game (js beta), the instructions say: Your detectFullHouse function should check if the user has rolled three of one number and two of another number. If so, it should update the third radio button to display a score of 25, with the correct attributes. If not, it should update the last radio button to display a score of 0, with the correct attributes. However when we look at the code in the following step 14 for this function we see this: Notice how the last radio button is updated regardless of the full house check? But the instructions said: "If not, it should update the last radio button...". People are trying to follow this instruction and failing and not understanding why (they use an if-else statement for example as in the code below) The instructions should be changed to match the requested code: Your detectFullHouse function should check if the user has rolled three of one number and two of another number. If so, it should update the third radio button to display a score of 25, with the correct attributes. It should also update the last radio button to display a score of 0, with the correct attributes. However, I noticed that the functions getHighestDuplicates and detectFullHouse are both updating the last radio button. So it seems like one of these need not do that? (so we could just not ask for this in this step since it is gonna get updated elsewhere anyway?) No response N/A I noticed this issue when I was attempting to help a camper on the forum:
I don't know why we are updating the (5,0) radio button when there is a non zero value i.e. full house, three of a kind, four of a kind ? Anything positive integer will result in more high score. I think we should only implement the last radio button the zero one when nothing above works. There is two scenario whether the None of the above is a choice which should be present every time OR we must give it as a last option to the user or maybe make it default when rolls are over. I just removed the updateRadioOption(5, 0); from the getHighestDuplicates && detectFullHouse locally in my machine and initiated it when all the 3 roll options are over, then it became the obvious choice. ! !

If you like my implementation I would love to raise a PR or if you have any other implementation logic, I would like to work on this issue :)
I propose updating the text to:
the text works but should we look at why so many of the functions in this project need to update the last radio button? I feel like updating the last radio should just happen independently of the various functions like getHighestDuplicates or detectFullHouse
In a production app, sure. Here, I think the reinforcement of how conditions work and how code after an block executes and such is good.
Okay fair enough, thanks.


Question: export const challengeMetaSelector = state => state[ns].challengeMeta; export const challengeTestsSelector = state => state[ns].challengeTests; export const consoleOutputSelector = state => state[ns].consoleOut; <ins> export const isChallengeCompletedSelector = state => { const completedChallenges = completedChallengesSelector(state); const { id: currentChallengeId } = challengeMetaSelector(state); return completedChallenges.some(({ id }) => id === currentChallengeId); }; </ins> export const isCodeLockedSelector = state => state[ns].isCodeLocked; export const isCompletionModalOpenSelector = state => state[ns].modal.completion;

In the new beta (currently at ), it would be great if a challenge page indicated somehow when the challenge has already been completed. Currently, since user inputed code is not saved, there is no indication on a challenge page that it has already been completed.
We need a check mark in the title or a badge or to indicate the same?
The most elegant thing I can think of to have something like the little circular check mark next to the title like how it is on the learn homepage - only if it's been solved, and don't show anything if it hasn't.
That would be a nice way to handle it. Please go forth if you are interested in this?


Question: const { formValues: { githubProfile, linkedin, twitter, website } } = this.state; <ins> const { state: githubProfileValidation, message: githubProfileValidationMessage } = this.getValidationStateFor(githubProfile); const { state: linkedinValidation, message: linkedinValidationMessage } = this.getValidationStateFor(linkedin); const { state: twitterValidation, message: twitterValidationMessage } = this.getValidationStateFor(twitter); const { state: websiteValidation, message: websiteValidationMessage } = this.getValidationStateFor(website); </ins> return ( <Fragment> <SectionHeader>Your Internet Presence</SectionHeader>

Describe the bug For field in , error state can not be triggered. Warning state will be triggered when an email address with incorrect domain is entered (for example: ). For all fields in , both error and success state can not be triggered. To Reproduce Steps to reproduce the behavior: to http://localhost:8000/settings to fill and to Describe the bug Expected behavior For field in , error state should be triggered instead of warning state. There should only be two states for an email address. Success state is when it is a valid and reachable email address. Error state is when it is an invalid and unreachable email address. For all fields in . Success state is when it is a valid and reachable URL. Error state is when it is an invalid and unreachable URL. Desktop (please complete the following information): OS: Windows 10 1809 Build .832 Browser Latest Chrome Version 77.0.3865.120 (Official Build) (64-bit)
Calling to discuss this from issue . What do you think about this? Are there anything to add or change from the Expected Behavior I described?
the only thing I'm not sure about is 'unreachable'. Do you just mean unreachable because the URL is malformed? Like , for example. If so, then I completely agree. cc
Yes of course. 'Unreachable' is only defined by malformed email format ( valid length, etc) and URL format (protocol, colon, double slash, etc). It is also possible to check the top level domain part against current existing TLD programatically. Other than that, for example checking real email address which is existing should be done by email confirmation / verification.


Question: "Return true if the passed string is a valid US phone number", "The user may fill out the form field any way they choose as long as it is a valid US number. The following are all valid formats for US numbers:", "555-555-5555, (555)555-5555, (555) 555-5555, 555 555 5555, 5555555555, 1 555 555 5555", <del> "For this challenge you will be presented with a string such as "800-692-7753" or "8oo-six427676;laskdjf". Your job is to validate or reject the US phone number based on any combination of the formats provided above. The area code is required. If the country code code is provided, you must confirm that the country code is "1". Return true if the string is a valid US phone number; otherwise false." </del> <ins> "For this challenge you will be presented with a string such as "800-692-7753" or "8oo-six427676;laskdjf". Your job is to validate or reject the US phone number based on any combination of the formats provided above. The area code is required. If the country code is provided, you must confirm that the country code is "1". Return true if the string is a valid US phone number; otherwise false." </ins> ], "tests": [ "expect(telephoneCheck("555-555-5555")).to.be.a("boolean");",

Need to document the rename challenge tool and the i18n sync tool. Sometime later this week. Not urgent.
I can take this on?
Go for it, Thanks!
I will start with the rename challenge tool, for the i18n sync, I will wait news if it works now


Question:
Do you have any questions:

  <textarea id="css-questions" name="css-questions" rows="5" cols="24"> Who is flexbox... </textarea>   <textarea id="css-questions" name="css-questions" rows="5" cols="24" placeholder="Who is flexbox..."></textarea>

<!-- 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. -- The final instructions for this step say: "Then, give the placeholder text describing an example answer." Since the instructions mention "placeholder" I think it is safe to assume that some people will think they should use the attribute on the to fulfill this requirement. But the code check test checks the of the : So using the attribute will result in the following hint: "You should give the placeholder text describing an example answer." Which does not make it clear that the example answer should be embedded in the instead of using the attribute. Based on the current instructions I think most users will assume that the attribute should be used to complete this step and the test should be updated accordingly. <!-- Please complete the following information. --- Device: Desktop OS: Linux/Fedora 34 Browser: Firefox Version: 95.0.2
On
I was going to fix this issue by updating the test in step 38 to check the placeholder attribute on the textarea but then I realized that if we make this change then the HTML in each step after 38 would also need to be updated to use the placeholder attribute as well. So the question is, do we want to use the placeholder attribute and update all of the remaining steps or do we want to reword the instructions in step 38 to make it clear that you should embed the question text in the textarea and not use the placeholder attribute?
That's a good question. The placeholder text matches wording from referring to the attribute. That would make me think, the intention is to use the attribute.
Agreed, this should probably be updated to use the placeholder attribute. Looks like I've got a lot of updates to include in the PR.
Thank you, for opening this. When I wrote this, I vaguely remember reading a resource mentioning using the attribute on was not the recommended approach. However, as I cannot find that, I agree using the attribute in this case seems like the better option. Yes, this will require a rewrite for all subsequent lessons. However, this usually is a simple Find and Replace.
Perfect. I'll submit a PR for this in just a bit.


Question: "title": "Set a Content Security Policy with helmet.contentSecurityPolicy()", "description": [ "As a reminder, this project is being built upon the following starter project on Glitch, or cloned from GitHub.",  "This challenge highlights one promising new defense that can significantly reduce the risk and impact of many type of attacks in modern browsers. By setting and configuring a Content Security Policy you can prevent the injection of anything unintended into your page. This will protect your app from XSS vulnerabilities, undesired tracking, malicious frames, and much more. CSP works by defining a whitelist of content sources which are trusted. You can configure them for each kind of resource a web page may need (scripts, stylesheets, fonts, frames, media, and so on…). There are multiple directives available, so a website owner can have a granular control. See HTML 5 Rocks, KeyCDN for more details. Unfortunately CSP in unsupported by older browser.",   "This challenge highlights one promising new defense that can significantly reduce the risk and impact of many type of attacks in modern browsers. By setting and configuring a Content Security Policy you can prevent the injection of anything unintended into your page. This will protect your app from XSS vulnerabilities, undesired tracking, malicious frames, and much more. CSP works by defining a whitelist of content sources which are trusted. You can configure them for each kind of resource a web page may need (scripts, stylesheets, fonts, frames, media, and so on…). There are multiple directives available, so a website owner can have a granular control. See HTML 5 Rocks, KeyCDN for more details. Unfortunately CSP is unsupported by older browser.",  "By default, directives are wide open, so it’s important to set the defaultSrc directive as a fallback. Helmet supports both defaultSrc and default-src naming styles. The fallback applies for most of the unspecified directives. In this exercise, use helmet.contentSecurityPolicy(), and configure it setting the defaultSrc directive to ["self"] (the list of allowed sources must be in an array), in order to trust only your website address by default. Set also the scriptSrc directive so that you will allow scripts to be downloaded from your website, and from the domain 'trusted-cdn.com'.", "Hint: in the "'self'" keyword, the single quotes are part of the keyword itself, so it needs to be enclosed in double quotes to be working." ],

Typo in the description. !
Just to make it clear, you are suggesting to change to . Is there any other typos that you found in this challenge?
Correct. That's the only typo I have found. I know it's minor issue but it will be a good opportunity to fix for beginners.
this is the file with the typo -
I am a little confused about challenge files. What about this file in repo? Where should one correct the mistakes?
im confused at the moment as well - there's some changes in progress regarding where the challenges are so I'm not sure if we should be making PR's involving seed files to the main repo or the curriculum repo - I would guess it will be over there in future but at the moment I'm not sure what's best
For now I am solving all typos in curriculum, so if anyone finds any typo in the challenges please refer me.


Question: assert(document.querySelectorAll('a').length >= 2); ``` <del> You should only add one opening anchor (`a`) tag. Please remove any extras. </del> <ins> You are missing a closing (`a`) tag after the image. </ins> ```js assert(document.querySelectorAll('a').length === 2);

I've run into this enough in the forums that it might be time to fix it. A lot of people leave off the closing tag when turning the image into a link. The hint they get is: "You should only add one opening anchor (a) tag. Please remove any extras." Which is confusing since the objective of the step is to add a second link to the page and the hint makes it sound like there should only be one. Instead, the hint should probably remind them that an anchor element needs both an opening and closing tag. Whether we want to spell it out even further by telling them that they are missing the closing tag I will leave up to the hive mind. If we don't want to be too explicit we could do something like: "Hint: Creating a link with the anchor element requires both an opening and closing tag." Or: "Hint: You must use both an opening and closing tag to create a link." Or if we want to be more direct: "Hint: You are missing a closing tag after the image." No response N/A No response
I think being explicit about a closing tag being needed is the way to go this early in the curriculum
Let us go with this.
Yeah I read through your Issue and it is quite confusing to get this hint. The explicit hint you mentioned is the way to go.
Can I make that change ? I just did this locally and works.
This has a help wanted tag, so anyone is free to open a PR for this.
I think that we need to decide exactly what to change - just changing the text of the hint without changing the associated test will cause more problems
Is this designed just to discourage newbies like me? Over an hour on this step. No previously posted code nor clarifications helped... just sent me down new rabbit holes. You need to know code to decipher the clarifications. Must be part of a hazing process. THIS code works as of the date of this posting: <a href=""<img src="" alt="A cute orange cat lying on its back."</a (eliminate the space between the closing anchor "a" and the "" <h 1Now I know I am crazy enough to continue down this road/ rabbit hole universe</h 1(extra spaces for effect, LOL)
please use the freeCodeCamp forum if you have questions about your code or you get stuck. This content is hard, but there is no intentional 'hazing'.


Question: Convert a given date from the Gregorian calendar to the Discordian calendar. <del> Note that in the Discordian calendar (Chaos 1, 3188 YOLD) is (January 1, 2022), in the Gregorian calendar. </del> <ins> Note that the day Chaos 1, 3188 YOLD in the Discordian calendar is the day January 1, 2022 in the Gregorian calendar. </ins> # --hints--

Just transcribing issues from crowdin. In this line: There is an extra comma before the anchor element that has to be removed. In this line: There is an incorrect use of parenthesis. It should become This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
Hey, I would like to work on this.


Question: # --description-- <del> In your `goTown` function, update your button `innerText` properties to be `Go to store`, `Go to cave`, and `Fight dragon`. Update your `onclick` properties to be `goStore`, `goCave`, and `fightDragon`, respectively. Finally, update your text's `innerText` property to be `You are in the town square. You see a sign that says Store.`. </del> <ins> In your `goTown` function, update your `button` elements' `innerText` properties to be `Go to store`, `Go to cave`, and `Fight dragon`. Update your `onclick` properties to be `goStore`, `goCave`, and `fightDragon`, respectively. Finally, update your text's `innerText` property to be `You are in the town square. You see a sign that says Store.`. </ins> # --hints--

In crowdin, I noticed that step 48 of the new JS course, build an rpg, uses a sentence that may need a grammar correction. Instead of “your button innerText” it should say “your buttons’ innerText”? Full sentence was: Grammar correction. No response N/A No response
Hello , Can you assign me this?
Should be changed to:
Thanks for opening this issue. This looks like something that can be fixed by "first-time" code contributors to this repository. 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.


Question: justify-content: space-around; flex-direction: row-reverse; margin-bottom: 0px; <ins> padding-top: 3px; padding-bottom: 3px; </ins> position: fixed; width: 100%; z-index: 1000;

When you sign in or change an option on settings, you get an alert banner up top. It could be a little thinner so it doesn't cut so close to the body elements <img width="1420" alt="Learn_freeCodeCamp_org" src="https://user-"
should we go all the way? <img width="1198" alt="Screen Shot 2019-10-19 at 12 39 56 AM" src="https://user-"
The layout element needs to be pushed below the notification. Currently it overlays on top of it.
Should I work on it?
Yes please. Note the the notification should be shorter in height and should also be "injected" in-between the nav and the layout instead of overlaying.


Question: Variable myStr should contain the string: `I am a "double quoted" string inside "double quotes".` ```js <del> assert(myStr === 'I am a "double quoted" string inside "double quotes".'); </del> <ins> assert(/I am a "double quoted" string inside "double quotes(."|".)$/.test(myStr)); </ins> ``` # --seed--

This is a dumb problem and I am new to GitHub so please forgive me for any weirdness. Basically, on this page, we see this explanation: This signals to JavaScript that the following quote is not the end of the string, but should instead appear inside the string. So if you were to print this to the console, you would get: Alan said, "Peter is learning JavaScript". and we are asked to make this string: I am a "double quoted" string inside "double quotes". However, I think that the period should be inside the quotations, grammatically. Like "double quotes." Thank you.
Thank you for your bug report, but I think this is in the realm of bike shedding
I do agree with that this is indeed a small typo but I also agree with that it is indeed a grammatical prob. Since this typo got noticed, I'd say let's fix it.
While I think it is fine to correct the typo, I think the tests should be loose enough to accommodate the period inside or outside the last double quote. The point of the challenge is escaping double quotes, so we do not want to get caught up in forcing the user to keep the period inside or outside the quotes. The reason I say this is the new curriculum is going in this direction. We are going to be lenient in the tests when it makes sense to. In my opinion, this is one of those cases.
Sure. Let's keep the tests lenient and fix the typo.
Is this still a first-timers issue now, since the contributor must also modify the test to accommodate both versions of the string?
Ooops. Forgot to update that. Thanks for the catch!
Thank you for your reply. I agree the grammar shouldn’t matter in the challenge. The problem was that when I tried to submit the answer with the “proper grammar,” it told me my answer was wrong, and I had to change it to the “improper” way. I’m an English teacher rather than a programmer, so completing the challenge with the improper grammar hurt my soul a little bit, haha.
Hey , I just made a PR () that fixes the grammar issue and it looks quite simple as there's no need to change the tests. So, let's open this up for , what do you say?

Just to add this: I do not see this as a bug/typo, because I mostly use British-styled English. So, the only reason we might change this is if we are trying to have uniformity about using only American-styled English within the curriculum.
both versions should be allowed, dot inside and dot outside. Your PR just changes wich version is allowed
I didn't knew that it differed in these two styles. If that is the case I'm in favour of closing this issue as it is proper English eitherway. The tests and the sentence in the test question isn't changed in my PR as it is correct. I only changed the example sentence in the PR. (Apologies for the trouble and misunderstanding )
the change discussed here about making both solutions work is not wanted anymore?
Re-opening.


Question: ```js { <del> username: "fcc_test" </del> <ins> username: "fcc_test", </ins> description: "test", duration: 60, date: "Mon Jan 01 1990",

There should be a comma for "username: "fcc_test", otherwise the JavaScript Object syntax is wrong. <img width="775" alt="image" src="https://user-"- Device: MacBook Air M1 OS: macOS Monterey 12.0.1 Browser: Chrome Version: 98.0.4758.109
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.


Question: You should add a `constructor` method to the `ShoppingCart` class. ```js <del> assert.match(code,  /classs+ShoppingCarts*{s*constructor(s*)s*/) </del> <ins> assert.match(code,  /classs+ShoppingCarts*{s*constructors*(s*)s*/) </ins> ``` Your `constructor` method should be empty. ```js <del> assert.match(code,  /classs+ShoppingCarts*{s*constructor(s*)s*{s*}s*}/) </del> <ins> assert.match(code,  /classs+ShoppingCarts*{s*constructors*(s*)s*{s*}s*}/) </ins> ``` # --seed--

the check for step 15 of the shopping cart does not allow a space to be placed to the immediate right-hand-side of the word constructor (just before the parenthesis), however that seems to be valid syntax. update the check for this step to allow a space to the immediate right-hand-side of the word constructor No response N/A No response
I found a similar issue with another step here: (it also doesn't allow the constructor to have a single space to the immediate right of the word constructor) Can this be fixed at the same time?


Question: # --hints-- <del> You should modify the pattern passed as the first argument to the `re.sub()` call using a negative lookbehind. TODO: add details/improve wording </del> <ins> You should modify the pattern passed as the first argument to the `re.sub()` call using a negative lookbehind. </ins> ```js ({ test: () => assert(runPython(`

There was a TODO comment left in the hints for the Equation Solver project <img width="759" alt="Screenshot 2024-09-30 at 11 11 37 AM" src=""The hint should be updated to the following: 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
can you please add label to this issue as "Hacktoberfest"
Hi, I'd like to contribute to this issue! I'll update the hint for the () call to use a negative lookbehind and submit a PR shortly. Thanks for the opportunity!
Hello! I'm interested in resolving this issue by refining the str method within the Equation class. My plan is to adjust the () function to incorporate a negative lookbehind, ensuring that the digit '1' is only replaced when it isn't preceded by another digit. This approach will prevent unintended substitutions in multi-digit numbers. I'll prepare a pull request with these modifications soon.
I would like to contribute to this issue. I have contributed to hacktoberfest last year as well. Please assign it to me.
the repo has the label, the issue label don't matter. 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.
Please do not make any changes outside what is outlined in the issue. The scope of the issue to only update the hint text to remove the TODO comment. Any other changes will not be accepted in a PR Thank you
Thank you for the clarification!

I'll ensure the changes in my PR are limited to updating the hint text and removing the TODO comment, as specified in the issue. I appreciate the guidance!
Thanks for the clarification Mam


Question: let textMessage = dedent( `**Tell us what's happening:** <ins> Describe your issue in detail here. </ins> ${ projectFormValues.length

Describe the bug Last week, I saw multiple posts where people asking for help didn’t write down what they needed help with. I think the help post template may be confusing some folks. Screenshots ! Additional context “Tell us what’s happening” looks a bit like an overall heading. I suggest the following changes to make it more obvious that people are supposed to write something down: Mockup !
Hello there, Thank you, for taking the time to open this. I believe it would help some Campers understand the need to add more information. However, I suspect the large majority just post without reading any further. The Discourse software does have a lot of cool features aiding the topic creating (e.g. Information about informative titles, showing similar topics). If others are in agreement, this would be an easy implementation, and could be put up for first timers? That being said, I find dedent to be pesky.
I'm not big on the idea of adding an extra heading. Perhaps just the extra describe prompt: Tell us what's happening: Describe your issue in detail here Your code so far: Your browser information: blah blah blah Mildly related - I think we should add a colon after "Your code so far" to match the other headings.
If it's a first-timer I'll let somebody do it but if not I can take care of making the changes. Your call!
Any decision on if we're opening this for first timers?
Can I work on this issue, being my first contribution to freeCodeCamp?
please go ahead.
Hi, I saw that this issue wanted to be done by someone a few days ago, but its still not been closed, I am also an newbie and am really eager to contribute so would be happy to help, and close it today. Was trying to find the template to change it, but couldn't find the file. Would it be possible for someone to point me to the right file? Thanks :)
Hey it's this one -
Thanks


Question: return n; } <del> intRightTriangles(1000); </del> <ins> console.log(intRightTriangles(500)); // 420 </ins> ``` </div>

<!-- 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: Project Euler 39 automated test for n=800 should expect 720, which is the correct answer [ [ 45, 336, 339 ], [ 72, 320, 328 ], [ 80, 315, 325 ], [ 120, 288, 312 ], [ 144, 270, 306 ], [ 180, 240, 300 ] ] Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: 79.0.3945.130 (Official Build) (64-bit) Operating System: MacOS If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):


Question: The link's text should be `cat photos`. You have either omitted the text or have a typo. ```js <del> const nestedAnchor = document.querySelector(`p > a`); assert( nestedAnchor.innerText.toLowerCase().replace(/s+/g, ' ') === 'cat photos' ); </del> <ins> const nestedAnchor = document.querySelector('p > a'); const innerContent = nestedAnchor.innerHTML; assert.isTrue(innerContent.trim() === 'cat photos'); ``` The text inside your anchor element has extra leading or trailing whitespace. The only space in the anchor text should be between the word `cat` and the word `photos`. ```js const nestedAnchor = document.querySelector('p > a'); const innerContent = nestedAnchor.innerHTML; assert.isNotTrue(/^s+|s+$/.test(innerContent)); </ins> ``` After nesting the anchor (`a`) element, the only `p` element content visible in the browser should be `See more cat photos in our gallery.` Double check the text, spacing, or punctuation of both the `p` and nested anchor element.

A camper managed to fail the challenge despite having a close enough correct solution for the challenge. It even displays correctly in the browser. I do not believe the tests should be failing if there are spaces around the words "cat photos" in the anchor element. The user should be proceeding to another challenge. No response Device: Desktop OS: Windows 10 Browser: FireFox Version: 118.0.2 No response
I think here we should actually expect correct whitespace.
They shouldn't be messing with that element in the first place in step 13. I think step 12 is more relevant for this issue. And yes, a lot of people add extra spaces in the link text and get bit by this. This was mentioned in issue and I think the consensus is that a test should be specifically to check for the extra white space. I would normally agree that extra white space should not be an issue and the tests should not be so strict about it. But for link text I can see the reasoning. If you add extra white space after "photos" then you will see the underline on the link extend past the word "photos" into the white space after the word. This is one of those few instances where white space actually does make a difference.
Hey, I am a first-timer and I would like to solve this issue
Please read our contributing guide. This issue is not marked as ready for contributions and we do not assign issues.
There is a test where the user is prompted for typos. So instead of writing a test for just detecting whitespaces can't we just mention to avoid whitespaces in that prompt? !
I think it would probably be better to mention whitespace separately since it's early in the curriculum
Sorry if I am wrong about this but do you mean we should make the test less strict and allow whitespaces?
Nope. I think we should check whitespace and typos separately.
does this work then?
The link's text should be . You have either whitespaces before or after the text javascript const nestedAnchor = $('p a')[0]; const hasWhiteSpaceBeforeCat = /^(nestedAnchor ); const hasWhiteSpaceAfterPhotos = /s+$/.test(nestedAnchor ); assert( hasWhiteSpaceBeforeCat hasWhiteSpaceAfterPhotos );
The test for the p element content probably also needs an adjustment to be agnostic to whitespace? And then this test for whitespace would follow?

This regex pattern tests true for sentences with single whitespace between words and no whitespaces before and after the starting and ending word respectively. You can try below code for verifying that So I can write a single test to verify if there are no extra whitespaces between words and no whitespaces before and after the first and last word. So if I get the innerText of the tag then I can just run the test on that to verify the text inside the nestedAnchor tag.
I'm talking about modifying the current test that checks forboth typos and spaces at the same time.
This is the current test for only typos.
The link's text should be cat photos. You have either omitted the text or have a typo. As far as I can understand you want this modification to the test right? javascript const nestedAnchor = $('p a')[0]; const pText = document.querySelector('p').innerText.toLowerCase(); //get the inner text which includes text inside anchor tag const typoCheck = nestedAnchor.innerText.toLowerCase().replace(/s+/g, ' ') === 'cat photos'; //checking for typos const whiteSpacesCheck = /^(S+sS+)+$/.test(pText); assert( typoCheck whiteSpacesCheck ); //if either is false then it will fail
I'm saying that test needs to be two tests.
I have three options of writing the test: telling the users to avoid whitespaces when the typo test fails and this text is prompted to the user 'The link's text should be cat photos. You have either omitted the text or have a typo or have extra whitespaces.' and not adding a new test. separate tests for checking typos and whitespaces. The link's text should be cat photos. You have either omitted the text or have a typo. AND The link text seems to contain extra whitespaces. both the tests into one single test. The link's text should be cat photos. You have either omitted the text or have a typo or have extra whitespaces. Please tell me which option solves the issue. If none of them are correct then please elaborate more on the proper solution I am unable to understand the proposed solution. Also sorry if this is causing you inconvenience.
Your option 2 is almost correct, but those two tests cannot be quite like that.

First we should check if the contents of the a element match the correct text with or without spaces. So ' cat photos ' or 'cat photos ' or ' cat photos ' or 'cat photos' should all pass while 'foo bar' would not. Then we should check if the contents of the a element are exactly 'cat photos'. The tests have to be in order.
I found another challenge that deals with the same anchor and spacing issue. I'd like to try to come up with some regex myself for the tests. I'll add an additional comment with some ideas.
I was thinking a little something for the I mentioned right before the last test You should not have extra spaces around the .
Is this the correct way now? The link's text should be cat photos. You have either omitted the text or have a typo. NEXT TEST The link's text should be cat photos. You either have leading or ending whitespaces.
The second test doesn't need to be that complicated. It should match for the string literal without extra spaces.
yeah sorry I was too engrossed in learning regex xD You can check the second test I have updated it.
should I raise a PR then? or is this issue not open for PRs?
I think the actual implementation details of the tests are better suited in a PR. I will open this up to contribution. If other challenges need the same change we can collect them in this issue and make it more general. 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
I will repeat what I posted in the PR here as well. If we are really concerned about the anchor element content we shouldn't be lowercasing it or removing anything and we should use or and not . Something about this I didn't realize is the spacing inside only happens if the element is followed by outside text (which seems bizarre). and will always show the actual element content. We should replace jQuery for any test we see that is using it.

hey everyone i think that when it comes to whitespaces - the user includes whitespaces before or after or in both sides of the anchor text - if we want to ignore whitespaces i think a regex should just be included in the source code and replaces it with an empty string ''" like showed in a code earlier. So that wouldn't be a big issue later on. And about typos normally they shouldn't be allowed. Like if the user is supposed to type 'cat photos' and instead they type 'cat photo' that obviously shouldn't pass and they shouldn't be able to go to the next challenge until they enter the exact anchor text asked. Hope this was understandable.
I think we agreed above that we don't want to ignore the whitespaces
oh ok i get it
I did the last instruction to delete the entire anchor element below the p element and it passed.


Question: Вы можете внести свой вклад в интересующую вас область: <del> 1. [Внести вклад в этот открытый репозиторий.](#contribute-to-this-open-source-codebase) </del> <ins> 1. [Внести вклад в этот открытый репозиторий.](#внести-свой-вклад-в-этот-open-source-проект) </ins> Помогите нам в создании или редактировании [обучающих статей](https://www.freecodecamp.org/guide), [задач по программированию](https://www.freecodecamp.org/learn) или исправлении ошибок на нашей обучающей платформе.

Describe your problem and how to reproduce it: Anchor links such is not working properly in several languages. For sure is not working in: Russian, Spanish, Chinese languages. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: Version 74.0.3729.169 (Official Build) (64-bit) Operating System: Windows 10 Pro 1809 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !
These 3/4 PRs (exlude one - which I PR'd to my own forked-repo) may close this issue. Please review them.


Question: import React, { Fragment, Component } from 'react'; import PropTypes from 'prop-types'; import { <ins> HelpBlock, </ins> FormControl, FormGroup, ControlLabel

Describe the bug For field in , error state can not be triggered. Warning state will be triggered when an email address with incorrect domain is entered (for example: ). For all fields in , both error and success state can not be triggered. To Reproduce Steps to reproduce the behavior: to http://localhost:8000/settings to fill and to Describe the bug Expected behavior For field in , error state should be triggered instead of warning state. There should only be two states for an email address. Success state is when it is a valid and reachable email address. Error state is when it is an invalid and unreachable email address. For all fields in . Success state is when it is a valid and reachable URL. Error state is when it is an invalid and unreachable URL. Desktop (please complete the following information): OS: Windows 10 1809 Build .832 Browser Latest Chrome Version 77.0.3865.120 (Official Build) (64-bit)
Calling to discuss this from issue . What do you think about this? Are there anything to add or change from the Expected Behavior I described?
the only thing I'm not sure about is 'unreachable'. Do you just mean unreachable because the URL is malformed? Like , for example. If so, then I completely agree. cc
Yes of course. 'Unreachable' is only defined by malformed email format ( valid length, etc) and URL format (protocol, colon, double slash, etc). It is also possible to check the top level domain part against current existing TLD programatically. Other than that, for example checking real email address which is existing should be done by email confirmation / verification.


Question: The default properties of an `hr` element will make it appear as a thin light grey line. You can change the height of the line by specifying a value for the `height` property. <del> Change the height the `hr` element to be `3px`. </del> <ins> Change the height of the `hr` element to be `3px`. </ins> # --hints--

Hello all! There's a grammar error on Step 68 of Project 2 (CSS Cafe Menu) in the new RWB. It reads: "Change the height the hr element to be 3px." It should read: "Change the height of the hr element to be 3px." Instructions should read: "Change the height of the hr element to read to be 3px." <img width="616" alt="Grammar Error" src="https://user-"- Device: MacBook Pro OS: macOS Monterey v12.3.1 Browser: Safari Version: 15.4 (.1.17.1.13) 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: 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.


Question: }); } <del> if (!user.name) { </del> <ins> // If the user does not have a name, and have set their name to public, // warn them. Otherwise, fallback to username if (!user.name && user.showName) { </ins> return res.json({ messages: [ {

If there is no name set in the settings, doesn't matter if name is public or private, instead of falling back to username, it gives an error and certificate is not shown
I assume the best UX is for a note to appear, if the Camper tries to set to public, without having first set to something.
the error appears also if name is not set and set to private - certificate does not appear saying that one has to put a name (I'm adding this on top message too)
Picture !
The objective here then is to show the username on the certification if the name is not set ? Maybe some message then must warn the camper that his username will be shown on the certification instead of his real name (I am not sure though that a certification given to a weird username would be ok)
already if the name is private the username is shown, this issue appears if the name is not set
Apologies if this has nothing to do with you, but I vaguely remember you being involved in the discussion I cannot find: Was there any conclusion as to disabling the certification until a Camper has set their name, and made it public?
Sorry for the late response here - The only thing that comes to mind is
Either we would need to remove having usernames as a fallback , or having a public name requirements when displaying certs. I now it might be inconvenient, but I vote for removing the fallback for simplicity and keeping the public name as a requirement.
Discussing in issue triage meeting. a camper sets the to a non-empty string and , the certificate renders with the . .When a camper sets the to an empty string and either or , the certificate does not render and redirects to with a flash message. We should update the behaviour of to mirror the behaviour of , and avoid using the username field as a fallback entirely.
Hello Is this issue solved ?


Question: As a reminder, this project is being built upon the following starter project on [Repl.it](https://repl.it/github/freeCodeCamp/boilerplate-infosec), or cloned from [GitHub](https://github.com/freeCodeCamp/boilerplate-infosec/). <del> Hackers can exploit known vulnerabilities in Express/Node if they see that your site is powered by Express. X-Powered-By: Express is sent in every request coming from Express by default. The `helmet.hidePoweredBy()` middleware will remove the X-Powered-By header. You can also explicitly set the header to something else, to throw people off. e.g. `app.use(helmet.hidePoweredBy({ setTo: 'PHP 4.2.0' }))` </del> <ins> Hackers can exploit known vulnerabilities in Express/Node if they see that your site is powered by Express. `X-Powered-By: Express` is sent in every request coming from Express by default. Use the `helmet.hidePoweredBy()` middleware to remove the X-Powered-By header. </ins> # --hints--

<!-- 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: In the first Helmet challenge it is said that to hide the X-powered-By set by default in some servers, can help to avoid attacks. I'm not saying this isn't true, but this is an extract from Helmet: They have an interesting side note for express:
Hello there, Thank you, for taking the time to open this. I am not sure I understand what you are saying needs to happen/ be changed? The current boilerplate file has what you mentioned: The idea behind the lesson is not how to use Helmetjs for Express apps, but what security measures exist, and what do they do.
You're welcome. I'd just include or link to helmet npm at least, or include that paragraph, because it's not really useful for security, as far as I can see. I mean, the exercise is to include Feel free to close it if it doesn't really help, no problem. I've read the boilerplate, it was great to see that :+1:
Ok, after doing more searching into this, I agree there are two things we might benefit from doing: 1) With the version we have set to be installed and used, can take arguements, but version cannot. So, I would suggest a camper not use an option. I.e. remove 2) Add some information along the lines of:
Yes, that'd be great, I was puzzled by the option too, cause they don't include it in the home page at least. Also, 3.21.3 isn't passing the exercise (the first one), don't know if this is just me, or there is some other update to do. Oops, just found out we need to remove from
I dunno, I really don't see much of a problem here. The challenge says that "Hackers can exploit known vulnerabilities in Express/Node if they see that your site is powered by Express." So it doesn't really claim that it adds security, more that it throws people off. Certainly, a determined person could figure out what is powering the app, this just makes it a little harder.

Since the version of helmet we are using allows for the option to set the header, I don't mind leaving that in - I suppose removing would probably be better at this point - although, only slightly. It's certainly nice to update lessons when a package changes, but it's also difficult to keep things up to date. The method works with helmet v3 and v4 so I'm not sure why it's suggested to use that. One thing that does bother me here is that the boilerplate has the that pointed out. So if you want to actually see the header, you can't without removing that line no matter what method or options you use. My vote goes to just removing that line from the boilerplate. I actually don't mind making adjustments to this, but I don't think it's particularly necessary or that the current lesson is inaccurate. Part of my suggestion has to do with the translation effort taking place with the curriculum. When a lesson changes, we will need to start updating it in across all languages. So a minor fix like this becomes a significant effort. All that being said - if the consensus is to make some changes, I won't fight it. If we do end up changing it, I would say to switch to the method. Side note: the method that's used a few lessons after this was removed in helmet v4.
That's not true just initiate the app, you'll see the header. Indeed, they use app.disable(...) cause that's what they recommend in Helmet, which is another reason to leave that header out, mostly when most users are using express, and the exercise itself. (To see the header just include the route in , instead of ) My point is: you don't want people to learn a useless setting. Idk, seems to me the whole section is rather weak.


Question: "nameEs": "Dale a cada elemento un ID único", "descriptionEs": [ "También quisiéramos referirnos a cada botón por su id utilizando jQuery.",  "Dale a cada uno de tus botones un id único, comenzando con target1 y terminando con target6."   "Dale a cada uno de tus botones un id único, comenzando con target1 y terminando con target6.", "Asegúrate que target1 a target3 queden en #left-well, mientras que target4 a target6 queden en #right-well."  ] }, {

[ ] Use Responsive Design with Bootstrap Fluid Containers [ ] Make Images Mobile Responsive [ ] Center Text with Bootstrap [ ] Create a Bootstrap Button [ ] Create a Block Element Bootstrap Button [ ] Taste the Bootstrap Button Color Rainbow [ ] Call out Optional Actions with Button Info [ ] Warn your Users of a Dangerous Action [ ] Use the Bootstrap Grid to Put Elements Side By Side [ ] Ditch Custom CSS for Bootstrap [ ] Use Spans for Inline Elements [ ] Create a Custom Heading [ ] Add Font Awesome Icons to our Buttons [ ] Add Font Awesome Icons to all of our Buttons [ ] Responsively Style Radio Buttons [ ] Responsively Style Checkboxes [ ] Style Text Inputs as Form Controls [ ] Line up Form Elements Responsively with Bootstrap [ ] Create a Bootstrap Headline [ ] House our page within a Bootstrap Container Fluid Div [ ] Create a Bootstrap Row [ ] Split your Bootstrap Row [ ] Create Bootstrap Wells [ ] Add Elements within your Bootstrap Wells [ ] Apply the Default Bootstrap Button Style [ ] Create a Class to Target with jQuery Selectors [ ] Add ID Attributes to Bootstrap Elements [ ] Label Bootstrap Wells [ ] Give Each Element a Unique ID [ ] Label Bootstrap Buttons [ ] Use Comments to Clarify Code
Working on this one


Question: **Instructions:** Write a function `insertionSort` which takes an array of integers as input and returns an array of these integers in sorted order from least to greatest. <del> **Note:** We are calling this function from behind the scenes; the test array we are using is commented out in the editor. Try logging `array` to see your sorting algorithm in action! </del> # --hints-- `insertionSort` should be a function.

<!-- 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 description says there is not a commented out array there I wouldn't know how to change that other than deleting the paragraph entirely Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Google Chrome Browser Version: 87.0.4280.77 Operating System: iOS 14.1 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):
Description is wrong. Code placeholder was changed in - test array moved from comment to function call argument, but description stayed same without any edits.
This seems quite reasonable. I will open this up to first timers
An issue with the help wanted or first timers only label is open for contribution. The first comprehensive PR created will be reviewed and merged. 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
I would Like to contribute to your cause i am a first timer and have not yet worked in big project but i want to start by freecodecamp
thank you for wanting to contribute, this issue has already a linked PR. Take a look at other issues with label "first timers only" and "help wanted" that do not have already a linked PR


Question: color: var(--secondary-color); } <del> .fcc-modal .close { color: var(--secondary-color); opacity: 100%; </del> <ins> button.close { color: inherit; background-color: transparent; </ins> font-size: 28px; <ins> opacity: 0.5; </ins> text-shadow: none; } <ins> button.close:hover, button.close:focus { color: inherit; opacity: 1; background-color: transparent; } </ins> .modal-content { background-color: var(--secondary-background); border-radius: 0px;

When in a challenge, any of modals that popup (completion, ask for help, etc..), have a little close button at the top right that has recently become very hard to see... !
Also, when you hover over it, it gets obscured by the hover effect: !
Seems like there's an opacity issue... <img width="698" alt="Screen Shot 2019-11-26 at 8 11 42 AM" src="https://user-"Removing that 1% opacity makes it look like it did before, but I can't pinpoint where it's coming from in the code.
Production or local?
The hover effect is visible in production and they are also a little hard to see.
please investigate.
table for reference...
Thanks for the confirmation. The latest master is now (as of this comment) live on .dev, if you want to confirm this issue is fixed. If yes, I will proceed with the deployment to .org
I have pushed further to production and can confirm that the issue is reproducible on both staging and production applications.
I have bumped this to crit path.

Please see below. The text has been shifted around a bit in some aspect ratios. We need to ensure that the text on certifications looks right on all screen sizes: <img width="1149" alt="5freeCodeCamporgonTwitterWearetakingfreeCodeCampdownsowecandeploysomemajorchangesWewillbebacksoonInthemeantimeourYouTubeisupandithas1000codingtutorialsonPythonSQLDataScience_andMachine_Lea" src="https://user-"
Can I get steps to reproduce? I can't see this on my dev build with any screen size.
I can't reproduce this either. Although on one load of the above cert, I did get the date with a dark font color... <img width="877" alt="Screen Shot 2019-10-18 at 7 20 31 AM" src="https://user-"But I couldn't reproduce this a second time. Seems like maybe some of the intended css isn't getting applied intermittently or something.
hmm. it seems like a theme related issue. all colors in the certificate should come from :root {} in the
Since we're dealing with formatting and whitespace of certificates here, should we not center this to the page? !
Is it not already centered I'm not sure what you are referring to. So I think I figured out how to reproduce my issue. The date gets the dark font when you open a cert in a new tab or go to the URL through the address bar. But gets the correct font when you just open the cert in the current tab from the portfolio page. Can anyone else check this?
I’m referring to vertical centring. See the white gap between the end of the certificate and where the browser ends
I put in a pull request to center the certificates vertically on large screens. I can't reproduce your font color issue. New tab and navigating with URL both show the correct font color for me. I also can't reproduce the font offset in the first screenshot. So I don't think there is anything else that can be done on this issue unless someone can reproduce these.
I am not very sure as well, could be some specific device or viewport size. Will check with the OP to test this. Thanks for the PR.

The problems that pointed out: were not addressed in , so this should not have been closed.
Can anyone else reproduce that? or Quincy's issue? I can still reproduce mine on production, but not locally. Perhaps it has worked itself out on master.
I will have a build pushed to dev within the hour. Would you like your user record there for testing?
Sure
Okay let's do a before and after, I am have your user record to .dev, and will let you know again on this thread when I have pushed a build.
I can reproduce it on production. I haven't had chance to do locally, but my guess is you'll need to build the client to see it.
The changes have now landed in production as well. Can you check?
it's something to do with client-only routes. If you build the client and then use to serve it, you see the problem Tom found. For some reason you get a 404 for the cert route and it loads, but the gets and so the certificate renders incorrectly. Everything works as expected when using .
Hello - This may help debug the issue. I do not have this issue when viewing the certificate from my profile page - after clicking the "View Full Stack Certification" button. <img width="1377" alt="Screen Shot 2019-11-21 at 9 27 44 AM" src="https://user-"I do have this issue when viewing the certificate while visiting the url directly. <img width="1372" alt="Screen Shot 2019-11-21 at 9 31 17 AM" src="https://user-"
i think some general theme based color styles are over writing that element styles, in this case if this case if we make the styles more specific, and apply to it should work. !
It's not just the fonts. The page sizing is also getting messed up when visiting from an external link. If you come from somewhere other than fCC, you'll see scrollbars.
I could not reproduce this on mac and chrome 78.0.3904.108. could you give tell me about the browser and operating system you are using.
See scrollbar to the right when I open it externally ! None if opened directly from fCC ! Also, notice whitespace is different
Alright, since we've the donation request, this issue has been rendered moot


Question: {`Your `} {this.getFormatedAmountLabel(donationAmount)} {` donation will provide `} <del> {this.convertToTimeContributed(donationAmount, duration)} </del> <ins> {this.convertToTimeContributed(donationAmount)} </ins> {` of learning to people around the world`} {duration === 'onetime' ? `.` : ` each ${duration}.`} </p>

Currently the donate page always has the left-most value selected by default. Instead, we want the center value selected by default. For example, here we would want the 50 is selected by default): <img width="517" alt="Supportournonprofit_freeCodeCamp_org" src="https://user-"

At freeCodeCamp's current level of efficiency, every dollar donated to our nonprofit translates to 50 hours worth of learning. Both the One-time and Annual options have the correct amounts, but for some reason the monthly doesn't have the correct amount: $50 should be 25,000 hours: <img width="507" alt="SupportournonprofitfreeCodeCamporg" src="https://user-"$35 should be 1,750 hours: <img width="517" alt="SupportournonprofitfreeCodeCamporg" src="https://user-"$5 should be 250 hours: <img width="522" alt="Supportournonprofit_freeCodeCamp_org" src="https://user-"
~The hour is calculated for the month like we discussed? For example $5: ~ Edit: Never mind, I realised the issue. Will fix.


Question: } .monaco-menu .action-label { <del> color: rgb(var(--highlight-color)); </del> <ins> color: var(--highlight-color); </ins> letter-spacing: 0.02em; }

If I try to select text with my mouse so I can copy/paste it or something - the selected text has the same background as the rest of the page. Making it difficult to see what is selected, and frustrating to try and select, well anything. ! This seems to occur across the entire site. Perhaps it was intentional or something, but I don't think it's a good ux. Note: the text does actually get selected, so you can still copy/paste it. Tested on Chrome and Firefox
Good catch. It'll be this PR: which didn't scope the change to challenge descriptions. I'll put together a quick fix. Edit: nevermind, it's just that has to be passed four values, not two. I don't quite understand how this ever worked.


Question: Use the `filter` property to `blur` the painting by `2px` in the `.canvas` element. <ins> Here's an example of a rule that add a 3px `blur`: ```css p { filter: blur(3px); } ``` </ins> # --hints-- You should set the `filter` property to `blur(2px)`.

It would make more sense for step 34 to have the filter syntax example, instead of it showing up in the next step. Explain and show the syntax. 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]
Yes, that totally needs to be done what about step 35? there I think the example is to remind people how to give same rules to multiple selectors. Should that be removed? double blur example?
Not sure if we need a selector list example as long as the hint text shows the selector. But I would like for the hint text to actually specify it as a selector list.


Question: assert.match(code, /localStorage.setItem(("|')data1/) ``` <del> Your `localStorage.setItem()` should have a key of `myTaskArr`. </del> <ins> Your `localStorage.setItem()` should have a value of `myTaskArr`. </ins> ```js assert.match(code, /localStorage.setItem(("|')data1,s*myTaskArr);?/)

So the problem is that the “hint” where it tells you what you should’ve have coded it tells you that you should have “data” as key, when you code that and it doesn’t work it tells you you should have “myTaskArr” as key, but that’s wrong it should tell you “myTaskArr” as “value”. So I was trying to have 2 keys, and obviously it was always wrong. The hint should tell you that "myTaskArr" is a value, not a key as it currently says. ! Device: Desktop PC OS: Windows 10 Browser: Edge Version: [e.g. 22] 120.0.2210.121
Note: Due to PR adding one more step, earlier in this project, the relevant step in codebase is 49 now. Although that change did not yet reach the production at this time.


Question: return array; // Only change code above this line } <del> insertionSort([1, 4, 2, 8, 345, 123, 43, 32, 5643, 63, 123, 43, 2, 55, 1, 234, 92]); </del> ``` # --solutions--

The following challenges have an example function call in the seed code. These function calls should be removed and the related tests should be clarified to reflect the call instead. This sorting challenge is correct and could be used for reference.
Hi, nhcarrigan. I'd like to try to help and solve it. I'm still learning about the project so I would like to ask a question so I can understand the issue better. There is a function call in the file.. bubleSort([1,2,3....]) (example: implement-bubble-) ! And it should be removed from the seed section and transferred to here, similarly to implement-quick-sort: ! ! Is it correct or are there other files that I should be concerned about?
That is correct, yes - this same change should be completed on the four files I've linked. I would, however, recommend holding off on working on this until we receive additional consensus that this is the best way to proceed. If you run in to any questions, feel free to review our or ask in our or the .
Sounds great!! Thanks for the fast response. I will wait until further notice.
Hi MuriloMarquesSantos, are you still interested in fixing this issue?


Question: ```html <style type='text/scss'> <ins> #square { width: 50px; height: 50px; background-color: red; } #rect-a { width: 100px; height: 50px; background-color: blue; } </ins> <del> #awesome { width: 150px; height: 150px; background-color: green; } </del> <ins> #rect-b { width: 50px; height: 100px; background-color: orange; } </ins> </style> <del> <div id="awesome"></div> </del> <ins> <div id="square"></div> <div id="rect-a"></div> <div id="rect-b"></div> </ins> ``` # --solutions-- ```html <style type='text/scss'> <del> @mixin border-radius($radius) { -webkit-border-radius: $radius; -moz-border-radius: $radius; -ms-border-radius: $radius; border-radius: $radius; } #awesome { width: 150px; height: 150px; background-color: green; @include border-radius(15px); } </del> <ins> @mixin shape($w, $h, $bg-color) { width: $w; height: $h; background-color: $bg-color; } #square { @include shape(50px, 50px, red); } #rect-a { @include shape(100px, 50px, blue); } #rect-b { @include shape(50px, 100px, orange); } </ins> </style> <del> <div id="awesome"></div> </del> <ins> <div id="square"></div> <div id="rect-a"></div> <div id="rect-b"></div> </ins> ```

Currently, the instructions within the module happen to be as follows: Newer CSS features take time before they are fully adopted and ready to use in all browsers. As features are to browsers, CSS rules using them may need vendor prefixes. Consider : For the sake of clarity, the above instructions should also explicitly point out which bits within the given code snippet are vendor prefixes, instead of just simply mentioning the word vendor prefixes within the instructions and expecting the users to figure out themselves as in which parts within the given code snippet are vendor prefixes. The instructions within the module should be as follows: Newer CSS features take time before they are fully adopted and ready to use in all browsers. As features are to browsers, CSS rules using them may need vendor prefixes ( , , etc ). Consider the property below: <img width="522" alt="image" src="https://user-"- Device: Laptop OS: macOS 13.0.1 Browser: Google Chrome Version: 107.0.5304.110 Would love to get some feedback from other members before I proceed ahead with making a PR for this issue. Thanks !
I would be fine with it being more explicit. Not sure if it is really needed but it wouldn't hurt. As an aside, using vendor prefixing to teach Mixins isn't a bad idea but the challenge just hasn't aged well. New features are now hidden behind feature flags and the standards have moved away from vendor prefixing. The box-shadow example seems very outdated.
Hey thanks for sharing the article. After reading the article which you have shared, I can think of the following options: Get rid of vendor prefixing from this challenge ( since the main focus of this challenge is to educate the users about Mixins ) and create a separate challenge to teach users about vendor prefixing. Get rid of the property in this challenge and instead, use such a CSS property in the example, which requires vendor prefixing ( came across an that lists some CSS properties that require vendor prefixing as of 2021 ) Let me know what you think about it.
I wouldn't mind if this was rewritten but everything except parts of the challenge text would need to be changed (the challenge text, the example, the seed code, the requirements, the tests). Motivation for rewriting the challenge: challenge is introducing an unnecessary topic of vendor prefixing. information about vendor prefixing is out of date.

Suggestion: Give a simple example in the challenge text. The mixin will take a font size and a bottom margin, it will reset all other margins. Seed code, in plain CSS to help make the challenge less copy-pasty. Solution/requirements
Thanks for the suggestion I'm happy to work on this issue. I will make a PR for this issue shortly, cheers !
You may want to wait with the PR until we get more consensus. You can start working on it but I can't guarantee that it will be approved if others disagree with the change.
Thanks for letting me know if that's the case, then I will wait and see what others think about the suggested change.
Let's go ahead and open this up, following lasjorg's suggestion above to rewrite the challenge. The entire front-end libraries certification is pretty outdated, and next on our roadmap for a complete overhaul. But this is a pretty low-hanging fruit to hit now.
Hi there, first of all I just want to thank you for the opportunity. This is my first time contributing and I decided to have a go at this issue and this is my attempt: As per suggestions, I removed any references to vendor prefixing as they are unnecessary and outdated. In this rewrite, I kept the general structure of the challenge text but modified to suit the new example code. However, I didn't use the example given by as I think it'll be better to build on the previous challenges. So I did my own simple example about individual styles on headings, which is covered in previous challenges. As for the task itself, I used suggestion with some add-ons. Tagging for visibility. Thank you! :)
Please open a pull request if you'd like your changes reviewed.
Oh right, I have opened a pull request however, I haven't tested the new code at all. Could someone point me to a guide on how to do that?
Hi, I've opened a new PR because I messed up my commit history and the previous PR got closed. Very sorry for the inconveniences, please let me know if there's anything I need to fix. Thank you!


Question: A pyramid generator is a program where you can set the type of character, the count for the pyramid, and the direction of the pyramid. The program will then generate a pyramid based on those inputs. <del> Click on the `"Check your code"` button to proceed to the next step and start the project. </del> <ins> Click on the "Check your code" button to proceed to the next step and start the project. </ins> # --hints--

There are some small issues that need to be fixed in the following files: optionfor elementsinline"Check your code" String` This looks like something that can be fixed by "first-time" code contributors to this repository. The files you should look at to work on a fix are those linked 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.
Hi I'd like to work on this issue. Thanks
Hey 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.


Question:
"Las funciones que aceptan argumentos deben aceptar sólo uno, y este tiene que ser una cadena.", "Estos métodos deben ser el único medio para interactuar con el objeto.", "Recuerda utilizar Leer-Buscar-Preguntar si te sientes atascado. Intenta programar en pareja. Escribe tu propio código."  ], "titleIt": "Crea una Persona", "descriptionIt": [ "Completa il costruttore dell'oggetto con i metodi specificati qui sotto:", "
getFirstName()ngetLastName()ngetFullName()nsetFirstName(first)nsetLastName(last)nsetFullName(firstAndLast)
", "Esegui i test per vedere il risultato atteso per ogni metodo.", "I metodi che richiedono un argomento devono accettarne solo uno e questo deve essere una stringa.", "Questi metodi devono essere l'unica maniera possibile di interagire con l'oggetto.", "Ricorda di usare Leggi-Cerca-Chiedi se rimani bloccato. Prova a programmare in coppia. Scrivi il codice da te."  ] }, {

Advanced Algorithm Scripting () Translate the challenge Advanced Algorithm Scripting in Italian
I'll be working on this


Question: } test.add(4); test.add(1); <ins> test.add(1); </ins> test.add(7); test.add(87); test.add(34);

When adding a new node ( or element ) to a binary search tree, I was supposed to compare the value supplied method with that of current node. But it seems odd to me that, despite not doing it at all, the testing script somehow ignored it. Here's the code I wrote I expect the unit test case to fail instead of to succeed. Also, if I slightly edit this LOC here: to Then I expect the said unit test case to pass. No response Device: Dell Latitude 5580 OS: Ubuntu 22.04 Browser: Brave Browser Version: 1.45.127 No response
is taking a look and this and will create a PR if a fix is identified.
The reason the "The add method should add elements according to the binary search tree rules." test passes is because the test does not test for adding duplicate keys. I've a pr that changes the test so it adds a duplicate key, and the solution in the docs still works. The code you wrote now fails (correctly). Your intended fix of changing to does not work, as if cr[direction] is null, you can't get its .value


Question: padding: 0; } <del> .sidebar ul li a { </del> <ins> .sidebar ul li a, .search a { </ins> color: var(--quaternary-color); } <del> .sidebar ul li > a:hover { </del> <ins> .sidebar ul li > a:hover, .search a:hover { </ins> color: var(--primary-color); }

Describe the bug if you type something in searchbar while using the dark mode, and hover over the produced links, it will hide the link. To Reproduce Steps to reproduce the behavior: to '' something over it how the hover is hiding the result Screenshots ! Browser: chrome
Can you please assign this to me
Hi I've been looking into the issue you reported regarding dark mode and hover behavior on the search results. I'd like to contribute a fix, but I'm having trouble locating the exact code or files that need modification. Could you please provide more specific details about the file or code that's related to this issue? A direct link to the relevant code or even just the file path would be immensely helpful. Your guidance would ensure that I'm making the correct changes to address this problem effectively. Thank you!


Question: assert.match(code, /consts+updates*=s*(?:(s*events*)|event)s*=>s*{s*consts+elements*=s*event.targets*;?s*consts+values*=s*element.value.replace(s*/s/gs*,s*('|"|`)1s*)s*;?s*ifs*(/); ``` <del> Your `if` condition should check if `value` includes the `id` of the `element`. </del> <ins> Your `if` condition should check that `value` does not include the `id` of the `element`. </ins> ```js assert.match(code, /consts+updates*=s*(?:(s*events*)|event)s*=>s*{s*consts+elements*=s*event.targets*;?s*consts+values*=s*element.value.replace(s*/s/gs*,s*('|"|`)1s*)s*;?s*ifs*(s*!value.includes(s*element.ids*)/);

The wording of the hint text does not match the instructions. The word not is missing from the hint. js (code, /consts+updates=s(?:(sevents))1s)s;?sifs(/); Your condition should check if includes the of the . Your condition should check if does not include the of the . ! NA No response
For some more context, the challenge is expecting , but if you input something like this: (no ), the hint is ifvalueidelement It should check that it does not include the id. So we can change the hint to the suggestion - I would change to though: ifvalueid.`` What do you think
Your condition should check that does not include the of the element. Sounds good.
Sounds like there is a conclusion for what to change the hint to, so I am opening this for contributions


Question: "challengeType": 0, "nameEs": "Crea un encabezado personalizado", "descriptionEs": [  "Crearemos un encabezado simple para nuestra aplicación de fotos de gatos poniéndolos en la misma línea.",   "Crearemos un encabezado simple para nuestra aplicación de fotos de gatos poniendo el título y la relajante imagen del gato en la misma línea.",  "Recuerda, Bootstrap usa un sistema de cuadrícula adaptativo, el cual facilita poner elementos en filas y especificar el ancho relativo de cada elemento. La mayoría de las clases de Bootstrap pueden aplicarse a un elemento div.", "Aquí hay un diagrama del funcionamiento de la cuadrícula de 12 columnas Bootstrap:", "",

[ ] Use Responsive Design with Bootstrap Fluid Containers [ ] Make Images Mobile Responsive [ ] Center Text with Bootstrap [ ] Create a Bootstrap Button [ ] Create a Block Element Bootstrap Button [ ] Taste the Bootstrap Button Color Rainbow [ ] Call out Optional Actions with Button Info [ ] Warn your Users of a Dangerous Action [ ] Use the Bootstrap Grid to Put Elements Side By Side [ ] Ditch Custom CSS for Bootstrap [ ] Use Spans for Inline Elements [ ] Create a Custom Heading [ ] Add Font Awesome Icons to our Buttons [ ] Add Font Awesome Icons to all of our Buttons [ ] Responsively Style Radio Buttons [ ] Responsively Style Checkboxes [ ] Style Text Inputs as Form Controls [ ] Line up Form Elements Responsively with Bootstrap [ ] Create a Bootstrap Headline [ ] House our page within a Bootstrap Container Fluid Div [ ] Create a Bootstrap Row [ ] Split your Bootstrap Row [ ] Create Bootstrap Wells [ ] Add Elements within your Bootstrap Wells [ ] Apply the Default Bootstrap Button Style [ ] Create a Class to Target with jQuery Selectors [ ] Add ID Attributes to Bootstrap Elements [ ] Label Bootstrap Wells [ ] Give Each Element a Unique ID [ ] Label Bootstrap Buttons [ ] Use Comments to Clarify Code
Working on this one