jiebi/CodeConvo huggingface dataset:
Change:
import React, { Fragment, Component } from 'react'; import PropTypes from 'prop-types'; import { <ins> HelpBlock, </ins> FormControl, FormGroup, ControlLabel

Discussion:
Describe the bug For field in , error state can not be triggered. Warning state will be triggered when an email address with incorrect domain is entered (for example: ). For all fields in , both error and success state can not be triggered. To Reproduce Steps to reproduce the behavior: to http://localhost:8000/settings to fill and to Describe the bug Expected behavior For field in , error state should be triggered instead of warning state. There should only be two states for an email address. Success state is when it is a valid and reachable email address. Error state is when it is an invalid and unreachable email address. For all fields in . Success state is when it is a valid and reachable URL. Error state is when it is an invalid and unreachable URL. Desktop (please complete the following information): OS: Windows 10 1809 Build .832 Browser Latest Chrome Version 77.0.3865.120 (Official Build) (64-bit)
Calling to discuss this from issue . What do you think about this? Are there anything to add or change from the Expected Behavior I described?
the only thing I'm not sure about is 'unreachable'. Do you just mean unreachable because the URL is malformed? Like , for example. If so, then I completely agree. cc
Yes of course. 'Unreachable' is only defined by malformed email format ( valid length, etc) and URL format (protocol, colon, double slash, etc). It is also possible to check the top level domain part against current existing TLD programatically. Other than that, for example checking real email address which is existing should be done by email confirmation / verification.
Change:
The default properties of an `hr` element will make it appear as a thin light grey line. You can change the height of the line by specifying a value for the `height` property. <del> Change the height the `hr` element to be `3px`. </del> <ins> Change the height of the `hr` element to be `3px`. </ins> # --hints--

Discussion:
Hello all! There's a grammar error on Step 68 of Project 2 (CSS Cafe Menu) in the new RWB. It reads: "Change the height the hr element to be 3px." It should read: "Change the height of the hr element to be 3px." Instructions should read: "Change the height of the hr element to read to be 3px." <img width="616" alt="Grammar Error" src="https://user-"- Device: MacBook Pro OS: macOS Monterey v12.3.1 Browser: Safari Version: 15.4 (.1.17.1.13) 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.
Change:
}); } <del> if (!user.name) { </del> <ins> // If the user does not have a name, and have set their name to public, // warn them. Otherwise, fallback to username if (!user.name && user.showName) { </ins> return res.json({ messages: [ {

Discussion:
If there is no name set in the settings, doesn't matter if name is public or private, instead of falling back to username, it gives an error and certificate is not shown
I assume the best UX is for a note to appear, if the Camper tries to set to public, without having first set to something.
the error appears also if name is not set and set to private - certificate does not appear saying that one has to put a name (I'm adding this on top message too)
Picture !
The objective here then is to show the username on the certification if the name is not set ? Maybe some message then must warn the camper that his username will be shown on the certification instead of his real name (I am not sure though that a certification given to a weird username would be ok)
already if the name is private the username is shown, this issue appears if the name is not set
Apologies if this has nothing to do with you, but I vaguely remember you being involved in the discussion I cannot find: Was there any conclusion as to disabling the certification until a Camper has set their name, and made it public?
Sorry for the late response here - The only thing that comes to mind is
Either we would need to remove having usernames as a fallback , or having a public name requirements when displaying certs. I now it might be inconvenient, but I vote for removing the fallback for simplicity and keeping the public name as a requirement.
Discussing in issue triage meeting. a camper sets the to a non-empty string and , the certificate renders with the . .When a camper sets the to an empty string and either or , the certificate does not render and redirects to with a flash message. We should update the behaviour of to mirror the behaviour of , and avoid using the username field as a fallback entirely.
Hello Is this issue solved ?
Change:
"nameEs": "Dale a cada elemento un ID único", "descriptionEs": [ "También quisiéramos referirnos a cada botón por su id utilizando jQuery.", <del> "Dale a cada uno de tus botones un id único, comenzando con <code>target1</code> y terminando con <code>target6</code>." </del> <ins> "Dale a cada uno de tus botones un id único, comenzando con <code>target1</code> y terminando con <code>target6</code>.", "Asegúrate que <code>target1</code> a <code>target3</code> queden en <code>#left-well</code>, mientras que <code>target4</code> a <code>target6</code> queden en <code>#right-well</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:
**Instructions:** Write a function `insertionSort` which takes an array of integers as input and returns an array of these integers in sorted order from least to greatest. <del> **Note:** We are calling this function from behind the scenes; the test array we are using is commented out in the editor. Try logging `array` to see your sorting algorithm in action! </del> # --hints-- `insertionSort` should be a function.

Discussion:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: The challenge description says there is not a commented out array there I wouldn't know how to change that other than deleting the paragraph entirely Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Google Chrome Browser Version: 87.0.4280.77 Operating System: iOS 14.1 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):
Description is wrong. Code placeholder was changed in - test array moved from comment to function call argument, but description stayed same without any edits.
This seems quite reasonable. I will open this up to first timers
An issue with the help wanted or first timers only label is open for contribution. The first comprehensive PR created will be reviewed and merged. 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
I would Like to contribute to your cause i am a first timer and have not yet worked in big project but i want to start by freecodecamp
thank you for wanting to contribute, this issue has already a linked PR. Take a look at other issues with label "first timers only" and "help wanted" that do not have already a linked PR
Change:
{`Your `} {this.getFormatedAmountLabel(donationAmount)} {` donation will provide `} <del> {this.convertToTimeContributed(donationAmount, duration)} </del> <ins> {this.convertToTimeContributed(donationAmount)} </ins> {` of learning to people around the world`} {duration === 'onetime' ? `.` : ` each ${duration}.`} </p>

Discussion:
Currently the donate page always has the left-most value selected by default. Instead, we want the center value selected by default. For example, here we would want the 50 is selected by default): <img width="517" alt="Supportournonprofit_freeCodeCamp_org" src="https://user-"

At freeCodeCamp's current level of efficiency, every dollar donated to our nonprofit translates to 50 hours worth of learning. Both the One-time and Annual options have the correct amounts, but for some reason the monthly doesn't have the correct amount: $50 should be 25,000 hours: <img width="507" alt="SupportournonprofitfreeCodeCamporg" src="https://user-"$35 should be 1,750 hours: <img width="517" alt="SupportournonprofitfreeCodeCamporg" src="https://user-"$5 should be 250 hours: <img width="522" alt="Supportournonprofit_freeCodeCamp_org" src="https://user-"
~The hour is calculated for the month like we discussed? For example $5: ~ Edit: Never mind, I realised the issue. Will fix.
Change:
} .monaco-menu .action-label { <del> color: rgb(var(--highlight-color)); </del> <ins> color: var(--highlight-color); </ins> letter-spacing: 0.02em; }

Discussion:
If I try to select text with my mouse so I can copy/paste it or something - the selected text has the same background as the rest of the page. Making it difficult to see what is selected, and frustrating to try and select, well anything. ! This seems to occur across the entire site. Perhaps it was intentional or something, but I don't think it's a good ux. Note: the text does actually get selected, so you can still copy/paste it. Tested on Chrome and Firefox
Good catch. It'll be this PR: which didn't scope the change to challenge descriptions. I'll put together a quick fix. Edit: nevermind, it's just that has to be passed four values, not two. I don't quite understand how this ever worked.
Change:
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)`.

Discussion:
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.
Change:
assert.match(code, /localStorage.setItem(("|')data1/) ``` <del> Your `localStorage.setItem()` should have a key of `myTaskArr`. </del> <ins> Your `localStorage.setItem()` should have a value of `myTaskArr`. </ins> ```js assert.match(code, /localStorage.setItem(("|')data1,s*myTaskArr);?/)

Discussion:
So the problem is that the “hint” where it tells you what you should’ve have coded it tells you that you should have “data” as key, when you code that and it doesn’t work it tells you you should have “myTaskArr” as key, but that’s wrong it should tell you “myTaskArr” as “value”. So I was trying to have 2 keys, and obviously it was always wrong. The hint should tell you that "myTaskArr" is a value, not a key as it currently says. ! Device: Desktop PC OS: Windows 10 Browser: Edge Version: [e.g. 22] 120.0.2210.121
Note: Due to PR adding one more step, earlier in this project, the relevant step in codebase is 49 now. Although that change did not yet reach the production at this time.
Change:
return array; // Only change code above this line } <del> insertionSort([1, 4, 2, 8, 345, 123, 43, 32, 5643, 63, 123, 43, 2, 55, 1, 234, 92]); </del> ``` # --solutions--

