jiebi/CodeConvo huggingface dataset:
Change:
*   <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

Discussion:
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
Change:
*, ::before, ::after { padding: 0; margin: 0; <ins> box-sizing: border-box; </ins> } --fcc-editable-region--

Discussion:
Someone in the forums pointed out that adding the property just to will not have the intended effect since the property is not inherited. It appears to me that removing this property completely from in the final product does not seem to make any difference to the layout. Do we need ? If so, if the intent is to apply it to all elements then it should probably be moved to the rule set. Either remove completely or move it into the ruleset. No response N/A No response
Pretty sure I saw this in another challenge too and it got fixed. The CSS used looks like the of setting the but with the actual inheriting missing from the code. It should be fixed, but I would not suggest we remove , setting that (in my opinion) is pretty much a best pratice.
I'm guessing it would be easier and take less explaining to update step 26 to add the on that selector and then remove the mention of it in step 27. Then update all the seed code.
Just a heads up, if lasjorg PR merged without issue, balance sheet project suffer the same issue, we can open a PR or issue for it, if the PR is merged. Except that the balance sheet project , doesn't do much and moving it break the layout.
Change:
Add all your code for these lessons in the `server.js` file between the code we have started you off with. Do not change or delete the code we have added for you. <del> BCrypt has already been added as a dependency, so require it ad `bcrypt` in your server. </del> <ins> BCrypt has already been added as a dependency, so require it as `bcrypt` in your server. </ins> Submit your page when you think you've got it right.

Discussion:
There is a typo in Understand BCrypt Hashes, is used instead of . Here is the typo 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 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.
Change:
<del> const assert = require('chai').assert; </del> <ins> const { assert, AssertionError } = require('chai'); const Mocha = require('mocha'); </ins> const { flatten } = require('lodash'); const path = require('path');

Discussion:
Describe the bug Several warnings in the Travis CI builds: To Reproduce Steps to reproduce the behavior: a PR the output in Travis CI build Expected behavior Cleaner builds; maybe reduce build time(?) Screenshots ! Additional context Error references this documentation: Live Demo in doc:
Change:
"passport-local": "^1.0.0", "passport-oauth": "^1.0.0", "passport-twitter": "^1.0.2", <ins> "ramda": "^0.10.0", </ins> "request": "^2.49.0", "sitemap": "^0.7.4", "uglify-js": "^2.4.15",

Discussion:
the first line in the function says - it wont pass testing unless you change it to Browser Name: Firefox Browser Version: 60.0.1 Operating System: High Sierra ! <hr!
You don't have to it, but because of strict mode it does need to be declared with , , or .
so its missing the then?
That's how I would update it.

i am suspecting another small bug, the next challenge after succesful code run in Bonfire: Chunky Monkey actually points to itself
Change:
The `copyMachine` function should utilize the `spread operator` with array `arr` ```js <del> assert(code.match(/...arr/)); </del> <ins> assert(code.match(/...s*arr/)); </ins> ``` # --seed--

