jiebi/CodeConvo huggingface dataset:
Change:
as ieahleen mentioned in Crowdin, there are multiple files with typos in them. they say These hints should be changed to because they are testing if there is a single self-closing 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.

Discussion:
assert($('head').length === 1); ``` <del> You should have a one a self-closing `link` element. </del> <ins> You should have one self-closing `link` element. </ins> ```js const link = document.querySelectorAll('link');

# --hints-- <del> You should have a one a self-closing `link` element. </del> <ins> You should have one self-closing `link` element. </ins> ```js assert(document.querySelectorAll('link').length === 1);

assert.match(code, /<link/) ``` <del> You should have a one a self-closing `link` element. </del> <ins> You should have one self-closing `link` element. </ins> ```js assert(document.querySelectorAll('link').length === 1);

assert.equal(heads?.length, 1); ``` <del> You should have a one a self-closing `link` element. </del> <ins> You should have one self-closing `link` element. </ins> ```js assert(document.querySelectorAll('link').length === 1);
Change:
In step 36 of catAppPhoto project, the hint in line 33 missing code block This should be changed to Here is the markdown file Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first. Happy contributing.

Discussion:
assert([...document.querySelector('form').attributes].length < 2); ``` <del> You should create an input element. Check the syntax. </del> <ins> You should create an `input` element. Check the syntax. </ins> ```js assert(document.querySelector('input'));
Change:
In step 18 of building a skyline project, there is a text that go against This should be deleted Here is the markdown file Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first. Happy contributing.
Hi , I would like to work on this issue. Could you assign it to me ?
Hi thanks for taking interest in it. Feel free to open pull request after you have read the guide, we have stopped assigning people unless they are an old contributor.

Discussion:
# --description-- <del> Your first building looks pretty good now. Let's make some more! Nest three new `div` elements in the `background-buildings` container and give them the classes of `bb2`, `bb3`, and `bb4` in that order. These will be three more buildings for the background. </del> <ins> Your first building looks pretty good now. Nest three new `div` elements in the `background-buildings` container and give them the classes of `bb2`, `bb3`, and `bb4` in that order. These will be three more buildings for the background. </ins> # --hints--
Change:
In the "Learn CSS Colors by Building a Set of Colored Markers" project, the step 12 description reads: Notice that your marker doesn't seem to have any color. The background color was actually applied, but since the marker div element is empty, it doesn't have any width or height by default. The div doesn't have any height by default, but as it's a block-level element it spans the entire width of the containing element (body). N/A N/A No response N/A No response
As not a native english speaker, I am confused. Can you provide more details, and an alternative you think will fit the current step?
I agree, it should only be height, not width. As you pointed out the element does have a width.
Suggested change, remove the "width or" from the sentence.
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: Change to make: the . Explanation: the div being a block element spans the width of the entire page, as such it is wrong information that should be removed. It is correct to say that it doesn't have an heigth. Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
This is my first "real" contribution to open source (let alone to FCC), so although it is a pretty insignificant one, feel free to provide me with any feedback and/or constructive criticism please!

Discussion:
# --description-- <del> Notice that your marker doesn't seem to have any color. The background color was actually applied, but since the marker `div` element is empty, it doesn't have any width or height by default. </del> <ins> Notice that your marker doesn't seem to have any color. The background color was actually applied, but since the marker `div` element is empty, it doesn't have any height by default. </ins> In your `.marker` CSS rule, set the `width` property to `200px` and the `height` property to `25px`.
Change:
If the user adds the new tag on the same line as the first tag then the test will fail. The hint will tell the user that they should have two tags, which they do. As soon as the new tag is moved to a new line then the test will pass. If we want to require that new tag be on a separate line then we should mention this in the instructions or give a hint that tells the user it must be on its own line. Otherwise we should update the test to stop checking for this. No response Confirmed in both Firefox and Chrome. No response
Thanks for opening this issue. This looks something that can be fixed by "first time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: Changes to make: You will need to change this test: The regex needs to become . Explanation: the matches everything but line breaks, so the pattern with matches all the line up to the , in case of two meta tags on the same line, it matches both of them at once. Adding the in front of makes it a lazy matching, meaning it will match as little as possible while satisfying the pattern, and if the two meta tags are on the same line it will end the match at the first . Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.