Discussion:
The following challenges have an example function call in the seed code. These function calls should be removed and the related tests should be clarified to reflect the call instead. This sorting challenge is correct and could be used for reference.
Hi, nhcarrigan. I'd like to try to help and solve it. I'm still learning about the project so I would like to ask a question so I can understand the issue better. There is a function call in the file.. bubleSort([1,2,3....]) (example: implement-bubble-) ! And it should be removed from the seed section and transferred to here, similarly to implement-quick-sort: ! ! Is it correct or are there other files that I should be concerned about?
That is correct, yes - this same change should be completed on the four files I've linked. I would, however, recommend holding off on working on this until we receive additional consensus that this is the best way to proceed. If you run in to any questions, feel free to review our or ask in our or the .
Sounds great!! Thanks for the fast response. I will wait until further notice.
Hi MuriloMarquesSantos, are you still interested in fixing this issue?
Change:
A pyramid generator is a program where you can set the type of character, the count for the pyramid, and the direction of the pyramid. The program will then generate a pyramid based on those inputs. <del> Click on the `"Check your code"` button to proceed to the next step and start the project. </del> <ins> Click on the "Check your code" button to proceed to the next step and start the project. </ins> # --hints--

Discussion:
There are some small issues that need to be fixed in the following files: optionfor elementsinline"Check your code" String` This looks like something that can be fixed by "first-time" code contributors to this repository. The files you should look at to work on a fix are those linked above. 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.
Hi I'd like to work on this issue. Thanks
Hey 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.
Change:
"Las funciones que aceptan argumentos deben aceptar sólo uno, y este tiene que ser una cadena.", "Estos métodos deben ser el único medio para interactuar con el objeto.", "Recuerda utilizar <a href='//github.com/FreeCodeCamp/freecodecamp/wiki/FreeCodeCamp-Get-Help' target='_blank'>Leer-Buscar-Preguntar</a> si te sientes atascado. Intenta programar en pareja. Escribe tu propio código." <ins> ], "titleIt": "Crea una Persona", "descriptionIt": [ "Completa il costruttore dell'oggetto con i metodi specificati qui sotto:", "<blockquote>getFirstName()ngetLastName()ngetFullName()nsetFirstName(first)nsetLastName(last)nsetFullName(firstAndLast)</blockquote>", "Esegui i test per vedere il risultato atteso per ogni metodo.", "I metodi che richiedono un argomento devono accettarne solo uno e questo deve essere una stringa.", "Questi metodi devono essere l'unica maniera possibile di interagire con l'oggetto.", "Ricorda di usare <a href='//github.com/FreeCodeCamp/freecodecamp/wiki/FreeCodeCamp-Get-Help' target='_blank'>Leggi-Cerca-Chiedi</a> se rimani bloccato. Prova a programmare in coppia. Scrivi il codice da te." </ins> ] }, {

Discussion:
Advanced Algorithm Scripting () Translate the challenge Advanced Algorithm Scripting in Italian
I'll be working on this
Change:
} test.add(4); test.add(1); <ins> test.add(1); </ins> test.add(7); test.add(87); test.add(34);

Discussion:
When adding a new node ( or element ) to a binary search tree, I was supposed to compare the value supplied method with that of current node. But it seems odd to me that, despite not doing it at all, the testing script somehow ignored it. Here's the code I wrote I expect the unit test case to fail instead of to succeed. Also, if I slightly edit this LOC here: to Then I expect the said unit test case to pass. No response Device: Dell Latitude 5580 OS: Ubuntu 22.04 Browser: Brave Browser Version: 1.45.127 No response
is taking a look and this and will create a PR if a fix is identified.
The reason the "The add method should add elements according to the binary search tree rules." test passes is because the test does not test for adding duplicate keys. I've a pr that changes the test so it adds a duplicate key, and the solution in the docs still works. The code you wrote now fails (correctly). Your intended fix of changing to does not work, as if cr[direction] is null, you can't get its .value
Change:
padding: 0; } <del> .sidebar ul li a { </del> <ins> .sidebar ul li a, .search a { </ins> color: var(--quaternary-color); } <del> .sidebar ul li > a:hover { </del> <ins> .sidebar ul li > a:hover, .search a:hover { </ins> color: var(--primary-color); }

Discussion:
Describe the bug if you type something in searchbar while using the dark mode, and hover over the produced links, it will hide the link. To Reproduce Steps to reproduce the behavior: to '' something over it how the hover is hiding the result Screenshots ! Browser: chrome
Can you please assign this to me
Hi I've been looking into the issue you reported regarding dark mode and hover behavior on the search results. I'd like to contribute a fix, but I'm having trouble locating the exact code or files that need modification. Could you please provide more specific details about the file or code that's related to this issue? A direct link to the relevant code or even just the file path would be immensely helpful. Your guidance would ensure that I'm making the correct changes to address this problem effectively. Thank you!
Change:
assert.match(code, /consts+updates*=s*(?:(s*events*)|event)s*=>s*{s*consts+elements*=s*event.targets*;?s*consts+values*=s*element.value.replace(s*/s/gs*,s*('|"|`)1s*)s*;?s*ifs*(/); ``` <del> Your `if` condition should check if `value` includes the `id` of the `element`. </del> <ins> Your `if` condition should check that `value` does not include the `id` of the `element`. </ins> ```js assert.match(code, /consts+updates*=s*(?:(s*events*)|event)s*=>s*{s*consts+elements*=s*event.targets*;?s*consts+values*=s*element.value.replace(s*/s/gs*,s*('|"|`)1s*)s*;?s*ifs*(s*!value.includes(s*element.ids*)/);

Discussion:
The wording of the hint text does not match the instructions. The word not is missing from the hint. js (code, /consts+updates=s(?:(sevents))1s)s;?sifs(/); Your condition should check if includes the of the . Your condition should check if does not include the of the . ! NA No response
For some more context, the challenge is expecting , but if you input something like this: (no ), the hint is ifvalueidelement It should check that it does not include the id. So we can change the hint to the suggestion - I would change to though: ifvalueid.`` What do you think
Your condition should check that does not include the of the element. Sounds good.
Sounds like there is a conclusion for what to change the hint to, so I am opening this for contributions
Change:
"challengeType": 0, "nameEs": "Crea un encabezado personalizado", "descriptionEs": [ <del> "Crearemos un encabezado simple para nuestra aplicación de fotos de gatos poniéndolos en la misma línea.", </del> <ins> "Crearemos un encabezado simple para nuestra aplicación de fotos de gatos poniendo el título y la relajante imagen del gato en la misma línea.", </ins> "Recuerda, Bootstrap usa un sistema de cuadrícula adaptativo, el cual facilita poner elementos en filas y especificar el ancho relativo de cada elemento. La mayoría de las clases de Bootstrap pueden aplicarse a un elemento <code>div</code>.", "Aquí hay un diagrama del funcionamiento de la cuadrícula de 12 columnas Bootstrap:", "<a href="http://i.imgur.com/FaYuui8.png" data-lightbox="img-enlarge"><img class="img-responsive" src="http://i.imgur.com/FaYuui8.png" title="Pulsa para agrandar" alt="una imagen que muestra el sistema de cuadrícula de Bootstrap"></a>",

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:
## --answers-- <del> `What do she does as our team lead?` </del> <ins> `What do she does as the team lead?` </ins> ### --feedback--

Discussion:
The fill-in-the-blank sentence doesn't match what the character says. The written sentence is: The character says: Note the "the", instead of "our". No response Device: all OS: all Browser: all Version: all No response
Thank you for reporting the issue. Note for maintainers: Step 54 () uses "our" instead of "the" in the quiz. I think it's fine as-is since there isn't associated audio/caption text, but I'd vote updating it, too, for consistency. This issue is open to first-time code contributors to this repository. Requirements: In Change the text in the tag from to In Change the text in the tag from to Change the fill-in-the-blank text from to Change the backtick placement in the description text from ` In Change the text of the answers from to 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.
Hi I've created a PR addressing these changes.