jiebi/CodeConvo huggingface dataset:
Change:
The instructions state "In your fourth tr element, add a th element with the text Total Liabilities." However it is not really clear that the user should or should not include a period. Users will have failed previous tasks if the period was omitted (periods are required on previous exercises) , therefore they will most likely add the period which will result in a failed test case. Also, if the period is included after "Liabilities", the error message gives "Your th element should have the text Total Liabilities." Which does not highlight the actual issue. Maybe making a different test case message that looks for the period would make it more understandable? The code above should highlight the issue of the period being present. The test case that is currently in place can confuse users that they have a spelling issue/spacing instead of the actual issue being the period at the end of "Liabilities". No response Device: Desktop OS: Windows 10 Browser: Chrome Version: Version 108.0.5359.125 No response
I was thinking, that we could change to But this doesn't make a coherent sentence. I am in favor of adding a new test.
I also think a new test case would be good.
Hi! We just opened a to fix it, but it was not accepted . Could you please kindly inform us some feedback about what was going wrong and what else we need to do? So that we can know where to focus. We appreciate any help, thank you!!
Hi Thanks for reaching out and creating a pull request. For reasons of sanity, we can't accept PRs from forks that organizations maintain. You should make a PR from your own personal GitHub account. You can collaborate with others and have commits made by multiple people, but one person needs to create the PR, and then others may push to the same PR should they wish. It is OK if you want to use the draft mode while collaborating. The person making the PR is responsible for ensuring the checklist is followed, tests are working, and so on. You can also commit on someone's behalf. See: Also, please create good, small, and succinct commit messages and PR titles. Keep your commits clean and avoid any merge commits unless you have conflicts to resolve. The final PR should not have dirty commits from collaborating on an organization fork like the previous PR. The reason is the maintainers of this project will need to validate your changes and the source of the commits. Keeping it clean makes everyone's lives easy. Thanks and happy coding!
Hi Mrugesh! Thank you for your precious feedback! I've switched back to my personal GitHub account, and made a pull request . This time the commits are clean and the messages are concise. Thank you for taking time reviewing! I appreciate any feedback. :D

Discussion:
assert(document.querySelectorAll('table')?.[1]?.querySelector('tbody')?.querySelectorAll('tr')?.[3]?.querySelector('th')); ``` <ins> Your text `Total Liabilities` should not include period `.`. ```js assert(document.querySelectorAll('table')?.[1]?.querySelector('tbody')?.querySelectorAll('tr')?.[3]?.querySelector('th')?.innerText !== 'Total Liabilities.'); ``` </ins> Your `th` element should have the text `Total Liabilities`. ```js
Change:
Users often delete the text or include it inside of the anchor text. Could we add a line to the instructions preventing this error? Common errors: Target solution: There should be a way to prevent these common errors. No response All No response
I'm happy to work on and fix this issue
While we are at it, I move that we include the opening and closing tags in the active editor region. I've see several people add these tags because they don't realize they are already there since they are in the gray area, far removed from the white editor region.
+1 to adding the p to the editable region
Just helped someone in the forums who extra tags on this step. Definitely need to put them in the editable region.
I am down to test moving them to the editor area first, if the issue persists, we can add new line After all, this looks like it's cased by a confusion 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.
I think I tried everything and it doesnt work
This isn't a location for help. You should use the Ask for Help button or go to the forum at

Discussion:
</section> </main> <footer> <del> <p> </del> --fcc-editable-region-- <del> No Copyright - freeCodeCamp.org </del> <ins> <p>No Copyright - freeCodeCamp.org</p> </ins> --fcc-editable-region-- <del> </p> </del> </footer> </body> </html>
Change:
I think we can clarify this step with one small tweak. Currently the instructions say Students seem to often miss what is going on here and try to make a combo img-anchor element. We could modify it to add a brief bit of context No response All No response
I'm happy to work on and fix this issue if that's alright with you?
I like what you've proposed here I think I might have proposed something similar for this step a while ago, but I'm getting old so my memory may not be as good as it used to be.
Thanks for creating an issue about this That should help cut down on the confusion in this step quite a bit. I vaguely recall mentioning something similar before, so it's great you opened up an issue so we can improve this step. feel free to open up a PR for this. We don't typically assign issues. Instead, we look for comments in issues like yours expressing interest, and the first comprehensive PR that's submitted is reviewed and merged.
Is this issue still open?
I see a "first timers only" tag and a "help wanted" tag on this issue. Are we just waiting on a couple of fixes to be chosen from, or can I work on this issue since I am a first timer?
Hey the first pull request that solves issue, while following contribution guidelines, will be merged.

