jiebi/CodeConvo huggingface dataset:
Change:
# --description-- <del> In this project, you will build a set of football team cards and learn about nested objects, object destructuring, default parameters, event listeners, and switch statements. All of the HTML and CSS for this project has been provided for you. </del> <ins> In this project, you will build a set of football team cards and learn about nested objects, object destructuring, and default parameters. All of the HTML and CSS for this project has been provided for you. </ins> Start by accessing the `id` called `"team"` from the HTML document and storing it in a `const` variable called `teamName`.

Discussion:
The description of the project to build football team cards in the js beta curriculum says: In this project, you will build a set of football team cards and learn about nested objects, object destructuring, default parameters, event listeners, and switch statements. But switch statements were introduced in the date formatter project (step 16, 17). I think the description should be modified therefore to not mention learning switch statements. I haven't actually done this project, so I don't actually know if it re-teaches switch statements or not. (it would be nice if the date formatter description mentioned learning about switch statements though) N/A N/A No response N/A No response
I don't really get the title of this challenge, what "modern javascript methods" is it referring to, is it just the ? Because surely both map and filter has already been taught at this point. I'm also not sure the switch is really needed. It seems a little verbose and a lot of boilerplate. Compared to say:
Let's go ahead and remove switch statements from the description and the first step.
I feel like the switch used in the code is because the idea of the challenge, among other things, was to teach it. It takes up a lot of the total code. Not mentioning it, doesn't really change that fact. Not unless, we remove the switch from the code as well.
That's a fair point. I'd be fine rewriting the challenge to use the example you shared earlier.
Hi! I am a new, first time contributor. Can I put up a PR for this issue? Seems like a simple fix, just removing 'switch statements' from description and first step
It could be seen as reinforcement. I'm not saying we have to remove it, I'm just saying it seems like part of the point of this challenge was to teach the switch, which is why it is in the description and the code. Not sure how often we use switch statements, but this project is definitely reinforcing it. So we might want to keep it just for that reason. This also isn't the first time we teach and it is in the description as well. Maybe that could be it, reinforcement. Or something like that?
changing the description slightly seems like an easy way to fix the issue
I like this copy, yeah.
Change:
> [!NOTE] > If you are using Apple Devices with M1 Chip to run the application locally, it is suggested to use Node v14.7 or above. You might run into issues with dependencies like Sharp otherwise. <ins> ## Working With Other Languages To see how the client renders in another language go to [testing the client app in a world language.](how-to-work-on-localized-client-webapp.md#Testing-the-Client-App-in-a-World-Language) </ins> ## Getting Help If you are stuck and need help, feel free to ask questions in the ['Contributors' category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay).