Discussion:
On , the task is to use the spread operator to copy an array. JS semantics allow the spread operator to have whitespace between it and the object it is being applied to. The following is valid: However, in the challenge, any whitespace between the operator and the value will cause the test to fail. The issue is with the test regex here: Which should probably be amended to: NOTE: this issue was , I am submitting it on their behalf. Whitespace between the spread operator and the object it is being applied to should not cause the test to fail. 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
Looks like a good beginner friendly fix to me
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.
Change:
"assert.deepEqual(myArray, [0,1,2,3,4], 'message: <code>myArray</code> should equal [0,1,2,3,4].');" ], "challengeSeed":[ <del> "ourArray = [];", </del> <ins> "var ourArray = [];", </ins> "for(var i = 0; i < 5; i++){", "  ourArray.push(i);", "}",

Discussion:
The left sidebar has var ourArray = []; But the code only has ourArray = []; Then the code has var myArray = []; It runs with our without the pink var (declaration I think)... Just might want to fix the typo or have it be consistent or explained that it will work either way... Challenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:
This is a typo. The seed code is missing in front of the initial declaration of ourArray. While this will run it's a bad practice and should be fixed.
thanks for pointing this out! Confirmed and marked as easy fixable. Also I've renamed the title of the issue, please, provide more descriptive title next time, thanks.
Change:
<strong>User Story #14:</strong> My legend should contain <code>rect</code> elements. <strong>User Story #15:</strong> The <code>rect</code> elements in the legend should use at least 4 different fill colors. <strong>User Story #16:</strong> I can mouse over an area and see a tooltip with a corresponding <code>id="tooltip"</code> which displays more information about the area. <del> <strong>User Story #16:</strong> My tooltip should have a <code>data-year</code> property that corresponds to the <code>data-year</code> of the active area. </del> <ins> <strong>User Story #17:</strong> My tooltip should have a <code>data-year</code> property that corresponds to the <code>data-year</code> of the active area. </ins> Here is the dataset you will need to complete this project: <code>https://raw.githubusercontent.com/freeCodeCamp/ProjectReferenceData/master/global-temperature.json</code> You can build your project by forking <a href='https://codepen.io/freeCodeCamp/pen/MJjpwO' target='_blank'>this CodePen pen</a>. Or you can use this CDN link to run the tests in any environment you like: <code>https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js</code> Once you're done, submit the URL to your working project with all its tests passing.

Discussion:
This project has two user stories that are listed as !
Thank you, for spotting this. This is an easy fix; Here is the culprit file:
hi , Can I go ahead with this?
Hello , As you are considered a Contributor (made at least 1 contribution), I suggest you leave this open to first timers. Thank you, for your understanding.
Hey I figured I'll mention here. I was not aware that we could not do it ourselves. I apologize for the inconvenience.
Hi can I work on this? I am a first-timer
Hi , I think this issue has already been picked up. Feel free to claim an issue with label .
I think that I sent it through but I'm unsure if I did it correctly. It might still need someone with Write access to accept the edits?
I can check it for you
Hi I'm unsure if I am doing this correctly but I have a pending pull request. It needs approval to be submitted.
Hello , sorry, things are quite busy. You have done what you needed to, and, as it stands, your PR is approved. Thank you, for your patience.
Ok thanks for the heads up!

It flashes the form fields for a second and then is blank between "Update your profile here:" and "Actions" headings. Here's the console error: TypeError: Cannot read property 'toLowerCase' of undefined at at at at l.$eval () at l.$digest () at l.$apply () at l () at O () at () That looks like it's on the $() on line 49. The JSON from my /account/api doesn't have a user.profile.username key. Maybe it would be a simple fix of piping? () '';
Which method did you use to sign up for freecodecamp? It's an issue of your username not existing.
Signed up with email.
How long ago did you sign up for FCC? On Mon Jan 12 2015 at 11:40:50 AM Justin Rogers wrote:
Around December 8th. Am I the only document without a username in the db?
Change:
<ins> require('dotenv').config({ path: `${__dirname}/../../.env` }); const core = require('@actions/core'); const { getFiles } = require('../../utils/files'); const { getStrings, changeHiddenStatus } = require('../../utils/strings'); const filename = core.getInput('filename'); const stringContent = core.getInput('string-content'); const hideString = async (projectId, fileName, string) => { const fileResponse = await getFiles(projectId); const targetFile = fileResponse.find(el => el.path.endsWith(filename)); if (!targetFile) { core.setFailed(`${fileName} was not found.`); return; } const stringResponse = await getStrings({ projectId, fileId: targetFile.fileId }); const targetString = stringResponse.find(el => el.data.text === string); if (!targetString) { core.setFailed(`${string} was not found.`); return; } await changeHiddenStatus(projectId, targetString.data.id, false); console.log('string unhidden!'); }; const projectId = process.env.CROWDIN_PROJECT_ID; hideString(projectId, filename, stringContent); </ins>

Discussion:
The challenge title of challenge Use && for a More Concise Conditional is not translatable on Crowdin ! (the greyed out text is for not translatable strings) An other challenge where the title is translatable ! this is the link for crowdin file: markdown file for the challenge:
mind taking a look?
I have manually marked the string as translatable today. After our workflows run tomorrow, I will confirm the string is still translatable - if it is not, I will investigate further.
Reopen if still and issue.
this actually happened again with last update
Just to add that this is also happening in pt-BR. The entry is blocked for translation. I suspect this has to do with the double ampersand.
Hello, we are a group of researchers developing machine learning techniques to locate issues suitable for newcomers, and our model consider this issue as likely a "good first issue". May we recommend you to label it as "good first issue" so newcomers know where to choose? Thank you!
thanks but it is not - this needs to be done through Crowdin pipeline, will need to do it, again
Change:
# --description-- <del> Continuing with the date theme, HTML5 also introduced the `time` element along with a `datetime` attribute to standardize times. The `datetime` attribute is an inline element that can wrap a date or time on a page. A `datetime` attribute holds a valid format of that date. This is the value accessed by assistive devices. It helps avoid confusion by stating a standardized version of a time, even if it's informally or colloquially written in the text. </del> <ins> Continuing with the date theme, HTML5 also introduced the `time` element along with a `datetime` attribute to standardize times. The `time` element is an inline element that can wrap a date or time on a page. A `datetime` attribute holds a valid format of that date. This is the value accessed by assistive devices. It helps avoid confusion by stating a standardized version of a time, even if it's informally or colloquially written in the text. </ins> Here's an example:

Discussion:
<!-- NOTE: If you want to become an author on freeCodeCamp, you can find everything here: --The sidebar text on "Standardize Times with the HTML5 datetime Attribute" says "The datetime attribute is an inline element that can wrap a date or time on a page." The attribute cannot be an inline element. Change it to: "The element is an inline element that can wrap a date or time on a page. " or "The is an inline element that can wrap a date or time on a page.". !
Hey good spot there I'll sort this
Change:
); }; <del> const MainFormControl = Object.assign(FormControl, { Feedback, Static }); </del> <ins> FormControl.Feedback = FormControlFeedback; FormControl.Static = FormControlStatic; </ins> <del> export { MainFormControl as FormControl }; </del> <ins> export { FormControl }; </ins>

