jiebi/CodeConvo huggingface dataset:
Change:
background-color: #c9d2fc; } <ins> --fcc-editable-region-- </ins> .cat-head { <del> --fcc-editable-region-- --fcc-editable-region-- </del> background: linear-gradient(#5e5e5e 85%, #45454f 100%); width: 205px; height: 180px; border: 1px solid #000; border-radius: 46%; } <ins> --fcc-editable-region-- </ins> ```

Discussion:
The active editor for step 9 is currently one empty line placed within the ruleset. Since the instructions above the editor are relatively long it makes it hard to see the selector, which has the potential to confuse people and cause them to unnecessarily add it again (I just dealt with a forum post that did this exact thing). In step 8 we have the active editor include the entire ruleset and leave a blank line for the new property to be . I would suggest we do the same thing for step 9, and leave three blank lines if possible since we are asking for three new properties to be . Step 10 and 11 also have a similar issue, but they are only changing the values of existing properties, so perhaps this is not as big an issue for those steps? I'm fine with keeping them as they are now. In the forum post the selector was again resulting in the following CSS: Have the active editor encompass the entire ruleset and leave three empty lines for the three new properties. No response N/A No response
Hey ! This change makes sense. I have looked through the forum and have seen the issue with campers getting confused. So it would be easy enough to fix. I will do a quick write up with the suggested changes and open it up for contribution I vote to leave steps 10 and 11 as they are for now, just because I haven't seen that pop up to much on the forum.
I am opening this up for first timer contributors since it is small fix. Please make sure to read the and first. Here is the file you will be working with You will need to change the editable region to include the entire ruleset It should produce this result which will make it clearer for campers what changes they will need to add. <img width="902" alt="Screenshot 2023-10-28 at 10 06 22 AM" src=""NOTE we do not assign issues. If you are interested in working on this, then read through the contributing docs and create a PR Happy contributing!
atempt
Change:
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--

Discussion:
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
Change:
const buildProxyConsole = proxyLogger => ctx => { const oldLog = ctx.window.console.log.bind(ctx.window.console); ctx.window.console.log = function proxyConsole(...args) { <del> proxyLogger(args.map(arg => JSON.stringify(arg)).join(' ')); </del> <ins> proxyLogger(args.map(arg => '' + JSON.stringify(arg)).join(' ')); </ins> return oldLog(...args); }; return ctx;

Discussion:
Describe the bug Because the log calls and that returns , just outputs an empty line. This is in contrast to which outputs . To Reproduce Steps to reproduce the behavior: to into the editor. the tests Expected behavior
Change:
This series of challenges introduces how to use Redux with React. In a React Redux app, you create a single Redux store that manages the state of your entire app. Your React components subscribe to only the pieces of data in the store that are relevant to their role. Then, you dispatch actions directly from React components, which then trigger store updates. <del> Improve this intro on [GitHub](https://github.com/freeCodeCamp/learn/tree/master/src/introductions/front-end-libraries/react-and-redux/index.md). </del>

Discussion:
Describe your problem and how to reproduce it: 1) Go to: 2) Find this text: "Improve this intro on GitHub." 3) Link to GitHub to improve the intro is broken Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: 79 Operating System: Mac OS 10.13.6 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! !
I am not even sure why that last sentence is present. I think it is best if it is removed completely from the introduction. If you see anymore links like this, please add them to this issue, so someone can create a PR to fix them all at the same time.
What do you think about removing the link to the redux website (the first word in the intro)
I think for now, we can leave it alone. I think the discussion of external links should be on a separate issue (if there is not already an outstanding issue). I thought I had an open issue at one point about external links. It may have gotten closed at some point (can't remember why).
Hey guys , the same issue is happening in the React and Redux section, please check:
Change:
- Fill in the usual HTML boilerplate. <del> - finally, add the following `h1` to the `body`: `<h1>Homepage</h1>` </del> <ins> - Finally, add the following `h1` to the `body`: `<h1>Homepage</h1>` </ins> ## Anchor Elements To create a link in HTML, you use the anchor element. An anchor element is defined by wrapping the text or another HTML element you want to be a link with an `<a>` tag.

Discussion:
The word "finally" should be capitalized. <img width="585" alt="Screenshot 2024-03-26 at 13 15 32" src=""- Capitalize the word "finally" in the following files:
This issue is open to first-time code contributors to this repository. The file that you should be updating is linked in the original post. Please make sure you read our as well as our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. 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.
Here is the PR for the fix:
Change:
```js const sum = (x, y, z) => { const args = [x, y, z]; <del> return args.reduce((a, b) => a + b, 0); </del> <ins> let total = 0; for (let i = 0; i < args.length; i++) { total += args[i]; } return total; </ins> } ```

Discussion:
The challenge is using the method which hasn't been introduced yet. I believe it is an artifact of the current section order (ES6 now comes before functional programming). You don't really need to understand how works to solve the challenge but just to avoid any confusion it might be better to change it to use a simple for loop. The guide post will need to be updated as well if this change is made. Should not contain code that is unfamiliar to the student. 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 post: Guide post:
hey i have fix this issue let you check PR
Change:
You should give the `meta` tag a `charset` of `UTF-8`. ```js <del> assert.equal(document.querySelector('head > meta')?.getAttribute('charset'), 'UTF-8'); </del> <ins> assert.equal(document.querySelector('head > meta')?.getAttribute('charset')?.toLowerCase(), 'utf-8'); </ins> ``` # --seed--

Discussion:
The value for is case-insensitive. Not sure if I missed any, but here are case-sensitive ones I found. Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-accessibility-by-building-a-quiz Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-css-animation-by-building-a-ferris-wheel Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-intermediate-css-by-building-a-picasso-painting Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-responsive-web-design-by-building-a-piano Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-the-css-box-model-by-building-a-rothko-painting a lot Both are valid The value for should be case insensitive for all challenges. 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]
Change:
var passedBonfireHash = !{JSON.stringify(bonfireHash)}; var challengeName = !{JSON.stringify(name)}; var started = Math.floor(Date.now() / 1000); <ins> var _ = R; </ins> .col-xs-12.col-sm-12.col-md-8 #mainEditorPanel form.code

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:
* Case Covers - Contrary to what you read on the internet, keeping the case covers on the computer aids cooling. Absence of the case covers disrupts air flow and can actually increase the heat inside the case. Room ventilation - Locate the computer where it is neutral to the rooms environmental registers. Keep the computer away from room heaters or vents at all times. * Room placement - Locate the computer away from windows or areas of strong sunlight exposure. Placement in closets can also provide challenges to cooling. <del> * Placement next to other computers - Locating the computer away from other equipment allows air to flow in and out of the computer. Placement close to other equipment can constrict air flow and increase heat. </del> <ins> * Placement next to walls and other computers - Locating the computer away from other equipment allows cool, clean, air to flow in and out of the computer. Placement close to other equipment can constrict air flow and increase heat. Placement next to a wall may also lead to the exhaust ports being completely blocked off and consequently increase heat. </ins> [Wikipedia - Article on computer cooling](https://en.wikipedia.org/wiki/Computer_cooling)

Discussion:
<!-- 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 page with the problem: If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !
I'm taking this
Change:
border-radius: 5px; background-color: var(--yellow-light); border-color: var(--yellow-light); <ins> color: black; font-weight: bold; </ins> } button#confirm-donation-btn:active, button#confirm-donation-btn:active:focus, button#confirm-donation-btn:hover { <del> color: var(--secondary-color); </del> <ins> color: black; </ins> background-color: #f2ba38; border-color: #f2ba38; }