Discussion:
Looking forward for reporting a security issue: Please report security issues by following our security policy: Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: The real url for spanish is so i expect that when running locally I could click on globe icon and then choose spanish to go to: http://localhost:8000/espanol/learn/javascript-algorithms-and-data-structures/basic-javascript/storing-values-with-the-assignment-operator But instead i get gatsby dev 404 page. Expected behavior I expect to be able to get to spanish version page. Screenshots If applicable, add screenshots to help explain your problem. <img width="1429" alt="image" src=""Additional context Add any other context about the problem here.
This is actually because the app doesn't build every language at once. It builds a single language - our internationalised sites are separate instances of the application. The language selector does not work locally because there is, in fact, nothing at the endpoint.
We could add a note to: like To see how the client renders in another language go to I think that should be enough.
Change:
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:
<Spacer /> {isOpen ? ( <ProjectModal <del> files={challengeFiles} </del> <ins> files={files} </ins> handleSolutionModalHide={handleSolutionModalHide} isOpen={isOpen} projectTitle={projectTitle}

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:
# --description-- <del> Now create an image tag and give it the `class` `"user-img"`. Use template interpolation to set the `src` attribute to `image` you destructured earlier. Set the `alt` attribute to `author` followed by the text `"avatar"`. Make sure there is a space between the `author` variable and the word `"avatar"`, for example, `"Quincy Larson avatar"`. </del> <ins> Now create an image tag and give it the `class` `"user-img"`. Use string interpolation to set the `src` attribute to `image` you destructured earlier. Set the `alt` attribute to `author` followed by the text `"avatar"`. Make sure there is a space between the `author` variable and the word `"avatar"`, for example, `"Quincy Larson avatar"`. </ins> # --hints--

Discussion:
When talking about template literals sometimes we use "template interpolation", I have not been able to find good documentation on this wording. It should be changed to "string interpolation" or "template literal" as needed. The changes needed are as follow: template interpolation -string interpolation use template interpolation -use string interpolation Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. 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.
Change:
- text: The anchor tag <code>color</code> should remain black, only add CSS rules for the <code>:hover</code> state. testString: assert($('a').css('color') == 'rgb(0, 0, 0)', 'The anchor tag <code>color</code> should remain black, only add CSS rules for the <code>:hover</code> state.'); - text: The anchor tag should have a <code>color</code> of blue on hover. <del> testString: assert(code.match(/a:hovers*?{s*?color:s*?blue;s*?}/gi), 'The anchor tag should have a <code>color</code> of blue on hover.'); </del> <ins> testString: assert(code.match(/a:hovers*?{s*?color:s*?(blue|rgba(s*?0s*?,s*?0s*?,s*?255s*?,s*?1s*?)|#00F|rgb(s*?0s*?,s*?0s*?,s*?255s*?))s*?;s*?}/gi), 'The anchor tag should have a <code>color</code> of blue on hover.'); </ins> ```

Discussion:
Good day, everybody! Hopefully you have had a great day so far :) I want to mention a possibility for improvement. In the lesson the task is: The code editor has a CSS rule to style all tags black. Add a rule so that when the user hovers over the tag, the is blue. The code window shows: The lesson doesn't allow to solve this task using HexCode: I think that this solution (and others; I tested rgb and rgba and both don't work as well) should be allowed as the code already entered suggests using this way of expressing "blue" and the task itself doesn't state anything about how to express it. Hex code and other ways of expressing "blue" were taught already at this point. ! michael-wise pointed this already out in the FCC forum. A bot referred him to GitHub, but I was unable to locate the issue here. Of course, this is just a minor issue, but I hope this nevertheless helps! All the best, Leo
I see what you mean - the test checks if the solution contains 'a:hover {color: blue}', not if the link actually turns blue. I'll see what I can do.
Change:
"assert.isFalse((/<i>/gi).test($("h3").html()), 'message: Do not alter any other text.');" ], "type": "waypoint", <del> "challengeType": 0 </del> <ins> "challengeType": 0, "nameEs": "Cambia el texto de un elemento usando jQuery", "descriptionEs": [ "Con jQuery, puedes cambiar el texto que está entre las etiquetas de apertura y cierre de un elemento.  Incluso puedes cambiar marcado HTML.", "jQuery tiene una función llamada <code>.html()</code> que te permite añadir etiquetas HTML y texto dentro de un elemento.  Cualquier contenido que estuviese previamente dentro del elemento será remplazado por completo con el contenido que proveas usando esta función.", "He aquí como reescribes y pones en itálicas el texto de nuestro encabezado:", "<code>$("h3").html("&#60;i&#62;jQuery Playground&#60;/i&#62;");</code>", "jQuery también tiene una función similar llamada <code>.text()</code> que sólo altera el texto sin añadir etiquetas.", "Cambia el botón con identificación <code>target4</code> de forma que su texto quede en itálicas." ] </ins> }, { "id": "bad87fee1348bd9aed708826",

Discussion:
[x] Learn how Script Tags and Document Ready Work [x] Target HTML Elements with Selectors Using jQuery [x] Target Elements by Class Using jQuery [x] Target Elements by ID Using jQuery [x] Delete your jQuery Functions [x] Target the same element with multiple jQuery Selectors [x] Remove Classes from an element with jQuery [x] Change the CSS of an Element Using jQuery [x] Disable an Element Using jQuery [x] Change Text Inside an Element Using jQuery [x] Remove an Element Using jQuery [x] Use appendTo to Move Elements with jQuery [x] Clone an Element Using jQuery [x] Target the Parent of an Element Using jQuery [x] Target the Children of an Element Using jQuery [x] Target a Specific Child of an Element Using jQuery [x] Target Even Numbered Elements Using jQuery [x] Use jQuery to Modify the Entire Page
Checking
Change:
const testStr1 = 'one^|uno||three^^^^|four^^^|^cuatro|'; const res1 = ['one|uno', '', 'three^^', 'four^|cuatro', '']; <del> // TODO add more tests </del> const testStr2 = 'a@&bcd&ef&&@@hi'; const res2 = ['a&bcd', 'ef', '', '@hi']; <ins> const testStr3 = 'hello^|world|how^are^you^|'; const res3 = ['hello|world', 'howareyou|']; </ins> ``` ## --seed-contents--

Discussion:
Hey any more context on this issue? Seems pretty empty to be already opened with the label.
the challenge needs more tests, it's not a high priority thing, that comment has been there for a few years already
Change:
# --description-- <del> The data you get from a `GET` request is not usable at first. To make the data usable, you can use the `.json()` method on the `Response` object to parse it into JSON. If you expand the `Prototype` of the `Response` object in the console, you will see the `.json()` method there. </del> <ins> The data you get from a `GET` request is not usable at first. To make the data usable, you can use the `.json()` method on the `Response` object to parse it into JSON. If you expand the `Prototype` of the `Response` object in the browser console, you will see the `.json()` method there. </ins> Remove `console.log(res)` and implicitly return `res.json()` instead.

Discussion:
in step 3 of the fcc authors project (js beta), they mention that we should " Open your console and expand the Response object to see what it contains." but it doesn't actually say that this means we should open the browser's console. It would be best to explicitly say "Open your browser's console and ..." instead. (Also step 4 mentions the console too but if we fix step 3, then hopefully people will remember which console was being referred to when they move to step 4) N/A specific reference to the browser's console is needed so as not to be confused with the fcc console No response N/A No response
I think we should apply the change to both step 3 and step 4 as campers might lose the context if they stop at step 3 and start step 4 some time later. I'm opening this issue to first-time code contributors to this repository. The changes you need to make are: Change "Open your console" to "Open the browser console" in Change "in the console" to "in the browser console" in We typically do not assign issues. Instead, we accept the most quality contribution followed by the one that is made first. Please make sure you read our as well as our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Happy contributing.
I have created a PR
Change:
editor.setSize("100%", "auto"); <ins> var attempts = 0; if (attempts) { attempts = 0; } </ins> // Default value for editor if one isn't provided in (i.e. a challenge) var nonChallengeValue = '/*Welcome to Bonfire, Free Code Camp's future CoderByte replacement.n' + 'Please feel free to use Bonfire as an in-browser playground and linting tool.n' +

Discussion:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --In the challenge CSS Flexbox: Use the flex-wrap Property to Wrap a Row or Column, the value wrap-reverse is defined: wrap-reverse: "wraps items from right-to-left if they are in a row, or bottom-to-top if they are in a column." This definition is not correct. Actually wrap-reverse wrap content changing de cross-axis direction, bottom to top in a row, and left to right in a column. Browser Name: Browser Version: Operating System:
I'd like to take on this issue please
Since the curriculum content is in the repo, I submitted the PR there.
Ok, thanks Simon.
Change:
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

Discussion:
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.) !
Change:
display: block } <del> } </del>  No newline at end of file <ins> } </ins>

