jiebi/CodeConvo huggingface dataset:
Code change:
# --hints-- <del> Your code should use the `hsl()` function to declare the color `green`. </del> <ins> Your code should use the `hsl()` function to declare the color green. </ins> ```js assert(code.match(/.greens*?{s*?background-colors*:s*?hsl/gi)); ``` <del> Your code should use the `hsl()` function to declare the color `cyan`. </del> <ins> Your code should use the `hsl()` function to declare the color cyan. </ins> ```js assert(code.match(/.cyans*?{s*?background-colors*:s*?hsl/gi)); ``` <del> Your code should use the `hsl()` function to declare the color `blue`. </del> <ins> Your code should use the `hsl()` function to declare the color blue. </ins> ```js assert(code.match(/.blues*?{s*?background-colors*:s*?hsl/gi));

Related discussion:
text: In the Responsive Web Design challenge there are these sentences As I don't think these colors are keywords, I propose to remove the backticks for translation purposes
Bit of a weird one, tbh. Those all are html color codes, but they're really just being used as names for colors. Anyways, it seems reasonable to stop using them as keywords, honestly.
I mean in this specific use case, considering also the table in the description with the hsl codes does not have the colors in backticks. And ok there are the name of the classes, but better needing to do something like " (ciano)" than keeping the colors untranslatable everywhere else imo
Sure, I agree that they shouldn't be keywords. I was just speculating as to why they're currently keywords.
Code change:
<Col className='certifications' sm={10} smPush={1}> <Link className='btn btn-lg btn-primary btn-block' <del> external={true} </del> to={`/certification/${username}/${cert.certSlug}`} > View {cert.title}

Related discussion:
text: If I click on a link to a certificate from my settings page, it opens in the same tab. If I click on one from the timeline on my portfolio, it opens in a new tab. We could probably make this consistent. I believe I made the timeline links open in a new tab because there's no nav on the cert pages, so the only way to get back to the site is with the browsers back button. I believe I have also heard an argument that they should open in the same tab so I'm not sure what the better way to go is.
sir.. i would like to solve this i contribute??
please go ahead . No assignment is necessary as described in our . The first comprehensive PR will be considered for review.
So should it open in a new tab or in the same tab? what should happen?
same question as shold happen??
I will double check with the dev team and get back to you.
My vote was to open them in a new tab - like I said, there's no nav on the certs so you have to use the browsers back button to get back to the website.
I agree
I was told, "If the user donates on the certificate, the redux store will not be updated on the other tab and would need a refresh". So, I think that for now, we should open them in the current tab - unless someone has a better solution to that.
Could you clarify this? If the user donates on the certificate opened on a new tab, the redux store will not be opened on the original (settings) tab? This does not sound much like a problem. In fact, I would have said that is expected behaviour, from past experience.
So If a user donates on their certificate the store on that tab gets updated (isDonating: true). When the user goes back to the previous tab to work on the challenges, she will see the donation modal. (unless refresh). Solutions: 1) keep a navigation on the certs and keep them in the same tab 2) open certs in new tab but sync state across tabs, Might find this one helpful.
What is the chosen path to solve this issue? Or am I missing something?
We have not come to an agreement regarding the way to move forward yet. The options are listed . Once we reach an agreement, we should make the experience consistent across the app.
Code change:
takeEvery(types.updateUserFlag, updateUserFlagSaga), takeLatest(types.submitNewAbout, submitNewAboutSaga), takeLatest(types.submitNewUsername, submitNewUsernameSaga), <del> takeLatest(types.validateUsername, validateUsernameSaga), </del> <ins> debounce(2000, types.validateUsername, validateUsernameSaga), </ins> takeLatest(types.submitProfileUI, submitProfileUISaga), takeEvery(types.verifyCert, verifyCertificationSaga) ];

