jiebi/CodeConvo huggingface dataset:
Code change:
# --description-- <del> Inside the `case` for `mm-dd-yyyy-h-mm`, set the `textContent` property of `currentDateParagraph` to `${month}-${day}-${year} ${hours} Hours ${minutes} Minutes`. </del> <ins> When the user selects the `Month, Day, Year, Hours, Minutes` option from the dropdown, you need to display the date in the format `mm-dd-yyyy h Hours m Minutes`. Inside the `case` for `mm-dd-yyyy-h-mm`, use string interpolation to assign the formatted date from above to the `textContent` property of `currentDateParagraph`. Make sure to use the `month`, `day`, `year`, `hours`, and `minutes` variables in your answer. </ins> # --hints-- <del> You should assign `${month}-${day}-${year} ${hours} Hours ${minutes} Minutes` to the `textContent` property of `currentDateParagraph`. </del> <ins> Your answer should follow this format: `mm-dd-yyyy h Hours m Minutes`. Replace `mm`, `dd`, `yyyy`, `h`, and `m` with the `month`, `day`, `year`, `hours`, and `minutes` variables you created earlier. </ins> ```js const pattern = /cases*('|")mm-dd-yyyy-h-mm1s*:s*currentDateParagraph.textContents*=s*`(${month}-${day}-${year} ${hours} Hours ${minutes} Minutes)`/;

Related discussion:
text: In step 28 of the date formatter project, the hint shows the solution, which is not hard to explain. This might not be ideal for learning, as a camper (especially a JS) beginner can go ahead and copy the solution from the hint without bothering to understand what the code does. ! N/A The solution should not be in the hint text because it can be described. We could go with something like this: If the text is too long, it is better to break the hint text and test into two. 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 same text is in the description, it would make sense to change description to not give out answer at the start.
Based on the activity I have seen on the forum, I think campers will struggle with connecting "interpolate the , , , , and " with the desired format we are asking from them. I think it would be best to show them the desired format in the description. something like this for the description
So we should leave the hint as is and modify the description text?
for the hint text we could go with this
Ok. Let's open it up for contribution then.
This has been opened 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 please use this for the updated description please use this for the updated hint text Happy coding
Code change:
testString: myRegex.lastIndex = 0; assert(myRegex.test('Eleanor Roosevelt')); - text: Your regex <code>myRegex</code> should return <code>false</code> for the string <code>Franklin Rosevelt</code> testString: myRegex.lastIndex = 0; assert(!myRegex.test('Franklin Rosevelt')); <ins> - text: Your regex <code>myRegex</code> should return <code>false</code> for the string <code>Frank Roosevelt</code> testString: myRegex.lastIndex = 0; assert(!myRegex.test('Frank Roosevelt')); </ins> - text: You should use <code>.test()</code> to test the regex. testString: assert(code.match(/myRegex.test(s*myStrings*)/)); - text: Your result should return <code>true</code>.

Related discussion:
text: <!-- 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: I'm on the Regular Expressions: Check For Mixed Grouping of Characters. I was able to pass this checkpoint with a solution that doesn't meet the objectives of the assignment. I used the following code: With this code I match just “Roosevelt” which is only part of the name(s), yet I still pass the assignment. Add a Link to the page with the problem: With this code I match just “Roosevelt” which is only part of the name(s) we are supposed to match for this assignment, yet I still pass the assignment. Tell us about your browser and operating system: Browser Name: Chrome Browser Version: Version 79.0.3945.117 (Official Build) (64-bit) Operating System: Windows 10 pro If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):
I think that the regex you've written should pass the test. The part is a capturing group, so the regex will match or . The as a quantifier will match the above 0 or 1 times. This means that your regex will capture as well as Unless, I'm mistaken, I hope this helps :)
Apologies... Actually, I've re-read the instructions. I think you may be onto something.
Yeah, the problem is that it matches the string " Roosevelt". A simple solution would be to add another test that makes sure it fails if you use, say, "Frank Roosevelt".
Would like to have a crack at this
Go ahead and create a PR.
Had a go Please see
Code change:
<p> <strong>Quincy Larson</strong> </p> <del> <p>Executive Director, freeCodeCamp.org</p> </del> <ins> <p>{t('certification.executive')}</p> </ins> </div> <Row> <del> <p className='verify'>Verify this certification at {certURL}</p> </del> <ins> <p className='verify'> {t('certification.verify', { certURL: certURL })} </p> </ins> </Row> </footer> </Row>