Discussion:
Looking forward for reporting a security issue: Please report security issues by sending an email to instead of raising a GitHub issue. Describe the bug The heights of the SVG files on the landing page vary, which causes the certification chart to look inconsistent. To Reproduce <img width="946" alt="zoomfloatingvideowindowandLearntoCode—ForFree—CodingCoursesforBusyPeople" src="https://user-"Desktop (please complete the following information): OS: Mac Browser: Chrome Version: Version 88.0.4324.96 (Official Build) (x86_64)
Hi Quincy, I let know about this already.
in min height, so should take care of it.
Change:
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); }

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

Is your feature request related to a problem? Please describe. The activities count on the search bar in both /learn, and /news is different than /forum. Describe the solution you'd like A clear and concise description of what you want to happen. Fix the count on activities. Additional context Add any other context or screenshots about the feature request here. <img width="629" alt="Screen Shot 2020-05-11 at 23 27 55" src="https://user-"<img width="730" alt="Screen Shot 2020-05-11 at 23 27 39" src="https://user-"
Change:
"Al usar el elemento <code>span</code>, puedes poner varios elementos juntos, e incluso darle diferentes estilos a partes diferentes del mismo elemento.", "Anida la palabra "love" en tu elemento "Things cats love" dentro de un elemento <code>span</code>. Luego, asigna a ese elemento <code>span</code> la clase <code>text-danger</code> para hacer que el texto sea rojo.", "Así es como lo harías con el elemento "Top 3 things cats hate":", <del> "<code>&#60;p&#62;Top 3 things cats &#60;span class = "text-danger"&#62;hate&#60;/span&#62;&#60;/p&#62;</code>" </del> <ins> "<code>&#60;p&#62;Top 3 things cats &#60;span class = "text-danger"&#62;hate:&#60;/span&#62;&#60;/p&#62;</code>" </ins> ] }, {

Discussion:
[ ] 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
Change:
# --description-- <del> You used the `inputVal` property as the `id` attribute for your paragraph elements. Now you can target those the paragraph elements with those `id`s. </del> <ins> You have set the `id` attribute for your paragraph elements to the `obj.inputVal` property. </ins> <del> Use the `.getElementById()` method to select the element with the `id` attribute with the value of the `inputVal` property of the current object. </del> <ins> Now, use `getElementById` to select the element with that attribute value, again using the `obj.inputVal` property. </ins> # --hints--

Discussion:
In the first paragraph, on the 2nd phrase, you can read: . Rectify to the following: No response . 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.
I would suggest we remove "those" and keep "the" so we are not repeating "those". I would also suggest using "attribute value"
The next paragraph reads pretty bad as well. It's just confusing to read. Maybe we can come up with something better. Edit: take two Or something like that?
I know the first line already mentioned "paragraph elements", so it is presumed that the second line is referring to that type of element. But as a newbie, when I read "to select the element with that attribute value", it seems any kind of element. Could we be more specific, and edit to "(...) to select the paragraph element (...)"?
It is selecting by so the element type doesn't matter. Saying what the element type is seems redundant to me. But if you or anyone else feel it would make it more clear, then I wouldn't be opposed to it.
Yes, you are right. Mentioning is what matters.
Change:
"" ], "solutions": [ <del> "function myTest(val) {n  if(val > 10) {n    return "10 or Bigger";n  } else if(val < 5) {n    return "Smaller than 5";n  } else {n    return "Between 5 and 10";n  }n}" </del> <ins> "function myTest(val) {n  if(val > 10) {n    return "Greater than 10";n  } else if(val < 5) {n    return "Smaller than 5";n  } else {n    return "Between 5 and 10";n  }n}" </ins> ], "tests": [ "assert(code.match(/else/g).length > 1, 'message: You should have at least two <code>else</code> statements');", "assert(code.match(/if/g).length > 1, 'message: You should have at least two <code>if</code> statements');", <del> "assert(myTest(0) === "Smaller than 5", 'message: <code>myTest(4)</code> should return "Smaller than 5"');", "assert(myTest(5) === "Between 5 and 10", 'message: <code>myTest(5)</code> should return "Smaller than 5"');", </del> <ins> "assert(myTest(0) === "Smaller than 5", 'message: <code>myTest(0)</code> should return "Smaller than 5"');", "assert(myTest(5) === "Between 5 and 10", 'message: <code>myTest(5)</code> should return "Between 5 and 10"');", </ins> "assert(myTest(7) === "Between 5 and 10", 'message: <code>myTest(7)</code> should return "Between 5 and 10"');", "assert(myTest(10) === "Between 5 and 10", 'message: <code>myTest(10)</code> should return "Between 5 and 10"');", <del> "assert(myTest(12) === "10 or Bigger", 'message: <code>myTest(12)</code> should return "10 or Bigger"');" </del> <ins> "assert(myTest(12) === "Greater than 10", 'message: <code>myTest(12)</code> should return "Greater than 10"');" </ins> ], "type": "waypoint", "challengeType": "1",

