jiebi/CodeConvo huggingface dataset:
Change:
**Tips** <del> - You can use the `el.style.display` property to show the `resetGameBtn` button and hide the `optionsContainer`. </del> <ins> Use the `style.display` property on an element, with the value `"block"` or `"none"`, to show or hide the element. </ins> # --hints--

Discussion:
In the last part of step 5 in the rock, paper, scissors review project, the instructions given say: If there is a winner, you will want to show the resetGameBtn button and hide the optionsContainer so the player can play again. Tips You can use the property to show the resetGameBtn button and hide the optionsContainer. I have 2 concerns here. 1- at no point is there any mention of what type of display the resetGameBtn requires (is it block, inline-block, flex...?) I guessed 'block' which worked but the lack of this detail made me hesitate. 2- the mention of '' is confusing. In the previous project, using style.display was discussed before in the rpg project () but it was never referred to or mentioned as '' before. I wasn't sure if 'el' meant the element in question or if there was an actual 'el' variable somewhere. I ended up going with what made sense (replacing the 'el' with the element reference) but I'm not sure how easy this would be for someone with only the last few js projects under their belt. A clarification would be great here. N/A N/A No response N/A No response
I fixed the wording of the challenge to make it more clear to the user.
This issue has not been triaged yet, in the future please do not create a PR until then. Anyway, I will open it up to contribution.
my bad sir, won't happen again.
Change:
return null; } <del> const { solution, githubLink, challengeFiles } = completedProject; </del> <ins> const { solution, githubLink, files } = completedProject; </ins> const onClickHandler = () => setSolutionState({ projectTitle, <del> challengeFiles, </del> <ins> files, </ins> solution, isOpen: true }); <del> if (challengeFiles) { </del> <ins> if (files) { </ins> return ( <button className='project-link-button-override'

Discussion:
When trying to view a JS solution, the following error appears in dev, explaining the issue in production. It seems we followed the expected prop-types too early (ref: ). The object is still an object literal. Reported on forum:
I have the same problem as I said in the forum, the bottom error says it responded with 404 to the request for the certification on JS algorithms and data structures. Seems like there's an issue with the backend reaching that certification. !
Change:
<main> <Spacer size={2} /> <FullWidthRow> <del> <Button block={true} bsSize='lg' bsStyle='primary' className='btn-invert' href={`/${username}`} </del> <ins> <Link className='btn-invert btn btn-lg btn-primary btn-block' to={`/${username}`} </ins> > Show me my public portfolio <del> </Button> </del> <ins> </Link> </ins> <Button block={true} bsSize='lg'

Discussion:
To reduce making api calls we should use Link from client/src/components/helpers/Link that utilizes Gatsby Link.
I can take a look at this one
Change:
.donation-form { display: flex; flex-direction: column; <del> width:80%; </del> <ins> width: 80%; </ins> justify-content: center; margin: 0 auto; }

Discussion:
!
Could you give a link to the page as then it might be easier to solve the issue?
This should be the case on the user's profile page. You can reproduce by setting the certificate keys to true in the user object.
I could work on this!
I am already working on it.
Thanks for letting me know!
a reasonable fix would be to give the grid that contains the profile a class and on the css, change the button under that class and have . you will end up with something like this. here it is on small and large screens <img width="681" alt="screen shot 2019-02-22 at 2 18 10 pm" src="https://user-"<img width="1095" alt="screen shot 2019-02-22 at 2 17 53 pm" src="https://user-"
Similar solution could be applied to these donate buttons probably. but the selectors should be very specific not to change the styling on other buttons in the platform. <img width="669" alt="screen shot 2019-02-23 at 2 09 14 pm" src="https://user-"<img width="502" alt="screen shot 2019-02-23 at 2 08 51 pm" src="https://user-"
Hey or Can you take this up? just updated us that he will be a bit busy with other things.
I'm on it
Change:
| Input number | Output number                         | | ------------ | ------------------------------------- | | 7259         | <code>2 hr, 59 sec</code>             | <del> | 728640059    | <code>1 d</code>                      | </del> <ins> | 86400        | <code>1 d</code>                      | </ins> | 6000000      | <code>9 wk, 6 d, 10 hr, 40 min</code> | <div style="font-size:115%; font-weight: bold;">Details</div>

Discussion:
In this table, the left column represents the same duration as in the right column, but in seconds. The left middle-left cell should be instead of . <img width="293" alt="2021-05-25 -Learn Rosetta Code Convert seconds to compound duration freeCodeCamp org" src="https://user-"
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 our chat room or the forum 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:
# --hints-- <del> You should call the `square_root_bisection` function with the `N` variable as the argument and print the result. </del> <ins> You should call the `square_root_bisection` function with the variable `N` as the argument. </ins> ```js ({

Discussion:
this makes look like you need to use , but the function call is enough to cause an output to the terminal. Possible solutions: NA NA NA No response
I'd update the instructions removing the part.
Hi, I'm looking to contribute to open source, could I take this ticket on as a way to onboard to this codebase? And also what is the process usually for grabbing a ticket and pushing a PR?
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:
## Instructions <section id='instructions'> <del> Use multiple <code>conditional operators</code> in the <code>checkSign</code> function to check if a number is positive, negative or zero. </del> <ins> Use multiple <code>conditional operators</code> in the <code>checkSign</code> function to check if a number is positive, negative or zero. The function should return "positive", "negative" or "zero". </ins> </section> ## Tests

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 instruction of challenge only tells user what they need to do, but not what their code should return. User would need to scroll down to see what the tests expect, in order to complete the challenge. Add a Link to the page with the problem:
Change:
# --description-- <del> Another important `meta` tag for accessibility and SEO is the `description` definition. The value of the `content` attribute is used by search engines to provide a description of your page. </del> <ins> Another important `meta` element for accessibility and SEO is the `description` definition. The value of the `content` attribute is used by search engines to provide a description of your page. </ins> <del> Add a `meta` tag with the `name` attribute set to `description`, and give it a useful `content` attribute. </del> <ins> Add a `meta` element with the `name` attribute set to `description`, and give it a useful `content` attribute. </ins> # --hints-- <del> You should add a new `meta` tag to the `head`. </del> <ins> You should add a new `meta` element to the `head`. </ins> ```js assert.equal(document.querySelectorAll('meta').length, 3);

Discussion:
related to In the new Responsive Design curriculum the words tag and element are used interchangebly The correct use should be element and tag (or at least, element is the whole thing, tag is the one that start with and end with and can be an opening tag, a closing tag or a self-closing tag). Should this be changed in the new curriculum?
Do we have many/any incorrect uses?
actually mostly not - there is some ambiguity with in the second step of the accessibility quiz I have been hasty
My concern was with these steps, which are about meta tags
That does look like something that should be standardised. Thank you, for listing them. I am opening this issue up for first timers only. The files that need changed are listed in the above reply. What needs changed There are a few uses of the word which should be changed to . Example Original: New: Note Not all uses of the word should be changed. Example: 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. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the
Hi - is it ok if i pick this up? First timer here
Change:
const DEBOUNCE_TIME = 100; <del> const searchClient = algoliasearch(algoliaAppId, algoliaAPIKey); </del> <ins> // If a key is missing, searches will fail, but the client will still render. const searchClient = algoliaAppId && algoliaAPIKey ? algoliasearch(algoliaAppId, algoliaAPIKey) : {}; </ins> const propTypes = { children: PropTypes.any,

Discussion:
Is there any reason not to put the real and in ? I reflexively put in a dummy key when I set this up, but now that I revisit this, that seems like a mistake.
Yes, actually it broke the .dev build unsurprisingly , I think noticed it and reported in the team chat. My bad for not catching this previously. The real fix is to ignore and move ahead when the keys are not available are default. We do this with google application credentials.
Oh, I assume it broke the build because .dev isn't using I didn't think of that... So, we should implement the fix and add the public keys to , right?
I was thinking something more along the lines of (example from api-server): I would try to avoid hundreds of contributors hitting the indexes locally. Ideally people should get their own keys. While the key and index is public, it's still not recommended to hit it?
As for the production keys, it's actually fine because the build should fail. I have since the keys in the build pipeline.
One thing: if we don't want contributors spamming search (fair enough!) I think there should be some docs that let people know what's what. Either that search isn't available in development or the steps they need to take to make it work.
I agree. We should add some docs on getting keys, or perhaps creating a test index and sharing that instead
Change:
extends ../layout-wide block content .row <del> .col-md-4.bonfire-top </del> <ins> .col-md-4 </ins> h4.text-center= name hr ol for step, index in description .row.checklist-element(id="#{dashedName + index}") <del> .col-xs-3.col-sm-1.col-md-2.padded-ionic-icon.text-center </del> <ins> .col-xs-2.col-sm-1.col-md-2.padded-ionic-icon.text-right </ins> input(type='checkbox' class='challenge-list-checkbox') <del> .col-xs-9.col-sm-11.col-md-10 </del> <ins> .col-xs-10.col-sm-11.col-md-10 </ins> li.step-text.wrappable!= step .col-xs-12.col-sm-12.col-md-8 .embed-responsive.embed-responsive-16by9

Discussion:
Anywhere from 1000px width to when the UI goes into responsive mode the numbers on the check list move into it's respective check box. Image posted bellow <img width="1109" alt="screen shot 2015-12-17 at 9 08 15 pm" src=""
Confirmed, although this is a pretty marginal corner case. There is maybe a 200px wide zone where there is overlap.
It happens quite a bit for me. Regardless I just want a softball for my first issue :) , Rex Schrader wrote: * |
This really isn't the issue with new UI (width < 760px). However, now checkboxes are awkwardly too far. !
Change:
"difficulty": 3.04, "description": [ "You can also target elements by their id attributes.", <del> "First target your <code>div</code> element with the id <code>target3</code> by using the <code>$("#target3")</code> selector.", </del> <ins> "First target your <code>button</code> element with the id <code>target3</code> by using the <code>$("#target3")</code> selector.", </ins> "Note that, just like with CSS declarations, you type a <code>#</code> before the id's name.", "Then use jQuery's <code>.addClass()</code> function to add the classes <code>animated</code> and <code>fadeOut</code>.", "Here's how you'd make the <code>button</code> element with the id <code>target6</code> fade out: <code>$("#target6").addClass("animated fadeOut")</code>."

Discussion:
Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. First target your div element with the id target3 by using the $("#target3") selector. div needs changing to button.
This is a duplicate of issue .
Change:
const res = await fetch('https://pokeapi-proxy.freecodecamp.rocks/api/pokemon/red'); // Fetch from proxy to simulate network delay if (!res.ok) { <del> await new Promise(resolve => setTimeout(resolve, 50)); // Brief additional delay to allow the alert to trigger </del> <ins> await new Promise(resolve => setTimeout(resolve, 1000)); // Additional delay to allow the alert to trigger </ins> assert.include(['pokémon not found', 'pokemon not found'], alertMessage.trim().replace(/[.,?!]+$/g, '').toLowerCase()); }

Discussion:
When testing one camper's code it fails some tests unless I increase all the delays to 1000ms, I tested with 500ms but that was not enough. I also saw the example project fail a test but it does pass more consistently (my guess is it is just faster with fewer async functions). To be on the safe side we should have a longer delay. I know 1000ms is a lot but better safe than sorry. Tests: Valid code should not fail because of "timing" issues. 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:
As this is a bug with a certificate project I the showstopper label.
Change:
if (err) { next(err); } <ins> var dashedNameFull = bonfire[bonfireNumber].name.toLowerCase().replace(/s/g, '-'); if (dashedNameFull != dashedName) { return res.redirect('/bonfires/' + dashedNameFull); } </ins> if (bonfire.length < 1) { req.flash('errors', { msg: "404: We couldn't find a bonfire with that name. Please double check the name."

Discussion:
From with feedback as Awesome work with the new radio! It's got much better performance than YouTube. Thought this feature was missing so I a simple version :) One known issue is that the song history won't update immediately after a song completes, but regularly every 20 seconds. This cause a slight delay when songs are changing. Perhaps song history updates could happen once some event inside the embedded coderadio player happens? I don't know what event to listen to, but that would be a significant improvement. !
I can work on creating a Song History component! :) Edit: Here what it looks with what I have: !
Hi everyone, I'm wondering if I can get repo right to push my branch so I can raise a PR for this feature. :)
Hey Brandon! Awesome you worked on this feature! You can fork the repo to your own GitHub account and then push your branch there. Then you can submit the PR even without write access directly to this repo. Have a nice day!
Change:
<ins> const isBrowser = typeof window !== 'undefined'; if (isBrowser) { window.dataLayer = window.dataLayer || []; } function gtag() { if (isBrowser) { window.dataLayer.push(arguments); } } gtag('js', new Date()); gtag('config', 'AW-795617839'); export function gtagReportConversion(url) { var callback = function() { if (typeof url !== 'undefined' && isBrowser) { window.location = url; } }; if (isBrowser) { gtag('event', 'conversion', { /* eslint-disable camelcase */ send_to: 'AW-795617839/AmfiCKHHs4gBEK_UsPsC', event_callback: callback }); } return false; } </ins>

Discussion:
I can work on this. A little confused though, since it appears to be there already. Does the mission statement go here? Please provide instructions, thanks.
Change:
JavaScript has seven primitive data types, with `String` being one of them. In JavaScript, a <dfn>string</dfn> represents a sequence of characters and can be enclosed in either single (`'`) or double (`"`) quotes. <del> Note that strings are <dfn>immutable</dfn>, which means once they are created, they cannot be changed. </del> <ins> Note that strings are <dfn>immutable</dfn>, which means once they are created, they cannot be changed. The variable can still be reassigned another value. </ins> Change your `"Hello"` string to use single quotes.

Discussion:
on it says For a beginner, this could be misleading, as they might think, they cannot change the variable. A description like:
We should avoid parenthetical information like that whenever we can, in my opinion. It makes the sentence much harder to parse.
Is it even worth mentioning here? The lesson doesn't show any consequences of immutability, so it might simply be better to remove the sentence.
I feel like it should be mentioned somewhere, but probably the first lesson where its needed
I think it is part of teaching strings. Here is how MDN words it: But it would certainly be worth circling back to it when it becomes relevant to make sure the practical implication of it is shown.
The description accurately mentions that strings in JavaScript are immutable, meaning their contents cannot be changed once created. However, it's important to clarify that while strings themselves are immutable, the variables holding them can be reassigned to new values. Therefore, no changes are necessary in this instance.
I agree, the description is correct, though for someone encountering variables, strings and immutability for the first time, they might get confused, thinking they cannot change the variable as it is a string, which is immutable. you learn how to reassign variables. Maybe not mentioning immutability at this early stage is the better choice.
Good point! Reassigning variables is key. Perhaps mentioning immutability later reinforces the distinction between variable and data type
I would be fine moving it to somewhere closer to where something like array mutation is taught.
I think we should at least update the text to say the variable can be reassigned another value. This early on in the learning process, the difference between a "value" and a "variable containing a value", is likely not that well understood. In some other challenge step, we then show what it actually means that a primitive value is immutable. After they know how to index into a value, then we can show an attempt to update an immutable value directly and explain why it doesn't work.
Let's start there, then. A PR which resolves this issue will update the text: To the text:
Change:
"<strong>User Story:</strong> I can edit these recipes.", "<strong>User Story:</strong> I can delete these recipes.", "<strong>User Story:</strong> All new recipes I add are saved in my browser's local storage. If I refresh the page, these recipes will still be there.", <ins> "<strong>Hint: </strong> You should prefix your local storage keys on CodePen, i.e. <code>_username_recipes</code>", </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.", "When you are finished, click the "I've completed this challenge" button and include a link to your CodePen.", "You can get feedback on your project from fellow campers by sharing it in our <a href='//gitter.im/freecodecamp/codereview' target='_blank'>Code Review Chatroom</a>. You can also share it on Twitter and your city's Campsite (on Facebook)."

Discussion:
I think there should be something to the project description for the recipe box project, that suggests that you should prefix the localStrorage keys. If a bunch of people use recipeBox for instance but use different data structures, someone else's app is gonna have problems looking for one format, but receiving another, if that key is already taking.
Change:
Create a `.env` file in the root of your project directory, and store the variable `MESSAGE_STYLE=uppercase` in it. <del> Then, in the `/json` GET route handler you created in the last challenge, transform the response object's message to uppercase if `process.env.MESSAGE_STYLE` equals `uppercase`. The response object should either be `{"message": "Hello json"}` or `{"message": "HELLO JSON"}`, depending on the `MESSAGE_STYLE` value. </del> <ins> Then, in the `/json` GET route handler you created in the last challenge access `process.env.MESSAGE_STYLE` and transform the response object's `message` to uppercase if the variable equals `uppercase`. The response object should either be `{"message": "Hello json"}` or `{"message": "HELLO JSON"}`, depending on the `MESSAGE_STYLE` value. </ins> **Note:** If you are using Replit, you cannot create a `.env` file. Instead, use the built-in <dfn>SECRETS</dfn> tab to add the variable.

Discussion:
We get so many forum posts all with the same issue with this challenge. People are accessing the environment variables outside the route handler, which doesn't work with the test. If we can somehow make it more clear where the variable should be accessed it would really help. Challenge:
I agree that this continues to be a problematic challenge, but how much clearer do you get than:
I don't actually think the sentence makes it that clear that the environment variable has to be evaluated inside the route handler. I would consider it unexpected behavior and it should be explained better. Or restructure the sentence somehow.
It's a bit of a clunky structure and I agree it could be worded better.
Change:
} </style> <header> <del> <img src="https://pbs.twimg.com/profile_images/378800000147359764/54dc9a5c34e912f34db8662d53d16a39_400x400.png" alt="Quincy Larson's profile picture" class="profile-thumbnail"> </del> <ins> <img src="https://freecodecamp.s3.amazonaws.com/quincy-twitter-photo.jpg" alt="Quincy Larson's profile picture" class="profile-thumbnail"> </ins> <div class="profile-name"> <h3>Quincy Larson</h3> <h4>@ossia</h4>

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 Twitter image in this challenge is broken: If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): <img width="1431" alt="LearnCSSFlexboxUsethealign-itemsPropertyintheTweetEmbedfreeCodeCamp_org" src="https://user-"