Discussion:
onChange: func value?: string componentClass?: string placeholder?: string name?: string required?: string rows?: 4 type?: 'text' 'url'FormControl FormControl.Feedback
Form control for chapter: Need to alter the props to account for chapter needs, here is the link to the chakira component
Which prop is being used in the chapter that we are not passing in the component library? Since chapter views are limited, it might be easier to create the components with learn specifications and use those props to control the component. does that make senes?
Instead of checking the chaikra library and comparing it with the current component, I am better off checking chapter itself for prop it's using. for example, in this file we are using and , so I note these down and check if these 2 props are different from the props we are using. depend on how different they are, I may do from the follow: Add new value to existing prop. Add new prop to the component. Do nothing.
Here is what I propose we do. We could continue building the components with the learn spec and ship them. For the second sprint, we collect the Chapter requirements and update the components accordingly.
Change:
"update-email": "Update my Email", "verify-email": "Verify Email", "submit-and-go": "Submit and go to next challenge", <ins> "submit-and-go-2": "Submit and go to next challenge (Ctrl + Enter)", "submit-and-go-3": "Submit and go to next challenge (Command + Enter)", </ins> "go-to-next": "Go to next challenge", <ins> "go-to-next-2": "Go to next challenge (Ctrl + Enter)", "go-to-next-3": "Go to next challenge (Command + Enter)", </ins> "ask-later": "Ask me later", "start-coding": "Start coding!", "go-to-settings": "Go to settings to claim your certification",