Discussion:
The hover animation of map button overlaps the ending of the search bar.  Browser Name, Version: Chrome (latest release) & Firefox (57.0.2). Operating System: Windows 10 Pro 32 bit. Mobile, Desktop, or Tablet: Desktop.
I would like to take on this issue if it still exists
I've already submitted a PR for it.
Change:
role='menu' > <li className='nav-news' role='menuitem'> <del> <Link external={true} to='/news'> </del> <ins> <Link external={true} sameTab={true} to='/news'> </ins> /news </Link> </li> <li className='nav-forum' role='menuitem'> <del> <Link external={true} to='/forum'> </del> <ins> <Link external={true} sameTab={true} to='/forum'> </ins> /forum </Link> </li>

Discussion:
The top nav items on the forum and news does not open in a new tab. We would like the same functionality on learn for consistency.
Do we want all external links to navigate without opening a tab? A quick search suggests that all the links in the footer open new tabs, as do a couple in . I think it's better UX to leave tab opening to the user, but I thought I'd check.
If you decide to go ahead with this, I'd like to have a go at this
I think we want this to remain as is except for the navigation links up top on the navbar, which are the most used links on the platform. This is to make it consistent with the behaviour on forum and news. can you proceed and make the changes. This will likely affect some of the routing. I would like to test this before working on the client app for chinese curriculum.
Change:
assert.equal(weapons[0].power, 5); ``` <del> Your second `weapons` object should have the `name` set to `dagger` and the `power` set to 30`. </del> <ins> Your second `weapons` object should have the `name` set to `dagger` and the `power` set to `30`. </ins> ```js assert.equal(weapons[1].name, 'dagger'); assert.equal(weapons[1].power, 30); ``` <del> Your third `weapons` object should have the `name` set to `claw hammer` and the `power` set to 50. </del> <ins> Your third `weapons` object should have the `name` set to `claw hammer` and the `power` set to `50`. </ins> ```js assert.equal(weapons[2].name, 'claw hammer'); assert.equal(weapons[2].power, 50); ``` <del> Your fourth `weapons` object should have the `name` set to `sword` and the `power` set to 100. </del> <ins> Your fourth `weapons` object should have the `name` set to `sword` and the `power` set to `100`. </ins> ```js assert.equal(weapons[3].name, 'sword');

Discussion:
There is a typo in Step 108, the word is single while it should be . Here is the typo in step 102, there is a missing code block in this line it should be this in step 81, there are three missing code blocks in these line they should be If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first. Happy contributing.
I would like to work on this.
feel free to open a pull request, after you have read .
I have opened a PR please let me know if there are any changes or improvements that needs to be done.
Change:
assert(labelElem.hasAttribute('for')); ``` <del> The new `label` element should have a `for` attribute with the value `loving`. You have either omitted the value or have a typo. Remember that attribute values should be surrounded with quotation marks. </del> <ins> The new `label` element should have a `for` attribute with the value `loving`.  Expected `--fcc-expected--`, but found `--fcc-actual--`. </ins> ```js const labelElem = $('input[type="checkbox"]')[0].nextElementSibling; <del> assert(labelElem.getAttribute('for').match(/^loving$/)); </del> <ins> assert.equal(labelElem.getAttribute('for'), 'loving'); </ins> ``` The text `Loving` should be nested within the new `label` element. You have either omitted the text or have a typo.

Discussion:
This is a common error on this Step - we should modify the hint to point out the capitalization User should receive hint that helps them see the capitalization error 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] No response
The current hint is: "The new element should have a attribute with the value . You have either omitted the value or have a typo. Remember that attribute values should be surrounded with quotation marks." Technically, the attribute value doesn't need to be wrapped in quotes since there are no spaces in the value. Also, it will pass if you don't use quotes for the value, so this part of the hint seems unneeded and should probably be removed. Are you thinking that we should have a separate test just to check whether the value has been capitalized? Or do you think we just add a warning to the current hint reminding them that capitalization (or lack thereof) matters?
I'm not quite sure what the best way forward would be. I just know what most questions for this step on the forum are related to Loving vs loving.
We do have dynamic hints we can use:
Change:
```js /** <del> Backend challenges don't need solutions, because they would need to be tested against a full working project. </del> <ins> Backend challenges don't need solutions, because they would need to be tested against a full working project. </ins> Please check our contributing guidelines to learn more. */ ```

Discussion:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Affected page Add a link to the coding challenge with the problem. Your code Copy and paste the code from the editor that you used in between the back-ticks below: Expected behavior Given that this is the Replit starter project and the GET route has no code, I expected test no. 3 to fail. Screenshots If applicable, add screenshots to help explain your problem. you can drag and drop, png, jpg, gif, etc. in this box. System (please complete the following information): Device: [PC] OS: [Windows 10] Browser: [chrome] Version: Version 91.0.4472.77 (Official Build) (64-bit) Additional context Add any other context about the problem here. I am working through this project and found test 3 passes even before I had written any code. I made a new copy of the Replit starter project and ran the tests to see if I could replicate the issue. Test 3 still passes. The github personal- file shows that it supposedly makes several post requests and a get request, but somehow it passes without GET or POST routes.
It seems asserts are not even run, because promises are not fulfilled. Not sure if this is to be expected, but I'm surprised there isn't timeout like in other tests. I guess internally that doesn't make test not finished, so there's nothing to timeout...? Adding before or each post request in , , , would make it timeout as expected.
Change:
# --hints-- <del> You could have `card_number = '4111-1111-4555-1141'` within the main function. </del> <ins> You should have `card_number = '4111-1111-4555-1141'` within the main function. </ins> ```js ({

Discussion:
The hint text should read "You should have" instead of "You could have".
This issue is open to first-time code contributors to this repository. The files that you should be updating are: We typically do not assign issues. Instead, we accept the most quality contribution followed by the one that is made first. Please make sure you read our as well as our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Happy contributing.