jiebi/CodeConvo huggingface dataset:
Code change:
<!-- 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 usage of the word "argument" ist unclear to me. The title of this challenge uses the word "parameter". Then the instructions state: "If an arrow function has a single argument, the parentheses enclosing the argument may be omitted." But the following snippet cited from the instructions shows the parameter "item" without parentheses: The functions are never invoked with an argument in the examples. As I understand it the sentence should say: "If an arrow function has a single parameter, the parentheses enclosing the parameter may be omitted." Add a Link to the page with the problem: or, Tell us about your browser and operating system: Browser Name: Browser Version: Operating System: If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):
Hello~! I agree that the verbiage is wrong here. should probably be replaced with in the examples and text, with the exception of the top line (which, at a quick glance, is the only correct use of ):
These are the ones that should be changed, I think. In fact, we could use instead.
I like that approach. Think this could be opened up to first timers?
I would go for: Just like a regular function, you can pass arguments into an arrow function. If an arrow function has a single parameter, the parentheses enclosing the parameter may be omitted. It is possible to pass more than one argument into an arrow function.
Sure, that works.

Related discussion:
text: ```js // doubles input value and returns it const doubler = (item) => item * 2; <ins> doubler(4); // returns 8 </ins> ``` <del> If an arrow function has a single argument, the parentheses enclosing the argument may be omitted. </del> <ins> If an arrow function has a single parameter, the parentheses enclosing the parameter may be omitted. </ins> ```js <del> // the same function, without the argument parentheses </del> <ins> // the same function, without the parameter parentheses </ins> const doubler = item => item * 2; ```
Code change:
<!-- 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 usage of the word "argument" ist unclear to me. The title of this challenge uses the word "parameter". Then the instructions state: "If an arrow function has a single argument, the parentheses enclosing the argument may be omitted." But the following snippet cited from the instructions shows the parameter "item" without parentheses: The functions are never invoked with an argument in the examples. As I understand it the sentence should say: "If an arrow function has a single parameter, the parentheses enclosing the parameter may be omitted." Add a Link to the page with the problem: or, Tell us about your browser and operating system: Browser Name: Browser Version: Operating System: If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):
Hello~! I agree that the verbiage is wrong here. should probably be replaced with in the examples and text, with the exception of the top line (which, at a quick glance, is the only correct use of ):
These are the ones that should be changed, I think. In fact, we could use instead.
I like that approach. Think this could be opened up to first timers?
I would go for: Just like a regular function, you can pass arguments into an arrow function. If an arrow function has a single parameter, the parentheses enclosing the parameter may be omitted. It is possible to pass more than one argument into an arrow function.
Sure, that works.

Related discussion:
text: ```js // multiplies the first input value by the second and returns it const multiplier = (item, multi) => item * multi; <ins> multiplier(4, 2); // returns 8 </ins> ``` </section>
Code change:
GitHub yesterday (November 16) which our Cypress CI depended. So, currently all Cypress tests in CI are failing. Just using the latest version of the Cypress GitHub action should do the trick. (We are currently running the outdated action.) !

Related discussion:
text: run: npm run seed - name: Cypress run <del> uses: cypress-io/github-action@v1 </del> <ins> uses: cypress-io/github-action@v2 </ins> with: record: ${{ env.CYPRESS_RECORD_KEY != 0 }} build: npm run build
Code change:
Describe your problem and how to reproduce it: While working on the Sudoku solver project, one scenario came up that wasn't clear to me how to handle. The scenario is what do you do, if I ask to check a value of a cell with an existing value? For my project, I chose to return a conflict with the row, column, and region. However, I checked what the example app returns. The results it returns are logically inconsistent, which tells me this use case is undefined. For the example app: https://sudoku- coordinate enter C3, for value enter 2 (the existing value), click Check Placement returns value to 9, App returns value to 1, App returns These response are not logically consistent. For the first one, it appears to be checking against all of the existing values in the puzzle. For the second and third cases, it appears to be checking after replacing the value. I would expect this use case to be defined as either, it's a conflict, because there is an existing value at that cell or to replace the value in that cell and then check if it is valid or not and return the appropriate results. Add a Link to the page with the problem: ://sudoku- Tell us about your browser and operating system: Browser Name: Google Chrome Browser Version: 87.0.4280.67 (Official Build) (x86_64) Operating System: macOS Mojave 10.14.6
Yes, seems odd that you can place a value over an existing spot and it can return as valid Seems like this should be the response Or something along those lines
I do agree that this should be handled as a valid placement (given that the number is already present in that cell). Unless there is objection/disagreement, I'd be willing to open this up for contribution.
I also vote to make it behave as if it replaces the cell before checking validity. Or something along those lines. I have opened this up for contributions.

