jiebi/CodeConvo huggingface dataset:
Change:
"</div>" ], "challengeType": 0, <del> "type": "waypoint" </del> <ins> "type": "waypoint", "nameEs": "Activa eventos de pulsación con jQuery", "descriptionEs": [ "En esta sección, vamos a aprender cómo obtener datos de las APIs. Las APIs - o interfaces de programación de aplicaciones - son herramientas que utilizan los computadores para comunicarse entre sí.", "También aprenderemos cómo actualizar HTML con los datos que obtenemos de estas API usando una tecnología llamada Ajax.", "En primer lugar, vamos a revisar lo que hace la función <code>$(document).ready()</code>. Esta función hace que todo el código dentro de ella se ejecute sólo hasta que nuestra página ha sido cargada.", "Hagamos que nuestro botón "Get message" cambie el texto del elemento con clase <code>message</code>.", "Antes de poder hacer esto, tenemos que implementar un <code>evento de pulsación</code> dentro de nuestra función <code>$(document).ready()</code>, añadiendo este código:", "<code>$("#getMessage").on("click", function(){</code>", "", "<code>});</code>" ] </ins> }, { "id": "bc000000000000000000001", <del> "title":  "Change Text with Click Events", </del> <ins> "title": "Change Text with Click Events", </ins> "description": [ "When our click event happens, we can use Ajax to update an HTML element.", "Let's make it so that when a user clicks the "Get Message" button, we change the text of the element with the class <code>message</code> to say "Here is the message".",

Discussion:
[x] Trigger Click Events with jQuery [x] Change Text with Click Events [x] Get JSON with the jQuery getJSON Method [x] Convert JSON Data to HTML [x] Render Images from Data Sources [x] Prefilter JSON [x] Get Geo-location Data
Trabajando en esta
Change:
Return an array with the current date in the formats: <ul> <li>2007-11-23</li> <del> <li>Sunday, November 23, 2007</li> </del> <ins> <li>Friday, November 23, 2007</li> </ins> </ul> <del> Example output: <code>['2007-11-23', 'Sunday, November 23, 2007']</code> </del> <ins> Example output: <code>['2007-11-23', 'Friday, November 23, 2007']</code> </ins> </section> ## Instructions

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 sample output in the sidebar has the date . The date should read . Source: and many other websites. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Firefox Browser Version: 82 Operating System: Linux Mint
Looks like a fix would entail editing the challenge - the tests themselves appear to be accurate. I will open this up to first timers. thanks for the catch!
Change:
{ name: 'keywords', content: metaKeywords.join(', ') } ]} > <ins> <link as='font' crossOrigin='anonymous' href={latoRegularURL} rel='preload' type='font/woff' /> <link as='font' crossOrigin='anonymous' href={latoLightURL} rel='preload' type='font/woff' /> <link as='font' crossOrigin='anonymous' href={latoBoldURL} rel='preload' type='font/woff' /> <link as='font' crossOrigin='anonymous' href={robotoRegularURL} rel='preload' type='font/woff' /> <link as='font' crossOrigin='anonymous' href={robotoBoldURL} rel='preload' type='font/woff' /> <link as='font' crossOrigin='anonymous' href={robotoItalicURL} rel='preload' type='font/woff' /> </ins> <style>{fontawesome.dom.css()}</style> </Helmet> <WithInstantSearch>

Discussion:
Describe the bug When you reload a page two style issues appear. The placeholder text moves slightly once the page has fully loaded. The search hits are briefly bold To Reproduce Steps to reproduce the behavior: to (or any page with search) the placeholder text move on the search bar anything the result appear briefly as bold, then change to a normal weight Expected behavior The page should start with the styles it ends up getting. Screenshots !
Hey, I wanna help with it. Where can I find the code for it? (First time contributing)
I'm not 100% sure where the problem is, but the , and components are all involved to some degree. Somehow the are not getting the right classes when first rendered I think. I'm planning to take a closer look myself, tomorrow, but you're welcome to submit a PR/share any insight. As you wish!
It turns out it wasn't anything to do with those components. The problem is that the font doesn't get loaded until it's needed - in this case when the search results appear. That causes a brief flash of and that's the cause of the problem. I'm going to look into pre-loading the fonts and clear this up.
Change:
onClick={() => togglePane('showPreviewPortal')} > <span className='sr-only'>{getPreviewBtnsSrText().portal}</span> <del> <FontAwesomeIcon icon={faExternalLinkAlt} /> </del> <ins> <FontAwesomeIcon icon={faWindowRestore} /> </ins> </button> </div> </div>

