jiebi/CodeConvo huggingface dataset:
Change:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Javascript Code Editor Steps to reproduce the behavior: the following code; ! Device: Laptop OS: Windows 10 Browser: Edge Version: 96.0.1054.34
Same goes for Map. I don't believe we teach Set or Map anywhere so it's maybe not super relevant. But the output should be as close to the browser console as possible I would think.
cc
My best guess is it has to do with the on the log here: But debugging has been a pain because that file does not hot-reload in the client.
Set is used in this under the coding interview prep section. While using is not specifically required for the task, the example code shown does have with an expected output underneath which with this bug will not be displayed in the output. This would be quite misleading for someone who pastes in the example code to the editor.
I dug into this a little bit: the problem is that relies on a fallback when running in the browser. This fallback does not know how to handle sets or maps and just returns . If anyone wants to work on this, the obvious approach is to check if the input is an or and then write some custom code to format them.
I take it we are leaving this open, as tests should probably be ?

Discussion:
'say-hello-to-html-elements', jQuery: '/learn/front-end-development-libraries/jquery/' + <del> 'target-html-elements-with-selectors-using-jquery' </del> <ins> 'target-html-elements-with-selectors-using-jquery', js: '/learn/javascript-algorithms-and-data-structures/basic-javascript/' + 'comment-your-javascript-code' </ins> }; const defaultOutput = `

); }); }); <ins> describe('Custom output for JavaScript objects', function () { beforeEach(() => { cy.visit(locations.js); cy.get(selectors.editor, { timeout: 15000 }) .first() .click() .focused() .type('{ctrl}a') .clear(); }); it('Set object', () => { cy.get(selectors.editor) .first() .click() .focused() .type( 'const set = new Set();{enter}set.add(1);{enter}set.add("set");{enter}set.add(10);{enter}console.log(set);' ); cy.get(selectors.defaultOutput).should('contain', 'Set(3) {1, set, 10}'); }); it('Map object', () => { cy.get(selectors.editor) .first() .click() .focused() .type( 'const map = new Map();{enter}map.set("first", 1);{enter}map.set("second", 2);{enter}map.set("other", "map");{enter}console.log(map);' ); cy.get(selectors.defaultOutput).should( 'contain', 'Map(3) {first => 1, second => 2, other => map})' ); }); }); </ins>
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: --Code from the : <!-- Add a clear and concise description of what you expected to happen. --If the while loop is removed from the , the following should fail (if 3 or more items ), but it does not: <!-- Please complete the following information. --- Device: Laptop OS: Windows 10 Browser: Chrome Version: 96 <!-- Add any other context about the problem here. --The is only testing with 2 items to a linked list. The test should fail if a third item is and the while loop is removed from the because the third item would would be to the linked list, but it would orphan the second item. My suggestion for an improved test:
Can I take this one?

Discussion:
var test = new LinkedList(); test.add('cat'); test.add('dog'); <del> return test.head().next.element === 'dog'; </del> <ins> test.add('fish'); return test.head().next.element === 'dog' && test.head().next.next.element === 'fish'; </ins> })() ); ```
Change:
I set the a:visited color to “gray” which changed the link color in the preview pane and even displayed the color picker box in the view with the color gray but when I clicked Check Your Code it didn’t accept my answer. I had to change it to “grey” with an ‘e’, not an ‘a’ to get the Step completed message. Now it does have the word “grey” with an ‘e’ in the directions, but I spell gray with an ‘a’ so that is what I did naturally. Do you want to accept a value of “gray” and “grey” as correct answers or will you only accept “grey”. If you only accept “grey” would it be possible to add a message asking the user to check their spelling? Otherwise, users may get frustrated and confused if they used “gray” and then they don’t understand why the answer is wrong. ! <!-- Please complete the following information. --- Device: [Laptop] OS: [Windows 10] Browser: [brave] Version: [Version 1.33.106 Chromium: 96.0.4664.110 (Official Build) (64-bit)] <!-- Add any other context about the problem here. --

Discussion:
You should set the `color` property to `grey`. ```js <del> const hasColor = new __helpers.CSSHelp(document).getCSSRules().some(x => x.style.color === 'grey'); </del> <ins> const hasColor = new __helpers.CSSHelp(document).getCSSRules().some(x => (x.style.color === 'grey' || x.style.color === 'gray')); </ins> assert(hasColor); ```

```js const aVisitedColor = new __helpers.CSSHelp(document).getStyle('a:visited')?.getPropertyValue('color'); <del> assert(aVisitedColor === 'grey'); </del> <ins> assert(aVisitedColor === 'grey' || aVisitedColor === 'gray'); </ins> ``` # --seed--
Change:
<!-- NOTE: If you want to become an author on freeCodeCamp, you can find everything here: --<!-- If you are reporting an issue with an article on our News publication, please follow this link to send an email to our editorial team --As stated in a by the example of a PR title () is misleading as this is not to be done manually; instead being perormed by automated pipelines. Visit the above page and scroll down to find the text: Remove this example from the documentation. <!-- If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box). --<img width="653" alt="Image of the invalid example of a pr title" src="https://user-"
Hello there If anything is done here, I would not remove it from the examples - I would change it to include something else that is relevant. Reason being, it is nice to have an example showing .
like we could make the last example something like , that is something we keep doing to avoid redirect to the EN docs from the other ones
I'd be in favour of implementing Ilenia's proposed change. Though I'm not sure anything needs to be fixed here. Yes, our translation PRs are automatic, but it's still a good example of a PR title.

Discussion:
- `fix(a11y): improved search bar contrast` - `feat: add more tests to HTML and CSS challenges` - `fix(api,client): prevent CORS errors on form submission` <del> - `docs(i18n): Chinese translation of local setup` </del> <ins> - `docs(i18n): fix links to be relative instead of absolute` </ins> ## Proposing a Pull Request
Change:
You can pass the test by assigning 10 to the variable after decrementing it past that value. It also doesn't seem like the... is not working. Incorrect code that is passing: Forum: Challenge: Tests:
I am happy with this being changed, but, personally, I see no issue here: The lesson teaches the operator, and that has been used. If the lesson were to give an element the text , and you did this, I would not expect you to fail the tests: Aside I might be becoming pessimistic in my teaching pedagogy, but we cannot truly expect to keep changing all these lessons forever, as more and more cases are found - there is a "good enough" point, IMO.
Yes, I believe that if a user uses the solution that stated, they know how works already, which fulfills the objective of the lesson.
I don't think your example is equivalent at all. The end value is supposed to be the result of decrementing, not just assigning a final value. Clearly, they do not if they can not decrement the starting value to the final value that is asked for. I see no reason why anyone that understands what the challenge is asking for would do that assignment. We are not just blindly looking for the operator to be used. We are looking for the value to be decremented to using the operator. An example would be a lesson where you ask someone to use a word in a sentence and they use the word incorrectly. They may have used the word but if it is used incorrectly they do not understand the word. Using it in a sentence means correctly using it, not just blindly shoving it into a sentence. I would think a test with a regex that looks for an assignment to be good enough here.
You're right, my bad. As I understand it, you want to use regex to check if an assignment is present, and if it is, fail the test? I think that would work well.
second test should be updated. Right now you can leave the initial code even though the test says it should be replaced. It should test that is not present in the code. that no assignment is used.
I see, thank you for the clarification!

Discussion:
`myVar = myVar - 1;` should be changed. ```js <del> assert( /lets*myVars*=s*11;s*/*.*s*([-]{2}s*myVar|myVars*[-]{2});/.test(code) ); </del> <ins> assert(!code.match(/myVars*=s*myVars*[-]s*1.*?;?/)); ``` You should not assign `myVar` with `10`. ```js assert(!code.match(/myVars*=s*10.*?;?/)); </ins> ``` You should use the `--` operator on `myVar`.
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: --<!-- Add a clear and concise description of what you expected to happen. --Tests should fail because the text is incorrect (it should not be surrounded by spaces or newlines). You see the hint: Also, it's quite easy to fail this challenge by having spaces or newlines around the "Camper Cafe Menu" string. It might be nice to have an additional test specifically to catch that.
The title element isn't stripped away, so I think we could query the DOM and look at the .

Discussion:
Your `<title>` element should be nested in your `<head>` element. ```js <del> assert(code.match(/<head>s*<title>.*</title>s*</head>/i)); </del> <ins> assert(code.match(/<head>s*<title>.*</title>s*</head>/si)); </ins> ``` Your `<title>` element should have the text `Camper Cafe Menu`. You may need to check your spelling. ```js <del> assert(code.match(/<title>camperscafesmenu</title>/i)); </del> <ins> assert.match(document.querySelector('title')?.innerText, /camper cafe menu/i); </ins> ``` # --seed--
Change:
!
Thanks for opening this issue. This looks something that can be fixed by "first time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
Thank you so much! Will do

Discussion:
It's better practice to choose one color as the dominant color, and use its complementary color as an accent to bring attention to certain content on the page. <del> First, in the `h1` rule, use the `rbg` function to set its background color to cyan. </del> <ins> First, in the `h1` rule, use the `rgb` function to set its background color to cyan. </ins> # --hints--
Change:
In lesson 10 of Learn Bash Scripting by Building Five Programs, the directions tell you to use this command: . But the command has an extra in questionnaire. The correct command should be !
I'm going to mark this issue for first-time contributors. Here is the file you should be looking at to work on a fix: Please make sure you have read . 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!
Hello, I have worked on that issue and solved it. Also made the PR , please refer it.
please link this issue in the PR, otherwise they are not linked
Hello, I am following guidelines created a new branch installed coderoad v0.9.3 committed changes on file now running command and getting error Please can anyone give any suggestions
The latest version branch from the repository needs to exist locally:
Mentioned PR.
I see this has been solved multiple times but I'm going to add to that as I complete my first contribution. Great documentation by the way! Super easy to setup my local environment!

Discussion:
extends ../layout block content <del> .jumbotron .col-sm-8.col-sm-offset-2 form(method='POST') </del> <ins> .col-sm-8.col-sm-offset-2.jumbotron form(method='POST', action="/forgot") </ins> h1 Forgot Password input(type='hidden', name='_csrf', value=_csrf) .form-group

button.btn.btn-primary(type='submit') i.fa.fa-key | Reset Password
Change:
<!-- NOTE: If you want to become an author on freeCodeCamp, you can find everything here: --<!-- If you are reporting an issue with an article on our News publication, please follow this link to send an email to our editorial team --<!-- Add a link to the page with the problem. --<!-- Describe the problem and how to reproduce it. --<!-- A clear and concise description of how you want to update it. --<!-- If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box). --!
Hi ! Thank you for finding this typo. I have the first timers only label since this is an easy fix. For those interested in fixing this issue, here is the file you need to change. Proposed fix: The border-radius property accepts up to four values to round the top-left, top-right, bottom-right, and bottom-left corners. Please also read through our . When the file is fixed, please make a PR referencing this issue and it will be reviewed. Happy contributing!
I'm going to start looking into this.
Thank you for fixing the issue. It was the first time for me on Github. I'm a total newbie in the webdev coding bootcamp.

Discussion:
# --description-- <del> The `border-radius` property accepts up to four values to round the round the top-left, top-right, bottom-right, and bottom-left corners. </del> <ins> The `border-radius` property accepts up to four values to round the top-left, top-right, bottom-right, and bottom-left corners. </ins> Round the top-left corner of `.three` by 30 pixels, the top-right by 25 pixels, the bottom-right by 60 pixels, and bottom-left by 12 pixels.
Change:
An issue was brought up in the forum where the user could not pass the challenge using firefox. They had the correct code and weren't using browser extensions. On google chrome and safari the test does pass. The test will only pass on Firefox using this code Correct answer not passing in firefox <img width="936" alt="Screen Shot 2022-01-25 at 8 44 56 AM" src="https://user-"Incorrect answer passing in firefox <img width="981" alt="Screen Shot 2022-01-25 at 8 45 31 AM" src="https://user-"- Device: [macbook pro] OS: [macOs Catalina] Browser: [Firefox] Version: [96.0.2]
Step 14 has the same issue. This is the correct code that passes in google chrome <img width="905" alt="Screen Shot 2022-01-25 at 8 57 21 AM" src="https://user-"Here is the same code but it doesn't pass with firefox <img width="915" alt="Screen Shot 2022-01-25 at 9 00 09 AM" src="https://user-"

Discussion:
You should give `.ground` a `background` of `linear-gradient(90deg, rgb(88, 175, 236), rgb(182, 255, 255))`. ```js <del> assert.include(['linear-gradient(90deg,rgb(88,175,236),rgb(182,255,255))', 'rgba(0,0,0,0)linear-gradient(45deg,rgb(118,201,255),rgb(247,255,222))repeatscroll0%0%'], new __helpers.CSSHelp(document).getStyle('.ground')?.getPropVal('background', true)); </del> <ins> assert.include(['linear-gradient(90deg,rgb(88,175,236),rgb(182,255,255))', 'rgba(0,0,0,0)linear-gradient(90deg,rgb(88,175,236),rgb(182,255,255))repeatscroll0%0%'], new __helpers.CSSHelp(document).getStyle('.ground')?.getPropVal('background', true)); </ins> ``` # --seed--

You should give `.left-mountain` a `background` of `linear-gradient(rgb(203, 241, 228), rgb(80, 183, 255))`. ```js <del> assert.include(['linear-gradient(rgb(203,241,228),rgb(80,183,255))', 'rgba(0,0,0,0)linear-gradient(45deg,rgb(118,201,255),rgb(247,255,222))repeatscroll0%0%'], new __helpers.CSSHelp(document).getStyle('.left-mountain')?.getPropVal('background', true)); </del> <ins> assert.include(['linear-gradient(rgb(203,241,228),rgb(80,183,255))', 'rgba(0,0,0,0)linear-gradient(rgb(203,241,228),rgb(80,183,255))repeatscroll0%0%'], new __helpers.CSSHelp(document).getStyle('.left-mountain')?.getPropVal('background', true)); </ins> ``` # --seed--

```html <!DOCTYPE html> <html> <head> <meta charset="UTF-8" /> <link rel="stylesheet" type="text/css" href="./styles.css" />
Change:
A file was create. A file was created. I have the first timers only label. Carefully read through the and the section on working with . After you have read through the contributing docs and fixed the typo, then you will make a PR in this . After you make the PR, someone from the team will review it. If you need help, then please ask on the or . Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing!

Discussion:
extends ../layout block content <del> .jumbotron .col-sm-8.col-sm-offset-2 form(method='POST') </del> <ins> .col-sm-8.col-sm-offset-2.jumbotron form(method='POST', action="/forgot") </ins> h1 Forgot Password input(type='hidden', name='_csrf', value=_csrf) .form-group

button.btn.btn-primary(type='submit') i.fa.fa-key | Reset Password
Change:
Should be adequate <!-- Please complete the following information. --- Device: [Laptop] OS: [openSUSE Tumbleweed] Browser: [Vivaldi] Version: 5.0]
Thank you for reporting this issue. This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging (PR ). This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue. If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding.
Wait, sorry, there are more adequates to fix. And it seems is doing it

Discussion:
# --description-- <del> Give each `fieldset` an adaquate `name` attribute. Then, give both unordered lists a `class` of `answers-list`. </del> <ins> Give each `fieldset` an adequate `name` attribute. Then, give both unordered lists a `class` of `answers-list`. </ins> Finally, use the `legend` to caption the content of the `fieldset` by placing a true/false question as the text content. # --hints-- <del> You should give the first `fieldset` an adaquate `name` attribute. _Hint: I would use `html-question-one`_ </del> <ins> You should give the first `fieldset` an adequate `name` attribute. _Hint: I would use `html-question-one`_ </ins> ```js assert.notEmpty(document.querySelectorAll('fieldset')?.[0]?.name);
Change:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. -- <!-- Copy and paste the code from the editor that you used in between the back-ticks below: --The code above shouldn't pass the challenge. In the challenge, it is asked to make the function addTogether return undefined If either argument isn’t a valid number. Please add a test case where the first argument isn’t a valid number, but the second is. Example:
Great catch! Thank you for reporting!

Discussion:
assert.isUndefined(addTogether(2)([3])); ``` <ins> `addTogether("2", 3)` should return `undefined`. ```js assert.isUndefined(addTogether('2', 3)); ``` </ins> # --seed-- ## --seed-contents--
Change:
<!-- NOTE: If you want to become an author on freeCodeCamp, you can find everything here: --<!-- If you are reporting an issue with an article on our News publication, please follow this link to send an email to our editorial team -- <!-- Add a link to the page with the problem. --View the string in Crowdin where the is being parsed as a separate sentence. This is grammatically incorrect anyway and should be updated. <!-- Describe the problem and how to reproduce it. --Update the sentence to: <!-- A clear and concise description of how you want to update it. --<!-- If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box). --

Discussion:
## Feedback on pull requests <del> > Congratulations! :tada: on making a PR and thanks a lot for taking the time to contribute. </del> <ins> > :tada: Congratulations on making a PR and thanks a lot for taking the time to contribute. </ins> Our moderators will now take a look and leave you feedback. Please be patient with the fellow moderators and respect their time. All pull requests are reviewed in due course.
Change:
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.

Discussion:
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.