Discussion:
# --description-- <ins> In previous steps you used an anchor element to turn text into a link. Other types of content can also be turned into a link by wrapping it in anchor tags. </ins> Turn the image into a link by surrounding it with necessary element tags. Use `https://freecatphotoapp.com` as the anchor's `href` attribute value. # --hints--
Change:
The challenge is using the method which hasn't been introduced yet. I believe it is an artifact of the current section order (ES6 now comes before functional programming). You don't really need to understand how works to solve the challenge but just to avoid any confusion it might be better to change it to use a simple for loop. The guide post will need to be updated as well if this change is made. Should not contain code that is unfamiliar to the student. 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] Forum post: Guide post:
hey i have fix this issue let you check PR

Discussion:
```js const sum = (x, y, z) => { const args = [x, y, z]; <del> return args.reduce((a, b) => a + b, 0); </del> <ins> let total = 0; for (let i = 0; i < args.length; i++) { total += args[i]; } return total; </ins> } ```

```js const sum = (...args) => { <del> return args.reduce((a, b) => a + b, 0); </del> <ins> let total = 0; for (let i = 0; i < args.length; i++) { total += args[i]; } return total; </ins> } ```
Change:
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:

Discussion:
# --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--
Change:
in the odin project, there is a sentence that is worded like it should be worded like Here is the file 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.
can I solve this?

Discussion:
The `<head>` element is where you put important meta-information about your webpages, and stuff required for your webpages to render correctly in the browser. Inside the `<head>`, you should not use any element that displays content on the webpage. ## The Charset Meta Element <del> You should always have the `meta` tag for the charset encoding of the webpage in the head element: `<meta charset="utf-8">`. </del> <ins> You should always have the `meta` tag for the `charset` encoding of the webpage in the `head` element: `<meta charset="utf-8">`. </ins> Setting the encoding is very important because it ensures that the webpage will display special symbols and characters from different languages correctly in the browser.
Change:
When adding a new node ( or element ) to a binary search tree, I was supposed to compare the value supplied method with that of current node. But it seems odd to me that, despite not doing it at all, the testing script somehow ignored it. Here's the code I wrote I expect the unit test case to fail instead of to succeed. Also, if I slightly edit this LOC here: to Then I expect the said unit test case to pass. No response Device: Dell Latitude 5580 OS: Ubuntu 22.04 Browser: Brave Browser Version: 1.45.127 No response
is taking a look and this and will create a PR if a fix is identified.
The reason the "The add method should add elements according to the binary search tree rules." test passes is because the test does not test for adding duplicate keys. I've a pr that changes the test so it adds a duplicate key, and the solution in the docs still works. The code you wrote now fails (correctly). Your intended fix of changing to does not work, as if cr[direction] is null, you can't get its .value

Discussion:
} test.add(4); test.add(1); <ins> test.add(1); </ins> test.add(7); test.add(87); test.add(34);
Change:
In the step: We see the text: "You can use a callback function in the style() method to change the styling for different elements." Which is a repetition in part of the later sentence "You can use a callback function in the style() method and include the conditional logic." I feel the first sentence can be skipped entirely and make for a better step overall. Instead of the current step text, we could rewrite as follows: No response N/A No response
opened pr that gets rid of first sentence

Discussion:
# --description-- <del> D3 is about visualization and presentation of data. It's likely you'll want to change the styling of elements based on the data. You can use a callback function in the `style()` method to change the styling for different elements. </del> <ins> D3 is about visualization and presentation of data. It's likely you'll want to change the styling of elements based on the data. </ins> For example, you may want to color a data point blue if it has a value less than 20, and red otherwise. You can use a callback function in the `style()` method and include the conditional logic. The callback function uses the `d` parameter to represent the data point: ```js
Change:
In the sentence: "There are several ways to add a tooltip to a visualization, this challenge uses the SVG <codetitle</codeelement." The comma should be a period (from an English grammar perspective, the sentence after a comma should not be a complete sentence but here it is. ) This is a comma splice. Ref: https://www-s3-,of%20equal%20weight%20and%20importance.) File: 04-data-visualization/data-visualization-with-d3/add-a-tooltip-to-a-d3- Use a period where the comma splice is located currently. No response not applicable No response
instead of , there should be . at the highlighted position. Is that correct? <img width="499" alt="Screenshot 2023-02-08 at 1 08 22 AM" src="https://user-"
yes burh
have you fixed the issue??
yes I fixed it.