Discussion:
Your code should have two `meta` elements. ```js <del> assert(code.match(/<meta.*/?>/g).length === 2); </del> <ins> assert(code.match(/<meta.*?/?>/g).length === 2); </ins> ``` Your `meta` element should have a `name` attribute with a value of `viewport`.
Change:
The test should allow that flexbox is only set inside a media query. As the test is written right now it doesn't seem possible. I didn't actually try logging out what the test is accessing. But I would assume from looking at the code that if the selector is inside a media query won't be what is expected. Forum: Allow flexbox to be set inside a media query. 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
Hi I've been looking to this issue and been able to solve it by iterating the rules if it's instanceof CSSMediaRule like the following: I know it's not efficient because media rules can be nested in others and I don't catch this cases, any suggestions how to parse the data in more efficient way? Thanks!
Is this issue still open?
feel free to open a PR if you think you can fix the issue

Discussion:
Your Product Landing Page should use CSS Flexbox at least once. ```js <ins> const hasFlex = (rule) => ["flex", "inline-flex"].includes(rule.style?.display) </ins> const stylesheet = new __helpers.CSSHelp(document).getStyleSheet() const cssRules = new __helpers.CSSHelp(document).styleSheetToCssRulesArray(stylesheet) <del> const usesFlex = cssRules.find(rule => { return rule.style?.display === 'flex' || rule.style?.display === 'inline-flex' </del> <ins> const mediaRules = new __helpers.CSSHelp(document).getCSSRules('media') const usesFlex = cssRules.find(rule => hasFlex(rule)) const usesFlexMedia = mediaRules.find(mediaRule => { return [...mediaRule.cssRules].find(rule => hasFlex(rule)) </ins> }) <del> assert(usesFlex) </del> <ins> assert(usesFlex || usesFlexMedia) </ins> ``` # --seed--
Change:
there is a typo in cramers-rule challenge, is used instead of which is wrong this sentence should be changed to Here is the markdown file Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first. Happy contributing.
Hi, May I work on this issue ?
of course, feel free to open pull request, after you have read the guide line

Discussion:
assert.exists(document.querySelector("div.fb1 > div.fb1a")); ``` <del> You should give the second new `div` a class of `fbab`. </del> <ins> You should give the second new `div` a class of `fb1b`. </ins> ```js assert.exists(document.querySelector("div.fb1 > div.fb1b"));
Change:
I never paid much attention to it before, but after someone tried to add a of 20 seconds to the challenge to pass test 2 (shown below), I think we should modify the wording to make it clear, the user should not purposely make a delay in the call. I was thinking something like the following for a replacement: 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
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 if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
I am not sure this wording is much better? Do we really need to mention the approximation used in the test? That is, can we make it:
It may not be much better. As far as the approximation being used in the text, it has been that way since the curriculum was ported over from the . I assume it was to account for some users with slow connections or maybe if someone ran the tests closed to midnight? The first commit this test appeared in was created by Quincy over 5 years ago.
To clarify, I am not questioning the need for an assertion approximation. I am questioning the need to mention it in the test text.
I am with you now. Whoever takes this issue on, please change the text to reflect suggestion shown below:

Discussion:
); ``` <del> The /now endpoint should return a time that is +/- 20 secs from now </del> <ins> The `/now` endpoint should return the current time. </ins> ```js (getUserInput) =>
Change:
Two of the typos are minor but one could be confusing In the first paragraph of the instructions (see below), there is a reference to The actual test number to change is and not , so it should be changed to reflect this. n/a No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response_
Hey, I created pull request for this issue.