Discussion:
A camper mentioned in his comment, that this icon below indicate to them that it's an external link not a popup. ! We can change it to clearer icon that show, that it's a popup. The original comment for context:
I found it interesting, that say you should use ellipsis (…) when there is some additional action required after the action (popup, dialog, confirmation) and it isn't clear by the action itself. This doesn't mean you should use an ellipsis whenever an action displays another window only when additional information is required to perform the action. Consequently, any command button whose implicit verb is to "show another window" doesn't take an ellipsis, such as with the commands About, Advanced, Help (or any other command linking to a Help topic), Options, Properties, or Settings. So maybe an ellipsis of some kind: in button's label or in the icon? More so, it's a part of too. If we were to stick with keeping an icon regardless, this regular feels like a better choice, with the arrow denoting there would be some kind of external interface but the enclosed square representing that it is not an external redirection, thus denoting some kind of popup or modal.
I think these guides are saying that the ellipses should be when the button opens a window that requires the user to enter more information or perform another action. This isn't the case here, so I don't think they are warranted in this instance. If we want to use a new icon then I would suggest we use one that has . I'm not suggesting that we use this exact icon. This is just an example of what I'm suggesting.
I second the use of some kind of variation of that icon. There's a small issue though, there's no such icon in the font awesome library for this so we'll have to find a different way to implement this.
Font awesome has an icon that could have the same meaning: Alternatively Material Icons has a specific preview icon if these can be used?
can you assign me this task?
issues with label, aren't open for contribution yet. You can however browse the label help wanted for open issues
allright sir
Both and both are plausible.
I'd suggest we should move forward to replace the icon with the icon. Should I move ahead and send over a PR? This is the output - !
Sure. Just make sure we don't need to add other dependencies to get that icon.
Change:
5. Install a code editor of your choice. <del> We highly recommend using [Visual Studio Code](https://code.visualstudio.com/) or Android Studio. We also recommend installing the official [extensions](https://docs.flutter.dev/get-started/editor?tab=vscode) </del> <ins> We highly recommend using [Visual Studio Code](https://code.visualstudio.com/) or Android Studio. We also recommend installing the official [extensions](https://docs.flutter.dev/get-started/editor?tab=vscode). </ins> ## Fork the repository on GitHub

Discussion:
in the docs, there is a line that is missing period at the end of it. These should have period in the end of it Here is the markdown file Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first. Happy contributing.
I will work on that
Change:
3. 帮助我们为[YouTube频道视频](https://www.youtube.com/channel/UC8butISFwT-Wl7EV0hUK0BQ/videos)添加字幕。 <del> ##贡献予开源代码库 </del> <ins> ## 贡献予开源代码库 </ins> 我们有数以千计的[编码挑战](https://learn.freecodecamp.org)和[指南文章](https://guide.freecodecamp.org)集中在这个庞大的开源代码库中。

Discussion:
Describe your problem and how to reproduce it: Anchor links such is not working properly in several languages. For sure is not working in: Russian, Spanish, Chinese languages. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: Version 74.0.3729.169 (Official Build) (64-bit) Operating System: Windows 10 Pro 1809 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !
These 3/4 PRs (exlude one - which I PR'd to my own forked-repo) may close this issue. Please review them.
Change:
shift = 3 --fcc-editable-region-- def caesar(): <ins> --fcc-editable-region-- </ins> alphabet = 'abcdefghijklmnopqrstuvwxyz' encrypted_text = ''

Discussion:
In the Building a Cipher project, comment is first mentioned in step 51: But in step 59, we actually introduce comment and its syntax: In step 51, we introduce function parameters, so I think mentioning comment here would be a little overwhelming. I think the comment introduction should either be moved to an earlier challenge or kept in step 59. If we move the comment introduction to an earlier challenge, step 51 can be kept as-is. But if we keep comment introduction in step 59, we should update step 51. Instead of asking the users to comment out the code, I wonder if we could ask them to remove the line entirely (though the code is in step 50, so it's probably a little odd to immediately remove it in the next step).
This does seems to be out of sequence. I would suggest to not comment out in step 51 and let the exception be(the resolution is there in the coming steps). This part of the instruction can be updated from: to:
If we don't ask to comment out the function call in step 51 and tell the campers they will work on fixing the error in the next steps, it would be logic to address the error in the console () and require to pass the two positional arguments to the function call in step 52. But then the function will seem to work fine, although it's still using the and variable inside its body instead of the function parameters. The alternative is to ignore the in the console for step 52, and address it directly in step 53. For that we should simply keep the function call instead of commenting it out and there is no need to swap the step order. Honestly, I don't like particularly any of these options.
Change:
## --seed-contents-- ```html ``` # --solutions--

Discussion:
An empty solution seed with the following format does not parse correctly in Crowdin: ! Adding an empty new-line between the backtick lines will parse correctly in Crowdin: ! The following files have empty seeds with the first format and need a blank line : JavaScript / Basic JavaScript comment your javascript code declare javascript variables declare string variables initializing variables with the assignment operator passing values to functions with arguments return a value from a function with return write reusable javascript with functions JavaScript / ES6 create a javascript promise JavaScript / Object Oriented Programming define a constructor function Front End Libraries / Bootstrap Create a bootstrap headline Front End Libraries / React Create a complex jsx element Quality Assurance Projects metric imperial converter Coding Interview Prep / Data Structures Create an ES6 Javascript Map
Hi, I'll add those blank lines. It'll be my first time contributing to an open-source project, though.
Please visit to find all the info you will need to get started with contributing a fix for this issue.
Alright. I'll go through the documentation.
Hi. First time contributor here. I have forked the free code camp files to my github page. I have cloned them locally, opened the appropriate folders into my VSCode editor and made the changes (though I was not able to find a # --seed-- in Quality Assurance Projects: metric imperial conversion) but now I have no idea of how to get the code back here. Is there some documentation with instructions on how to do that? Thanks in advance.
Change:
.container <del> .row.flashMessage.negative-30 </del> <ins> .row.flashMessage </ins> .col-xs-12.col-sm-8.col-sm-offset-2.col-md-6.col-md-offset-3 if (messages.errors || messages.error) .alert.alert-danger.fade.in

Discussion:
We need to push these notifications down so there's a reasonable space between them and the navbar (perhaps 20px?). !
It's been years since I've done a PR :) I managed to have the website downloaded locally and all that. It seemed that the overlapping was caused by a class negative-30 that gave a margin-top: -30px. Removed it for flash partial view. It is also used in 2 other places but not sure right now if needed or not.
Thanks for your PR. CamperBot automatically closed it. Could you follow its instructions and try again? We'd value your help with this.
Sure thing. I actually made a separate branch (as in the instructions) but what I did was merge that branch into main one and did the PR from the main one. Now, I realise that I should have made the PR from that branch so that CamperBot will work.
Change:
<br /> <br /> **Projects**:  [Random Quote Machine](https://www.freecodecamp.org/learn/front-end-libraries/front-end-libraries-projects/build-a-random-quote-machine), [Markdown Previewer](https://www.freecodecamp.org/learn/front-end-libraries/front-end-libraries-projects/build-a-markdown-previewer), [Drum Machine](https://www.freecodecamp.org/learn/front-end-libraries/front-end-libraries-projects/build-a-drum-machine), [JavaScript Calculator](https://www.freecodecamp.org/learn/front-end-libraries/front-end-libraries-projects/build-a-javascript-calculator), [25 + 5 Clock](https://www.freecodecamp.org/learn/front-end-libraries/front-end-libraries-projects/build-a-25--5-clock) #### 4. Data Visualization Certification - [Data Visualization with D3](https://learn.freecodecamp.org/data-visualization/data-visualization-with-d3)

Discussion:
This is a broken link. <img width="1440" alt="Screen Shot 2020-09-21 at 12 43 27 PM" src="https://user-"<img width="1148" alt="Screen Shot 2020-09-21 at 12 43 55 PM" src="https://user-"Recommended fix, suggestions (how would you update it?): Two ideas for fixing this come to mind: In the , we want to change both links to match the current application. Here is the code that should be to fix the issue: Set up routes for the old paths to redirect to the current paths. I'm unsure of exactly how to do this.
Change:
cursor: pointer; } <ins> #nav-lang-menu li:first-child { border-bottom: 0.1rem solid var(--gray-45) !important; } </ins> button.nav-link:focus { color: var(--tertiary-color); background-color: var(--tertiary-background);

Discussion:
The language selection menu is not intuitive about the no. of available options. It's a bit paradoxical at the moment: You will not notice additional options until you start scrolling while being on top of the options. You will not start scrolling until you know there are additional options. to '/learn' on 'Menu' down to 'Change Language' the cursor on the options Scrolling while being in the area of the listed options. menu should be very clean and intuitive. "Cancel Change" option should have some form of visual separation. https://user- Device: All Devices OS: All OS Browser: All Browsers Version: All Versions No response
this will start becoming evident with more languages on the list. The quickest and simplest way this can be handled is by slightly increasing the height of the list and decreasing the height of the hover-state highlight (each item). That will leave some space at the bottom of the last item, intuitively letting the user know there is more to be looked at. Currently, the perfect-sized (height) items and the overall height of the list make it difficult to notice more entries. Finally, that "Cancel" option should be a different color or have some form of visual separation.
is this issue still being worked on? If not, I would like to take it.
That makes sense, I thought we fixed that. should be removed for and
or anyone else interested, this is up for grabs.
This is what makes the language menu full length so no vertical scroll bar appears. Originally, I had the language menu set so that a vertical scroll bar would appear if it was taller than the main menu. But it was decided that there shouldn't be a vertical scroll bar, the language menu should be as tall as necessary so no scroll bar was needed. Is this what we still want? Even as we continue to add even more languages?
thanks for bringing this up. Ideally we would need to show as many languages as possible in a viewport and display a minified scroll bar if the list exceeds the height viewport minus of the navigation. We could show a scrollbar initially as you recommended, but the dropdown needs expand further than the main menu if needed.
Change:
# --description-- <del> Congratulations! You finished the lessons on React and Redux. There's one last item worth pointing out before you move on. Typically, you won't write React apps in a code editor like this. This challenge gives you a glimpse of what the syntax looks like if you're working with npm and a file system on your own machine. The code should look similar, except for the use of `import` statements (these pull in all of the dependencies that have been provided for you in the challenges). The "Managing Packages with npm" section covers npm in more detail. </del> <ins> Congratulations! You finished the lessons on React and Redux. There's one last item worth pointing out before you move on. Typically, you won't write React apps in a code editor like this. This challenge gives you a glimpse of what the syntax looks like if you're working with a file system on your own machine. The code should look similar, except for the use of `import` statements (these pull in all of the dependencies that have been provided for you in the challenges). </ins> Finally, writing React and Redux code generally requires some configuration. This can get complicated quickly. If you are interested in experimenting on your own machine, the <a href="https://www.freecodecamp.org/news/install-react-with-create-react-app/" target="_blank" rel="noopener noreferrer nofollow">Create React App</a> comes configured and ready to go.

Discussion:
Currently, the instructions in module, mention about subsection, which is a subsection of a completely different course ( i.e. course ). At the moment, those instructions in module, only mention the name of the "Managing Packages with NPM" subsection and no link has been provided to that particular subsection. Keeping that in mind, I believe to make it easier for the user to navigate to the subsection from within the instructions of module, a link to the subsection should be provided within the module. Hence, taking the above point into consideration, I believe the last line in the first paragraph of module, should be changed from: To The last line in the first paragraph of module, should be changed to: <img width="1440" alt="image" src=""
can i can solve the above issue?
Hello! can I solve this bug.
Personally, I would entirely remove that sentence. It is not common to maintain the links across the challenges, and it does not really provide useful information, as Campers are not expected to go directly to the npm section. On top of that, I would remove the mention of in all sentences - npm != React; there is nothing special about import statements, and there is no direct link between npm and import statements.
Thanks for the feedback your comment makes a lot of sense. Taking your suggestion into consideration, what do you think about the following:
Hello, can I resolve this issue?
Iooks decent. I would leave in the bit about:
Thanks for the confirmation ! I will go ahead and create a PR then. Cheers!
Change:
overflow-wrap: anywhere; } <ins> :not(pre) > code { border: 1px solid var(--secondary-color); } </ins> .challenge-instructions code { white-space: break-spaces; }

Discussion:
Unnecessary borders are displayed around each line in the solution code of certification projects. For example: to someone's certification page on 'View' ('View Code') to see the solution code Each line in the solution code should not have borders around it ! Device: Laptop OS: Windows 10 Browser: Chrome Version: 114.0.5735.199 (Official Build) (64-bit) The border seems to be in
Hi the borders on the code doesnt seem to be a good UX. I would like to take up this issue.
Hello! I would like to work on this issue. Seems to be a quick fix.
Hey. Contributions are very welcome. Please take a look at to get started.
! Would this sample look better ?
I have fixed the issue and created a pull request . Please review it and let me know if there are any concerns.
To solve the issue move the properties in , to CSS selector that affects the challenges' layout, or doesn't affect the setting layout.
Simply removing the border property in fixes the issue ! ! Is it fine if done this way? I have reverted the changes I made to the bootstrap file back to its original form.
How can we find those code files from the repo ? If the particular link to the file is not provided in the issue.
Hello I would like to request to be assigned to fix this
Hi! I would like to take up this issue
Change:
.night .footer a:hover { color: #606f7b; <ins> outline-offset: 1px; outline: 1px dashed #A0A0A0; </ins> }

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: At the moment, the clickable area of footer links are spanning the full width of their parent div. I'm not sure if this is on purpose, but IMHO, they should fit to their content instead, since a user could get navigated to another page if they accidentally click somewhere within the clickable area. This issue is on , but it is down for maintenance at the moment. The screenshot is of my local fCC. !
Is that actually a problem, though? I think having list items spread like that is pretty common. It could be a problem if you aimed for, say, Learn and got News, but there's a reasonable amount of space between them. How about if the box were subtly highlighted on hover?
Thanks for the threads
Tbh, this is the first time I have seen footer items spread like that, though it is common to me to see that on a navbar. I have no problem with leaving it as is, but adding background color on hover would be great.
I, personally, would prefer if only the text was clickable - but it works either way.
Personally I like the wider boxes, because I'm lazy and click in the general vicinity of things. So, I've a PR for the highlight approach, since that was a really easy fix. If that doesn't seem right we can always shrink the links onto the text.