Discussion:
# --description-- <del> A tooltip shows more information about an item on a page when the user hovers over that item. There are several ways to add a tooltip to a visualization, this challenge uses the SVG `title` element. </del> <ins> A tooltip shows more information about an item on a page when the user hovers over that item. There are several ways to add a tooltip to a visualization. This challenge uses the SVG `title` element. </ins> `title` pairs with the `text()` method to dynamically add data to the bars.
Change:
Someone in the forums pointed out that adding the property just to will not have the intended effect since the property is not inherited. It appears to me that removing this property completely from in the final product does not seem to make any difference to the layout. Do we need ? If so, if the intent is to apply it to all elements then it should probably be moved to the rule set. Either remove completely or move it into the ruleset. No response N/A No response
Pretty sure I saw this in another challenge too and it got fixed. The CSS used looks like the of setting the but with the actual inheriting missing from the code. It should be fixed, but I would not suggest we remove , setting that (in my opinion) is pretty much a best pratice.
I'm guessing it would be easier and take less explaining to update step 26 to add the on that selector and then remove the mention of it in step 27. Then update all the seed code.
Just a heads up, if lasjorg PR merged without issue, balance sheet project suffer the same issue, we can open a PR or issue for it, if the PR is merged. Except that the balance sheet project , doesn't do much and moving it break the layout.

Discussion:
# --description-- <del> To start your CSS, normalize the CSS rules by targeting all elements with `*`, including the `::before` and `::after` pseudo-selectors. Set the `padding` property and `margin` property both to `0`. </del> <ins> To start your CSS, normalize the CSS rules by targeting all elements with `*`, including the `::before` and `::after` pseudo-selectors. Set the `padding` and `margin` properties both to `0` and set the `box-sizing` property to `border-box`. </ins> # --hints--

assert(new __helpers.CSSHelp(document).getStyle('*, ::before, ::after')?.margin === '0px'); ``` <ins> Your `*, ::before, ::after` selector should have a `box-sizing` property set to `border-box`. ```js assert(new __helpers.CSSHelp(document).getStyle('*, ::before, ::after')?.boxSizing === 'border-box'); ``` </ins> # --seed-- ## --seed-contents--

This will make it easier for you to work with `rem` units later, as `2rem` would be 20px. <del> Also, set the `box-sizing` property to `border-box`. </del> # --hints-- You should create an `html` selector.

assert(new __helpers.CSSHelp(document).getStyle('html')?.fontSize === '62.5%'); ``` <del> Your `html` selector should have a `box-sizing` property set to `border-box`. ```js assert(new __helpers.CSSHelp(document).getStyle('html')?.boxSizing === 'border-box'); ``` </del> # --seed-- ## --seed-contents--

*, ::before, ::after { padding: 0; margin: 0; <ins> box-sizing: border-box; </ins> } --fcc-editable-region--

*, ::before, ::after { padding: 0; margin: 0; <ins> box-sizing: border-box; </ins> } html { font-size: 62.5%; <del> box-sizing: border-box; </del> } --fcc-editable-region--