Related discussion:
text: }; ``` <ins> If `value` submitted to `/api/check` is already placed in `puzzle` on that `coordinate`, the returned value will be an object containing a `valid` property with `true` if `value` is not conflicting. ```js async (getUserInput) => { const input = '..9..5.1.85.4....2432......1...69.83.9.....6.62.71...9......1945....4.37.4.3..6..'; const coordinate = 'C3'; const value = '2'; const data = await fetch(getUserInput('url') + '/api/check', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ puzzle: input, coordinate, value }) }); const parsed = await data.json(); assert.property(parsed, 'valid'); assert.isTrue(parsed.valid); }; ``` </ins> If the puzzle submitted to `/api/check` contains values which are not numbers or periods, the returned value will be `{ error: 'Invalid characters in puzzle' }` ```js
Code change:
Describe your problem and how to reproduce it: Challenge description gives slightly different task, to what needs to be done to pass tests. Challenge is about , which looks at the beginning like (skipping zero at start): Challenge description asks to create function returning n-th member of the sequence. However expected values in tests, and sample solution don't match that. sternBrocot(2) should return 3. sternBrocot(3) should return 5. sternBrocot(5) should return 11. sternBrocot(7) should return 19. sternBrocot(10) should return 39. Function matching tests would be one returning at which position in sequence number is encountered for first time. Original challenge on Rosetta Code - have both these variations as a part of task, so that's most likely how it sneaked in. Add a Link to the page with the problem:
I vote to have the function return the position in the sequence of the argument. We wouldn't need to change the tests, just the description.
I'm in favour of that approach as well.

Related discussion:
text: # --instructions-- <del> Create a function that returns the $ n^{th} $ member of the sequence using the method outlined above. </del> <ins> Create a function that returns the position in the Stern-Brocot sequence at which $ n $ is first encountered, where the sequence is generated with the method outlined above. Note that this sequence uses 1 based indexing. </ins> # --hints--
Code change:
Describe the bug Last week, I saw multiple posts where people asking for help didn’t write down what they needed help with. I think the help post template may be confusing some folks. Screenshots ! Additional context “Tell us what’s happening” looks a bit like an overall heading. I suggest the following changes to make it more obvious that people are supposed to write something down: Mockup !
Hello there, Thank you, for taking the time to open this. I believe it would help some Campers understand the need to add more information. However, I suspect the large majority just post without reading any further. The Discourse software does have a lot of cool features aiding the topic creating (e.g. Information about informative titles, showing similar topics). If others are in agreement, this would be an easy implementation, and could be put up for first timers? That being said, I find dedent to be pesky.
I'm not big on the idea of adding an extra heading. Perhaps just the extra describe prompt: Tell us what's happening: Describe your issue in detail here Your code so far: Your browser information: blah blah blah Mildly related - I think we should add a colon after "Your code so far" to match the other headings.
If it's a first-timer I'll let somebody do it but if not I can take care of making the changes. Your call!
Any decision on if we're opening this for first timers?
Can I work on this issue, being my first contribution to freeCodeCamp?
please go ahead.
Hi, I saw that this issue wanted to be done by someone a few days ago, but its still not been closed, I am also an newbie and am really eager to contribute so would be happy to help, and close it today. Was trying to find the template to change it, but couldn't find the file. Would it be possible for someone to point me to the right file? Thanks :)
Hey it's this one -
Thanks

