jiebi/CodeConvo huggingface dataset:
Code change:
], [ "5a9d7295424fe3d0e10cad14", <del> "Cascading CSS variables" </del> <ins> "Inherit CSS Variables" </ins> ], [ "5a9d72a1424fe3d0e10cad15",

Related discussion:
text: I don't think this challenge is described correctly. The idea that a variable is only available to the element and it's children has nothing to do with cascading. It's a clear definition of scope. Cascading is the concept that if there are multiple of a thing, the last one wins, which is described in the previous challenge related to fallbacks. Just my 2cents for what it's worth, but if I had someone come in for an interview and tell me cascading was the idea that a variable could only be used by an element and it's children, I would consider that a wildly misunderstood concept.
Thanks for reporting this! While this challenge isn't intended to introduce the concepts of cascade and inheritance, it clearly does not use the terms correctly. I'll have a go at rewriting the challenge to show that CSS variables behave like ordinary properties in this respect.
for what it's worth, this was discussed a little bit in a previous issue that was never resolved - - perhaps it should be reworded since it has now come up multiple times.
Code change:
}; ``` <ins> If `value` submitted to `/api/check` is already placed in `puzzle` on that `coordinate`, the returned value will be an object containing a `valid` property with `true` if `value` is not conflicting. ```js async (getUserInput) => { const input = '..9..5.1.85.4....2432......1...69.83.9.....6.62.71...9......1945....4.37.4.3..6..'; const coordinate = 'C3'; const value = '2'; const data = await fetch(getUserInput('url') + '/api/check', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ puzzle: input, coordinate, value }) }); const parsed = await data.json(); assert.property(parsed, 'valid'); assert.isTrue(parsed.valid); }; ``` </ins> If the puzzle submitted to `/api/check` contains values which are not numbers or periods, the returned value will be `{ error: 'Invalid characters in puzzle' }` ```js