Related discussion:
text: The certification files () have been uploaded to Crowdin for translation. However, the React Component itself does not use the translation helper for the text within the certification (such as ). The component and files should be updated to allow this.
Code change:
render() { const { duration, planId, amount } = this.state; const isSubscription = duration !== 'onetime'; <ins> if (!paypalClientId) { return null; } </ins> return ( <PayPalButtonScriptLoader amount={amount} <del> clinetId={paypalClientId} </del> <ins> clientId={paypalClientId} </ins> createOrder={(data, actions) => { return actions.order.create({ purchase_units: [

Related discussion:
text: Describe the bug The PayPal sdk gets called by the local site, even when there are no keys specified in .env To Reproduce Steps to reproduce the behavior: to any page with a donation component the console a 400 error Expected behavior If the keys are missing, PayPal should not be contacted. Screenshots !
/cc
Hello guys! Does this happen on page or somewhere else too? Can't recreate it anymore, happend only once. I'd like to help with that issue if you don't mind Also, I noticed PaypalButton has a typo -in props, example:
it should happen if you hard refresh on donation page. (and on donation modal) That script loads the button. A solution would be to check for paypalClientId in the render of PaypalButton component and return PayPalButtonScriptLoader only if paypalClientId is truthy.
PR is ready. Could you please take a look? Also about the Stripe issue. I'm not sure if it's expected/known but if I don't configure the key for stripe, the page isn't loading for me at all. <img width="1054" alt="CleanShot 2020-05-11 at 02 59 29 src="https://user-"
Yikes, that seems like it needs a fix as well. Thanks for catching that.
Code change:
except: continue if len(exp_ball_list_copy) == 0: <del> success += 1 probability = success/num_experiments </del> <ins> success += 1 probability = success/num_experiments </ins> return probability ```

Related discussion:
text: Faulty method of the class can expose itself only during function tests. Case when number of balls to draw is higher than number of balls in hat is not tested explicitly, but it can fail function test, as it includes such experiment. - - Depending on the number of balls to draw and number of balls in Hat: Remove the required number of balls randomly selected, from the Hat. If number of balls to draw is higher than the number of balls, return all the balls. Test for the method checks only the first case: The second behavior is not checked explicitly, but it's a part of the second sub-case in the function test. This creates situation where passing method test and failing function test, can suggest to camper that issue lies in the function. Example with faulty method: Error: Adding test to check second behavior of the method would make debugging easier for campers, as it would show more clearly where is the issue. No response n/a No response
Code change:
{ objectID: `default-hit-${searchQuery}`, query: searchQuery, <del> url: `https://freecodecamp.org/news/search/?query=${encodeURIComponent( </del> <ins> url: `https://www.freecodecamp.org/news/search/?query=${encodeURIComponent( </ins> searchQuery )}`, title: `See all results for ${searchQuery}`,

Related discussion:
text: Describe the bug Using the search-Field and clicking "See all results ..." To Reproduce Steps to reproduce the behavior: to '' on 'Search Field' and enter s.th. I did "Flutter" and then I clicked "See all results for Flutter" error: "404 Page not found" I think the error is easy to fix: The automatic created result link after clicking has double "news"-part: if I manually remove one "news" as the result would be the correct one.
Thanks for the report! It seems it's a problem with redirection. redirects to and the link is to which redirects to cc:
Thank you for reporting this This was also a problem on /news. I deployed a quick fix and am working on PRs now. I noticed that we could change the URLs in the search related files from to This seems to get around the problematic redirect, at least for search results. Still an issue we need to investigate further for other use cases.
search is still broken? I can't get anything to load for generic searches.
what sort of generic searches are not loading for you? Things seem to be working on my end whether I search from .org/ or .news/.
working on my side on news and learn from multiple locations for the initial test case.
!
Should it say something like "No results for for 'this is a generic search', please try a different query"?
Thanks for the gif, I see what you mean now. The behavior should be a message that says "No tutorials found" and not to allow the search to complete. There's a PR for this on News , and I'll start working on the implementation in the main repo.
I am going close this since the above prs address the issue. Feel free to reopen if you think this issue has been closed by mistake.
Has the fix landed on production. I am able to reproduce the issue?
has not landed yet on learn. but you could see the fix on /news
The query string is passed on to the news application. URL is available on the GIF that I sent.
we deployed the updated theme to News, so you shouldn't be able to enter a long string there and hit the search results page. Once the fix to Learn is deployed you won't be able to pass long strings with no hits to News like in the GIF.
Code change:
{ objectID: `default-hit-${searchQuery}`, query: searchQuery, <del> url: `https://freecodecamp.org/news/search/?query=${encodeURIComponent( </del> <ins> url: `https://www.freecodecamp.org/news/search/?query=${encodeURIComponent( </ins> searchQuery )}`, title: `See all results for ${searchQuery}`,

Related discussion:
text: Quick follow up, is there anything that is preventing us from deploying?
sorry for the delay in deploying. We just got access to the client VM to clear out the old builds. We'll do that later today and get all these changes out.
Great, thanks for confirming. Apologies I have the keys to the VMs a couple days ago. I missed letting you know. I have also cleared the older builds. You should be able to simply run a build. Thanks.
No worries man. Thank you for adding our keys. We should have checked to see if we had access yet. We're just about to go in now and run a build.
This fix has been deployed. The problem in the gif above should no longer be possible on or
Code change:
Your code should have two `meta` elements. ```js <del> assert(code.match(/<meta.*/?>/g).length === 2); </del> <ins> assert(code.match(/<meta.*?/?>/g).length === 2); </ins> ``` Your `meta` element should have a `name` attribute with a value of `viewport`.

Related discussion:
text: If the user adds the new tag on the same line as the first tag then the test will fail. The hint will tell the user that they should have two tags, which they do. As soon as the new tag is moved to a new line then the test will pass. If we want to require that new tag be on a separate line then we should mention this in the instructions or give a hint that tells the user it must be on its own line. Otherwise we should update the test to stop checking for this. No response Confirmed in both Firefox and Chrome. No response
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: Changes to make: You will need to change this test: The regex needs to become . Explanation: the matches everything but line breaks, so the pattern with matches all the line up to the , in case of two meta tags on the same line, it matches both of them at once. Adding the in front of makes it a lazy matching, meaning it will match as little as possible while satisfying the pattern, and if the two meta tags are on the same line it will end the match at the first . Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in 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.
Code change:
) return drawn <del> def experiment(hat, expected_balls, num_balls_drawn, num_experiments): </del> <ins> def experiment(hat, expected_balls, num_balls_drawn, num_experiments): </ins> expected_balls_list = [] drawn_list = [] success = 0

Related discussion:
text: Faulty method of the class can expose itself only during function tests. Case when number of balls to draw is higher than number of balls in hat is not tested explicitly, but it can fail function test, as it includes such experiment. - - Depending on the number of balls to draw and number of balls in Hat: Remove the required number of balls randomly selected, from the Hat. If number of balls to draw is higher than the number of balls, return all the balls. Test for the method checks only the first case: The second behavior is not checked explicitly, but it's a part of the second sub-case in the function test. This creates situation where passing method test and failing function test, can suggest to camper that issue lies in the function. Example with faulty method: Error: Adding test to check second behavior of the method would make debugging easier for campers, as it would show more clearly where is the issue. No response n/a No response
Code change:
Typeface plays an important role in the accessibility of a page. Some fonts are easier to read than others, and this is especially true on low-resolution screens. <del> Change the font for both the `h1` and `h2` elements to `Verdana`, and use another sans-serif _web safe_ font as a fallback. </del> <ins> Change the font for both the `h1` and `h2` elements to `Verdana`, and use another web-safe font in the sans-serif family as a fallback. </ins> Also, add a `border-bottom` of `4px solid #dfdfe2` to `h2` elements to make the sections distinct.

Related discussion:
text: <!-- 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. --in here should exist <code</codeelement: &lt;codesans-serif&lt;/code ! <!-- If applicable, add screenshots to help explain your problem. you can drag and drop, png, jpg, gif, etc. in this box. --<!-- Please complete the following information. --win11 Firefox Device: [e.g. iPhone6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.4] Browser: [e.g. chrome, safari] Version: [e.g. 22] <!-- Add any other context about the problem here. --I want to modify it myselfbut I don't know how to deal with it. I don't know how to find him
Hi thanks for raising this issue, but there's nothing to fix here. The reason is that sans-serif is not being used as a programming term here, it is referring to the class of fonts. Multiple different fonts, such as Arial and Helvetica, fall into this class.
Hi@ Verdana similarly referring to the class of fonts, but please note picture, Verdana is surrounded <codeVerdana </code! in here should keep consistent
Thanks, that's a good point. I think Verdana should simply be plain text for consistency.
and The instruction to set the preferential font to is not a suggestion for a family of fonts. It is an instruction to use the code-word as the preferential font. It should remain within a element. Specifically, we are talking about family-names and generic-names : is not a generic-name font.
It's a bit of grey area, to be honest, but I feel like this is not really code. Reason being, it's just the name of specific font family called Verdana. It's not a keyword or part of any specific language, it just a string id that lets you get a via a rule.
Am I missing something?
Code change:
Typeface plays an important role in the accessibility of a page. Some fonts are easier to read than others, and this is especially true on low-resolution screens. <del> Change the font for both the `h1` and `h2` elements to `Verdana`, and use another sans-serif _web safe_ font as a fallback. </del> <ins> Change the font for both the `h1` and `h2` elements to `Verdana`, and use another web-safe font in the sans-serif family as a fallback. </ins> Also, add a `border-bottom` of `4px solid #dfdfe2` to `h2` elements to make the sections distinct.

Related discussion:
text: The challenge expects Campers to use the code , if they put anything else, it will fail. js const gs = (s) =new __helpers.CSSHelp(document).getStyle(s); const style = gs('h1, h2') gs('h2, h1'); assert.include(style?.fontFamily, 'Verdana'); `
and sans-serif both part of the actual css code !
My two cents, for what it's worth. I think Verdana should remain marked up as code since the instructions are specifically telling the user to use Verdana for the initial font. I've found other courses that have the font name marked up as code in the instructions as well. And it just seems that in general, whenever the instructions tell the user exactly what value to add, the value is marked up as code. And I also think that sans-serif should not be marked up as code since it is referring to a family of fonts and the tests will accept five different fonts for the fallback, so we aren't telling the user specifically what to use here. I'm guessing any confusion stems from the fact that one of the acceptable fall back fonts is sans-serif itself. Perhaps we could reword this a little? "..., and use another web-safe font in the sans-serif family as a fallback."
Thank you all very muchI understand itsans-serif is a family, Verdana is a sans-serif family menber. I think the suggestion is very good. <br !
Let's go with wording, I think that should be clearer than what we have.
How should I further locate where the file is !
is the file you need. We're in the process of making it easier to search for individual steps, but for now you can search for the title (Step 17 in this case) within that folder. For instance
&nbsp;thank you ---Original--- From: "Oliver Date: Fri, Apr 8, 2022 19:10 PM To: Cc: Subject: Re: [freeCodeCamp/freeCodeCamp] in here should exist <code&gt;</code&gt;element (Issue ) is the file you need. We're in the process of making it easier to search for individual steps, but for now you can search for the title (Step 17 in this case) within that folder.
Code change:
Typeface plays an important role in the accessibility of a page. Some fonts are easier to read than others, and this is especially true on low-resolution screens. <del> Change the font for both the `h1` and `h2` elements to `Verdana`, and use another sans-serif _web safe_ font as a fallback. </del> <ins> Change the font for both the `h1` and `h2` elements to `Verdana`, and use another web-safe font in the sans-serif family as a fallback. </ins> Also, add a `border-bottom` of `4px solid #dfdfe2` to `h2` elements to make the sections distinct.

Related discussion:
text: For instance grep -r 'Step 17' — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID:
Code change:
id: 'execute-challenge', label: 'Run tests', /* eslint-disable no-bitwise */ <del> keybindings: [monaco.KeyMod.CtrlCmd | monaco.KeyCode.Enter], </del> <ins> keybindings: [ monaco.KeyMod.CtrlCmd | monaco.KeyCode.Enter, monaco.KeyMod.WinCtrl | monaco.KeyCode.Enter ], </ins> run: () => { if (props.usesMultifileEditor && !isFinalProject(props.challengeType)) { if (challengeIsComplete()) {

Related discussion:
text: Even though on macOS it would seem that Ctrl+Enter does not work & Cmd+Enter does; website still tells you to use Ctrl+Enter. I think this might end up being confusing for some - and should be fairly straightforward of a change. All coding pages You must use macOS for this issue. to any coding challenge your changes will see button underneath says "Check your code (Ctrl + Enter)" Ctrl + Enter will happen. Cmd + Enter behaviour will occur. It should tell the user correct shortcut (Cmd + Enter) instead of (Ctrl + Enter) depending on the platform. <img width="647" alt="Screenshot 2022-06-09 at 16 52 28" src="https://user-"- Device: M1 MacBook Pro OS: macOS 12.0.1 Browser: Safari Version: 15.1 No response
I would like to handle this issue as a first contribution. My proposal would be to use (). Use Ctrl + Enter as a fallback and define a special case for macOS cases. Alternatively we could use () however that is not widely supported as opposed to . As far as I can tell on mobile we don't show modifier keys on the button; so I'll preserve that behaviour. I can't change the labels on this issue - I don't think this is severe enough to be classified as a bug based on definition; my apologies regarding that.
Hey thanks for raising this issue and don't worry about the labels, they need to be handled by maintainers. What you've suggested does sound good to me, so if you're happy to take this on, that's awesome.
I've created the PR however; I've updated non English translations as well in here to use dynamic values; however not really sure how to align it with the crowdin. Since updated translations should coincide with this change; any opinions on this?
Do not worry, I think you are putting too much effort into it. Simply drop the changes to those files and as the bot mentioned, they will get updated eventually via our translation workflow. As for the bug itself: I am 100% sure at some point we introduced a regression, because (in addition to the implicit Cmd + Enter) was working since the inception of the code editor. do you happen to know if this was just an accident with the new editor?