jiebi/CodeConvo huggingface dataset:
Change:
"intro": [ "Node.js is a JavaScript runtime that allows developers to write backend (server-side) programs in JavaScript. Node.js comes with a handful of built-in modules — small, independent programs — that help with this. Some of the core modules include HTTP, which acts like a server, and File System, a module to read and modify files.", "In the last set of courses you learned to install and manage packages from npm, which are collections of smaller modules. These packages can help you build larger, more complex applications.", <del> "Express is a lightweight web application framework, and is one of the most popular packages on npm. Express makes it much easier to create a server and handle routing for your application, which handles things like direct people to the correct page when they visit a certain endpoint like <pre>/blog</pre>.", </del> <ins> "Express is a lightweight web application framework, and is one of the most popular packages on npm. Express makes it much easier to create a server and handle routing for your application, which handles things like directing people to the correct page when they visit a certain endpoint like <pre>/blog</pre>.", </ins> "In this course, you'll learn the basics of Node and Express including how to create a server, serve different files, and handle different requests from the browser." ] },

Discussion:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. -- This is a repeat of , it should say "like ". <img width="1440" alt="image" src="https://user-"- Device: MacBook Air (M1, 2020) OS: macOS Monterey 12.0.1 Browser: Chrome Version: 99.0.4844.84
Hi thanks for reporting this. The problem is almost certainly something to do with hydration because if you go to and then click through to Back End Development and APIs appears as expected. However, if you reload the page, it disappears.
Actually, scratch that theory: is in the page source and somehow it's removed on page load.
"direct" should also be "directing". which handles things like directing people to the correct page when the visit a certain endpoint like Overall though it's a fairly confusing description of routing.
Not sure if it's just me, but the bug doesn't seem to be reproducible. I tried on both Firefox 98.0.2 (64-bit) and Chrome Version 99.0.4844.84 - Windows 10 <details<summaryScreenshots</summary! ! </details
It has come back for me too, not sure if that's the case for everyone else in this thread: <img width="1440" alt="image" src="https://user-"
It's not clear why it's started working again, but I can no-longer reproduce the issue with . That said, the issue brought up (direct should be directing) is good for first timers, so I'll open this up.
I would like to be assigned this
Change:
--- <del> The link's has the mouse is over it. </del> <ins> The mouse cursor is over the link. </ins> ---

Discussion:
I'm not sure how to fix this sentence, probably or ?
is pretty clear.
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. We typically do not assign issues. Instead, we accept the most quality contribution followed by the one that is made first. 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. Happy contributing.
Change:
isSignedIn: PropTypes.bool, stripe: PropTypes.shape({ createToken: PropTypes.func.isRequired <del> }) </del> <ins> }), theme: PropTypes.string </ins> }; const initialState = { donationAmount: 500,

Discussion:
Describe the bug ! The input text on the darkmode version of the donate page () are not readable so you cannot see what you are typing. To Reproduce Steps to reproduce the behavior: to '' with darkmode enabled. on the input labled 'Your Card Number:' and enter some numbers. entered input is not readable as the color of the input text is the same as the background-color of the input. bug applies to the credit card expiration and CVC inputs. ! Desktop (please complete the following information): OS: Win10 Browser Brave/Chrome/Firefox
Change:
"nameEs": "Agrega iconos de Font Awesome a los botones", "descriptionEs": [ "Font Awesome es una librería de iconos muy conveniente. Estos iconos son imágenes vectoriales, almacenadas en formato <code>.svg</code>, y son tratados como si fueran fuentes. Puedes especificar su tamaño usando pixeles, y tomarán el tamaño de fuente de su elemento HTML padre.", <ins> "Puedes añadir Font Awesome a cualquier aplicación sólo incluyendo y agregando el siguiente código al comienzo de tu HTML:", "<code>&#60;link rel="stylesheet" href="//maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css"/&#62;</code>", "En este caso, ya lo hemos agregado por tí a esta página tras bambalinas.", "El elemento <code>i</code> originalmente era usado para hacer textos en itálicas, pero ahora comunmente se usa para iconos.  Le agregas clases de Font Awesome al elemento <code>i</code> para convertirlo en un ícono, por ejemplo:", "<code>&lt;i class="fa fa-info-circle"&gt;&lt;/i&gt;</code>", </ins> "Usa Font Awesome para agregar un icono de "pulgar arriba" <code>thumbs-up</code> a tu botón de like dándole un elemento <code>i</code> con las clases <code>fa</code> y <code>fa-thumbs-up</code>." ] },

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:
import './searchbar-base.css'; import './searchbar.css'; <del> // Configure react-hotkeys to work with the searchbar configure({ ignoreTags: ['select', 'textarea'] }); </del> const propTypes = { innerRef: PropTypes.object, isDropdownEnabled: PropTypes.bool,

Discussion:
Describe the bug Entering 'n' or 'p' in the solution URL of projects takes me back to the previous('p') or next('n') challenge. To Reproduce to any project section where URL is required 'n' or 'p' in the URL field Expected behavior This should only happen when the text field is not in focus. Desktop (please complete the following information): OS: Windows 10 Pro 32 Bit Pro Browser: Chrome Version: 77.0.3865.90
Change:
], "tests": [ "assert($("body").css("background-color") === "rgb(255, 0, 0)", 'Give your <code>body</code> element the <code>background-color</code> of red.')", <del> "assert(editor.match(/#FF0000/g) && editor.match(/#FF0000/g).length > 0, 'Use the <code>hex code</code> for the color red instead of the word <code>red</code>. For example <code>body { color&#58; #FF0000; }</code>.')" </del> <ins> "assert(editor.match(/#FF0000/ig) && editor.match(/#FF0000/ig).length > 0, 'Use the <code>hex code</code> for the color red instead of the word <code>red</code>. For example <code>body { color&#58; #FF0000; }</code>.')" </ins> ], "challengeSeed": [ "<style>",

Discussion:
! Same with the other waypoints that ask for a hex code that includes alpha chars.
Green worked fine.. blue has case issue.
Change:
.universal-nav a.translations-link { visibility: hidden; } <ins> body .content { max-width: 100%; } </ins> } /****** Cover Page ******/

Discussion:
<!-- NOTE: If you want to become an author on freeCodeCamp, you can find everything here: --<!-- If you are reporting an issue with an article on our News publication, please follow this link to send an email to our editorial team --Describe your problem and how to reproduce it: Viewing Documentation in mobile view as shown in bellow image the content is narrower. Need to make the content little more wider for easy readability. This is also true in landscape view lot of empty space left both sides. Add a Link to the page with the problem: Recommended fix, suggestions (how would you update it?): If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! !
Thanks for the report I agree that margins are too wide. Would you be interested in creating a PR to fix this?
sure will work on this issue
Change:
When an element is selected, the Styles tab will show all the currently applied styles, as well as any styles that are being overwritten (indicated by a strikethrough of the text). For example, if you use the inspector to click on the “Your Career in Web Development Starts Here” header on <a href="https://www.theodinproject.com/" target="_blank">the The Odin Project homepage</a>, on the right-hand side you’ll see all the styles that are currently affecting the element, as seen below: <img src="https://cdn.freecodecamp.org/curriculum/odin-project/the-box-model/overwritten-style.png" alt="CSS code snippet in the developer console showing .hero_main-heading with applied margin-bottom: 100px, padding-bottom: 1.875rem, .accent color #ce973e. h1 style rules include font-size, weight, letter-spacing, with its margin-bottom: 2rem overridden."> # --assignment-- Play around with Chrome Dev Tools and see if you can answer the following question.

Discussion:
The Assignment section is not displayed correctly. <img width="707" alt="Screenshot 2024-09-06 at 07 11 32" src="" Add an empty line between these:
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. We typically do not assign issues. Instead, we accept the most quality contribution followed by the one that is made first. 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. Happy contributing.
Change:
superBlock, t, theme = Themes.Default, <ins> showCodeAlly, </ins> user, fetchUser, updateAllChallengesInfo

Discussion:
The page gets stuck and goes blank with you leave the relational database challenges. to 'Start the course' the fCC logo/button in the nav goes blank and nav disappears Page not to go blank. Clicking fCC logo should go to /learn No response Same on Chrome and Firefox Console errors: <img width="671" alt="Screen Shot 2023-02-16 at 11 44 19 AM" src="https://user-"
Change:
</main> --fcc-editable-region-- <footer> </footer> --fcc-editable-region-- </div>

Discussion:
While I was replying to a forum question, I realised that step 65 of the Cafe Menu section accepts an incorrect answer. The challenge is to nest an anchor element inside a element, like this: But the student had nested the p element inside the anchor element, like this: The tests accept that (incorrect) answer - but only if the closing tag is malformed ( instead of ). It's a weirdly specific case, I know, but is there any way to have the tests pick this up? Ideally, the tests would recognise that the elements are incorrectly nested and not allow the incorrect code to pass the tests. 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] Link to the relevant forum post:
Here is the file I think, it's best to not do anything. The next challenge isn't about css, and they can see the correct format in it
This is how the browser renders the HTML. If we scope the selectors it should fail. We really do not need or , or the case-insensitive not exactly matching regex. We can also extend the third test so that its assert message would trigger, with the incorrect code in question.
Hi Muhammed I'm not sure whether I'm allowed/supposed to reply to these mails - if not, please let me know! Anyway, I did wonder whether I should even raise this as an issue. But given that the test lets the incorrect code through, I felt I should at least flag it as a problem. I don't think it will happen too often, though - they'd need to both misunderstand the instructions and get the closing tag wrong. So, I totally understand the decision to leave this one alone. Thanks for getting back to me. Cheers Moira
Change:
.then((res) => res) ``` <del> Chain the `.then()` method to your `fetch` call. Inside the `.then()` method, add a callback function with `res` as a parameter, then log the `res` to the console so you can see the `Response` object. Open your console and expand the `Response` object to see what it contains. </del> <ins> Chain the `.then()` method to your `fetch` call. Inside the `.then()` method, add a callback function with `res` as a parameter, then log the `res` to the console so you can see the `Response` object. Open your browser console and expand the `Response` object to see what it contains. </ins> Again, don't terminate the code with a semicolon yet.

Discussion:
in step 3 of the fcc authors project (js beta), they mention that we should " Open your console and expand the Response object to see what it contains." but it doesn't actually say that this means we should open the browser's console. It would be best to explicitly say "Open your browser's console and ..." instead. (Also step 4 mentions the console too but if we fix step 3, then hopefully people will remember which console was being referred to when they move to step 4) N/A specific reference to the browser's console is needed so as not to be confused with the fcc console No response N/A No response
I think we should apply the change to both step 3 and step 4 as campers might lose the context if they stop at step 3 and start step 4 some time later. I'm opening this issue to first-time code contributors to this repository. The changes you need to make are: Change "Open your console" to "Open the browser console" in Change "in the console" to "in the browser console" in We typically do not assign issues. Instead, we accept the most quality contribution followed by the one that is made first. 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. Happy contributing.
I have created a PR
Change:
], [ "http://i.imgur.com/GxvrsFb.gif", <del> "Un gif mostrandote como hacer una búsqueda avanzada en Google. Primero, escribimos la consulta "jquery no corre cuando mi página carga". Entonces damos clic en el botón de herramientas y cambiamos la selección de "En cualquier momento" a "en el último año". Entonces hacemos clic en un resultado o leemos a través del artículo y encontramos nuestra respuesta.", "Si eso no ayudo, busca en Google. Buenas búsquedas en Google toman mucha práctica. Cuando buscas en Google, usualmente querrás incluir el lenguaje o framework que estás usando. También querrás limitar los resultados a un período reciente.", </del> <ins> "Un gif mostrándote como hacer una búsqueda avanzada en Google. Primero, escribimos la consulta "jquery no corre cuando mi página carga". Entonces damos clic en el botón de herramientas y cambiamos la selección de "En cualquier momento" a "en el último año". Entonces hacemos clic en un resultado o leemos a través del artículo y encontramos nuestra respuesta.", "Si eso no ayudo, busca en Google. Realizar buenas búsquedas en Google requiere mucha práctica. Cuando buscas en Google, usualmente querrás incluir el lenguaje o entorno (framework) que estás usando. También querrás limitar los resultados a un período reciente.", </ins> "" ], [ "http://i.imgur.com/LZYU7p2.gif", <del> "Un gif mostrandonos como seguir el enlace inferior para ir a nuestra sala de chat de ayuda y preguntar "jquery no corre cuando mi página carga".", "Si eso no te ayudó, preguntale a tus amigos. Si tienes problemas, puedes preguntar a tus compañeros campistas en nuestra sala de chat.", </del> <ins> "Un gif mostrándonos como seguir el enlace inferior para ir a nuestra sala de chat de ayuda y preguntar "jquery no corre cuando mi página carga".", "Si eso no te ayudó, pregúntale a tus amigos. Si tienes problemas, puedes preguntar a tus compañeros campistas en nuestra sala de chat.", </ins> "https://gitter.im/FreeCodeCamp/Help" ], [ "http://i.imgur.com/ZRgXraT.gif", <del> "Un gif mostrandonos nuestro mapa de desafíos.", </del> <ins> "Un gif mostrándonos nuestro mapa de desafíos.", </ins> "Ahora estas listo para empezar a programar. El botón de  "Mapa" en tu esquina superior derecha te mostrará nuestro mapa de desafíos. Te recomendaos que completes los desafíos de arriba hacía abajo, a un ritmo sostenible. Nuestra comunidad de código abierto esta constantemente mejorando nuestros desafíos, así que no te sorprendas si cambian o se mueven alrededor. No te preocupes por volver hacia atrás - solo continúa avanzando. Siempre puedes ir a tu desafío más reciente pulsando el botón de "Aprender".", "" ]

Discussion:
[X] Learn how Free Code Camp Works [X] Create a GitHub Account and Join our Chat Rooms [X] Configure your Code Portfolio [X] Join a Campsite in Your City [X] Learn What to Do If You Get Stuck
Change:
] ], "type": "hike", <del> "challengeType": 6 </del> <ins> "challengeType": 6, "nameEs": "Herramientas de desarrollo de Chrome: Las auditorías", "descriptionEs": [ "La herramienta de auditoría te guía para mejorar tu página paso a paso.", "En este vídeo, se utiliza esta herramienta con un generador de citas aleatorias desarrollado como uno de los proyectos de desarrollo de interfaces.", "Las sugerencias que se ven, se generan automáticamente con la función de auditoría.", "Es importante tenerlas en cuenta para contextualizarlos con el resto de conocimiento que tienes de tu sitio.", "A veces, puede ser que sea lo acertado, pero en ocasiones, por tu situación las sugerencias que da son equivocadas.", "Usa esta herramienta cuando desees mejorar tu sitio o aplicación, pero no sepas por dónde empezar." ] </ins> }, { "id": "56b15f15632298c12f31517d",

Discussion:
[x] Chrome Dev Tools: Elements [x] Chrome Dev Tools: Network [x] Chrome Dev Tools: Sources [x] Chrome Dev Tools: Timeline [x] Chrome Dev Tools: Profiles [x] Chrome Dev Tools: Resources [x] Chrome Dev Tools: Audits [x] Chrome Dev Tools: Console [x] Chrome Dev Tools: Summary
Working on it
Change:
"id": "a5de63ebea8dbee56860f4f2", "title": "Diff Two Arrays", "description": [ <del> "Compare two arrays and return a new array with any items not found in both of the original arrays.", </del> <ins> "Compare two arrays and return a new array with any items only found in one of the original arrays.", </ins> "Remember to use <a href='//github.com/FreeCodeCamp/freecodecamp/wiki/How-to-get-help-when-you-get-stuck' target='_blank'>Read-Search-Ask</a> if you get stuck. Try to pair program. Write your own code." ], "challengeSeed": [

Discussion:
Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2547.0 Safari/537.36</code. My following code successfully satisfies the criteria and all the tests, except one due to an inconsistency. ! The returned array will be sorted due to my method. The last test has no issue with my output being in sorted order, yet expects the output to retain the same order, as my output is not accepted. This is inconsistent, and it should also accept the answer regardless of its order. To bypass this I would have to implement a check to see if one of the given arrays is empty and if so, return the other as is, which is not part of the exercise's criteria.
Thanks guys!

The Bonfire says "Compare two arrays and return a new array with any items not found in both of the original arrays.". If you can't find an item in both arrays then the result will be infinite. The wording may be less confusing if it says: "Compare two arrays and return a new array with any items in the second array that are not found in the first."
Working on this!
"Compare two arrays and return a new array with any items in the second array that are not found in the first or any items in the first array that are not found in the second." i.e. "Return any items which doesn't exist in both the arrays."
Change:
import { bindActionCreators } from 'redux'; import { createSelector } from 'reselect'; import { SearchBox } from 'react-instantsearch-dom'; <del> import { HotKeys, configure } from 'react-hotkeys'; </del> <ins> import { HotKeys, ObserveKeys } from 'react-hotkeys'; </ins> import { isEqual } from 'lodash'; import {

Discussion:
Describe the bug Entering 'n' or 'p' in the solution URL of projects takes me back to the previous('p') or next('n') challenge. To Reproduce to any project section where URL is required 'n' or 'p' in the URL field Expected behavior This should only happen when the text field is not in focus. Desktop (please complete the following information): OS: Windows 10 Pro 32 Bit Pro Browser: Chrome Version: 77.0.3865.90