jiebi/CodeConvo huggingface dataset:
Change:
Describe the bug When you open a dropdown for any of the certificate, if the subtopic has 3 digit number of challenges it gets pushed to the next line. I think that it would be better if kept in same line. Screenshots ! !

Discussion:
.map-title-completed { margin-left: auto; <del> width: 90px; </del> <ins> width: 100px; </ins> padding-left: 20px; }
Change:
!
Could you give a link to the page as then it might be easier to solve the issue?
This should be the case on the user's profile page. You can reproduce by setting the certificate keys to true in the user object.
I could work on this!
I am already working on it.
Thanks for letting me know!
a reasonable fix would be to give the grid that contains the profile a class and on the css, change the button under that class and have . you will end up with something like this. here it is on small and large screens <img width="681" alt="screen shot 2019-02-22 at 2 18 10 pm" src="https://user-"<img width="1095" alt="screen shot 2019-02-22 at 2 17 53 pm" src="https://user-"
Similar solution could be applied to these donate buttons probably. but the selectors should be very specific not to change the styling on other buttons in the platform. <img width="669" alt="screen shot 2019-02-23 at 2 09 14 pm" src="https://user-"<img width="502" alt="screen shot 2019-02-23 at 2 08 51 pm" src="https://user-"
Hey or Can you take this up? just updated us that he will be a bit busy with other things.
I'm on it

Discussion:
.donation-form { display: flex; flex-direction: column; <del> width:80%; </del> <ins> width: 80%; </ins> justify-content: center; margin: 0 auto; }