Discussion:
# --instructions-- <del> Within `tests/2_functional-tests.js`, in the `'Submit the surname "Vespucci" in the HTML form'` test (`// #5`), automate the following: </del> <ins> Within `tests/2_functional-tests.js`, in the `'Submit the surname "Vespucci" in the HTML form'` test (`// #6`), automate the following: </ins> 1.  Fill in the form with the surname `Vespucci` 2.  Press the submit button
Change:
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.

Discussion:
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)`.

Create a rule that targets both `.one` and `.two` and increase their `blur` effect by 1 pixel. <del> Here's an example of a rule that increases the `blur` of two elements: ```css h1, p { filter: blur(3px); } ``` </del> # --hints-- <del> You should have a `.one, .two` selector. </del> <ins> You should have a `.one, .two` selector list. </ins> ```js const oneTwo = new __helpers.CSSHelp(document).getStyle('.one, .two');
Change:
in the docs, there is a line that is missing period at the end of it. These should have period in the end of it Here is the markdown file Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first. Happy contributing.
I will work on that

Discussion:
5. Install a code editor of your choice. <del> We highly recommend using [Visual Studio Code](https://code.visualstudio.com/) or Android Studio. We also recommend installing the official [extensions](https://docs.flutter.dev/get-started/editor?tab=vscode) </del> <ins> We highly recommend using [Visual Studio Code](https://code.visualstudio.com/) or Android Studio. We also recommend installing the official [extensions](https://docs.flutter.dev/get-started/editor?tab=vscode). </ins> ## Fork the repository on GitHub
Change:
In the file curriculum/challenges/english/14-responsive-web-design-22/learn-html-forms-by-building-a-registration- There is a typo, "chose" should be "choose". If you would like to fix this issue please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
I would like to work on this
Go for it.
Added updated wording and is linked to issue.
We have two pull requests with the same change.

Discussion:
# --description-- <del> Users will be allowed to chose either a `Personal Account` or `Business Account`. </del> <ins> Users will be allowed to choose either a `Personal Account` or `Business Account`. </ins> To do this, within each of the first two `label` elements, add one `input` element with `type="radio"`.
Change:
When working on the file we are asked to write a function. There is a typo in the last sentence of the info you give. "Make sure the "repsonse" you... no code needed just fix the typo, lol 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
Thank you for opening this issue. Tutorial is located at: This tutorial is using CodeRoad VS Code extension, specific guidelines how to contribute to them can be found on Making PR for this issue will require following parts referring to making changes on the branch. Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
I can fix this typo :)

Discussion:
return res.redirect('/forgot'); } res.render('account/reset', { <del> title: 'Password Reset' </del> <ins> title: 'Password Reset', token: req.params.token </ins> }); }); };