Discussion:
Return statement Issue: JS Line 3: Return statement text should be "Greater than 10" instead of "10 or bigger" Challenge Link : Browser Version : v47.0.2526.106 (64-bit) Operating System Version : Mac OS X 10.11.2 Steps to reproduce: to the above challenge link and check the text. (Optional)Read/Run the below test case in the above waypoint challenge page myTest(10) should return "Between 5 and 10" Screenshot 1: ! Screenshot 2: !
:+1: yes "10 or bigger" means
This same waypoint has some more minor bugs associated with it (in the test cases). They are : To save PR Reviewer time, I am merging this very minor issues in one and creating one commit to fix this.
Change:
# --hints-- <del> You should have `if (next_empty := self.find_empty_cell()) is None:` withing `solver`. </del> <ins> You should have `if (next_empty := self.find_empty_cell()) is None:` within `solver`. </ins> ```js const tCode = code.replace(/r/g, '');

Discussion:
Typo on Step 61 of Sudoku Solver project in Scientific Computing with Python (Beta) cert: "withing" in the hint text when I'm sure you meant "within". <img width="595" alt="Screen Shot 2024-03-21 at 1 39 54 PM" src=""Thanks for all the content!
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.
Change:
display: flex; justify-content: center; align-items: center; <del> background: lightblue; </del> }

Discussion:
To Reproduce Steps to reproduce the behavior: to /learn or /settings with the theme set to dark off internet connection and wait Actual behavior The offline warning message shows up, but the text is quite hard to read. Screenshots <img width="1680" alt="Screen Shot 2020-11-09 at 12 22 16 AM" src="https://user-"
WCAG does say the contrast is only 1.41:
The notification background is hardcoded and the font color is being handled based on theme. We have let bootstrap handle the styling for the notifications since they handle the font color and the background and look well on both themes. So doing the followings should do the trick. Add as a class here: and remove the from here:
I think the best way is to implement luma-corrected calculations. The first obvious implication of going with a luma-corrected approach is that the notification background color needs to switch to an RBG declaration for the backgrounds, calculate the luma from whatever method we choose, and use it on the foreground color declaration, which can (and will) still be HSL color. I am saying this because this would allow the font color to switch based on the contrast of the notification background contrast from to and vice versa.
can I work on this? I might need help. please guide me.
that is a cool trick. Thanks for sharing the link. Since are planning to move off of bootstrap, we should consider luma-corrected calculations in how we implement our dark/light themes during the rewrite process. Meanwhile, I think we could move forward with making the simple change that resolves this issue. sure. Make sure you read this: