jiebi/CodeConvo huggingface dataset:
Change:
style: { base: { fontSize: '18px', <del> color: `${theme === 'night' ? '#fff' : '#0a0a23'}` </del> <ins> color: `${theme === 'night' ? '#fff' : '#0a0a23'}`, '::placeholder': { color: `#858591` } </ins> } } };

Discussion:
! Steps to reproduce the behavior: on night mode challenges until the donate modal shows up has black text on fCC blue background Note that the text is white or light gray when you start typing - it's just the placeholder text that you can't read.
So the place holder text appears when stripe loads in the background. We should keep the form behind a loader and only display it once stripe loads.
That would fix the font color of the placeholder text? Seems like some CSS would work, but you're closer to that area than me. To be clear, I'm talking about the placeholder credit card number and expiration date in the screen shot. It might be hard to see the text, but it's there.
I think we can simply change the placeholder text color using css and it will probably work fine.
! changing the color here would work
That would change the color of the input but not the placeholder. Although there should be an option for that. this is strange since I get the following on production. <img width="389" alt="Screen Shot 2021-10-06 at 11 35 48 AM" src="https://user-"
Just gave it a quick test: Chrome 94.0.4606.61 - works - shows what's in screen shot Firefox 92.0 - doesn't work - shows what's in my screen shot So it seems to be a firefox issue. Can anyone else reproduce this in firefox?
Yup. I'm using Firefox Developer and it looks like this: !
Change:
# --description-- <del> Create a selector to target your `td` elements within your table body. Give them a width to fill the viewport, with a minimum and maximum of `4rem`. This approach ensures that the width is fixed, whereas setting `width` specifically would allow the elements to shrink to the container (because we are using flexbox). </del> <ins> Create a selector to target your `td` elements within your table body. Give them a width to fill the viewport, with a minimum and maximum of `4rem`. This approach ensures that the width is fixed, whereas setting `width` specifically would allow the elements to shrink to the container. </ins> # --hints--