*, ::before, ::after { padding: 0; margin: 0; <ins> box-sizing: border-box; </ins> } html { font-size: 62.5%; <del> box-sizing: border-box; </del> } body {

::after { padding: 0; margin: 0; <ins> box-sizing: border-box; </ins> } html { font-size: 62.5%; <del> box-sizing: border-box; </del> } body {
Change:
CSS Learn Typography/Nutrition Label: Step 31 “Create an .small-text selector and set the font-size to” the “an” should actually be an “a”. Windows 11/ Chrome browser Version 110.0.5481.78 (Official Build) (64-bit)
It helps if you use the New Issue template. ! Link to challenge: Suggested correction:
Would you like to solve this issue? Or shall I go for it? Feel free to try
iam new to opensource i love to work on this issue.
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
To solve this issue, change this line from to Here is the file 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 prolific contributors will guide you through this.

Discussion:
The `rem` unit stands for `root em`, and is relative to the font size of the `html` element. <del> Create an `.small-text` selector and set the `font-size` to `0.85rem`, which would calculate to be roughly `13.6px` (remember that you set your `html` to have a `font-size` of `16px`). </del> <ins> Create a `.small-text` selector and set the `font-size` to `0.85rem`, which would calculate to roughly `13.6px` (remember that you set your `html` to have a `font-size` of `16px`). </ins> # --hints--
Change:
In the multi-file editor, if the preview pane is toggled off and then on again, any output in the console will be cleared. Granted, the user can always check their code again to get the console output back. But I'm assuming this is not intended behavior? Any page using the multi-file editor the Survey Form in the new RWD the Console button so it is showing below the preview. the tests. the Preview button to hide the preview. the Preview button again to show the preview. that the console output resets. Console output should not reset if the preview pane is toggled off/on. No response N/A No response
Here is what I tried, so anyone in the future save time: Changing lowerJaw to JSX didn't help. TabPane change display to , but React doesn't care and preserve the state. if you turn to JSX, so react preserve the state, it won't render at all. monaco wants it to be an element. I don't know if this helps, but I personally think if become JSX, then React can do its thing and preserve the state. I have no idea how to make monaco accept JSX instead of Element, so I am going to stop there, maybe someone else the same issue. Here is the file with the issue Here is the react-wrapper for the monaco, maybe it does have a way to do it
I have looked it more up And I don't think, it is possible to inject JSX element inside the editor. I am maybe wrong, but the easiest solution, is to have the editor in instruction and lowerjaw in different tab, is that possible?
I think the console output is not related to the editor per say. We just need to investigate output, consoleOutputSelector, and consoleOut state in redux store and see at what point it gets reset.

Discussion:
return [ takeLatest(types.executeChallenge, executeCancellableChallengeSaga), takeLatest( <del> [ types.updateFile, types.previewMounted, types.challengeMounted, types.resetChallenge ], </del> <ins> [types.updateFile, types.challengeMounted, types.resetChallenge], </ins> previewChallengeSaga ), <ins> takeLatest(types.previewMounted, previewChallengeSaga, { flushLogs: false }), </ins> takeLatest(types.projectPreviewMounted, previewProjectSolutionSaga) ]; }
Change:
The test fails to catch the difference between an element and class selector The hint is But the first hint should be displayed instead: The regex fails to tell the difference between an element and class selector. No response All No response
We should just use the method on the class to look for . Examples of this can be seen in other tests. 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
Hi My name is Om Bansal and this is my first time contributing to open source can i work on this issue?
Go for it - we will accept the first fully correct PR that fixes the issue.

Discussion:
You should use the `body` element selector. ```js <del> assert.match(code, /bodys*{/); </del> <ins> assert.exists(new __helpers.CSSHelp(document).getStyle('body')); </ins> ``` You should use the `background` property in the `body` selector.
Change:
The page gets stuck and goes blank with you leave the relational database challenges. to 'Start the course' the fCC logo/button in the nav goes blank and nav disappears Page not to go blank. Clicking fCC logo should go to /learn No response Same on Chrome and Firefox Console errors: <img width="671" alt="Screen Shot 2023-02-16 at 11 44 19 AM" src="https://user-"

Discussion:
userSelector, isOnlineSelector, isServerOnlineSelector, <ins> showCodeAllySelector, </ins> userFetchStateSelector } from '../../redux/selectors';

isOnlineSelector, isServerOnlineSelector, userFetchStateSelector, <ins> showCodeAllySelector, </ins> userSelector, ( isSignedIn,

isOnline: boolean, isServerOnline: boolean, fetchState: UserFetchState, <ins> showCodeAlly: boolean, </ins> user: User ) => ({ isSignedIn,

isServerOnline, fetchState, theme: user.theme, <ins> showCodeAlly, </ins> user }) );

showFooter?: boolean; isChallenge?: boolean; block?: string; <ins> showCodeAlly: boolean; </ins> superBlock?: string; t: TFunction; }

superBlock, t, theme = Themes.Default, <ins> showCodeAlly, </ins> user, fetchUser, updateAllChallengesInfo

/> ) : null} <SignoutModal /> <del> {isChallenge && ( </del> <ins> {isChallenge && !showCodeAlly && ( </ins> <div className='breadcrumbs-demo'> <BreadCrumb block={block as string}

challenge => challenge.id === challengeId ); <del> const breadcrumbs = document.querySelector('.breadcrumbs-demo'); showCodeAlly && breadcrumbs?.remove(); </del> return showCodeAlly ? ( <LearnLayout> <Helmet title={`${blockName}: ${title} | freeCodeCamp.org`} />