font-weight: normal; } <ins> .donation-form .btn { white-space: normal; } </ins> .modal-close-btn-container { display: flex; justify-content: center;

.StripeElement--focus { border-color: #66afe9; outline: 0; <del> box-shadow: inset 0 1px 1px rgba(0,0,0,.075), 0 0 8px rgba(102, 175, 233, 0.6); </del> <ins> box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 8px rgba(102, 175, 233, 0.6); </ins> }

import { userByNameSelector } from '../../../redux'; import FullWidthRow from '../../helpers/FullWidthRow'; import { ButtonSpacer, Spacer } from '../../helpers'; <ins> import './certifications.css'; </ins> const mapStateToProps = (state, props) => createSelector(

return cert.show ? ( <Fragment key={cert.title}> <Row> <del> <Col sm={10} smPush={1}> </del> <ins> <Col className='certifications' sm={10} smPush={1}> </ins> <Link to={`/certification/${username}/${cert.showURL}`}> <Button block={true}

}) { const renderCertShowWithUsername = curry(renderCertShow)(username); return ( <del> <FullWidthRow> </del> <ins> <FullWidthRow className='certifications'> </ins> <h2 className='text-center'>freeCodeCamp Certifications</h2> <br /> {hasModernCert ? (

<ins> .certifications .btn { white-space: normal; } </ins>
Change:
the text is touching the edges of the screen when the screen is between 650 and 750 pixels. Probably needs to wrapped in a grid container but not sure. <img width="706" alt="screen shot 2019-02-19 at 9 10 15 am" src="https://user-"
I have created PR to fix this. There was a media query that sets padding for small sizes (<630px device width). So I just padding for larger devices.

Discussion:
align-items: center; max-width: 960px; margin: 0 auto; <ins> padding: 0 20px; </ins> } @media screen and (max-width: 630px) { .learn-page-wrapper { <del> padding: 0 25px; </del> <ins> padding: 0 15px; </ins> } }
Change:
I think the video for this challenge should be updated. It does not show the proper nesting of both the p elements inside the main element. It also has one error as one of the p elements are not closed properly.
Any comments?
Agreed with lasjorg, In this exercise a new paragraph should be below the first, with a main tag then to wrap around both paragraphs. In the video, the main tag is around the newly second paragraph only, plus the newly paragraph has an opening p tag at the end instead of a closing p tag. For contrast, the very next video has the main and paragraph tags the way they should be. Discovered this error when my daughter ran into difficulty with this exercise, and when she watched the video became even more confused.
Any thoughts?
I will redo that video.

Discussion:
id: bad87fee1348bd9aecf08801 title: Introduction to HTML5 Elements challengeType: 0 <del> videoUrl: 'https://scrimba.com/p/pVMPUv/c4Ep9Am' </del> <ins> videoUrl: 'https://scrimba.com/p/pVMPUv/cBkZGpt7' </ins> --- ## Description
Change:
<!-- 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 challenge i found an error. single qoute symbol is wrong in guide section. symbol of single qoute should be this (') but it is showing this ("). Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: chrome Browser Version: 71.0.3578.98 (Official Build) (64-bit) Operating System: ubuntu 18.04 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !
Good catch! I recommend changing the current line 9 in to the following: which will then display as the following: JavaScript allows the use of both single (<code'</code) and double (<code"</code) quotes to declare a string. Deciding which one to use generally comes down to personal preference, with some exceptions.

Discussion:
## Description <section id='description'> <del> JavaScript allows the use of both single ('') and double ("") quotes to declare a string. Deciding which one to use generally comes down to personal preference, with some exceptions. </del> <ins> JavaScript allows the use of both single (<code>'</code>) and double (<code>"</code>) quotes to declare a string. Deciding which one to use generally comes down to personal preference, with some exceptions. </ins> Having two choices is great when a string has contractions or another piece of text that's in quotes. Just be careful that you don't close the string too early, which causes a syntax error. Here are some examples of mixing quotes: <blockquote>// These are correct:<br>const grouchoContraction = "I've had a perfectly wonderful evening, but this wasn't it.";<br>const quoteInString = "Groucho Marx once said 'Quote me as saying I was mis-quoted.'";<br>// This is incorrect:<br>const uhOhGroucho = 'I've had a perfectly wonderful evening, but this wasn't it.';</blockquote>
Change:
Please consider adding the to It's a useful, open-sourced Angular CRUD application starter with NgRx state management and Firebase backend.
- please feel free to submit a Pull Request with the content you would like to have . If you have questions or concerns regarding a Pull Request, please feel free to drop by the I have the help wanted label as well in case anyone else is interested.
Adding the label. This looks like a good first PR for a new contributor.
Hi. I am new to this. Can I take this on?
Thanks, ;) of course, you can take this on
I stil do not see it here:
We still haven’t deployed the current master to production. It will be done shortly

Discussion:
*   <a href='https://angular.io/' target='_blank' rel='nofollow'>Angular</a> - The Angular Homepage *   <a href='https://angular.io/guide/styleguide' target='_blank' rel='nofollow'>Angular Style Guide</a> - Detailed best practices for Angular Development *   <a href='https://material.angular.io/' target='_blank' rel='nofollow'>Angular Material</a> - Excellent UI Framework that was built for Angular <ins> * <a href='https://github.com/mdbootstrap/Angular-Bootstrap-Boilerplate' target='_blank' rel='nofollow'>Angular Bootstrap Boilerplate</a> - Free, responsive CRUD application starter with NgRx state management, Firebase backend and material design </ins> ### Specific-topic Pages
Change:
This PR () a new challenge so we need to create the associated guide article in this area of the code: you expressed interest in this - not sure if you started working on it yet. Let us know if you want to do it or not, or if you need any help. If you don't want to actually write the article you could just create the file and place the "stub text" in it.
I will give it a go.
How do I preview the guide locally? I get a 404 on all guides when I try to view them locally.
You will temporarily need to copy to and then run . Just make sure not to commit any of the files you add to the mock-guide.
Thanks for the info. Should the guide instructions not have this information? I don't think I saw this mentioned anywhere.
Probably should be in the instructions.

Discussion:
<ins> --- title: Use the value attribute with Radio Buttons and Checkboxes --- ## Use the value attribute with Radio Buttons and Checkboxes To pass the challenge, add the `value` attribute to the `input` elements of type `checkbox` and `radio`. Use the `input` label text, in lowercase, as the value for the attribute. The `value` attribute will make sure the choices are identifiable when the form is submitted. Example form with value attributes: ```html <form action="/submit-sandwich"> <label><input type="radio" name="bread" value="wheat"> Wheat</label> <label><input type="radio" name="bread" value="ciabatta"> Ciabatta</label><br> <label><input type="checkbox" name="fillings" value="chicken"> Chicken</label> <label><input type="checkbox" name="fillings" value="tuna"> Tuna</label> <label><input type="checkbox" name="fillings" value="mayo"> Mayo</label><br> <textarea placeholder="Allergies, and extra information"></textarea><br> <button type="submit">Order Sandwich</button> </form> ``` </ins>  No newline at end of file
Change:
Describe your problem and how to reproduce it: For , the correct answer should be something like: But this code will also pass all the tests, even when it is incorrect: This can be solved by simply changing the order of the variables in the second test, so that is at index 0, thus disabling the incorrect answer, like this I'd be glad to contribute and fix this myself if the issue is confirmed and the solution approved. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: 73.0.3683.86 (Official Build) (64-bit) Operating System: macOS Sierra v10.12.5 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): Here's a screenshot taken after running all the tests. As you can see, all the tests passed, even when the answer is incorrect. !
Can I work on this?
Good catch! I can confirm the current tests do not test all the cases. I am fine with you implementing the change you suggest on a PR.
Since already offered to fix on a PR, I will leave it up to him to decide if he wants to move forward with the PR or is OK letting you create the PR.
Sorry. I was not aware of his PR. I will leave it up to him to decode.
Thanks for the confirmation! Actually this would be my first contribution, so I would really like to give it a shot. But if I run into problems, I'll let you know so you can contribute as well :)
No worries. Feel free to ping me if you run into problems. Happy contributing!

Discussion:
tests: - text: <code>quickCheck(["squash", "onions", "shallots"], "mushrooms")</code> should return <code>false</code> testString: assert.strictEqual(quickCheck(['squash', 'onions', 'shallots'], 'mushrooms'), false, '<code>quickCheck(["squash", "onions", "shallots"], "mushrooms")</code> should return <code>false</code>'); <del> - text: <code>quickCheck(["squash", "onions", "shallots"], "onions")</code> should return <code>true</code> testString: assert.strictEqual(quickCheck(['squash', 'onions', 'shallots'], 'onions'), true, '<code>quickCheck(["squash", "onions", "shallots"], "onions")</code> should return <code>true</code>'); </del> <ins> - text: <code>quickCheck(["onions", "squash", "shallots"], "onions")</code> should return <code>true</code> testString: assert.strictEqual(quickCheck(['onions', 'squash', 'shallots'], 'onions'), true, '<code>quickCheck(["onions", "squash", "shallots"], "onions")</code> should return <code>true</code>'); </ins> - text: <code>quickCheck([3, 5, 9, 125, 45, 2], 125)</code> should return <code>true</code> testString: assert.strictEqual(quickCheck([3, 5, 9, 125, 45, 2], 125), true, '<code>quickCheck([3, 5, 9, 125, 45, 2], 125)</code> should return <code>true</code>'); - text: <code>quickCheck([true, false, false], undefined)</code> should return <code>false</code>
Change:
Describe your problem and how to reproduce it: There is no link mentioned for Regex Resources in the Spinal Tap Case Guide Article. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: 73.0.3683.103 Operating System: Windows 10
Hi I have created a PR that should close this issue. Please reference PR

Discussion:
#### Relevant Links *   <a href='https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String' target='_blank' rel='nofollow'>String global object</a> <del> *   <a>JS Regex Resources</a> </del> <ins> *   <a href='https://guide.freecodecamp.org/javascript/regular-expressions-reference/' target='_blank' rel='nofollow'>JS Regex Resources</a> </ins> *   <a href='http://forum.freecodecamp.com/t/javascript-string-prototype-replace/15942' target='_blank' rel='nofollow'>JS String Prototype Replace</a> *   <a href='http://forum.freecodecamp.com/t/javascript-string-prototype-tolowercase/15948' target='_blank' rel='nofollow'>JS String Prototype ToLowerCase</a>
Change:
I had some style issues on my firefox browser from the "Dark Mode" extension/add-on. Specifically these two issues: - After some frustration and help I found the add-on to be the problem. I'm not sure if there's anything that can be done to avoid issues like this, but I figured it could be discussed a little bit.
It would be tricky to come up with a generic solution, since it depends on the behaviour of each extension. For example, we could stop 's problem, passing with only the seed code, by adding a filter like this: That would fix the issue, but relies on an implementation detail of the extension. I guess we could solve them on a case-by-case basis, but it might be better to put a warning somewhere. Perhaps something that pops up when tests fail?
A warning might be the only way to go - adding tests on a case by case basis just isn't practical - browsers vary and change - extensions change and there's a ton of them. I'm a little concerned with a warning on the pop-up as well - it might make users start looking for problems with an extension when their code is the problem.
That's a good point. Maybe just a suggestion to turn them off at the start of the curriculum, then.
I really don't see a good spot for a warning like that - I remember a notice at one point to use chrome for the best experience, but I'm not sure where it is anymore - next to that might have been a good spot - or perhaps - I don't think too many people are having issue with this so we can probably just leave it alone.
Putting something on the support page could work. How about something like: #### I cannot pass a challenge, but I think my code is correct Some browser extensions can interfere with challenge tests. If you are using any, try disabling them and run the tests again. If the problem remains, click the challenge's 'Ask for Help' button to post on the forum. You will need to create a forum account if you don't already have one.
That actually sounds pretty good
Cool, I'll pop that in a PR.

Discussion:
</Link> . </p> <ins> <h4>I cannot pass a challenge, but I think my code is correct</h4> <p> Some browser extensions can interfere with challenge tests. If you are using any, try disabling them and running the tests again. If the problem remains, click the challenge's 'Ask for Help' button to post on the forum. You will need to create a forum account if you don't already have one. </p> </ins> <h4>I have a support question that isn't answered here.</h4> <p> You can ask for help on our forum, and the freeCodeCamp volunteer
Change:
There's a period on its own paragraph on the home page... ! Here's where the issue lies... Perhaps adding the period in the tag

Discussion:
<Link className='large-p underlined-link' external={true} to='/donate'> make a tax-deductible donation here </Link> <ins> . </ins> </p> <del> .<Spacer /> </del> <ins> <Spacer /> </ins> <BigCallToAction /> <Spacer /> <Spacer />
Change:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: The test case is passed though I have not the s tag around the word Google in the h4 tag, it is counting the s tag around Google word in the p tag as valid. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Google Chrome Browser Version: Version 74.0.3729.131 (Official Build) (64-bit) Operating System: Windows 10 64-bit If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !
Thank you for reporting this bug. I can confirm it needed to be fixed and I have created a pull request () which should resolve the issue.

Discussion:
```yml tests: - text: Your code should add one <code>s</code> tag to the markup. <del> testString: assert($('s').length == 1, 'Your code should add one <code>s</code> tag to the markup.'); </del> <ins> testString: assert($('s').length == 1); </ins> - text: A <code>s</code> tag should wrap around the Google text in the <code>h4</code> tag. It should not contain the word Alphabet. <del> testString: assert($('s').text().match(/Google/gi) && !$('s').text().match(/Alphabet/gi), 'A <code>s</code> tag should wrap around the Google text in the <code>h4</code> tag. It should not contain the word Alphabet.'); </del> <ins> testString: assert($('h4 > s').text().match(/Google/gi) && !$('h4 > s').text().match(/Alphabet/gi)); </ins> - text: Include the word Alphabet in the <code>h4</code> tag, without strikethrough formatting. <del> testString: assert($('h4').html().match(/Alphabet/gi), 'Include the word Alphabet in the <code>h4</code> tag, without strikethrough formatting.'); </del> <ins> testString: assert($('h4').html().match(/Alphabet/gi)); </ins> ```
Change:
I noticed this while looking at another issue. Glitch is giving me an error when using version "1.0" in my file. It only seems to work when I use a third number: "1.0.0" - I'm not sure if this has always been the case since I don't think it threw this error in the past. But suggests to use a two digit version. It should probably be changed if this isn't allowed. EDIT: actually the project will still run with the invalid version - I thought it was causing the project not to run. But glitch does still give an error about it.
made a PR :+1:

Discussion:
A <code>version</code> is one of the required fields of your package.json file. This field describes the current version of your project. Here's an example: ```json <del> "version": "1.2", </del> <ins> "version": "1.2.0", </ins> ``` </section>
Change:
<!-- 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: At the moment, the clickable area of footer links are spanning the full width of their parent div. I'm not sure if this is on purpose, but IMHO, they should fit to their content instead, since a user could get navigated to another page if they accidentally click somewhere within the clickable area. This issue is on , but it is down for maintenance at the moment. The screenshot is of my local fCC. !
Is that actually a problem, though? I think having list items spread like that is pretty common. It could be a problem if you aimed for, say, Learn and got News, but there's a reasonable amount of space between them. How about if the box were subtly highlighted on hover?
Thanks for the threads
Tbh, this is the first time I have seen footer items spread like that, though it is common to me to see that on a navbar. I have no problem with leaving it as is, but adding background color on hover would be great.
I, personally, would prefer if only the text was clickable - but it works either way.
Personally I like the wider boxes, because I'm lazy and click in the general vicinity of things. So, I've a PR for the highlight approach, since that was a really easy fix. If that doesn't seem right we can always shrink the links onto the text.

Discussion:
.footer .col-header { padding-bottom: 5px; <ins> padding-left: 5px; </ins> font-weight: bold; } .footer a:not([class*='inline']) { display: block; <ins> padding-left: 5px } .footer a:hover { outline-offset: 1px; outline: 1px dashed #A0A0A0; background-color: #ffbe41; </ins> } .night .footer {

.night .footer a:hover { color: #606f7b; <ins> outline-offset: 1px; outline: 1px dashed #A0A0A0; </ins> }

.night .landing-page #top-right-nav li > a, .night #top-right-nav li > span { color: #fff; } <ins> .night .landing-page a { color: #006400; } .night .landing-page a:hover { color: #001800; } </ins> /* End night mode override */ .black-text {
Change:
Following the conventions decided upon in , we should change the instruction in the "Remove Elements from a Linked List" challenge - to Add a Link to the page with the problem: The file to be changed is . Since this is a simple change, we would welcome Pull Requests from first time contributors.
I can do it. Should i make the same change in the portuguese version too?
No, just make the change for the English version.

Discussion:
## Instructions <section id='instructions'> Write a <code>remove</code> method that takes an element and removes it from the linked list. <del> Note The <code>length</code> of the list should decrease by one every time an element is removed from the linked list. </del> <ins> <strong>Note:</strong> The <code>length</code> of the list should decrease by one every time an element is removed from the linked list. </ins> </section> ## Tests
Change:
Describe your problem and how to reproduce it: When you try to change contibution guidelines language - you'll see how the languages table's order is desynchronized and in several languages you cannot find new Greek language. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: Version 74.0.3729.169 (Official Build) (64-bit) Operating System: Windows 10 Pro 1809 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !

Discussion:
<table> <tr> <ins> <!-- Do not translate this table --> </ins> <td> Read these guidelines in </td> <td><a href="/CONTRIBUTING.md"> English </a></td> <del> <td><a href="/docs/chinese/CONTRIBUTING.md"> 中文 </a></td> <td><a href="/docs/russian/CONTRIBUTING.md"> русский </a></td> </del> <td><a href="/docs/arabic/CONTRIBUTING.md"> عربي </a></td> <del> <td><a href="/docs/spanish/CONTRIBUTING.md"> Español </a></td> </del> <ins> <td><a href="/docs/chinese/CONTRIBUTING.md"> 中文 </a></td> </ins> <td><a href="/docs/portuguese/CONTRIBUTING.md"> Português </a></td> <ins> <td><a href="/docs/russian/CONTRIBUTING.md"> Русский </a></td> <td><a href="/docs/spanish/CONTRIBUTING.md"> Español </a></td> <td><a href="/docs/greek/CONTRIBUTING.md"> Ελληνικά </a></td> </ins> </tr> </table>