Discussion:
The phrase "because we are using flexbox" is not clear here. There was no flexbox for table or tr or td. It is not clear why setting width to 100vw works in such way It will be cool to have clear explanation about setting td width to 100vw in table No response Device: MacBook Pro OS: Ventura 13.0.1 Browser: Chrome Version: 109.0.5414.119 No response
Where is the code of this issue?
I believe it's in the folder, written in one of its files.
Have you fixed the issue yet ?
I am waiting for the issue to be triaged by a maintainer.
This issue is related and might lead to a different code solution for step 52:
The phrase needs to be removed from the challenge description. An issue with the or 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 The file to be changed is:
Change:
"</div>" ], "challengeType": 0, <del> "type": "waypoint" </del> <ins> "type": "waypoint", "nameEs": "Convierte datos JSON a datos HTML", "descriptionEs": [ "Ahora que estamos obteniendo datos de una API JSON, mostremóslos en nuestro HTML.", "Podemos usar el método <code>.forEach()</code> para recorrer nuestros datos y modificar nuestros elementos HTML.", "En primer lugar, vamos a declarar una variable llamada <code>html</code> con <code>var html = "";</code>.", "Después, iteremos a traveś de nuestro JSON, añadiendo más HTML a esa variable. Cuando se termina el ciclo, vamos a presentarla. ", "Aquí está el código que hace esto:", "<code>json.forEach(function(val) {</code>", "<code>&nbsp;&nbsp;var keys = Object.keys(val);</code>", "<code>&nbsp;&nbsp;html += "&lt;div class = 'cat'&gt;";</code>", "<code>&nbsp;&nbsp;keys.forEach(function(key) {</code>", "<code>&nbsp;&nbsp;&nbsp;&nbsp;html += "&lt;b&gt;" + key + "&lt;/b&gt;: " + val[key] + "&lt;br&gt;";</code>", "<code>&nbsp;&nbsp;});</code>", "<code>&nbsp;&nbsp;html += "&lt;/div&gt;&lt;br&gt;";</code>", "<code>});</code>" ] </ins> }, { "id": "bb000000000000000000004", <del> "title":  "Render Images from Data Sources", </del> <ins> "title": "Render Images from Data Sources", </ins> "description": [ "In the JSON that we receive data from Free Code Camp's Cat Photo API.", "We've seen from the last two lessons that each object in our JSON array contains an <code>imageLink</code> key with a value that is the url of a cat's image.",

Discussion:
[x] Trigger Click Events with jQuery [x] Change Text with Click Events [x] Get JSON with the jQuery getJSON Method [x] Convert JSON Data to HTML [x] Render Images from Data Sources [x] Prefilter JSON [x] Get Geo-location Data
Trabajando en esta
Change:
assert.isTrue(rulesContainer.checkVisibility()); ``` <del> When your `rulesBtn` is clicked, your `rulesBtn` should say `Hide Rules`. </del> <ins> When your `rulesBtn` is clicked, your `rulesBtn` should say `Hide rules`. </ins> ```js <del> assert.strictEqual(rulesBtn.innerText.trim(), "Hide Rules"); </del> <ins> assert.strictEqual(rulesBtn.innerText.trim(), "Hide rules"); </ins> ``` When your `rulesBtn` is clicked again, your `isModalShowing` should be `false`.

Discussion:
Initial text of the button is . After step clicking button is expected to change text to , capitalizing the second word. Clicking it again is expected to change text to . Which is too differing from initial capitalization. n/a Capitalization should be consistent throughout the project. Either Show rules and Hide rules; or Show Rules and Hide Rules. No response n/a No response
We will do this option
Change:
<div> <ChallengeTitle introPath={introPath} <ins> isCompleted={isChallengeCompleted} </ins> nextChallengePath={nextChallengePath} prevChallengePath={prevChallengePath} showPrevNextBtns={showPrevNextBtns}

Discussion:
In the new beta (currently at ), it would be great if a challenge page indicated somehow when the challenge has already been completed. Currently, since user inputed code is not saved, there is no indication on a challenge page that it has already been completed.
We need a check mark in the title or a badge or to indicate the same?
The most elegant thing I can think of to have something like the little circular check mark next to the title like how it is on the learn homepage - only if it's been solved, and don't show anything if it hasn't.
That would be a nice way to handle it. Please go forth if you are interested in this?
Change:
<!-- AUDIO REFERENCE: <del> Jake: Hey. You are Sarah, right? I'm Jake, from Security. </del> <ins> Jake: Hey. You're Sarah, right? I'm Jake, from Security. </ins> --> # --description--

Discussion:
Change "You are Sarah" to "You're Sarah" in step 150, 154, and 155 of Learn Greetings in your First Day at the Office. The change is to match the caption text. (The text isn't visible on the Task 155 page, but in the code.) Change "You are Sarah" to "You're Sarah" in the following files:
We introduce contraction form in task 1 () so I assume we would want to use contractions in later tasks. But I'll wait for the curriculum team to confirm before opening this issue up for contribution. (If we don't want to use contraction in these tasks, the caption text should be updated to match the fill the blank text.)
Change:
{ allowedTags: [], allowedAttributes: [] <del> }); </del> <ins> }).replace(/&quot;/g, '"'); </ins> if (data.body !== sanitizedBody) { req.flash('errors', { msg: 'HTML is not allowed'

Discussion:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Test for this lesson may not check the syntax for any constructor syntax, instead looks like it's tested by output. EIther user provide the constructor(correct/expected way) or not, challenge passes. Browser Name: Chrome Browser Version: 67 Operating System: Win7
I'm on it.
following solution works to passs the test: function makeClass() { "use strict"; / Alter code below this line / class Vegetable { constructor(Vegetable) { this. Vegetable = Vegetable; } } / Alter code above this line / return Vegetable; } const Vegetable = makeClass(); const carrot = new Vegetable('carrot'); (); // =should be 'carrot'
Hello, Unfortunately, this solution doesn't work for me. (The same as in the "Hint": ) Error message: // running tests should return carrot. // tests completed
sorry to hear that! Would you mind posting your solution here so we could take a look?
Hello Kristofer, Thank you for your email. (ES6: Use class Syntax to Define a Constructor Function) I have already got help from FreeCodeCamp. I used the solution from "HINT", but it didn't work. class Vegetable { constructor(Vegetable){ this.Vegetable = Vegetable; } } What worked is the code below: class Vegetable { constructor(name) { = name; } } Thank you. Kind regards, Zsolt
Change:
"convert('Dolce & Gabbana');" ], "tests": [ <del> "assert.strictEqual(convert('Dolce & Gabbana'), 'Dolce &amp; Gabbana', 'should escape characters');", "assert.strictEqual(convert('Hamburgers < Pizza < Tacos'), 'Hamburgers &lt; Pizza &lt; Tacos', 'should escape characters');", "assert.strictEqual(convert('Sixty > twelve'), 'Sixty &gt; twelve', 'should escape characters');", "assert.strictEqual(convert('Stuff in "quotation marks"'), 'Stuff in &quot;quotation marks&quot;', 'should escape characters');", "assert.strictEqual(convert("Shindler's List"), 'Shindler&apos;s List', 'should escape characters');", "assert.strictEqual(convert('<>'), '&lt;&gt;', 'should escape characters');", </del> <ins> "assert.match(convert('Dolce & Gabbana'), /Dolce &(amp|AMP|#x00026|#38); Gabbana/, 'should escape characters');", "assert.match(convert('Hamburgers < Pizza < Tacos'), /Hamburgers &(lt|LT|#x0003C|#60); Pizza &(lt|LT|#x0003C|#60); Tacos/, 'should escape characters');", "assert.match(convert('Sixty > twelve'), /Sixty &(gt|GT|#x0003E|#62); twelve/, 'should escape characters');", "assert.match(convert('Stuff in "quotation marks"'), /Stuff in &(quot|QUOT|#x00022|#34);quotation marks&(quot|QUOT|#x00022|#34);/, 'should escape characters');", "assert.match(convert("Shindler's List"), /Shindler&(apos|#x00027|#39);s List/, 'should escape characters');", "assert.match(convert('<>'), /&(lt|LT|#x0003C|#60);&(gt|GT|#x0003E|#62);/, 'should escape characters');", </ins> "assert.strictEqual(convert('abc'), 'abc', 'should handle strings with nothing to escape');" ], "MDNlinks": [

Discussion:
Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. The capital letter versions of HTML entities are not valid for the tests. Perhaps you could or them through. Also maybe you could remind users to include the ";" at the end of their entities in the description. Thanks for all your teams great work! I'm loving
I fixed the allowed capitalization. The shows every entity with a semicolon at the end, so I don't think it's necessary to add a reminder.
Change:
import { userByNameSelector } from '../../../redux'; import FullWidthRow from '../../helpers/FullWidthRow'; import { ButtonSpacer, Spacer } from '../../helpers'; <ins> import './certifications.css'; </ins> const mapStateToProps = (state, props) => createSelector(

Discussion:
!
Could you give a link to the page as then it might be easier to solve the issue?
This should be the case on the user's profile page. You can reproduce by setting the certificate keys to true in the user object.
I could work on this!
I am already working on it.
Thanks for letting me know!
a reasonable fix would be to give the grid that contains the profile a class and on the css, change the button under that class and have . you will end up with something like this. here it is on small and large screens <img width="681" alt="screen shot 2019-02-22 at 2 18 10 pm" src="https://user-"<img width="1095" alt="screen shot 2019-02-22 at 2 17 53 pm" src="https://user-"
Similar solution could be applied to these donate buttons probably. but the selectors should be very specific not to change the styling on other buttons in the platform. <img width="669" alt="screen shot 2019-02-23 at 2 09 14 pm" src="https://user-"<img width="502" alt="screen shot 2019-02-23 at 2 08 51 pm" src="https://user-"
Hey or Can you take this up? just updated us that he will be a bit busy with other things.
I'm on it
Change:
import { createExecuteChallengeSaga } from './execute-challenge-saga'; import { createCurrentChallengeSaga } from './current-challenge-saga'; import { challengeTypes } from '../../../../utils/challengeTypes'; <ins> import { completedChallengesSelector } from '../../../redux'; </ins> export const ns = 'challenge'; export const backendNS = 'backendChallenge';

Discussion:
In the new beta (currently at ), it would be great if a challenge page indicated somehow when the challenge has already been completed. Currently, since user inputed code is not saved, there is no indication on a challenge page that it has already been completed.
We need a check mark in the title or a badge or to indicate the same?
The most elegant thing I can think of to have something like the little circular check mark next to the title like how it is on the learn homepage - only if it's been solved, and don't show anything if it hasn't.
That would be a nice way to handle it. Please go forth if you are interested in this?
Change:
print('plain text:', message) print('encrypted text:', encrypted_text) --fcc-editable-region-- <del> # caesar() </del> <ins> caesar() </ins> --fcc-editable-region-- ```

Discussion:
In the Building a Cipher project, comment is first mentioned in step 51: But in step 59, we actually introduce comment and its syntax: In step 51, we introduce function parameters, so I think mentioning comment here would be a little overwhelming. I think the comment introduction should either be moved to an earlier challenge or kept in step 59. If we move the comment introduction to an earlier challenge, step 51 can be kept as-is. But if we keep comment introduction in step 59, we should update step 51. Instead of asking the users to comment out the code, I wonder if we could ask them to remove the line entirely (though the code is in step 50, so it's probably a little odd to immediately remove it in the next step).
This does seems to be out of sequence. I would suggest to not comment out in step 51 and let the exception be(the resolution is there in the coming steps). This part of the instruction can be updated from: to:
If we don't ask to comment out the function call in step 51 and tell the campers they will work on fixing the error in the next steps, it would be logic to address the error in the console () and require to pass the two positional arguments to the function call in step 52. But then the function will seem to work fine, although it's still using the and variable inside its body instead of the function parameters. The alternative is to ignore the in the console for step 52, and address it directly in step 53. For that we should simply keep the function call instead of commenting it out and there is no need to swap the step order. Honestly, I don't like particularly any of these options.
Change:
.iframe-scroll { position: fixed !important; margin-top: 75px; <del> z-index: 9999; </del> <ins> z-index: 1; </ins> } } @media only screen and (max-width: 992px) {

Discussion:
! This effects longer lines of codes by making it impossible to select code when trying to insert the cursor with the mouse. I saw where a commit to make the iphone stand out over footer by adding a z-index of 9999 but 9999 is too high. I'm doing a pull request right now that fixes the cover up issue on the code editor and still keeps the iphone above the footer as Quincy wanted. Thanks, Charles
Thanks, I didn't even think about the modal when I set the z-index that high. I'm taking a look at your pull request now.
Change:
"Let's delete the <code>"tails"</code> property from <code>myDog</code>." ], "tests": [ <del> "assert(myDog.bark === undefined, 'message: Delete the property <code>"bark"</code> from <code>myDog</code>.');" </del> <ins> "assert(myDog.tails === undefined, 'message: Delete the property <code>"tails"</code> from <code>myDog</code>.');" </ins> ], "challengeSeed": [ "var ourDog = {",

Discussion:
Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; WOW64; rv:41.0) Gecko/ Firefox/41.0</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: Issue: Properties box says: "Let's delete the "tails" property from myDog." Test success statement: "Delete the property "bark" from myDog." Test succeeds on deleting bark property, not tails.
I noticed that too !
Change:
## ![:rotating_light:](https://forum.freecodecamp.com/images/emoji/emoji_one/rotating_light.png?v=3 ":rotating_light:") Intermediate Code Solution: ```javascript <del> rating = watchList.map( (item) => ({"title":item["Title"], "rating":item["imdbRating"]}) ); </del> <ins> const rating = watchList.map(item => ({title: item["Title"], rating: item["imdbRating"]})); </ins> ``` ### Code Explanation: Using ES6 notation, each item in array is processed to extract title and rating.

Discussion:
I created a solution for this exercise, and it failed. When I looked at the hint solution, my code was basically the same. When I plug the hint solution into the code and run the test, it fails, also. The output window displays 'rating is not defined' four times. When I copy everything to JS Fiddle and run the code, it works as expected.
Did you ask this question on the forum and present the code you tried? That is the best place to ask. If you present your code to others on the forum and they conclude it is valid code which should pass the tests, then open an issue and present your code here also.
The problem is just that 'rating' has not been declared. The challenge code seems to be fine, but the guide should perhaps be a little stricter.
Change:
```js let testStr = "Pumpkin"; <del> let testRegex = /P(engu|umpk)in/g; </del> <ins> let testRegex = /P(engu|umpk)in/; </ins> testRegex.test(testStr); // Returns true ```

Discussion:
Link to the challenge: Adding a global flag to the regular expression has the test fail for the first two assertions. This can be confusing considering also how the challenge is introduced, since the code snippet explaining the concept shows the global flag being used. Update the code snippet introducing the challenge: However, since the global flag should not affect the outcome of the test (to what I can ascertain), a better suggestion would be to update the test itself, to account for its presence.
Thanks for the detailed report! I think it would make sense to do both. The isn't necessary, so it should not be there and it's not wrong, so we should not reject it.
It might be better to remove the global flag from the challenge example unless we also explain how and give some info on . I think in order to really know if we should fail the test when using the global flag we would have to consider how the code is supposed to run. Are we "emulating" that each is being run in isolation or are they executed one after the other.
Agreed. This challenge focuses on teaching the user about groups - the use of over seem incidental to me, as does the presence of the flag. Also, the challenge asks you to make sure so it's only asking you to use against once.
But it is when the test is called multiple times on the same regex. Isn't this kind of the same as when users use global variables which end up causing the user's code to fail for all tests except the first because the the global variable does not get reset each time?
I'm dumb - I'd completely failed to realise it's being run twice, once in the user's code and again in the tests. You're quite right and PR fixes that.
Challenge: Fails with: Passes with:
The example/seed code moves to 14. I guess one easy option would be to change the example string to something like "Fun with regular expressions!", that should let all the tests pass and accept the global flag. The problem is if the camper uses a different string to test the regex it may fail. So we might just have to reset before running the tests.
I assumed it would be the exact same fix as what Tom did:
yep, that's what I concluded. I think we can apply Tom's fix in , rather than modifying the tests. Either works, but that should be more concise.
Change:
"challengeType": 0, "nameEs": "Elige elementos HTML usando selectores y jQuery", "descriptionEs": [ <del> "Ahora tenemos una <code>función de documento listo</code>.", "Ahora vamos a escribir nuestra primera instrucción jQuery. Todas las funciones de jQuery comienzan con un <code>$</code>, al que suele referirse como <code>operador de signo de dólar</code>, o simplemente como <code>bling</code>. ", "jQuery a menudo selecciona un elemento HTML con un <code>selector</code>, y luego hace algo a ese elemento.", </del> <ins> "Ya tenemos una <code>función de documento listo</code>.", "Ahora vamos a escribir nuestra primera instrucción jQuery. Todas las funciones de jQuery comienzan con un <code>$</code>, al que suele referirse como <code>operador dólar</code>, o simplemente como <code>bling</code>. ", "jQuery a menudo selecciona un elemento HTML con un <code>selector</code>, y luego le hace algo a ese elemento.", </ins> "Por ejemplo, hagamos que todos tus elementos <code>button</code> reboten. Sólo tienes que añadir este código dentro de la función de documento listo: ", "<code>$("button").addClass("animated bounce")</code>", <del> "Ten en cuenta que ya hemos incluido tanto la biblioteca jQuery como la biblioteca Animate.css en segundo plano para que pueda utilizarlos en el editor. Así que estás usando jQuery para aplicar la clase <code>bounce</code> de Animate.css a sus elementos <code>button</code>." </del> <ins> "Ten en cuenta que ya hemos incluido tanto la biblioteca jQuery como la biblioteca Animate.css en segundo plano para que pueda utilizarlos en el editor. Así que estás usando jQuery para aplicar la clase <code>bounce</code> de Animate.css a tus elementos <code>button</code>." </ins> ] }, {

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