Discussion:
We are using the class to conditionally hide some text on mobile screens: This class comes from Bootstrap, which is something we are going to remove (). So instead of using the class, we can use an check, like this (which is also a little more consistent with how we've handled this kind of conditional rendering): Update the file to replace the class with an check. I noticed that we are using multiple methods for mobile device detection, so I think the check should be standardized, and there should be a shared util for this check. But I'm leaving this out of the scope of this issue, and will create a separate issue for it.
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.
I already have a pull request that technically resolves this. While it is done the same way we did the lower-jaw i.e checks for a desktop instead of being mobile , it does solve the problem and pass the tests.
Change:
# --description-- <del> Give each `fieldset` an adaquate `name` attribute. Then, give both unordered lists a `class` of `answers-list`. </del> <ins> Give each `fieldset` an adequate `name` attribute. Then, give both unordered lists a `class` of `answers-list`. </ins> Finally, use the `legend` to caption the content of the `fieldset` by placing a true/false question as the text content. # --hints-- <del> You should give the first `fieldset` an adaquate `name` attribute. _Hint: I would use `html-question-one`_ </del> <ins> You should give the first `fieldset` an adequate `name` attribute. _Hint: I would use `html-question-one`_ </ins> ```js assert.notEmpty(document.querySelectorAll('fieldset')?.[0]?.name);

Discussion:
Should be adequate <!-- Please complete the following information. --- Device: [Laptop] OS: [openSUSE Tumbleweed] Browser: [Vivaldi] Version: 5.0]
Thank you for reporting this issue. This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging (PR ). This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue. If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding.
Wait, sorry, there are more adequates to fix. And it seems is doing it
Change:
# --description-- <del> Your `output.innerHTML` string will need a `span` element. Create that, and give it a `class` attribute set to the `surplusOrDeficit` variable, but lowercased. </del> <ins> When you need to lower case a string, you can use the <dfn>toLowerCase()</dfn> method. This method returns the calling string value converted to lower case. </ins> <del> Strings have a `.toLowerCase()` method that can help you with this. Do not give your `span` any text yet. </del> <ins> ```js const firstName = 'JESSICA'; console.log(firstName.toLowerCase()); // Output: jessica ``` Your `output.innerHTML` string will need a `span` element. Create that, and give it a `class` attribute set to the `surplusOrDeficit` variable. Your `surplusOrDeficit` variable should be converted to lower case using the `toLowerCase()` method. Do not give your `span` any text yet. </ins> # --hints--

Discussion:
We introduce the method in step 79, but do not provide a code example. For consistency, we should provide code examples for these methods when they are first introduced. js const firstName = 'JESSICA'; (firstName.toLowerCase()); // Output: jessica ` 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
Hello :) newbie here, I am going to tackle this task. PR will be published soon.
Change:
Inside the callback function, create a new `const` variable called `collisionDetectionRules` and assign it an empty array. <del> Inside that array, add a boolean expression that checks if the player's `y` position plus the player's height is less than or equal to the platform's `y` position. </del> <ins> Inside that array, add a boolean expression that checks whether the player's `y` position plus the player's height is less than or equal to the platform's `y` position. </ins> # --hints--

Discussion:
following task ask for : reading this line suggests/ indicates to me writing an "if" statement inside of the array although that could be my understanding of the sentence my suggestion would be to update the sentence to the following No response Device: [macBook pro] OS: [Ventura 13.4.1 ] Browser: [chrome ] Version: [121.0] No response
Hi ! Thank you for creating this issue. I think the re wording makes sense. The only thing, I would change would be the first part of that sentence. We should mention explicitly that they are adding to the array. I will go ahead and open this up for contribution for
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
I updated the instructions of step 78 and committed the changes. Please have a look at that Thank you
I am sorry but since I am new to open-source contributions, I accidentally closed the previous PR. I am making a new Pull Request please have a look at that.
Change:
background-color: var(--theme-color); } <del> #universal-nav-logo img { </del> <ins> #universal-nav-logo svg { </ins> display: block; width: auto; height: 25px;

Discussion:
Nav logo should be served a react svg component in the codebase for reference. The alt text should read: ''
Removing the first timers, because it may not be very trivial.
I would love to get this done. Please assign it to me.
Issue assignment is not necessary, we accept the first valid PR, which follows our contribution guidelines.
Thanks for the heads up, I thought we still followed the assignment rule like in the past. I will submit a PR soon.
There you go, making an exception because of your interest :) Happy contributing!
Hi how is this coming along. Are you still working on this?
Hi I will be making a PR today hopefully. Was stuck in some other work.
Hi I ran into an Eslint issue, when I converted SVG to JSX the svg path code is so lengthy that I get Any hint on how I can manage this? tried running the but it doesn't work.
You should be able to wrap using the lines at 80 in your code editor if you happen to use VS Code? Let's make a PR or share a link to your repo/branch for more context. Thanks.
Created a PR with ESLint max-len disabled. I tried wrapping the code to multiple lines but some string blocks are very long and would break the svg if put on a new line.