Related discussion:
text: On the settings page, you can change your username. Any time you stop typing, it reads from the database to see if the username is available - we could change it so that it only makes a query when the user is ready. So instead of when they stop typing, we just let them choose the name they want, then when they click save we check if it's available. Not sure how big of a deal this is, I'm guessing users don't change their username often. Every little bit helps?
I've always wondered about this one. Definitely agree that we shouldn't hit the DB until the camper tries to submit.
I think we can go with the current implementation but wait for a meaningful pause to make sure the user is intending to submit the new username for validity check.
Code change:
challengeFile.fileKey === fileKey ? { ...challengeFile, ...updates } : { ...challengeFile } <del> ) </del> <ins> ), isBuildEnabled: true </ins> }; }, [actionTypes.storedCodeFound]: (state, { payload }) => ({

Related discussion:
text: Some users are encountering the error in the linked video. See the forum for more discussion. All Console error messages should clear so users can run code No response various No response
If I revert the change from it seems to fix it.
I am also facing this issue while doing javascript datastructures and algorithms course. The console errors are stuck and the solution is to refresh the page everysingle time.
I also face this issue while doing a JavaScript data structures and algorithms course. The console errors are stuck and the solution is to refresh the page every single time.
Thanks for tracking that down, it was defintiely the culprit.
Code change:
return [ takeLatest(types.executeChallenge, executeCancellableChallengeSaga), takeLatest( <del> [ types.updateFile, types.previewMounted, types.challengeMounted, types.resetChallenge ], </del> <ins> [types.updateFile, types.challengeMounted, types.resetChallenge], </ins> previewChallengeSaga ), <ins> takeLatest(types.previewMounted, previewChallengeSaga, { flushLogs: false }), </ins> takeLatest(types.projectPreviewMounted, previewProjectSolutionSaga) ]; }

Related discussion:
text: In the multi-file editor, if the preview pane is toggled off and then on again, any output in the console will be cleared. Granted, the user can always check their code again to get the console output back. But I'm assuming this is not intended behavior? Any page using the multi-file editor the Survey Form in the new RWD the Console button so it is showing below the preview. the tests. the Preview button to hide the preview. the Preview button again to show the preview. that the console output resets. Console output should not reset if the preview pane is toggled off/on. No response N/A No response
Here is what I tried, so anyone in the future save time: Changing lowerJaw to JSX didn't help. TabPane change display to , but React doesn't care and preserve the state. if you turn to JSX, so react preserve the state, it won't render at all. monaco wants it to be an element. I don't know if this helps, but I personally think if become JSX, then React can do its thing and preserve the state. I have no idea how to make monaco accept JSX instead of Element, so I am going to stop there, maybe someone else the same issue. Here is the file with the issue Here is the react-wrapper for the monaco, maybe it does have a way to do it
I have looked it more up And I don't think, it is possible to inject JSX element inside the editor. I am maybe wrong, but the easiest solution, is to have the editor in instruction and lowerjaw in different tab, is that possible?
I think the console output is not related to the editor per say. We just need to investigate output, consoleOutputSelector, and consoleOut state in redux store and see at what point it gets reset.
Code change:
# --hints-- <ins> You should have four `article` elements in your second `section`. ```js const secondSection = document.querySelectorAll('section')[1] const articles = secondSection.querySelectorAll('article') assert(articles.length === 4) ``` </ins> You should have four `.dessert` elements. ```js

Related discussion:
text: In step 53 of the Building a Cafe Menu project: Adding by mistake three p elements inside a single article element (instead of three different article elements), I received an unhelpful hint message. Code: Hint: I think that the hint should say something like: You should add three new article elements.
I don't think this hint is necessary wrong or needs to change - there's a test that makes sure there's no spaces between the elements. It fails and gives that message. It just gives the message for the first test that fails. The idea then would be to use the hint to try and solve the step. If you remove the spaces, as the hint suggests, you will pass the step. Although, because I did not add the three new elements, it should not have passed. I think we should just add another hint and test, probably near the top of the tests - maybe the first test, that checks that three new article elements were and we can use the suggestion as the hint. Then, that would be the first test to fail, and you would get the hint about the number of article elements.
<section<h2Desserts</h2<article class="item"<p class="dessert"Donut</p<p class="price"1.50</p<p class="dessert"Cherry Pie</p<p class="price"2.75</p<p class="dessert"Cheesecake</p<p class="price"3.00</p<p class="dessert"Cinnamon Roll</p<p class="price"2.50</p</article</section
Code change:
# --instructions-- <del> Add version "1.1.0" of the `@freecodecamp/example` package to the `dependencies` field of your `package.json` file. </del> <ins> Add version `1.1.0` of the `@freecodecamp/example` package to the `dependencies` field of your `package.json` file. </ins> **Note:** `@freecodecamp/example` is a faux package used as a learning tool.

Related discussion:
text: In RTL, these texts will be broken, because they are a mix of special character, numbers, which follow different direction in RTL than LTR. ~1.2.13 1.2.x 1.x.x To fix these, add code elements around the version number. File: change to there are multiple instances in these files All of them should be wrapped in code elements Speaking of weird interactions. Using special characters that relay on direction will break in RTL, because it will be reverted, in example. will be we can wrap in
I want to contribute towards this issue. Can you assign this issue to me.
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
Code change:
"Return the provided string with the first letter of each word capitalized.", "For the purpose of this exercise, you should also capitalize connecting words like 'the' and 'of'." ], <del> "challengeEntryPoint": "titleCase("I'm a little tea pot")", </del> <ins> "challengeEntryPoint": "titleCase("I'm a little tea pot");", </ins> "challengeSeed": "function titleCase(str) {n  return str;rn}", "tests": [ "expect(titleCase("I'm a little tea pot")).to.be.a('String');",

Related discussion:
text: Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. content: ""; // when you addany extra space outside the empty string will not pass this challenge. Can't you add any whitespace?
I believe this is by intention, rather than being a bug. You can, but you would do so using a few different means such as margin, padding, or positioning depending on the situation and what you are trying to accomplish. The content attribute of the :before and :after attributes would not interpret arbitrary white space in the way I believe you are asking.
I see what you mean, the tests are too strict. I could fix this if a moderator approves that the tests need to be changed.
We just launched the new curriculum and learning platform. Please take a look at it: Do you still think this challenge is confusing or overly hard? If so, we would welcome improvements to this challenge.
I will look into the tests tomorrow.
You're the man. Thanks! Please keep us posted
I will prepared this and a couple of others for first timers. If the issue is not taken in a couple of days, I will come back and fix them. Let me know if you want me to fix them immediately The location of the test that needs to be changed: the new line should be: "testString": "assert((/.heart:befores?{[sS]content:s?""s?;/gi), 'The <codecontent</codeof the <codeheart:before</codeselector should be an empty string.');"
FYI on the issues page it encourages fist timers to search for the "good first issue" label which does not exist. It should say "first timers welcome" !
Does the issue still exist if not then I would like to work on it?
sorry for the late response. Yes it is open.
could you link me to the page where you're seeing this?  Then I can update it.
It is on the issues page when I sign in with my moderator account.
please review my PR regarding this issue.
Code change:
"Return the provided string with the first letter of each word capitalized.", "For the purpose of this exercise, you should also capitalize connecting words like 'the' and 'of'." ], <del> "challengeEntryPoint": "titleCase("I'm a little tea pot")", </del> <ins> "challengeEntryPoint": "titleCase("I'm a little tea pot");", </ins> "challengeSeed": "function titleCase(str) {n  return str;rn}", "tests": [ "expect(titleCase("I'm a little tea pot")).to.be.a('String');",

Related discussion:
text: OK - thanks for letting me know - I still can't see it for some reason so you would be a better person to QA this.
Code change:
"Return the provided string with the first letter of each word capitalized.", "For the purpose of this exercise, you should also capitalize connecting words like 'the' and 'of'." ], <del> "challengeEntryPoint": "titleCase("I'm a little tea pot")", </del> <ins> "challengeEntryPoint": "titleCase("I'm a little tea pot");", </ins> "challengeSeed": "function titleCase(str) {n  return str;rn}", "tests": [ "expect(titleCase("I'm a little tea pot")).to.be.a('String');",

Related discussion:
text: Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:
you need a closing brace after the quoted class.
thanx
Code change:
"Return the provided string with the first letter of each word capitalized.", "For the purpose of this exercise, you should also capitalize connecting words like 'the' and 'of'." ], <del> "challengeEntryPoint": "titleCase("I'm a little tea pot")", </del> <ins> "challengeEntryPoint": "titleCase("I'm a little tea pot");", </ins> "challengeSeed": "function titleCase(str) {n  return str;rn}", "tests": [ "expect(titleCase("I'm a little tea pot")).to.be.a('String');",

Related discussion:
text: for step 38 here: the new user needs to set up an SSH key to push to github. the key is given by C9, but it's not clear to me how to add it to github, a simple copy /paste to my SSH keys in my account isn't working. This should be clarified for new users of c9. Not sure if it's needed for every c9 workspace or just once, but I guess github is seeing c9 as a new computer?
Here is a set of instructions that worked for me: In the bottom left of your C9 dashboard is a section called “Add-on Services”. Click “activate” next to the “GitHub” icon (if you haven’t already). When the pop up appears, tell it to allow access to your account. This should complete the link between GitHub account and your C9 account. While still on the dashboard, look to the right under “Account Settings” for the link “Show your SSH key”. Click on it, and copy the value which appears. Go to the GitHub SSH settings page, and click “Add SSH Key” Enter the title “C9″, paste the SSH Key into the “Key” box, and click “Add Key”.
Excellent. Thank you for pointing this out. I'll add this.
Code change:
"Return the provided string with the first letter of each word capitalized.", "For the purpose of this exercise, you should also capitalize connecting words like 'the' and 'of'." ], <del> "challengeEntryPoint": "titleCase("I'm a little tea pot")", </del> <ins> "challengeEntryPoint": "titleCase("I'm a little tea pot");", </ins> "challengeSeed": "function titleCase(str) {n  return str;rn}", "tests": [ "expect(titleCase("I'm a little tea pot")).to.be.a('String');",

Related discussion:
text: The description does not specify to preserve the title case of the word replaced. Although the tests somehow expect the title case to be preserved if the word is getting replaced. We should either: A. change the test B. Add a note in the description about this quirk.
Code change:
"Return the provided string with the first letter of each word capitalized.", "For the purpose of this exercise, you should also capitalize connecting words like 'the' and 'of'." ], <del> "challengeEntryPoint": "titleCase("I'm a little tea pot")", </del> <ins> "challengeEntryPoint": "titleCase("I'm a little tea pot");", </ins> "challengeSeed": "function titleCase(str) {n  return str;rn}", "tests": [ "expect(titleCase("I'm a little tea pot")).to.be.a('String');",

Related discussion:
text: It would be really helpful for each bonfire solution on a user's profile to include a link to the original exercise, esp. for non-FCC users.
Great point. I'm doing so. Thanks!
Code change:
"Return the provided string with the first letter of each word capitalized.", "For the purpose of this exercise, you should also capitalize connecting words like 'the' and 'of'." ], <del> "challengeEntryPoint": "titleCase("I'm a little tea pot")", </del> <ins> "challengeEntryPoint": "titleCase("I'm a little tea pot");", </ins> "challengeSeed": "function titleCase(str) {n  return str;rn}", "tests": [ "expect(titleCase("I'm a little tea pot")).to.be.a('String');",

Related discussion:
text: In the ux-improvements branch: Looks like this is an issue with the seed data here:
Thanks! I've fixed the copy for all of these waypoints.
No problem. You may already know this, but it's still showing the Mongo video...
Code change:
}); ``` <ins> The `draw` method should behave correctly when the number of balls to extract is bigger than the number of balls in the hat. ```js ({ test: () => { pyodide.FS.writeFile("/home/pyodide/probability_calculator.py", code); pyodide.FS.writeFile( "/home/pyodide/test_module.py", ` import unittest import probability_calculator from importlib import reload reload(probability_calculator) probability_calculator.random.seed(95) class UnitTests(unittest.TestCase): maxDiff = None def test_hat_draw_2(self): hat = probability_calculator.Hat(yellow=5,red=1,green=3,blue=9,test=1) actual = hat.draw(20) expected = ['yellow', 'yellow', 'yellow', 'yellow', 'yellow', 'red', 'green', 'green', 'green', 'blue', 'blue', 'blue', 'blue', 'blue', 'blue', 'blue', 'blue', 'blue', 'test'] self.assertEqual(actual, expected, 'Expected hat draw to return all items from hat contents.') actual = len(hat.contents) expected = 0 self.assertEqual(actual, expected, 'Expected hat draw to leave no items in contents.') ` ); const testCode = ` from unittest import main import test_module from importlib import reload reload(test_module) t = main(module='test_module', exit=False) t.result.wasSuccessful() `; const out = __pyodide.runPython(testCode); assert(out); }, }); ``` </ins> The `experiment` method should return a different probability.

Related discussion:
text: Faulty method of the class can expose itself only during function tests. Case when number of balls to draw is higher than number of balls in hat is not tested explicitly, but it can fail function test, as it includes such experiment. - - Depending on the number of balls to draw and number of balls in Hat: Remove the required number of balls randomly selected, from the Hat. If number of balls to draw is higher than the number of balls, return all the balls. Test for the method checks only the first case: The second behavior is not checked explicitly, but it's a part of the second sub-case in the function test. This creates situation where passing method test and failing function test, can suggest to camper that issue lies in the function. Example with faulty method: Error: Adding test to check second behavior of the method would make debugging easier for campers, as it would show more clearly where is the issue. No response n/a No response
Code change:
</Col> <Col md={7} sm={12}> <div data-cy='issue-date' className='issue-date'> <del> Issued&nbsp; </del> <ins> {t('certification.issued')}&nbsp; </ins> <strong>{format(certDate, 'MMMM d, y')}</strong> </div> </Col>

Related discussion:
text: The certification files () have been uploaded to Crowdin for translation. However, the React Component itself does not use the translation helper for the text within the certification (such as ). The component and files should be updated to allow this.
Code change:
Puedes optar por contribuir a cualquier área de tu interés: <del> 1. [Contribuir a esta base de código fuente abierto.](#contribute-to-this-open-source-codebase) </del> <ins> 1. [Contribuir a esta base de código fuente abierto.](#contribuye-a-esta-base-de-código-abierto) </ins> Ayúdanos a crear o editar [artículos de guía](https://www.freecodecamp.org/guide), [desafíos de codificación](https://www.freecodecamp.org/learn) o a corregir errores en la plataforma de aprendizaje.

Related discussion:
text: 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.
Code change:
Your `#video` should have a `src` attribute ```js <del> const el = document.getElementById('video') assert(!!el && !!el.src) </del> <ins> let el = document.getElementById('video') const sourceNode = el.children; let sourceElement = null; if (sourceNode.length) { sourceElement = [...video.children].filter(el => el.localName === 'source')[0]; } if (sourceElement) { el = sourceElement; } assert(el.hasAttribute('src')); </ins> ``` You should have a `form` element with an `id` of `form`

Related discussion:
text: The following test (user story) prevents my previously passing project from passing: Important: Notice I use instead of just I never claimed to be a UI expert Do we want to keep such a test? No response Unrelated No response
Maybe you should update your project Honestly I think small tweaks are going to be okay - my tribute page fails because the image needs a height now.
I am also happy with small tweaks, but we did (largely) want to keep the requirements exactly the same. The only change we agreed upon is to add requirements for tags.
Looks like they accommodated for the tag in that test. Maybe we can just add it here too.
although, I think it's good, that we moved on from the old test. tag is extremely useful in html, it has attribute that help developers use less needed css, which lead to better experience, . it should be accepted to use Edit: if you paste this code in it won't pass although there is a media query but in the html Edit: I changed the for easier testing