Related discussion:
text: let textMessage = dedent( `**Tell us what's happening:** <ins> Describe your issue in detail here. </ins> ${ projectFormValues.length
Code change:
Maybe this was done intentionally to give learning programmers more leeway. If that's not the case though, it's a bug. Describe your problem and how to reproduce it: In the -challenge, the request clearly is to add the new tag AFTER the previous p-tag. However, the following code also gets accepted as a correct solution. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Firefox Browser Version: 87.0 (64-bit) Operating System: Linux (Linux Mint) If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! !
I think this can go either way, but I'm leaning towards changing the directions, and removing the to give the more leeway for newcomers, to somewhat like: This is ofcourse just my opinion, I would love for others to pitch in...
I like the change. The less explicit version seems to better describe how the page is already behaving.
I agree that this sounds like a good change :) Maybe is the way to go, to indicate it shouldn't be over the tag.
As we do not want any confusion about what the element should wrap. I suggest the following: I am opening 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. 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
Sure, I'll do my best!
See . I wrote this. I changed the second line to improve it with , while still keeping it similar to the previous description.

Related discussion:
text: # --instructions-- <del> Create a second `p` element after the existing `p` element with the following kitty ipsum text: `Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.` </del> <ins> Create a second `p` element with the following kitty ipsum text: `Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.` </ins> <del> Then, create a `main` element and nest the two `p` elements inside the `main` element. </del> <ins> Then, create a `main` element and nest only the two `p` elements inside the `main` element. </ins> # --hints--
Code change:
There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved. Error type: Cannot find preset's package (githubwhitesource/merge-confidence:beta)

Related discussion:
text: { "matchUpdateTypes": ["minor", "patch", "pin", "digest"], "matchCurrentVersion": "!/^0/", <del> "automerge": true }, { </del> <ins> "automerge": true, </ins> "rebaseWhen": "behind-base-branch" } ],
Code change:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. -- <!-- Add a link to the coding challenge with the problem. --<!-- Copy and paste the code from the editor that you used in between the back-ticks below: -- Expected to see Clothing withdrawal transactions (-25.55) on output but only seeing the 'transfer from food $50'. Transfer method passes but the food transfer of 50 but it is 0. <!-- Add a clear and concise description of what you expected to happen. --<!-- If applicable, add screenshots to help explain your problem. you can drag and drop, png, jpg, gif, etc. in this box. --<!-- Please complete the following information. --- Device: PC Desktop OS: Windows 10 Browser: Firefox Version: 93.0 <!-- Add any other context about the problem here. --I've since updated my transfer method to use the withdrawal and deposit functions to accomplish the task correctly. It seems the Transfer method test case needs a bit of an upgrade to make sure withdrawals are working.
The test for transfer function is not checking if the amount is deducted or , But only checks for the ledger entries. Adding two additional tests for deduction and addition will fix this issue.
I tossed up a PR for this: I two asserts to the existing test.

Related discussion:
text: h4.negative-10.text-nowrap Community Builder img.profile-image(src='https://s3.amazonaws.com/freecodecamp/branden-byers.jpg' alt="Branden Byers picture") h4.text-nowrap Madison, Wisconsin <del> p.negative-10 "I'm a massage therapist and Stay-at-home-dad. I learned Hypercard, then Rails, but now I feel at home with JavaScript." </del> <ins> p.negative-10 "Cookbook author and stay-at-home-dad. Started coding as a kid, got distracted, but now I'm back in full JavaScript force!" </ins> .col-xs-12.col-sm-4.col-md-3.team-member h3.negative-10.text-nowrap Michael Johnson h4.negative-10.text-nowrap Nonprofit Coordinator
Code change:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. -- <!-- Add a link to the coding challenge with the problem. --<!-- Copy and paste the code from the editor that you used in between the back-ticks below: -- Expected to see Clothing withdrawal transactions (-25.55) on output but only seeing the 'transfer from food $50'. Transfer method passes but the food transfer of 50 but it is 0. <!-- Add a clear and concise description of what you expected to happen. --<!-- If applicable, add screenshots to help explain your problem. you can drag and drop, png, jpg, gif, etc. in this box. --<!-- Please complete the following information. --- Device: PC Desktop OS: Windows 10 Browser: Firefox Version: 93.0 <!-- Add any other context about the problem here. --I've since updated my transfer method to use the withdrawal and deposit functions to accomplish the task correctly. It seems the Transfer method test case needs a bit of an upgrade to make sure withdrawals are working.
The test for transfer function is not checking if the amount is deducted or , But only checks for the ledger entries. Adding two additional tests for deduction and addition will fix this issue.
I tossed up a PR for this: I two asserts to the existing test.

Related discussion:
text: h4.negative-10.text-nowrap Live Content Manager img.profile-image(src='https://s3.amazonaws.com/freecodecamp/jason-rueckert.jpg' alt="Jason Rueckert's picture") h4.text-nowrap Seattle, Washington <del> p.negative-10 "My high school job was testing basketball shoes for Nike. I learned code to work smarter, not harder. I have no thyroid." </del>  No newline at end of file <ins> p.negative-10 "My high school job was testing basketball shoes for Nike. I learned code to work smarter, not harder. I have no thyroid." </ins>
Code change:
In the The Property section of Curriculum File Structure documentation there's reference to file. That file no longer exists, and the relevant helper function is now in file. It's needed to point to the correct file and/or adjust the wording in the section. Here are the files that you should be looking at to work on a fix: 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.

Related discussion:
text: ## The `dashedName` Property <del> The `dashedName` property is used to generate the URL path for the superblock, block, or challenge. These should generally match what the `/utils/dasherize.js` helper would output for the file name. </del> <ins> The `dashedName` property is used to generate the URL path for the superblock, block, or challenge. These should generally match what the `/utils/slugs.js` helper would output for the file name. </ins>
Code change:
Step 36 says However this is false, anchor tags are not self-closing. I believe it meant to say which is the self-closing tag introduced in the previous steps.  Wasn't sure where to report this so I also posted about it on the forums at .
Good eye!
Hi ! Thank you for bringing up this issue. This is an easy fix to change anchor elements to img elements. I have the first timers only label for those who are interested in making their first PR.
Could I take this issue? I'm looking for a good first contribution.
Hi ! Any issue with the first timers only label is up for grabs. The first PR that has the correct changes will be reviewed and merged into the main codebase. Here is the file that needs changing. Happy contributing !

Related discussion:
text: # --description-- <del> The `input` element allows you several ways to collect data from a web form. Like anchor (`a`) elements, `input` elements are <dfn>self-closing</dfn> and do not need closing tags. </del> <ins> The `input` element allows you several ways to collect data from a web form. Like `img` elements, `input` elements are <dfn>self-closing</dfn> and do not need closing tags. </ins> Nest an `input` element in the `form` element.
Code change:
The following code passes all the challenge's tests, but it is incorrect (it fails to find if is the last element of The code above should not pass the challenge. ! Device: Macbook Pro OS: 10.13.6 Browser: Firefox Version: 97.0.1
Checking against the solution on the forum, it appears that should return . We could add a test to the challenge that checks this, which would resolve this issue.
Yes, that should be all it takes to resolve this issue.
I'm going to go ahead and open this up for first time contributors. A PR to resolve this issue will: Add a test to that asserts returns . If you are interested in working on this issue, we recommend starting with our , and you are welcome to join our if you have any questions.
can I do the code in python ?
No. Our challenges run on Javascript. In this case, you don't need to write a new impl of the algorithm or anything. You just need to add an additional test case that matches the one given above.
Sure, unless wants to take this, I will

Related discussion:
text: assert.deepEqual(binarySearch(_testArray, 13), [13]); ``` <ins> `binarySearch(testArray, 70)` should return `[13, 19, 22, 49, 70]`. ```js assert.deepEqual(binarySearch(_testArray, 70), [13, 19, 22, 49, 70]); ``` </ins> # --seed--
Code change:
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

Related discussion:
text: # --description-- <del> You may be familiar with the `meta` tag already; it is used to specify information about the page, such as the title, description, keywords, and author. </del> <ins> You may be familiar with the `meta` element already; it is used to specify information about the page, such as the title, description, keywords, and author. </ins> <del> Give your page a `meta` tag with an appropriate `charset` value. </del> <ins> Give your page a `meta` element with an appropriate `charset` value. </ins> The `charset` attribute specifies the character encoding of the page, and, nowadays, `UTF-8` is the only encoding supported by most browsers.