Related discussion:
text: Describe your problem and how to reproduce it: While working on the Sudoku solver project, one scenario came up that wasn't clear to me how to handle. The scenario is what do you do, if I ask to check a value of a cell with an existing value? For my project, I chose to return a conflict with the row, column, and region. However, I checked what the example app returns. The results it returns are logically inconsistent, which tells me this use case is undefined. For the example app: https://sudoku- coordinate enter C3, for value enter 2 (the existing value), click Check Placement returns value to 9, App returns value to 1, App returns These response are not logically consistent. For the first one, it appears to be checking against all of the existing values in the puzzle. For the second and third cases, it appears to be checking after replacing the value. I would expect this use case to be defined as either, it's a conflict, because there is an existing value at that cell or to replace the value in that cell and then check if it is valid or not and return the appropriate results. Add a Link to the page with the problem: ://sudoku- Tell us about your browser and operating system: Browser Name: Google Chrome Browser Version: 87.0.4280.67 (Official Build) (x86_64) Operating System: macOS Mojave 10.14.6
Yes, seems odd that you can place a value over an existing spot and it can return as valid Seems like this should be the response Or something along those lines
I do agree that this should be handled as a valid placement (given that the number is already present in that cell). Unless there is objection/disagreement, I'd be willing to open this up for contribution.
I also vote to make it behave as if it replaces the cell before checking validity. Or something along those lines. I have opened this up for contributions.
Code change:
function* validateUsernameSaga({ payload }) { try { <del> yield delay(500); </del> const { exists } = yield call(getUsernameExists, payload); yield put(validateUsernameComplete(exists)); } catch (e) {

Related discussion:
text: On the settings page, you can change your username. Any time you stop typing, it reads from the database to see if the username is available - we could change it so that it only makes a query when the user is ready. So instead of when they stop typing, we just let them choose the name they want, then when they click save we check if it's available. Not sure how big of a deal this is, I'm guessing users don't change their username often. Every little bit helps?
I've always wondered about this one. Definitely agree that we shouldn't hit the DB until the camper tries to submit.
I think we can go with the current implementation but wait for a meaningful pause to make sure the user is intending to submit the new username for validity check.
Code change:
# --description-- <del> Changing the `bottom-margin` to `5px` looks great. However, now the space between the `Cinnamon Roll` menu item and the second `hr` element does not match the space between the top `hr` element and the `Coffee` heading. </del> <ins> Changing the `margin-bottom` to `5px` looks great. However, now the space between the `Cinnamon Roll` menu item and the second `hr` element does not match the space between the top `hr` element and the `Coffee` heading. </ins> Add some more space by creating a class named `bottom-line` using `25px` for the `margin-top` property.

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. -- In the instructions, is an invalid css property. It should be . Alternatively, we could remove the code quotes and replace it with bottom margin. ! <!-- Please complete the following information. --- Device: Laptop OS: Windows 10 Browser: firefox Version: 98.0.1 (64-bit) <!-- Add any other context about the problem here. --
Thank you, for taking the time to open this. For simplicity, let us go with "". I have opened this up to first-timers only. An issue with the help wanted or first timers only 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
I would like to contribute Apologies for the redundant question here
Code change:
], "tests": [ "assert($("body").css("background-color") === "rgb(0, 0, 0)", 'Your <code>body</code> element should have a black background.')", <del> "assert(editor.match(/rgbs*(s*0s*,s*0s*,s*0s*)/ig), 'Use <code>rgb</code> to give your <code>body</code> element the <code>background-color</code> of black. For example <code>body { color&#58; rgb&#40;0&#44; 0&#44; 0&#41;; }</code>.')" </del> <ins> "assert(editor.match(/rgbs*(s*0s*,s*0s*,s*0s*)/ig), 'Use <code>rgb</code> to give your <code>body</code> element the <code>background-color</code> of black. For example <code>body { background-color&#58; rgb&#40;0&#44; 0&#44; 0&#41;; }</code>.')" </ins> ], "challengeSeed": [ "<style>",

Related discussion:
text: Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. Text for objective two says "Use rgb to give your body element the background-color of black. For example body { color: rgb(0, 0, 0); }." There should be "background-" in front of the "color" in the example.
Fixed with
Code change:
## Instructions <section id='instructions'> <del> Change the <code>while</code> loop in the code to a <code>do...while</code> loop so that the loop will push the number 10 to <code>myArray</code>, and <code>i</code> will be equal to <code>11</code> when your code finishes running. </del> <ins> Change the <code>while</code> loop in the code to a <code>do...while</code> loop so that the loop will only push the number 10 to <code>myArray</code>, and <code>i</code> will be equal to <code>11</code> when your code finishes running. </ins> </section> ## Tests

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: The description of the problem and the solution that passes are not the same. The code that passes this section would give you the wrong answer to the instructions. write the proper code for the instructions and it will not pass. try it. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: CHROME Browser Version: Version 71.0.3578.98 Operating System: OSX If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):
Can you be more specific? For example, what code passes the challenge which you think goes against the instructions?
I just came up with this solution based on the instructions and passed the test cases. ! After thinking about it more I can see how the instructions might be misleading. The following code pushes the number 10 to myArray, and i will be equal to 11 when the code finishes running, but the array equals [5, 6, 7, 8, 9, 10]. It might be less confusing if the instructions said "Change the loop in the code to a loop so that the loop will push only the number 10 to , and will be equal to when your code finishes running. !
the first pic is the way i tried it first and it wouldn't pass. i got it to pass changing the while: } while (i < 5); that should not have passed. i also had a few connection issues with that one. like i clicked on run test and the page would lockup. i would close my browser, reopen it, go to your page, click on curriculum, and it gave me a 404 error message a few times. Have a great day! Jeremiah Kalb
The code should definitely pass the tests, because you just need the loop to iterate one time. So, the while loop condition should evaluate to in the first iteration (which it does with that code). If you start with the original seeded code, is and not , so it is not going to add other numbers anyway.
Code change:
## Instructions <section id='instructions'> <del> Change the <code>while</code> loop in the code to a <code>do...while</code> loop so that the loop will push the number 10 to <code>myArray</code>, and <code>i</code> will be equal to <code>11</code> when your code finishes running. </del> <ins> Change the <code>while</code> loop in the code to a <code>do...while</code> loop so that the loop will only push the number 10 to <code>myArray</code>, and <code>i</code> will be equal to <code>11</code> when your code finishes running. </ins> </section> ## Tests

Related discussion:
text: That being said, the wording change you suggest might not be a bad idea. Would you be interested in creating a PR for this change you suggest?
I would love to do that.
How's your PR coming along?
I'm pretty sure I finished with it. Is there anything else I need to do with it? The correct PR is
this how i got mine to pass // Setup const myArray = []; let i = 10; // Only change code below this line do { (i); i++; } while (1 < 0);
Code change:
import security from './plugins/security'; import sessionAuth from './plugins/session-auth'; import { settingRoutes } from './routes/settings'; <ins> import { deprecatedEndpoints } from './routes/deprecated-endpoints'; </ins> import { auth0Routes, devLoginCallback } from './routes/auth'; import { testMiddleware } from './middleware'; import prismaPlugin from './db/prisma';

Related discussion:
text: Thanks for noticing this, Sem. As this route has been deprecated for a while, we should be able to safely sunset this route - NOT have it in the new API.
Reopening it as we're migrating deprecated endpoints as discussed in todays API meeting
Code change:
"We can use if statements in JavaScript to only execute code if a certain condition is met.", "if statements require some sort of boolean condition to evaluate.", "Example:", <del> "<code> if (1 == 2) {</code>", </del> <ins> "<code> if (1 === 2) {</code>", </ins> "<code>&thinsp;&thinsp;return(true);</code>", "<code>}</code>", "<code>else {</code>",

Related discussion:
text: Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. Example: if (1 == 2) { //should be === return(true); } else { return(false); } Let's use if and else statements to make a coin-flip game. Create an if-else statement to return heads if the flip var is zero and to return tails if it's not.
Code change:
## Description <section id='description'> <del> You may recall from <a href="waypoint-comparison-with-the-equality-operator" target="_blank">Comparison with the Equality Operator</a> that all comparison operators return a boolean <code>true</code> or <code>false</code> value. </del> <ins> You may recall from <a href="learn/javascript-algorithms-and-data-structures/basic-javascript/comparison-with-the-equality-operator" target="_blank">Comparison with the Equality Operator</a> that all comparison operators return a boolean <code>true</code> or <code>false</code> value. </ins> Sometimes people use an if/else statement to do a comparison, like this: <blockquote>function isEqual(a,b) {<br>&nbsp;&nbsp;if (a === b) {<br>&nbsp;&nbsp;&nbsp;&nbsp;return true;<br>&nbsp;&nbsp;} else {<br>&nbsp;&nbsp;&nbsp;&nbsp;return false;<br>&nbsp;&nbsp;}<br>}</blockquote> But there's a better way to do this. Since <code>===</code> returns <code>true</code> or <code>false</code>, we can return the result of the comparison:

Related discussion:
text: ! !
It is always best if you post an actual link to the challenge also. Thank you.
Here is the URL. Babar Khan
I would love to fix that issue, could I?
Sure. You will need to setup and test your changes locally.
How to setup ?
Start by taking a look at . If you have further questions or run into any problems, check out our . You can post your questions there and someone will get back with you.
Thank you all for reporting and helping to resolve this issue.
Babar Khan