jiebi/CodeConvo huggingface dataset:
Change:
describe('request-authorization', () => { describe('isWhiteListedPath', () => { const authRE = /^/auth//; <ins> const confirmEmailRE = /^/confirm-email$/; </ins> const newsShortLinksRE = /^/n/|^/p//; <ins> const publicUserRE = /^/api/users/get-public-profile$/; const publicUsernameRE = /^/api/users/exists$/; </ins> const resubscribeRE = /^/resubscribe//; const showCertRE = /^/certificate/showCert//; // note: signin may not have a trailing slash const signinRE = /^/signin/; <ins> const statusRE = /^/status/ping$/; </ins> const unsubscribedRE = /^/unsubscribed//; const unsubscribeRE = /^/u/|^/unsubscribe/|^/ue//; const updatePaypalRE = /^/donate/update-paypal/; const whiteList = [ authRE, <ins> confirmEmailRE, </ins> newsShortLinksRE, <ins> publicUserRE, publicUsernameRE, </ins> resubscribeRE, showCertRE, signinRE, <ins> statusRE, </ins> unsubscribedRE, unsubscribeRE, updatePaypalRE

Discussion:
These should be available without any access tokens: [x] Used for public profile views. [x] Used for confirming and email. [x] Health Check
Change:
return array; // Only change code above this line } <del> mergeSort([1, 4, 2, 8, 345, 123, 43, 32, 5643, 63, 123, 43, 2, 55, 1, 234, 92]); </del> ``` # --solutions--

Discussion:
The following challenges have an example function call in the seed code. These function calls should be removed and the related tests should be clarified to reflect the call instead. This sorting challenge is correct and could be used for reference.
Hi, nhcarrigan. I'd like to try to help and solve it. I'm still learning about the project so I would like to ask a question so I can understand the issue better. There is a function call in the file.. bubleSort([1,2,3....]) (example: implement-bubble-) ! And it should be removed from the seed section and transferred to here, similarly to implement-quick-sort: ! ! Is it correct or are there other files that I should be concerned about?
That is correct, yes - this same change should be completed on the four files I've linked. I would, however, recommend holding off on working on this until we receive additional consensus that this is the best way to proceed. If you run in to any questions, feel free to review our or ask in our or the .
Sounds great!! Thanks for the fast response. I will wait until further notice.
Hi MuriloMarquesSantos, are you still interested in fixing this issue?
Change:
# --hints-- <del> You should use an `a` element selector. ```js assert.exists(new __helpers.CSSHelp(document).getStyle('a')); ``` </del> You should give the `a` element a `color` of `#dfdfe2`. ```js <del> assert.equal(new __helpers.CSSHelp(document).getStyle('a')?.color, 'rgb(223, 223, 226)'); </del> <ins> const linkElement = document.querySelector("a"); assert.equal(window.getComputedStyle(linkElement)?.color, 'rgb(223, 223, 226)'); </ins> ``` # --seed--

Discussion:
Multiple CSS selectors are valid for this challenge, but only passes the tests. My code passes the tests. No response Device: Laptop OS: Windows 11 Browser: Edge Version: 119 Related: ,
I think the best thing to do here would be to query the DOM for the element directly, check the resulting colour from the query, and assert it is the colour we expect.
Before : ! After Adding the CSS block : ! The color changes, but the cant proceed forward successfully. I wish to contribute
Umm, I'm having second thoughts about this issue. Is it by design that the challenges only check one or two answers? I've seen few other complaints so maybe the vast majority of campers don't have a problem. Don't fix what's not broken, as they say...
I've heard it said before here that valid code should always pass. Ya, you don't need all of those elements in the selector list to change this link color, but the instructions are ambiguous enough that they don't say you can't have them. Granted, most people aren't going to get that detailed, but I have seen more than a few times in the forum where people used or for this step and can't figure out why it isn't passing, even though the hint is telling them to just use . So I do think this step should be fixed and suggestion is right on. Unless we want to change the instructions to require that they only use the element in the selector list.
This issue is open for contribution. The file that you should be updating is Requirements: Remove the "You should use an element selector." test Replace with in the "You should give the element a color of ." test Please make sure you read our as well as our from a pull request, 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:
The following challenges will make use of the `chat.pug` file. So, in your `routes.js` file, add a GET route pointing to `/chat` which makes use of `ensureAuthenticated`, and renders `chat.pug`, with `{ user: req.user }` passed as an argument to the response. Now, alter your existing `/auth/github/callback` route to set the `req.session.user_id = req.user.id`, and redirect to `/chat`. <del> Add `http` and `socket.io` as a dependency and require/instantiate them in your server defined as follows: </del> <ins> Add `socket.io@~2.3.0` as a dependency and require/instantiate it in your server defined as follows, with `http` (comes built-in with Nodejs): </ins> ```javascript const http = require('http').createServer(app);

Discussion:
Advanced Node and Express section needs package versions to the instructions, as discussed in: Example: " Add <codepassport.socketio</codeversion <codeX.X.X</code, <codeconnect-mongo</codeversion <codeX.X.X</code, and <codecookie-parser</codeversion <codeX.X.X</codeas dependencies and require them as <codepassportSocketIo</code, <codeMongoStore</code, and <codecookieParser</coderespectfully. " Before this is undertaken: [x] Wait for to be merged [ ] Discuss which versions to use and how to convey this ( or )
I am leaning more toward the requirement, myself. With the carat prefix, will install the latest minor version. In theory, updates to the minor version are backwards compatible and shouldn't create any issues with the tests or challenges. However, minor versions can include depreciation notices like . The feature will still work, but this could be confusing to a camper. Using the tilde prefix means will install the latest patch version, which includes bug fixes but shouldn't lead to any depreciation notices. I think this will offer the best long-term compatibility with our tests and challenge instructions.
Well, it has happened: Last versions which definitely work: I have tested this. Now, discussion: 1) Just ask for to be installed 2) Also change the lesson/code to work with this latest version?
Hey how is this show stopper coming along?
Ah yes... I have updated the label, because it should have been removed by . Can a PR automatically remove an issue's label? Otherwise, this issue is still open and help wanted , as there are many packages which need their versioning fixed. If no one else, I can slot in some time for this tomorrow.
No rush. Thanks for confirming, I have removed the assignment since this is no longer a showstopper.
thank you so much for the Thank you for the suggestion. It helped me alot
Change:
As seen in the previous challenge, `const` declaration alone doesn't really protect your data from mutation. To ensure your data doesn't change, JavaScript provides a function `Object.freeze` to prevent data mutation. <del> Once the object is frozen, you can no longer add, update, or delete properties from it. Any attempt at changing the object will be rejected without an error. </del> <ins> Any attempt at changing the object will be rejected, with an error thrown if the script is running in strict mode. </ins> ```js let obj = {

Discussion:
At the top, the challenge says, " Any attempt at changing the object will be rejected without an error." A few lines later it says, "The and obj.newProp assignments will result in errors". This seems to be conflicting information - will there be an error or not? Maybe the 2nd part should say "The and obj.newProp assignments will be rejected". !
Oddly, when I run the tests I can see an error in the log: [TypeError: Cannot assign to read only property 'PI' of object '#<Object'] But when I run the same code in jsFiddle there is no error in the console. Update: When I add "use strict" in jsFiddle I get an error. This challenge should definitely mention that you only get an error in strict mode! One of the previous challenges about "let" and "const" mention strict mode briefly, but it might be good to explain strict mode more. This page was helpful:
I do agree that some clarification here would be beneficial. Possibly changing that first line to `Any attempt at changing the object will be rejected, with an error thrown if the script is running in strict mode. And the second line being Thoughts?
That seems like a good solution Nich, I'll put a help wanted label on it!
Change:
"  </div>", "  <div class = "row text-center">", "    <div class = "col-xs-12 well message">", <del> "      The message will go here","   </div>", </del> <ins> "      The message will go here", "   </div>", </ins> "  </div>", "  <div class = "row text-center">", "    <div class = "col-xs-12">",

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

Discussion:
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-"
Change:
] ], "type": "hike", <del> "challengeType": 6 </del> <ins> "challengeType": 6, "nameEs": "Herramientas de desarrollo de Chrome: Recursos", "descriptionEs": [ "El panel de Recursos te permite inspeccionar los recursos que se cargan en la página, incluyendo IndexedDB o bases de datos SQL Web, almacenamiento local y de sesión, las galletas (cookies), memoria caché de aplicaciones, imágenes, fuentes y hojas de estilo.", "Puedes ver y editar toda esta información dentro del navegador.", "A medida que vayas construyendo aplicaciones web más avanzadas, juega con el panel de recursos y verás cómo te ayudará a entender los requisitos de tu aplicación y de tu página en tiempo real.", "Revisa documentación más detallada aquí: developers.google.com/web/tools/iterate/manage-data/index" ] </ins> }, { "id": "56b15f15632298c12f31517e",

Discussion:
[x] Chrome Dev Tools: Elements [x] Chrome Dev Tools: Network [x] Chrome Dev Tools: Sources [x] Chrome Dev Tools: Timeline [x] Chrome Dev Tools: Profiles [x] Chrome Dev Tools: Resources [x] Chrome Dev Tools: Audits [x] Chrome Dev Tools: Console [x] Chrome Dev Tools: Summary
Working on it
Change:
margin-top: 1.45rem; } <ins> .intro-layout p, .intro-layout li { font-family: 'Lato', sans-serif; } </ins> .intro-toc .list-group-item { margin: 5px auto; }

Discussion:
<!-- 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: Add a Link to the page with the problem: 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):
Change:
### --feedback-- <del> Places where you can buy and eat food. Don't forget the stress mark. </del> <ins> Places where you can buy and eat food. Don't forget the stress mark (`é`). </ins> # --scene--

Discussion:
Describe the bug Task 37 requires typing in one of the blanks. This can be problematic due to the letter, which might not be present in the used keyboard layout. Expected behavior I don't want to say to use completely different word for the fill the blank, as at some point there might be no other choice. There could be some kind way to ease up procuring of the letter in question, for example including it in the feedback, so it can be copied.
Hi I would love to work on this. If someone could point me in the right direction, that would be amazing!
Hi Thank you for being eager to contribute. This issue has not been triaged yet. Feel free to share your insights and ideas on the matter. However as far as the code contributing, take a look at the issues with label. 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. Thank you and happy coding.
Yes, I think in both of those challenges we can update the "Don't forget the stress mark." in the feedback to: "Don't forget the stress mark ()."
I will open the issue to contribution with this as the solution
Change:
background-image: none; box-shadow: inset 0 1px 4px rgba(0, 0, 0, 0.3); } <del> .btn-link { </del> <ins> .btn-link, .btn-link:focus, .btn-link:active { </ins> color: inherit; border: none; text-decoration: underline; background: transparent; <ins> padding: 0; outline: 0; </ins> } <del> .btn-link:hover { </del> <ins> .btn-link:hover, .btn-link:focus:active { </ins> background: var(--tertiary-background); text-decoration: none; color: inherit;

Discussion:
Describe the bug The 'Show other ways to donate' button looks like a link until you click on it, when it looks like a button. To Reproduce Steps to reproduce the behavior: to /donate on 'Show other ways to donate' : ! Expected behavior I think it should always look like a button, since clicking on it modifies the page rather than takes you to a new one.
I'll look into this.
Thanks If you could check with Ahmad as to what he wants here before submitting a PR (since he's worked on the formatting very recently), that would be great. I suspect he's a little busy right now, though, so I just put this issue here to keep track of it.
Yeap. I'll talk to him after a day or two.
Please assign this to me if possible.
i see your concern with consistency, and this button looks like a link by design. The behaviour is caused by the :focus state of the button. thanks for your interest. we could make the button behave identical to a link by targeting :hover and :focus:hover styles. Let's agree on the solution before the implementation. on a second thought this might not even be an issue. before the users click on the button, it looks like a link so they are not distracted from the main task. but when users click on it, the focus state keeps the button more visible. what do you think?
The other ways to donate should be an actual link and styled as such not a button.
if you are still interested in working on this issue, could please go ahead with replacing the 'Show other ways to donate' button with an actual link with onClick={this.toggleOtherOptions}.
Thanks! Going straight away to fix it.
Change:
"<code>g</code> means that we want to search the entire string for this pattern.", "<code>i</code> means that we want to ignore the case (uppercase or lowercase) when searching for the pattern.", "<code>Regular expressions</code> are usually surrounded by <code>/</code> symbols.", <del> "Let's try selecting all the occurances of the word <code>and</code> in the string <code>George Boole and Alan Turing went to the shop and got some milk</code>. We can do this by replacing the <code>.+</code> part of our regular expression with the current <code>regular expression</code> with the word <code>and</code>." </del> <ins> "Let's try selecting all the occurrences of the word <code>and</code> in the string <code>George Boole and Alan Turing went to the shop and got some milk</code>. We can do this by replacing the <code>.+</code> part of our regular expression with the current <code>regular expression</code> with the word <code>and</code>." </ins> ], "tests":[ "assert(test==2, 'Your <code>regular expression</code> should find two occurrences of the word <code>and</code>');",

Discussion:
In waypoint description there is a word with missing letter "r" and wrong letter - "a" instead "e" . I don't know English well, therefore this typo a slightly confused me:) !
Change:
const mapStateToProps = createSelector( userSelector, <del> ({ theme = 'default' }) => ({ theme }) </del> <ins> ({ theme = 'night' }) => ({ theme }) </ins> ); const mapDispatchToProps = dispatch =>

Discussion:
to replicate. go to incognito do not sign in go to learn choose a challenge !
I can take a look at this
thank you. There might to be other inconsistencies with the theme. If you try different scenarios like switching the theme, logging in logging out, and visiting the challenge page. That should expose any related issues that needs fixing. let me know if I could be of any help.
in displaytheme is in charge of the code editor's theme. and in the theme colors get injected. we need night mode by default if not signed in
I haven't tested, but it does look like the cause. Hope you don't mind raising a PR, since I don't want to take your credit
I pointed it out for you. But yea, I have it ready.
Change:
"difficulty": "1.06", "description": [ "Return an array consisting of the largest numbers in the provided array. The array will contain 4 sub-arrays.", <del> "Remember, you an iterate through an array with a simple for loop, and access each member with array syntax arr[i] .", </del> <ins> "Remember, you can iterate through an array with a simple for loop, and access each member with array syntax arr[i] .", </ins> "If you are writing your own Chai.js tests, be sure to use a deep equal statement instead of an equal statement when comparing arrays." ], "challengeEntryPoint": "largestOfFour([[4, 5, 1, 3], [13, 27, 18, 26], [32, 35, 37, 39], [1000, 1001, 857, 1]]);",

Discussion:
Need to document the rename challenge tool and the i18n sync tool. Sometime later this week. Not urgent.
I can take this on?
Go for it, Thanks!
I will start with the rename challenge tool, for the i18n sync, I will wait news if it works now
Change:
In the Elements pane, you can see the entire HTML structure of your page. You can click on any of the elements in this pane to select that specific element. Alternatively, you can click the blue-highlighted icon shown below on the left, and hover over any element on the page. <del> <img src="https://cdn.freecodecamp.org/curriculum/odin-project/the-box-model/inspector-icon.png" alt="Aweb development environment with developer tools open, highlighting a blue inspector icon in the top-left for selecting webpage elements to view HTML structure and styles."> </del> <ins> <img src="https://cdn.freecodecamp.org/curriculum/odin-project/the-box-model/inspector-icon.png" alt="A web development environment with developer tools open, highlighting a blue inspector icon in the top-left for selecting webpage elements to view HTML structure and styles."> </ins> When an element is selected, the Styles tab will show all the currently applied styles, as well as any styles that are being overwritten (indicated by a strikethrough of the text). For example, if you use the inspector to click on the “Your Career in Web Development Starts Here” header on <a href="https://www.theodinproject.com/" target="_blank">the The Odin Project homepage</a>, on the right-hand side you’ll see all the styles that are currently affecting the element, as seen below:

Discussion:
There is a typo in the alt text: Fix the typo in the following files:
This issue is open to first-time code contributors to this repository. The files that you should be updating are linked in the original post. 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.
Change:
import { createExecuteChallengeSaga } from './execute-challenge-saga'; import { createCurrentChallengeSaga } from './current-challenge-saga'; import { challengeTypes } from '../../../../utils/challengeTypes'; <del> import { userSelector } from '../../../redux'; </del> export const ns = 'challenge'; export const backendNS = 'backendChallenge';

Discussion:
I did not see anyone raising this issue, but I don't think the background of the preview in default or night mode should be anything other than white unless the coding exercise specifically changes the background to something else. The preview should be exactly what you would see in a browser. In almost all the challenges, the background would be white. !
I share your concerns The reason we changed the color of the display is that a white display is discomforting to the eye on night mode when everything else is dark. so we injected some styles to harmonize the view in general. That convention was carried over to light mode.
It might be better to default to white in light mode, same as the editor. As for night mode, some of the css challenges might need some changes to look reasonable in both modes. For instance, in night mode, looks like this: ! If we change the seed code to it would become ! It would have to be case-by-case, though.
That is a very good point. I will defer this to
Logically, I have to agree with - displaying anything other than what the code in the editor would produce might confuse campers. But it is a little rough on the eyes to have the white background on night mode. And the current theme looks a lot better - so it's a tough call. I scrolled through a number of challenges, and there's quite a few that don't look right with the blue background. So there might be a decent amount of work to go through and fix all of them.
I really like the new theme, but a preview should be a true preview. We want to make this like the real world. Developers working in some kind of night mode on their favorite local editors, still expect to check the "real" result of the code they have written on a browser or in a preview mode in their local editors. The night mode should only apply to the editor or the non-preview part of the FCC site. Anything else is just not realistic.
The preview should be white.
I agree with everyone here on this thread. The preview should remain white. Note that soon the preview won't always be there on the right side "brightening up" the user interface and ruining people's night mode experience.

Soon we will have a single column layout where you the preview only shows up when you click a button to show it, or it loads in a separate tab. - could you update the styling on this so that the preview area is unaffected by our styling?
Definitely.