from: 'Team@freecodecamp.com', subject: 'Reset your Free Code Camp password', text: [ <del> 'You are receiving this email because you (or someone else)', </del> <ins> 'You are receiving this email because you (or someone else)n', </ins> 'requested we reset your Free Code Camp account's password.nn', <del> 'Please click on the following link, or paste this into your', </del> <ins> 'Please click on the following link, or paste this into yourn', </ins> 'browser to complete the process:nn', 'http://', req.headers.host, '/reset/', token, 'nn', <del> 'If you did not request this, please ignore this email and', </del> <ins> 'If you did not request this, please ignore this email andn', </ins> 'your password will remain unchanged.n' <del> ].join(' ') </del> <ins> ].join('') </ins> }; transporter.sendMail(mailOptions, function(err) { if (err) { return done(err); }

extends ../layout block content <del> .col-sm-8.col-sm-offset-2 form(method='POST') legend Reset Password </del> <ins> .col-sm-8.col-sm-offset-2.jumbotron form(action='/reset/#{token}', method='POST') h1 Reset Password </ins> input(type='hidden', name='_csrf', value=_csrf) .form-group label(for='password') New Password
Change:
The language selection menu is not intuitive about the no. of available options. It's a bit paradoxical at the moment: You will not notice additional options until you start scrolling while being on top of the options. You will not start scrolling until you know there are additional options. to '/learn' on 'Menu' down to 'Change Language' the cursor on the options Scrolling while being in the area of the listed options. menu should be very clean and intuitive. "Cancel Change" option should have some form of visual separation. https://user- Device: All Devices OS: All OS Browser: All Browsers Version: All Versions No response
this will start becoming evident with more languages on the list. The quickest and simplest way this can be handled is by slightly increasing the height of the list and decreasing the height of the hover-state highlight (each item). That will leave some space at the bottom of the last item, intuitively letting the user know there is more to be looked at. Currently, the perfect-sized (height) items and the overall height of the list make it difficult to notice more entries. Finally, that "Cancel" option should be a different color or have some form of visual separation.
is this issue still being worked on? If not, I would like to take it.
That makes sense, I thought we fixed that. should be removed for and
or anyone else interested, this is up for grabs.
This is what makes the language menu full length so no vertical scroll bar appears. Originally, I had the language menu set so that a vertical scroll bar would appear if it was taller than the main menu. But it was decided that there shouldn't be a vertical scroll bar, the language menu should be as tall as necessary so no scroll bar was needed. Is this what we still want? Even as we continue to add even more languages?
thanks for bringing this up. Ideally we would need to show as many languages as possible in a viewport and display a minified scroll bar if the list exceeds the height viewport minus of the navigation. We could show a scrollbar initially as you recommended, but the dropdown needs expand further than the main menu if needed.

Discussion:
cursor: pointer; } <ins> #nav-lang-menu li:first-child { border-bottom: 0.1rem solid var(--gray-45) !important; } </ins> button.nav-link:focus { color: var(--tertiary-color); background-color: var(--tertiary-background);

overflow-y: auto; scrollbar-width: auto; /* lang menu should always be full height */ <del> height: 19.9rem; </del> } /* main menu must be at least as tall as lang menu (when displayed)

background-color: var(--gray-10) !important; } <ins> .nav-lang-menu li:first-child .nav-link:hover { color: var(--love-dark) !important; } </ins> .nav-lang-button { display: flex; justify-content: space-between;
Change:
In step 29 of the Learn HTML Forms by Building a Registration Form challenge, there seems to be incorrect seed code. The checkbox for accepting terms and conditions is missing a , so when the step first opens it displays a plain text input instead of a checkbox. N/A A checkbox should be rendered instead of a text input. ! Device: Laptop OS: Ubuntu 20.04 Browser: Firefox (104), Chrome (105) No response
Whoops! Yeah, that should be fixed. Thanks for opening this issue. This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: 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.
Sounds good! I'll submit a PR to fix it!

Discussion:
<fieldset> <label for="personal-account"><input id="personal-account" type="radio" name="account-type" /> Personal Account</label> <label for="business-account"><input id="business-account" type="radio" name="account-type" /> Business Account</label> <del> <label for="terms-and-conditions"><input id="terms-and-conditions" required /> I accept the terms and conditions</label> </del> <ins> <label for="terms-and-conditions"><input id="terms-and-conditions" type="checkbox" required /> I accept the terms and conditions</label> </ins> </fieldset> --fcc-editable-region-- <fieldset></fieldset>
Change:
The sentence is worded strangley: We should refphrase this sentence to something like: ! 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
An issue with the first timers only label is open for contribution by first time contributors only. 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 from to
Can i work in this issue ?
Go for it my friend! Just make sure to create a new branch when you make the changes!

Discussion:
# --description-- <del> Add a `title` and a `meta` elements to the `head`. Give your project a title of `Registration Form`, and give a `charset` attribute with a value of `UTF-8` to your `meta` element. </del> <ins> Add a `title` and a `meta` element to the `head`. Give your project a title of `Registration Form`, and give a `charset` attribute with a value of `UTF-8` to your `meta` element. </ins> # --hints--