Dataset Preview
The full dataset viewer is not available (click to read why). Only showing a preview of the rows.
The dataset generation failed because of a cast error
Error code:   DatasetGenerationCastError
Exception:    DatasetGenerationCastError
Message:      An error occurred while generating the dataset

All the data files must have the same columns, but at some point there are 3 new columns ({'title', '_id', 'text'}) and 3 missing columns ({'query', 'pos', 'neg'}).

This happened while the json dataset builder was generating data using

hf://datasets/jiebi/CodeConvo/freeCodeCamp/c2i/dev/corpus.jsonl (at revision c2b8f63232065408d1c90f0148838dabc96b136c)

Please either edit the data files to have matching columns, or separate them into different configurations (see docs at https://hf.co/docs/hub/datasets-manual-configuration#multiple-configurations)
Traceback:    Traceback (most recent call last):
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 1871, in _prepare_split_single
                  writer.write_table(table)
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/arrow_writer.py", line 623, in write_table
                  pa_table = table_cast(pa_table, self._schema)
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/table.py", line 2293, in table_cast
                  return cast_table_to_schema(table, schema)
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/table.py", line 2241, in cast_table_to_schema
                  raise CastError(
              datasets.table.CastError: Couldn't cast
              _id: string
              title: string
              text: string
              to
              {'query': Value(dtype='string', id=None), 'pos': Sequence(feature=Value(dtype='string', id=None), length=-1, id=None), 'neg': Sequence(feature=Value(dtype='null', id=None), length=-1, id=None)}
              because column names don't match
              
              During handling of the above exception, another exception occurred:
              
              Traceback (most recent call last):
                File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1438, in compute_config_parquet_and_info_response
                  parquet_operations = convert_to_parquet(builder)
                File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1050, in convert_to_parquet
                  builder.download_and_prepare(
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 925, in download_and_prepare
                  self._download_and_prepare(
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 1001, in _download_and_prepare
                  self._prepare_split(split_generator, **prepare_split_kwargs)
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 1742, in _prepare_split
                  for job_id, done, content in self._prepare_split_single(
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 1873, in _prepare_split_single
                  raise DatasetGenerationCastError.from_cast_error(
              datasets.exceptions.DatasetGenerationCastError: An error occurred while generating the dataset
              
              All the data files must have the same columns, but at some point there are 3 new columns ({'title', '_id', 'text'}) and 3 missing columns ({'query', 'pos', 'neg'}).
              
              This happened while the json dataset builder was generating data using
              
              hf://datasets/jiebi/CodeConvo/freeCodeCamp/c2i/dev/corpus.jsonl (at revision c2b8f63232065408d1c90f0148838dabc96b136c)
              
              Please either edit the data files to have matching columns, or separate them into different configurations (see docs at https://hf.co/docs/hub/datasets-manual-configuration#multiple-configurations)

Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.

query
string
pos
sequence
neg
sequence
}; ``` <del> A request to `/api/:date?` with a valid date should return a JSON object with a `unix` key that is a Unix timestamp of the input date in milliseconds </del> <ins> A request to `/api/:date?` with a valid date should return a JSON object with a `unix` key that is a Unix timestamp of the input date in milliseconds (as type Number) </ins> ```js (getUserInput) =>
[ "The test requires that the value is of type Number. But you have to look at the example response given and realize it is a number and not a string. We do pretty often get forum posts about this so maybe this needs to be made more clear? Challenge:\nI feel like observing the behaviour of the demo API and figuring out how your own API differs from the spec is an important part of the project, where giving too much information up-front might not be desirable because then people can complete it on autopilot instead of having learning experiences. There is something to be said more generally though about the current difficulty in debugging why your code fails one of the project requirements, as unlike the Frontend Libraries Cert you can't see the actual output of any failed tests.\nI completely agree but it would be nice if the test blocks were formatted a bit better. Like the response on its own line using a fenced code block with some highlighting. I know it would make it take up more space but I think that would be worth it. Just as an example: ! Although, I don't think providing the types in the specs is that unreasonable either.\nBTW, the type is provided for the other response: I'm not suggesting we spoon-feed the students, just that we give them clear instructions.\nPersonally, \"in milliseconds\" suggests it should be a number to me. But that could be more due to my experience than anything else. I don't see a reason why this shouldn't be clarified, so I'm on board. Maybe just adding a note will work?\nI would be fine with just a mention of the type in the message. Edit: maybe (as type Number) just to avoid any confusion?\nWorks for me! Will go ahead and open up for first timers. This looks like 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: 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. 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.", "I created a full-stack JavaScript app that is functionally similar to this: https://timestamp- you can check it at github repo I also requested a pull. and how it works I uploaded a video , please accept my pull request and merge it https://user-\nThis is an issue about adding type information to one of the test output blocks. We do not merge people's projects. You submit the project on the challenge page and it gets tested.\nok but there's a problem that every time after refresh it changes its localhost port because of this it's hard to deploy it\nPlease use the if you need help with the curriculum." ]
[]
`button1` represents your first `button` element. These elements have a special property called `onclick`, which you can use to determine what happens when someone clicks that button. <del> You can access properties in JavaScript a couple of different ways. The first is with <dfn>dot notation</dfn>. Accessing the `onclick` property of a button would look like: </del> <ins> You can access properties in JavaScript a couple of different ways. The first is with <dfn>dot notation</dfn>. Here is an example of using dot notation to set the `onclick` property of a button to a function reference. </ins> ```js <del> button.onclick </del> <ins> button.onclick = myFunction; </ins> ``` <ins> In this example, `button` is the button element, and `myFunction` is a reference to a function. When the button is clicked, `myFunction` will be called. </ins> Use dot notation to set the `onclick` property of your `button1` to the function reference of `goStore`. Note that `button1` is already declared, so you don't need to use `let` or `const`. # --hints--
[ "We still have a lot of confusion on the forum about step 41 I think adding a code example of what they need to do will help. Here is my proposed update to the step. js button.onclick = myFunction; ` see explanation above see explanation above 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\nJust a note - that will be step 40 currently\nThis 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 Happy coding" ]
[]
**Examples** ```js <del> 5 > 3 7 > '3' 2 > 3 '1' > 9 </del> <ins> 5 > 3 // true 7 > '3' // true 2 > 3 // false '1' > 9 // false </ins> ``` <del> In order, these expressions would evaluate to `true`, `true`, `false`, and `false`. </del> # --instructions-- Add the greater than operator to the indicated lines so that the return statements make sense.
[ "The student has to go all the way down up to the explanation \"In order, these expressions would evaluate to true, false, true, and true.\" to realize what the result of the operations is. My suggestion is that the second section of the code should look like this: 1 == 1 // true 1 == 2 // false 1 == '1' // true \"3\" == 3 // true instead of the screenshot attached. <!-- Add a link to the coding challenge with the problem. -- <!-- If applicable, add screenshots to help explain your problem. you can drag and drop, png, jpg, gif, etc. in this box. --!\nI would be fine with this change. Any interest in making a PR for it\n, Can I? I don't know how to do it and I have never done it in my life, but besides that, I would like to do it by myself using some guide you could give me. I have never used GitHub in the past. And this will help me to contribute even more to this awesome project.\nWe have some . It may look a little intimidating, but if you follow the instructions it's not bad. The file where this needs to be fixed is Technically, you can edit the file on github and make a PR from there - which can work for some simple fixes, but you can't see and test your changes. I think we would accept those if you want to do that, but I would recommend setting the project up locally at some point if you want to contribute regularly. To be clear, we usually like to get second opinion before making changes like this - since we don't have that, I can't guarantee a PR would be merged - but I think others would be fine with the change so if you want to make a PR, go ahead.\nThis change seems good. For context, we got rid of a lot of comments since we'd need to translate them. However, these are keywords and don't need translation.\nshall I take this up?\nCould you clarify if this is actually what we wanted, because this is exactly what we removed 12 months ago in:\nYes, this is okay because these instances specifically are only keywords that don't get translated anyway." ]
[]
# --instructions-- <del> Build `myStr` over several lines by concatenating these two strings: `This is the first sentence. ` and `This is the second sentence.` using the `+=` operator. Use the `+=` operator similar to how it is shown in the editor. Start by assigning the first string to `myStr`, then add on the second string. </del> <ins> Build `myStr` over several lines by concatenating these two strings: `This is the first sentence. ` and `This is the second sentence.` using the `+=` operator. Use the `+=` operator similar to how it is shown in the example. Start by assigning the first string to `myStr`, then add on the second string. </ins> # --hints--
[ "The challenge instructions says \"Use the <code+=</codeoperator similar to how it is shown in the editor.\", but the seed code is empty It should mention the example instead of the editor. This needs the change of one word, as such I am opening this issue to first timers. This is the challenge And its related file Issues are not assigned, the first comprehensive PR is reviewed. If you haven't already done so, read the contributing guidelines at If you need any help feel free to reach on the contributors subforum on the forum, or the contributor chatroom at" ]
[]
Camper Cat has a search field on his Inspirational Quotes page that he plans to position in the upper right corner with CSS. He wants the search `input` and submit `input` form controls to be the first two items in the tab order. Add a `tabindex` attribute set to `1` to the `search` `input`, and a `tabindex` attribute set to `2` to the `submit` `input`. <ins> Another thing to note is that some browsers may place you in the middle of your tab order when an element is clicked. An element has been added to the page that ensures you will always start at the beginning of your tab order. </ins> # --hints-- Your code should add a `tabindex` attribute to the `search` `input` tag.
[ "Describe your problem and how to reproduce it: The info for the challenge said that.. And the challenge is.. However, after I put on the both the input and the button, then I press \"TAB\" it isn't the first thing that is selected! In fact, it's not even selected! And I had successfully finished the course. Also, I already checked the and I think it's trying to do the opposite. But again, as I'm a newbie, I don't know wheter I'm wrong or right, I just wanted to ask is this the desired goal? Thank you. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Mozilla Browser Version: 66.0.5 (64-bit) Operating System: LSB Version: n/a Distributor ID: ManjaroLinux Description: Manjaro Linux Release: 18.0.4 Codename: Illyria\nSo, positive tabindices are weird. If you follow the instructions, click on the preview pane and shift-tab (i.e. tab backwards), it should focus on the submit button. Shift-tabbing again takes you to the search box. Why exactly mouse clicks put you in the middle of the tab order isn't clear to me. If you navigate to the preview pane entirely by the keyboard, it should focus in the expected order. The search box comes first, then the button and finally the three links. The easiest way I found to see this was to click on the test output box (below the editor) and tab from there. Probably not. I defer to here. In particular I think that we would be better off using this challenge to warn about the problems that come along with using positive values for .\nOh ok, thanks for clearing that up. I did try your suggestion by clicking the test output box first then tab from there, and it works like it used to be (as it should in instruction). But let me take a conclusion, so there's a mistake with the context in the course and it isn't my fault?\nI don't think you did anything wrong. In fact, it was helpful that you looked into how it actually behaved and let us know it was a little weird! The challenge isn't wrong exactly, but I think the issues with positive indices could be highlighted a bit more.", "Perhaps by inviting campers to tab around the preview panel and see the strange behaviour you noticed. This will need a bit more discussion before we try changing the challenge, though." ]
[]
<br /> <br /> **Projects**: [Timestamp Microservice](https://www.freecodecamp.org/learn/apis-and-microservices/apis-and-microservices-projects/timestamp-microservice), [Request Header Parser](https://www.freecodecamp.org/learn/apis-and-microservices/apis-and-microservices-projects/request-header-parser-microservice), [URL Shortener](https://www.freecodecamp.org/learn/apis-and-microservices/apis-and-microservices-projects/url-shortener-microservice), [Exercise Tracker](https://www.freecodecamp.org/learn/apis-and-microservices/apis-and-microservices-projects/exercise-tracker), [File Metadata Microservice](https://www.freecodecamp.org/learn/apis-and-microservices/apis-and-microservices-projects/file-metadata-microservice) #### 6. Quality Assurance Certification <del> - [Quality Assurance and Testing with Chai](https://learn.freecodecamp.org/information-security-and-quality-assurance/quality-assurance-and-testing-with-chai) - [Advanced Node and Express](https://learn.freecodecamp.org/information-security-and-quality-assurance/advanced-node-and-express) </del> <ins> - [Quality Assurance and Testing with Chai](https://www.freecodecamp.org/learn/quality-assurance/quality-assurance-and-testing-with-chai/) - [Advanced Node and Express](https://www.freecodecamp.org/learn/quality-assurance/advanced-node-and-express/) </ins> <br /> <br /> **Projects**: [Metric-Imperial Converter](https://www.freecodecamp.org/learn/quality-assurance/quality-assurance-projects/metric-imperial-converter), [Issue Tracker](https://www.freecodecamp.org/learn/quality-assurance/quality-assurance-projects/issue-tracker), [Personal Library](https://www.freecodecamp.org/learn/quality-assurance/quality-assurance-projects/personal-library), [Sudoku Solver](https://www.freecodecamp.org/learn/quality-assurance/quality-assurance-projects/sudoku-solver), [American British Translator](https://www.freecodecamp.org/learn/quality-assurance/quality-assurance-projects/american-british-translator) #### 7. Scientific Computing with Python Certification - [Introduction to Python for Everybody](https://learn.freecodecamp.org/scientific-computing-with-python/python-for-everybody)
[ "This is a broken link. <img width=\"1440\" alt=\"Screen Shot 2020-09-21 at 12 43 27 PM\" src=\"https://user-\"<img width=\"1148\" alt=\"Screen Shot 2020-09-21 at 12 43 55 PM\" src=\"https://user-\"Recommended fix, suggestions (how would you update it?): Two ideas for fixing this come to mind: In the , we want to change both links to match the current application. Here is the code that should be to fix the issue: Set up routes for the old paths to redirect to the current paths. I'm unsure of exactly how to do this." ]
[]
You should add a `forEach` loop that iterates through the `platforms` array. ```js <del> assert.match(code, /elses+ifs*(.*)s*{s*platforms.forEach(s*((s*platforms*)|platform)s*=>s*{s*(.*?)s*}s*)s*;?/); </del> <ins> assert.match(code, /elses+ifs*(.*)s*{s*platforms.forEach(s*((s*platforms*)|platform)s*=>s*{?s*(.*?)s*}?s*)s*;?/); </ins> ``` You should use the addition assignment operator to add 5 to the platform's `x` position. ```js <del> assert.match(code, /platforms.forEach(s*((s*platforms*)|platform)s*=>s*{s*platform.position.xs*+=s*5s*;?s*}s*)s*;?/); </del> <ins> assert.match(code, /platforms.forEach(s*((s*platforms*)|platform)s*=>s*{?s*platform.position.xs*+=s*5s*;?s*}?s*)s*;?/); </ins> ``` # --seed--
[ "Implicitly returning the callback passed into won't pass the test. This should pass at least for this step, and the following step as well. I found out later that curly brackets are missed here. The hint/error message is also not helpful here because the code provided above does exactly what the hint asks campers to do. I suggest adding \"Please use curly brackets for the callback for this step\" or modifying the corresponding test. ! Device: Laptop OS: Windows 11 Browser: FireFox Version: 125.0.2 (64-bit) No response\nYes, these two steps should be updated to allow for implicit returns." ]
[]
- text: Your code should use the <code>filter</code> method. testString: assert(code.match(/.filter/g)); - text: Your code should not use a <code>for</code> loop. <del> testString: assert(!code.match(/fors*?(.+?)/g)); </del> <ins> testString: assert(!code.match(/fors*?([sS]*?)/g)); </ins> - text: '<code>filteredList</code> should equal <code>[{"title": "Inception","rating": "8.8"},{"title": "Interstellar","rating": "8.6"},{"title": "The Dark Knight","rating": "9.0"},{"title": "Batman Begins","rating": "8.3"}]</code>.' testString: 'assert.deepEqual(filteredList, [{"title": "Inception","rating": "8.8"},{"title": "Interstellar","rating": "8.6"},{"title": "The Dark Knight","rating": "9.0"},{"title": "Batman Begins","rating": "8.3"}]);'
[ "<!-- 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 identified three challenges where the for loop validation does not work if newlines are used in the arguments. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Google Chrome Browser Version: 79.0.3945.88 Operating System: Ubuntu 18.04 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! ! !" ]
[]
"Por ejemplo, pairwise([1, 4, 2, 3, 0, 5], 7) debe devolver 11 porque 4, 2, 3 y 5 pueden ser emparejados para obtener una suma de 7", "pairwise([1, 3, 2, 4], 4) devolvería el valor de 1, porque solo los primeros dos elementos pueden ser emparejados para sumar 4. ¡Recuerda que el primer elemento tiene un índice de 0!", "Recuerda utilizar <a href='//github.com/FreeCodeCamp/freecodecamp/wiki/FreeCodeCamp-Get-Help' target='_blank'>Read-Search-Ask</a> si te sientes atascado. Intenta programar en pareja. Escribe tu propio código." <ins> ], "titleIt": "A coppie", "descriptionIt": [ "Dato un array <code>arr</code>, trova le coppie di elementi la cui somma è uguale al secondo argomento passato <code>arg</code>. Ritorna quindi la somma dei loro indici.", "Se ci sono più coppie possibili che hanno lo stesso valore numerico ma indici differenti, ritorna la somma degli indici minore. Una volta usato un elemento, lo stesso non può essere riutilizzato per essere accoppiato con un altro.", "Per esempio <code>pairwise([7, 9, 11, 13, 15], 20)</code> ritorna <code>6</code>. Le coppia la cui somma è 20 sono <code>[7, 13]</code> e <code>[9, 11]</code>. Possiamo quindi osservare l'array con i loro indici e valori.", "<table class="table"><tr><th><b>Indice</b></th><th>0</th><th>1</th><th>2</th><th>3</th><th>4</th></tr><tr><td>Valore</td><td>7</td><td>9</td><td>11</td><td>13</td><td>15</td></tr></table>", "Qui sotto prendiamo gli indici corrispondenti e li sommiamo.", "7 + 13 = 20 &#8594; Indici 0 + 3 = 3<br>9 + 11 = 20 &#8594; Indici 1 + 2 = 3<br>3 + 3 = 6 &#8594 Ritorna <code>6</code>", "Ricorda di usare <a href='//github.com/FreeCodeCamp/freecodecamp/wiki/FreeCodeCamp-Get-Help' target='_blank'>Leggi-Cerca-Chiedi</a> se rimani bloccato. Prova a programmare in coppia. Scrivi il codice da te." </ins> ] } ]
[ "Advanced Algorithm Scripting () Translate the challenge Advanced Algorithm Scripting in Italian\nI'll be working on this" ]
[]
challenge => challenge.id === challengeId ); <del> const breadcrumbs = document.querySelector('.breadcrumbs-demo'); showCodeAlly && breadcrumbs?.remove(); </del> return showCodeAlly ? ( <LearnLayout> <Helmet title={`${blockName}: ${title} | freeCodeCamp.org`} />
[ "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-\"" ]
[]
"<span class='text-info'>Bonus User Story:</span>As a user, I can click a button to see a random Wikipedia entry.", "<span class='text-info'>Bonus User Story:</span>As a user, when I type in the search box, I can see a dropdown menu with autocomplete options for matching Wikipedia entries.", "<span class='text-info'>Hint:</span> Here's an entry on using Wikipedia's API: <code>http://www.mediawiki.org/wiki/API:Main_page</code>.", <del> "Remember to use <a href='/field-guide/how-do-i-get-help-when-I-get-stuck' target='_blank'>RSAP</a> if you get stuck. Try using <a href='http://api.jquery.com/jquery.each/'>jQuery's $.getJSON()</a> to consume APIs.", </del> <ins> "Remember to use <a href='/field-guide/how-do-i-get-help-when-I-get-stuck' target='_blank'>RSAP</a> if you get stuck. Try using <a href='http://api.jquery.com/jquery.getjson/'>jQuery's $.getJSON()</a> to consume APIs.", </ins> "When you are finished, click the "I've completed this challenge" button and include a link to your CodePen. If you pair programmed, you should also include the Free Code Camp username of your pair.", "If you'd like immediate feedback on your project, click this button and paste in a link to your CodePen project. Otherwise, we'll review it before you start your nonprofit projects.<br><br><a class='btn btn-primary btn-block' href='https://twitter.com/intent/tweet?text=Check%20out%20the%20project%20I%20just%20built%20with%20%40FreeCodeCamp:%20%0A%20%23LearnToCode%20%23JavaScript' target='_blank'>Click here then add your link to your tweet's text</a>" ],
[ "Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. Step : \"Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON() to consume APIs.\" incorrectly to this url: It should link to: Unless that misdirection is meant to be tricky for the student ;)\nThis is a duplicate of\nKind of. This one is referring to a different page (challenge/zipline), but I did notice that all of the Ziplines have the same bug.\nThis was fixed ages ago, right? Please close.\nThis isn't actually fixed. The erroneous link still exists in these ziplines: Maybe it's not an issue because we'll be switching over to the content at soon? But I thought you should know that the issue hasn't actually been fixed yet. Actually, the only reason that it isn't an issue on the beta site is that none of the ziplines seem to link directly to the jquery json page.\nThis was fixed in prior to the branch being available through Now they seem to have changed how the ziplines look, so it wouldn't be an issue regardless. Since all changes seem to happen on the branch before ending up in production, issues that are fixed in should probably be considered fixed, even though it might be better to merge small fixes like this into production at a quicker rate than what is the current reality.\nThanks for the explanation! That makes sense. I'm not privy to staging, so I didn't realize it had been fixed there." ]
[]
import '../Donation.css'; const propTypes = { <del> getValidationState: PropTypes.func.isRequired </del> <ins> getValidationState: PropTypes.func.isRequired, theme: PropTypes.string </ins> }; const style = { base: { <del> color: '#0a0a23', </del> fontSize: '18px' } };
[ "Describe the bug ! The input text on the darkmode version of the donate page () are not readable so you cannot see what you are typing. To Reproduce Steps to reproduce the behavior: to '' with darkmode enabled. on the input labled 'Your Card Number:' and enter some numbers. entered input is not readable as the color of the input text is the same as the background-color of the input. bug applies to the credit card expiration and CVC inputs. ! Desktop (please complete the following information): OS: Win10 Browser Brave/Chrome/Firefox" ]
[]
"assert(typeof((new MotorBike()).seats) === 'number', '<code>seats</code> should be have a <code>engines</code> attribute set to a number.');" ], "challengeSeed":[ <del> "// Let's add the properties engine and seats to the car in the same way that the property wheels has been added below. They should both be numbers.", </del> <ins> "// Let's add the properties engines and seats to the car in the same way that the property wheels has been added below. They should both be numbers.", </ins> "var Car = function() {", " this.wheels = 4;", " this.engines = 1;",
[ "Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. the instructions call for a property of engine, the test is looking for engines. <img width=\"1043\" alt=\"screen shot 2015-08-18 at 12 49 26 pm\" src=\"\"" ]
[]
# --description-- <del> Your first building looks pretty good now. Let's make some more! Nest three new `div` elements in the `background-buildings` container and give them the classes of `bb2`, `bb3`, and `bb4` in that order. These will be three more buildings for the background. </del> <ins> Your first building looks pretty good now. Nest three new `div` elements in the `background-buildings` container and give them the classes of `bb2`, `bb3`, and `bb4` in that order. These will be three more buildings for the background. </ins> # --hints--
[ "In step 18 of building a skyline project, there is a text that go against This should be deleted Here is the markdown file 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. 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.\nHi , I would like to work on this issue. Could you assign it to me ?\nHi thanks for taking interest in it. Feel free to open pull request after you have read the guide, we have stopped assigning people unless they are an old contributor." ]
[]
}, parameterHints: { enabled: false <del> } </del> <ins> }, tabSize: 2 </ins> }; this._editor = null;
[ "This is pretty minor, and I'm not sure if it's in our control. But if you go to any challenge that has the built in code editor. Pressing tab adds four spaces to the code. It would be nice to switch that to two if possible. I think two spaces is the standard, but perhaps it's just my preference.\nAgree\nIt's an option we can set:" ]
[]
If your ternary is falsy, it should display the string `N/A`. ```js <del> assert.match(code, /s*<ps*>s*Nickname:s*${s*nicknames*(?:!==s*null)?s*?s*nicknames*:s*('|"|`)N/A1}s*</p>s*/) </del> <ins> assert.match(code, /s*<ps*>s*Nickname:s*${s*nicknames*(?:!==s*null)?s*?s*nicknames*:s*('|"|`)N/A1s*}s*</p>s*/) </ins> ``` # --seed--
[ "A camper was unable to pass the test with either of the following answers The issue had to deal with spacing after the This has to be fixed because they got the correct answer see explanation above see explanation above 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\nI'd love to take a crack at this. However, I'm struggling to find the relevant files the . If someone could help point me in the right direction that would be amazing!\nit's here\nAwesome! I'll take a look later! Thanks again for the help, I much appreciate it!" ]
[]
- text: All elements from the first array should be added to the second array in their original order. testString: assert.deepEqual(frankenSplice([1, 2, 3, 4], [], 0), [1, 2, 3, 4]); - text: The first array should remain the same after the function runs. <del> testString: assert(testArr1[0] === 1 && testArr1[1] === 2); </del> <ins> testString: frankenSplice(testArr1, testArr2); assert.deepEqual(testArr1, [1, 2]); </ins> - text: The second array should remain the same after the function runs. <del> testString: assert(testArr2[0] === "a" && testArr2[1] === "b"); </del> <ins> testString: frankenSplice(testArr1, testArr2); assert.deepEqual(testArr2, ["a", "b"]); </ins> ```
[ "<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --JavaScript Algorithms and Data Structures -Basic Algorithm Scripting: Slice and Splice problem description The instruction for this challenge says \"The input arrays should remain the same after the function runs.\". However, the solution where \"arr2\" has been changed was accepted. This is the solution that was accepted: Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Mozilla FIrefox Browser Version: 72.0.2 (64-bit) ! Operating System: Win 10 x64 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):" ]
[]
<ins> /* global expect */ import { transformEditorLink } from '../utils'; describe('create-question-epic', () => { describe('transformEditorLink', () => { const links = [ { input: 'https://some-project.camperbot.repl.co', expected: 'https://replit.com/@camperbot/some-project' }, { input: 'https://some-project.glitch.me/', expected: 'https://glitch.com/edit/#!/some-project' }, { input: 'https://github.com/user/repo-name', expected: 'https://github.com/user/repo-name' } ]; it('should correctly transform app links to editor links', () => { links.forEach(link => { expect(transformEditorLink(link.input)).toStrictEqual(link.expected); }); }); it('should not transform editor links in GitHub submission', () => { links.forEach(link => { expect(transformEditorLink(link.expected)).toStrictEqual(link.expected); }); }); }); }); </ins>
[ "In , if a user has submitted a project link, it will display the project's working view instead of the source code. I am not so sure adding the solution links as is currently functioning is helping much. See . Instead of showing the final project link, it would be more useful to show the source code link. In the linked forum post, going to the project results in the \"Hmmm.... We Couldn't Reach Your Repl\" page. For at least , we should restructure the link (if needed) to show the editable version of the project. For example, if the user submits , then we show . For Codepen projects, this is not an issue, but for Backend projects where the source code is not readily available, we either need to make my above suggested changes or remove this feature for backend challenges/projects. If a user is hosting their own project, then the same issue arises. Unless they submit a GitHub link to their project source code, a final project view does not help us identify problems for the user.\nI was recently thinking about this, and just wondered how stable it would be to transform the Camper's URL into the project code URL. If you think this is a decent feature to have, and worth it, then I am willing to throw something together. I will put out a POC, now. Side Note: I have been looking into the fiasco, as some lessons still cause the dents." ]
[]
color: var(--text-color-tertiary); } <ins> @media screen and (max-width: 768px) { .markdown-section { max-width: 90%; padding: 40px 15px 40px 15px; } } </ins> /****** CODE HIGHLIGHTING ******/ .token.string { color: #42b983;
[ "<!-- NOTE: If you want to become an author on freeCodeCamp, you can find everything here: --<!-- If you are reporting an issue with an article on our News publication, please follow this link to send an email to our editorial team --Describe your problem and how to reproduce it: Viewing Documentation in mobile view as shown in bellow image the content is narrower. Need to make the content little more wider for easy readability. This is also true in landscape view lot of empty space left both sides. Add a Link to the page with the problem: Recommended fix, suggestions (how would you update it?): If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! !\nThanks for the report I agree that margins are too wide. Would you be interested in creating a PR to fix this?\nsure will work on this issue" ]
[]
The `meta` tag should set the `charset` to `UTF-8`. ```js <del> assert(document.querySelector('meta').getAttribute('charset') === 'UTF-8'); </del> <ins> assert(document.querySelector('meta').getAttribute('charset')?.toLowerCase() === 'utf-8'); </ins> ``` Your code should have a `title` element.
[ "The value for is case-insensitive. Not sure if I missed any, but here are case-sensitive ones I found. Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-accessibility-by-building-a-quiz Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-css-animation-by-building-a-ferris-wheel Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-intermediate-css-by-building-a-picasso-painting Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-responsive-web-design-by-building-a-piano Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-the-css-box-model-by-building-a-rothko-painting a lot Both are valid The value for should be case insensitive for all challenges. 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]" ]
[]
state[ns].projectFormValues || {}; export const challengeDataSelector = state => { <del> const { theme } = userSelector(state); </del> const { challengeType } = challengeMetaSelector(state); let challengeData = { challengeType }; if (
[ "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. !\nI 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.\nIt 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.\nThat is a very good point. I will defer this to\nLogically, 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.\nI 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.\nThe preview should be white.\nI 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?\nDefinitely." ]
[]
# --hints-- <del> Your `html` element should be below the `DOCTYPE` declaration. </del> <ins> Your `DOCTYPE` declaration should be at the beginning of your HTML. </ins> ```js <del> assert(code.match(/(?<!<htmls*>)<!DOCTYPEs+htmls*>/gi)); </del> <ins> assert(__helpers.removeHtmlComments(code).match(/^s*<!DOCTYPEs+htmls*>/i)); </ins> ``` Your `html` element should have an opening tag.
[ "Several. One example is The hint for this step seems to indicate that the user must add the element below the (there must be at least one new line separating them). Hint: \"Your element should be below the declaration.:\" So the expected behavior would be that the user will not pass this step until they add the element below the . <!-- Please complete the following information. --- Device: Desktop OS: Linux/Fedora 34 Browser: Firefox Version: [e.g. 22] This is happening for several courses. The regex used for this test is not enforcing the newline between the elements. If this requirement is important enough to be enforced then we should probably come up with one regex that enforces this requirement and use it for all courses.\nOne possible regex I am using as a solution for this is:\nAffected pages: : js 57 assert((/^s<!DOCTYPEs+htmls[sS]<shtmls/gi)); 58 : js 55 assert((/(?&lt;!&lt;htmls)&lt;!DOCTYPEs+htmls/gi)); 56 : js 53 assert((/(?<!<htmls)<!DOCTYPEs+htmls/gi)); 54 : js 55 assert((/(?&lt;!&lt;htmls)&lt;!DOCTYPEs+htmls/gi)); 56 : js 17 assert((/(?<!<htmls)<!DOCTYPEs+htmls/gi)); 18 : js 17 assert((/(?&lt;!&lt;htmls)&lt;!DOCTYPEs+htmls/gi)); 18 : js 41 assert((/(?<!<htmls)<!DOCTYPEs+htmls/gi)); 42 : js 53 assert((/(?&lt;!&lt;htmls)&lt;!DOCTYPEs+htmls*/gi)); 54\nIf the regex from is the way we want to go, I'd be happy to start working on it in the pages linked by .\nI was eventually going to get around to updating these but please, feel free to step in. My solution above was officially merged into main so I'm assuming that's acceptable to use for these as well.\nI'm beginning to wonder if we should even have a requirement that the DOCTYPE be on its own separate line?", "I can't seem to find any documentation that says this is required and the W3C HTML validator accepts it without being on a new line. Also, we don't seem to be enforcing separate lines for other types of tags. But the DOCTYPE does need to be the first element on the page, which I don't think we are currently testing for, so I propose we test for that instead and get rid of the separate line requirement.\nAs far as the tests go, I suggest we stick with this: If the HTML spec can parse it, it is valid, and should be accepted, unless the instructions specifically say, for example, \"add a semi-colon at the end of the value\" So, as I can see in the spec, there is no requirement for the DOCTYPE and the element to be on separate lines:\nWould you agree with me then that instead of testing for DOCTYPE being on a separate line we should be testing that the DOCTYPE is the first element on the page? This brings us back to another I found in which there are JS comments in the code string before the HTML begins: Not impossible to work around, just wanted to make whoever ultimately works on this aware of it.\nIt wouldnt surprise me if that's the why the test was written that way, because if doctype isnt the first element, how else would you check it's current placement? It would be in relation to the html tag, right?\nIdeally, yes. As I mentioned below, we do have a solution to the comment thing, but it is a work-in-progress.\nI have submitted a that fixes the source of this issue (css comments before the html in the code string) which if approved will allow us to easily test that the DOCTYPE declaration is the first element in the HTML.\nshould i close my initial pull request since you said in your pull request that you were going to fix the others once yours gets approved and merged? I dont mind helping update the other docs with the new test once it's approved if you want me to. either way, just let me know !\nWe've had a couple of reports in the support inbox that the negative lookbehind used in some of these tests is failing in Safari, so it's great that either or (pending update) will take care of that as well. At the moment seems more flexible, and allows valid code to pass without forcing a particular style.", "It'll also be good to move away from regex for this type of test.\nIf __helpers.removeHtmlComments(code) is preferred, we could modify in that direction or accept alternatively.\nYes, is the final PR to put this issue to rest. I did an initial PR for just one course and it has already been merged. is using the same solution, just updating the remaining courses that need it." ]
[]
<ins> --- title: Use the d3.max and d3.min Functions to Find Minimum and Maximum Values in a Dataset --- ## Use the d3.max and d3.min Functions to Find Minimum and Maximum Values in a Dataset This is a stub. <a href='https://github.com/freecodecamp/guides/tree/master/src/pages/certifications/data-visualization/data-visualization-with-d3/use-the-d3.max-and-d3.min-functions-to-find-minimum-and-maximum-values-in-a-dataset/index.md' target='_blank' rel='nofollow'>Help our community expand it</a>. <a href='https://github.com/freecodecamp/guides/blob/master/README.md' target='_blank' rel='nofollow'>This quick style guide will help ensure your pull request gets accepted</a>. <!-- The article goes here, in GitHub-flavored Markdown. Feel free to add YouTube videos, images, and CodePen/JSBin embeds --> </ins>
[ "<!-- 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: Link to the guide on the challenge Data Visualization: Data Visualization with D3: Use the and Functions to Find Minimum and Maximum Values in a Dataset is pointing to the wrong place Incidentally, the challenge page uses the d3-max and d3-min in the url while the guide page uses and Add a Link to the page with the problem: Get a Hint button brings the camper to which is 404 - Page not found Correct link is Tell us about your browser and operating system: Browser Name: Mozilla Firefox for Ubuntu canonical - 1.0 Browser Version: 62.0.3 Operating System: Ubuntu 18.04 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):\n/ If you can guide me to where this file might be located. I can check....\nSolution <body<scriptconst positionData = [[1, 7, -4],[6, 3, 8],[2, 9, 3]] // Add your code below this line const maxX = (positionData, (d) =d[2]); const output = maxX ; // Change this line // Add your code above this line (\"body\") .append(\"h2\") .text(output) </script</body" ]
[]
"users"), true); ``` <del> `truthCheck([{id: 1, data: {url: "https://freecodecamp.org", name: "freeCodeCamp}}, {id: 2, data: {url: "https://coderadio.freecodecamp.org/", name: "CodeRadio"}}, {id: null, data: {}}], "data")` should return `true`. </del> <ins> `truthCheck([{id: 1, data: {url: "https://freecodecamp.org", name: "freeCodeCamp"}}, {id: 2, data: {url: "https://coderadio.freecodecamp.org/", name: "CodeRadio"}}, {id: null, data: {}}], "data")` should return `true`. </ins> ```js assert.strictEqual(truthCheck(
[ "<!-- 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. --The test cases are missing a closing quote in what is displayed in the challenge and there is no way to tell if it's the same under the hood or not - probably not because the code won't even run the way it is shown in the challenge. The word \"freeCodeCamp\" in those examples has a \" in front of it but not after it - causing the code to fail. What is the proper thing to do? Just fix it? - - Your browser information: User Agent is: <codeMozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:98.0) Gecko/ Firefox/98.0</codeChallenge: Everything Be True Link to the challenge: <!-- Add a clear and concise description of what you expected to happen. --When the test cases are used to develop a solution to the challenge the code fails. Please add a closing quote to the last two test cases shown on the challenge page so that they may be used directly in our efforts to develop a solution to the challenge. <!-- 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. --- 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. --\nThanks 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: 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. 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.", "Hi , I'm new to open source and would love to contribute to this\n:+1:, no need to ask for permission. Issues labelled with or are open for contributions. My previous comment includes couple of links that should help with getting started and if you'd get stuck.\nHey It seems you have opened a pr on your own version of the repository. Do you mind opening it here instead? Have a nice day and happy coding\nHi I'm so sorry, hope I did it right this time!\nClosed with" ]
[]
ROLLBAR_CLIENT_ID='post_client_id from rollbar dashboard' ALGOLIA_ADMIN_KEY=123abc <del> ALGOLIA_APP_ID='Algolia app id from dashboard' ALGOLIA_API_KEY='Algolia api key from dashboard' </del> <ins> ALGOLIA_APP_ID=X5V7KWJ4RB ALGOLIA_API_KEY=a45d2b80c97479bbda5cf5c55914230f </ins> AUTH0_CLIENT_ID=stuff AUTH0_CLIENT_SECRET=stuff
[ "Is your feature request related to a problem? Please describe. Without Algolia keys a contributor cannot use the search feature on their local machine, limiting their ability to contribute in this area. Describe the solution you'd like The documentation should include instructions on how to get keys or set up a 'mock' search:\nFor me, I think very few people would work on the search itself. So, we would be okay to getting asked for developer keys on a need basis. And as for everyone else, will it be possible to render a message like \"search is not available during dev\" in the dropdown? /cc\nI wouldn't mind having a public API key and app ID available in case someone wants to work on the search components or tests. We have a dev app available on Algolia that I can set up with the News index. I believe there's a limit on 50,000 operations a month for dev apps, which should be enough for anyone who wants to work on the search. If we hit the limit Algolia should just return an error for the rest of the month." ]
[]
CROWDIN_API_URL: 'https://freecodecamp.crowdin.com/api/v2/' CROWDIN_PROJECT_ID: ${{ secrets.CROWDIN_PROJECT_ID_CURRICULUM }} CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_CAMPERBOT_SERVICE_TOKEN }} <ins> - name: Unhide Title of Use && For a More Concise Conditional uses: ./tools/crowdin/actions/unhide-specific-string with: filename: 'react/use--for-a-more-concise-conditional.md' string-content: 'Use &amp;&amp; for a More Concise Conditional' env: CROWDIN_API_URL: 'https://freecodecamp.crowdin.com/api/v2/' CROWDIN_PROJECT_ID: ${{ secrets.CROWDIN_PROJECT_ID_CURRICULUM }} CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_CAMPERBOT_SERVICE_TOKEN }} </ins>
[ "The challenge title of challenge Use && for a More Concise Conditional is not translatable on Crowdin ! (the greyed out text is for not translatable strings) An other challenge where the title is translatable ! this is the link for crowdin file: markdown file for the challenge:\nmind taking a look?\nI have manually marked the string as translatable today. After our workflows run tomorrow, I will confirm the string is still translatable - if it is not, I will investigate further.\nReopen if still and issue.\nthis actually happened again with last update\nJust to add that this is also happening in pt-BR. The entry is blocked for translation. I suspect this has to do with the double ampersand.\nHello, we are a group of researchers developing machine learning techniques to locate issues suitable for newcomers, and our model consider this issue as likely a \"good first issue\". May we recommend you to label it as \"good first issue\" so newcomers know where to choose? Thank you!\nthanks but it is not - this needs to be done through Crowdin pipeline, will need to do it, again" ]
[]
Now you need to create a `draw` method for the `CheckPoint` class. <del> Inside the `draw` method, add a `fillStyle` property to the `ctx` object and set it to `"#f1be32"`. </del> <ins> Inside the `draw` method, assign the `fillStyle` property on the `ctx` object the hex color `"#f1be32"`. </ins> Below the `fillStyle` property, use the `fillRect` method on the `ctx` object and pass in the `x`, `y`, `width`, and `height` properties as arguments.
[ "in step 98 of the platformer game, there are a couple of small issues that can be fixed. 1- the check is too strict for spaces because it doesn't accept this code: Note the extra space between the word draw and the parenthesis. Without the extra space, the code is accepted. For the second issue, the wording used in the step \"add a fillStyle property to the ctx object\" is not what I would expect given that fillStyle is a property of the canvas object and not something we 'add' to it. I would suggest a rewrite to \"set the fillStyle property of the ctx object\" instead. As seen above. slight wording change needed and a looser check to allow a space between the word draw and the parenthesis. No response N/A No response" ]
[]
terms = [] for n, coefficient in self.coefficients.items(): if not coefficient: <del> coefficient </del> <ins> continue </ins> --fcc-editable-region-- if n == 0: terms.append(f'{coefficient:+}')
[ "I have completed this, but noticed there is an error in the code which doesn't seem to cause any problems during the lessons. In lesson 20 we use an if statement (seen in the first code block below) and the action is . This stays the same in steps 21 through 25. However from steps 26 onwards has been replaced by as highlighted in the second code block below. (Please note that I did not change the code and have pressed Reset a number of times but the code stays the same) Please advise First code block: Second code block: I expect code that passed to stay the same and be correct - is the code in the second code block above correct? No response Device: HP Laptop OS: Windows 10 Browser: Firefox Version: 128.0.2 No response\nThanks for reporting this. The answer is no, that snippet of code is not correct and it should be fixed. Each occurrence of should be replaced with" ]
[]
# --description-- <del> Now your `showAnimation()` function is set up. But if you look closely at your `checkUserInput()` function, you'll notice that it's not very DRY – you're calling `parseInt()` to convert `numberInput.value` into a number several times. </del> <ins> Now your `showAnimation()` function is set up. But if you look at your `checkUserInput()` function, you'll notice that it is calling `parseInt()` to convert `numberInput.value` into a number several times. </ins> <del> A simple way to fix this is to create a new variable to store the converted number. Then you only have to convert the number once and can use it throughout the function. </del> <ins> This is generally a poor practice, for reasons like performance concerns or even just the fact that you'd have to change your logic in multiple places to update the `parseInt()` call. To fix this, create a new variable to store the converted number. Then you only have to convert the number once and can use it throughout the function. </ins> Create a new variable called `inputInt` and assign it the number converted from `numberInput.value`.
[ "Step 77 of the decimal to binary converter project (js beta) says this: Now your showAnimation() function is set up. But if you look closely at your checkUserInput() function, you'll notice that it's not very DRY – you're calling parseInt() to convert into a number several times. I don't think the DRY acronym was introduced before and so this would be a confusing sentence to parse. If the acronym is required, then a definition should be presented. N/A N/A No response N/A No response\nEven if we do give a definition, the principle is introduced pretty haphazardly. It's perfectly fine that we make the camper aware that some code is being repeated that should be consolidated. But I don't think we need to introduce the DRY principle. The DRY principle has both pros and cons. Mentioning it as an absolute, without any depth to the subject, is questionable. This is especially true for learners/beginners, which tend to create premature abstractions and over-abstractions the minute they hear about the DRY principle.\nI personally think the lesson works without any reference to DRY\nMy initial reaction is also to just remove it. Maybe something like:\nwould it also be possible to say something about why it is desirable to not call parseInt several times? Is it a good time to mention for eg that this is waste of processing power or can introduce errors in the code or something like that which would be relevant to know?\nSure, building on lasjorg's suggestion:" ]
[]
] ], "type": "hike", <del> "challengeType": 6 </del> <ins> "challengeType": 6, "nameEs": "JavaScript Lingo: MDN y Documentación", "descriptionEs": [ "Esta es una introducción básica a MDN y el concepto de la documentación.", "MDN, Mozilla Developer Network, es una fantástica colaboración de fuentes abiertas que documenta no sólo JavaScript, sino muchos otros lenguajes y temas. Si no has oído hablar de ellos, deberías darles un vistazo ahora. Personalmente obtengo mucha información de developer.mozilla.org/en-US/docs/Web/JavaScript ", "Cuando digo documentación, estoy hablando acerca de la información que se proporciona sobre el producto a sus usuarios. La documentación de MDN no necesariamente está escrita por la gente detrás de JS. Brendan Eich creó JS en 1995, pero hoy en día el proyecto continúa creciendo gracias a un esfuerzo comunitario. ", "A medida que continúes aprendiendo JavaScript, jQuery, y prácticamente cualquier otro lenguaje o servicio para desarrollo o programación, la documentación será tu amiga.", "Cuanto más rápido te sientas cómodo leyendo y referenciando documentación, más rápido crecerás como desarrollador.", "Estos vídeos no van a enseñarte JavaScript - te presentan términos y conceptos que serán valiosos a medida que continúes practicando y aprendiendo." ] </ins> }, { "id": "56b15f15632298c12f31518d",
[ "[ ] JavaScript Lingo: MDN and Documentation [ ] JavaScript Lingo: Value Types [ ] JavaScript Lingo: Variables & camelCase [ ] JavaScript Lingo: Arrays & Objects [ ] JavaScript Lingo: Finding and Indexing Data in Arays [ ] JavaScript Lingo: Manipulating Data [ ] JavaScript Lingo: Math [ ] JavaScript Lingo: Loops [ ] JavaScript Lingo: Regular Expressions\nWorking on this one" ]
[]
"Crea una función que devuelva el número total de permutaciones de las letras en la cadena de texto provista, en las cuales no haya letras consecutivas repetidas", "Por ejemplo, 'aab' debe retornar 2 porque, del total de 6 permutaciones posibles, solo 2 de ellas no tienen repetida la misma letra (en este caso 'a').", "Recuerda utilizar <a href='//github.com/FreeCodeCamp/freecodecamp/wiki/FreeCodeCamp-Get-Help' target='_blank'>Read-Search-Ask</a> si te sientes atascado. Intenta programar en pareja. Escribe tu propio código." <ins> ], "titleIt": "Niente ripetizioni, per favore", "descriptionIt": [ "Ritorna il numero totale di permutazioni della stringa passata che non hanno lettere consecutive riptetute. Assumi che tutti i caratteri nella stringa passata siano unici.", "Per esempio, <code>aab</code> deve ritornare 2, perchè la stringa ha 6 permutazioni possibili in totale (<code>aab</code>, <code>aab</code>, <code>aba</code>, <code>aba</code>, <code>baa</code>, <code>baa</code>), ma solo 2 di loro (<code>aba</code> e <code>aba</code>) non contengono la stessa lettera (in questo caso <code>a</code> ripetuta).", "Ricorda di usare <a href='//github.com/FreeCodeCamp/freecodecamp/wiki/FreeCodeCamp-Get-Help' target='_blank'>Leggi-Cerca-Chiedi</a> se rimani bloccato. Prova a programmare in coppia. Scrivi il codice da te." </ins> ] }, {
[ "Advanced Algorithm Scripting () Translate the challenge Advanced Algorithm Scripting in Italian\nI'll be working on this" ]
[]
<strong>User Story:</strong> I can see whether freeCodeCamp is currently streaming on Twitch.tv. <strong>User Story:</strong> I can click the status output and be sent directly to the freeCodeCamp's Twitch.tv channel. <strong>User Story:</strong> if a Twitch user is currently streaming, I can see additional details about what they are streaming. <del> <strong>Hint:</strong> See an example call to Twitch.tv's JSONP API at <a href='http://forum.freecodecamp.org/t/use-the-twitchtv-json-api/19541' target='_blank'>http://forum.freecodecamp.org/t/use-the-twitchtv-json-api/19541</a>. <strong>Hint:</strong> The relevant documentation about this API call is here: <a href='https://dev.twitch.tv/docs/v5/reference/streams/#get-stream-by-user' target='_blank'>https://dev.twitch.tv/docs/v5/reference/streams/#get-stream-by-user</a>. </del> <ins> <strong>Hint:</strong> The relevant documentation about Twitch.tv's JSON API is here: <a href='https://dev.twitch.tv/docs/api/reference/#get-streams' target='_blank'>https://dev.twitch.tv/docs/api/reference/#get-streams</a>. </ins> <strong>Hint:</strong> Here's an array of the Twitch.tv usernames of people who regularly stream: <code>["ESL_SC2", "OgamingSC2", "cretetion", "freecodecamp", "storbeck", "habathcx", "RobotCaleb", "noobs2ninjas"]</code> <del> <strong>UPDATE:</strong> Due to a change in conditions on API usage explained <a href='https://blog.twitch.tv/client-id-required-for-kraken-api-calls-afbb8e95f843#.f8hipkht1' target='_blank'>here</a> Twitch.tv now requires an API key, but we've built a workaround. Use <a href='https://wind-bow.glitch.me' target='_blank'>https://wind-bow.glitch.me/twitch-api</a> instead of twitch's API base URL (i.e. https://api.twitch.tv/kraken ) and you'll still be able to get account information, without needing to sign up for an API key. </del> <ins> <strong>UPDATE:</strong> Due to a change in conditions on API usage, Twitch.tv requires an API key, but we've built a workaround. Use <a href='https://wind-bow.glitch.me' target='_blank'>https://wind-bow.glitch.me/helix</a> instead of twitch's API base URL (i.e. https://api.twitch.tv/helix ) and you'll still be able to get account information, without needing to sign up for an API key. </ins> Remember to use <a href='http://forum.freecodecamp.org/t/how-to-get-help-when-you-are-stuck/19514' target='_blank'>Read-Search-Ask</a> if you get stuck. When you are finished, click the "I've completed this challenge" button and include a link to your CodePen. You can get feedback on your project by sharing it with your friends on Facebook.
[ "The current Twitch Tv API v5 is deprecated and will be completely replaced by the end of 2018. Just an FYI so the challenge may be updated to the new API or new challenge proposed.\nthanks for bringing to this our attention! The doesn't suggest using the API directly, but instead to use a workaround we've implemented so you don't need an API key. However, this workaround may and probably does use the API V5 (someone would need to verify this). Sidenote: just for Twitch announcing the API deprecation and removal cc/\nmaybe a contact us page that integrates the google map API ? allows the user not only view the location but also get directions??\nJust started working on the Twitch API challenge and it uses the V5 API. Also the fcc wrapper documentation says: is for V5, the new one uses . Also while at it, the wrapper should probably update the link to the documentation. It still links to , the current documentation for the V5 API is at The challenge itself already links to new location.\njust to clarify, you are suggesting a new API challenge with the Google Map API? If so, that could be an interesting challenge, as it is something that many developers might want to make for themself on their own personal page. I like the idea. However, we might be able to just update the Gomix instance with the new Twitch API (I'm not sure how much effort this would take). thanks for the additional details on the Kraken vs Helix API names. Indeed, we should at least change the wrapper link.\ncan you open a PR with these changes?\nThe wrapper project is on my glitch account, and at the moment it is using my api key. I'll make camperbot's account a collaborator of the project in glitch, so freecodecamp will own the project. Is changing to the only change required ? If so I will edit my project in the next days.\nThe root URL of the API changing isn't the only difference. I'm still new, so someone more experienced should probably have a look at the . But I think for the and routes there should be nearly no changes necessary. The route on the other hand is completely gone in the new API. But you can get the interesting data from the route anyways.", "Additionally the route now returns a instead of the name of the game, so if people should be able to display the game name in their projects we should probably implement the route to allow them to get the name from the id.\nAt the moment my proxy passes everything that in the url comes after to . It will not work as is with the new api. I'll update it so that if you hit the url or it use the old api, if we hit it uses the new api. What do you think ?\nSorry for the delayed answer. Yes, I'm suggesting something new :)\nThat appears to be a reasonable update. I haven't really looked into the new API much so we'd have to test it out. But for now, that seems like a sensible update. awesome, just checking :) If we end up not replacing it with your Google Maps API contact page, that might be a nice addition to the projects to work on.\nThat sounds good to me. Please let us know once you've made the change and verified that it still works!\nDid you ever get a chance to update this?\nNo sorry. It's not so easy to make it work for both the old and new projects. Il dom 3 giu 2018, 16:37 Quincy Larson scritto:\n/ / I think this issue should take high priority now since we have just a month before the API is deprecated and holiday season is starting so everyone would not be free at all times\nIt looks like this will be deprecated in just a couple weeks. Could you help update our Glitch project?\nI'm having a look at it. I'll try to migrate to the new api before next year. In the meantime the service has a cache db and a static list of users (the ones in the example exercise). It can keep working in 'emergency' mode indefinitely serving a limited number of twitch users data. Also it seems that somebody is using it outside the scope of freeCodeCamp. I have blacklisted the domain, but we need to be careful. I'll let you know.\nI have a working api locally on my computer. / do you want me to deploy it now ? or should I wait until the end of December ?", "The new API will be not backward compatible, but I am serving a static data snapshot at the old enpoint , for the 8 users listed in the exercise description. The new API endpoint will be . Also, the api now is in my glitch account. I think We should transfer the ownership to freeCodeCamp (camperbot ?). Let me know.\nthe new api can be tested here https://em-ant-twitch- . my old twitch project still works with the served static data. I will deploy the code to wind-bow before new year. We also need to update the challenge description and update the forum post I will submit a PR with the text changes. Can anybody update the forum article ?\nYes - we should transfer ownership to CamperBot for simplicity. And I can update the forum post. What specific changes should I make?\nthe forum post is about CORS issues and and using jsonp callback, but the new api doesn't support anymore jsonp, and our proxy on glitch accepts cross-origin requests. We could smiply remove the link to the forum post from the challenge description, or update it with an example of the new api (with jquery, as in the old example)\nwhich would you recommend? If you want me to update the post, I can do so - just tell me what update you'd like to make to it.\nI updated the PR removing the link to the forum post. I think that post is not relevant anymore for the new api.\nAwesome! Thanks for fixing this and for updating the challenge! It always feels good to close one of these issues that's nearly a year old! I've updated the old Forum post we were linking to with your updated instructions. I agree, we shouldn't link to that post anymore. But now if people end up on that post they'll have your new instructions. As always, thanks for your help, and thanks to everyone on this thread who helped us arrive at this solution!\nthe new version on the api is deployed on wind- it's always a pleasure to help." ]
[]
# --hints-- <del> You should declare an `addEntry` variable. ```js assert.isDefined(addEntry); ``` Your `addEntry` variable should be a function. </del> <ins> You should declare an `addEntry` function. </ins> ```js assert.isFunction(addEntry);
[ "The instructions in step 18 of the js beta to build a calorie counter says: Start by declaring a cleanInputString function that takes a str parameter. However if you misspell the function's name you receive this hint: You should declare a cleanInputString variable. I believe this message should be changed to say \"function\" instead of \"variable\" the hint should refer to a not a No response N/A No response\nSimilar issue was seen in step 28 where the hint said: You should declare an isInvalidInput variable. while the instructions were again to create a function: Start by creating a function called isInvalidInput – it should take a single str parameter. And again, similar issue in step38 hint says: You should declare an addEntry variable. while the step is asking for a function\nFrom Pyramid Generator A function is a block of code that can be reused throughout your application. Functions are declared with the following syntax:\nStep 42 mentioned in the previous comment should be fixed. It should say: “The function declaration tells JavaScript that the name identifier is going to be a function.” (Replacing ‘variable’ with ‘identifier’ and ‘keyword’ with ‘declaration’) My understanding is that a function is actually an object in js but I would be surprised if a js course starts telling learners to “declare an object called myFunction” instead of saying “declare a function called myFunction”. Edited…\nStep 42 should be a separate issue IMO. It shouldn't be lumped in with the corrections being made to the calorie counter steps\nHere the updates for this issue remove this hint and test js assert.isDefined(cleanInputString); the current second hint and test should say this instead js assert.isFunction(cleanInputString); remove this hint and test js assert.isDefined(isInvalidInput) remove this hint and test js assert.isDefined(addEntry); udpate the second hint to the following js assert.isFunction(addEntry); `" ]
[]
h3 { font-size: 1rem; } <ins> .btn-cta { font-size: 1.2rem; } </ins> } .text-center {
[ "The font size for the CTA could use similar breakpoints for the h1, h2. and set to 1.2 - 1.3 rem !\nI'd like to work on this.\ncan i?\nWhere is this button?" ]
[]
Fulfill the user stories and pass all the tests below to complete this project. Give it your own personal style. Happy Coding! <ins> **Note:** Be sure to add `<link rel="stylesheet" href="styles.css">` in your HTML to link your stylesheet and apply your CSS </ins> # --hints-- You should have a `main` element with an `id` of `main-doc`.
[ "With the new format, a lot of people are not linking their css files to the HTML document. It is coming up a lot on the forum. Especially for those that are going through the Legacy curriculum. I think we should add a message underneath the sample projects, to remember to link the CSS file. Proposed change: Remember to link your CSS file in the HTML document. <img width=\"460\" alt=\"Screen Shot 2022-05-14 at 8 57 10 AM\" src=\"https://user-\"\nI had trouble fixing , because I didn't link To I hope this will be implemented\nI think we should do this." ]
[]
"testString": "assert(code.match(/.reduce/g), 'Your code should use the <code>reduce</code> method.');" }, { <del> "text": "The <code>averageRating</code> should equal 8.675.", "testString": "assert(averageRating == 8.675, 'The <code>averageRating</code> should equal 8.675.');" </del> <ins> "text": "The <code>averageRating</code> should equal 8.52.", "testString": "assert(averageRating == 8.52, 'The <code>averageRating</code> should equal 8.52.');" </ins> }, { "text": "Your code should not use a <code>for</code> loop.",
[ "<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Browser Name: Firefox Browser Version: 60.0.2 (up-to-date) Operating System: macOS High Sierra, v10.13.5 <img width=\"407\" alt=\"screen shot 2018-06-13 at 11 16 17\" src=\"https://user-\"<img width=\"227\" alt=\"screen shot 2018-06-13 at 11 16 38\" src=\"https://user-\"\nWhile (8.8 + 8.6 + 9.0 + 8.3 + 7.9) / 5 = 8.52, the instructions say As Christopher Nolan didn't direct all of the movies listed, why do we need to find the average of all 5? In other words, don't we need to find the average of the movies that only have listed, which does comes to 8.675?\nGood catch. I missed the “Nolan” qualification. I’ll see that it stays as/is. Thank you.\nthank you for pointing that out! I also missed that. I'll revert the PR now.\nReopened with\nCan someone confirm that no change is required? If yes please comment and close.\nno change is required for this challenge. Here's a working solution: With that the original test, 8.675, passes." ]
[]
assert.equal(document.querySelector('.dessert-card')?.children[1].className, 'dessert-price'); ``` <del> Your first `p` element should have the text of the `price` variable with a dollar sign in front of it. </del> <ins> Your first `p` element should have the dollar sign `"$"` followed by the value of the `price` variable. </ins> ```js assert.equal(document.querySelector('.dessert-card')?.children[1].textContent, '$12.99');
[ "In the Step 12 of module: \"Learn Basic OOP by Building a Shopping Cart\". The phrase \"with a dollar sign in front of it\" might sound like the dollar sign should come after the price value, but it actually means before the price. To avoid this ambiguity, a clearer way to phrase it could be: \"Precede the price with a dollar sign ($).\" Or \"Display the price with a dollar sign ($) before the value.\" This wording explicitly states that the dollar sign should come before the price, avoiding any confusion. ! 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\nRight, but that's what \"front\" means - it's the beginning. e.g. \"I was at the front of the queue, so I was served first\". That said, when you write it might be confusing since the hint is \"Your first element should have the text of the variable with a dollar sign in front of it.\". I can see people reading that and thinking that they do have a dollar sign in front of it. Perhaps the hint would be better as \"Your first element should have the text of the variable with a dollar sign in front of it. For example, using \"\nThe phrase would be a good to avoid all these confusion which has been to the pull request\nThis issue is open for contribution. A PR which resolves this issue should: Update the instructions to read classdessert-price\"$\"price`\nIs this PR Still Open?\nthe issue is open for contribution, but there are already two PRs that aim to close this issue" ]
[]
addTranslation, deleteTranslation, getLanguageTranslations, <del> deleteLanguageTranslations </del> <ins> deleteLanguageTranslations, changeHiddenStatus </ins> };
[ "<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Affected page Your code Copy and paste the code from the editor that you used in between the back-ticks below: Expected behavior Text with the example code is not translatable - which is fine. However, the text lower is translatable and this will create confusion for end users on other languages. Screenshots Untrabslatable example: ! vs. Translatable output of the exmple: ! System (please complete the following information): Device: Laptop OS: Windows 10 Browser: chrome Version: 91.0.4472.77 Additional context Add any other context about the problem here.\nI think this is expected behaviour. That is because its and example we would not translate it.\nSure... then the description of the output should not be translated either and right now it is.\nI think The description should be translated. Which I understand it currently is. This gives the context of the example that follows. The example text line should NOT be translated because it's a literal output of the code. Which I understand it currently is not. It looks like we would want the current behaviour though I would wait for someone else to confirm.\nI was just thinking under translation context: people looking at this page in other languages will see on the page: if you write a text like this (in English): ..... that code produces the output (for example in Romania ): Acesta este ul link către la care poți ajunge. I personally would be confused how English is rendered into Romanian by itself\nI believe all the other languages are translating the example and instructions, so you are correct both should be translated.\nthe example in code can't be translated the example can't be translated, so if the result is translated it will never match in English it says Here's a link to for you to follow. where in Spanish it says Aquí hay un enlace a para que lo sigas. where the second line would be how the code above should appear it is translated in Chinese too, and I think we translated it also in Italian But it stands more correct to be kept in English as actual rapresentation of what the result of the code is\nThanks, that is what my initial thought was like I mentioned.", "I think we should get this change in all languages and have a check to catch changes as a warning. can you guide us here?\nUnfortunately our current workflow doesn't have a quick way to mark a specific string as non-translatable. I could probably put something together, but IMHO it might be worth re-wording the challenge instead.\nHmm, did Crowdin not have a way to manually mark it non-translatable? I might be mistaken though.\nWe can do that, yes - we would need to revert the translations for the languages which have translated it. However, I believe that hidden state is lost every time the file is re-uploaded.\nHmm, I see. Thanks for clarifying all this. I am glad that I double-checked with you. Do you mind sending a quick support request to Crowdin, seeking advice?\nSure thing - will add that to the list today and CC you :)\nOkay I slept on this, and decided to see if there was a way to automate this process. PR coming shortly.\nnow that this has been merged do we need to do anything over on Crowdin or in our codebase to reset the strings?\nThanks for the reminder I have gone through and cleared the existing translations for this string - it should come down in English for all languages going forward.\nAwesome, thanks for taking care of it." ]
[]
The `fieldset` element is used to group related inputs and labels together in a web form. `fieldset` elements are <dfn>block-level elements</dfn>, meaning that they appear on a new line. <del> Nest the `Indoor` and `Outdoor` radio buttons within a `fieldset` element, and don't forget to indent the buttons. </del> <ins> Nest the `Indoor` and `Outdoor` radio buttons within a `fieldset` element, and don't forget to indent the radio buttons. </ins> # --hints--
[ "The instruction looks kinda confusing. The word can be replaced by . ! <!-- 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. --\nYeah - I see what you mean here. While it's implicit and really a nitpick, we can be clear as water in verbiage." ]
[]
<ins> --- title: Improve Compatibility with Browser Fallbacks --- ## Improve Compatibility with Browser Fallbacks <!-- The article goes here, in GitHub-flavored Markdown. Feel free to add YouTube videos, images, and CodePen/JSBin embeds --> We need to add a fallback to the ```background``` property of the ```.black-box`` class. ### Example ```css :root { --black-color: black; } .black-box { background: var(--black-color); width: 100px; height: 100px; } ``` ## Solution Add a fallback to the ```background``` property before the existing background declaration: ```css :root { --black-color: black; } .black-box { background: black; background: var(--black-color); width: 100px; height: 100px; } ``` </ins>
[ "redirects to the wrong Guide article URL, causing a 404.\nI would like to do this. Can you assign this to me?\nSure - thanks for volunteering to tackle this. Yes - please keep me posted on your progress :)\nIt is the 'Get a hint' button on the page. Probably needs a stub to avoid the 404.\nis contributing to the guide a thing too? adding a stub here: should help. More challenging: write the guide :)\nYes - we would welcome your contributions to the guide.\nIs the issue sorted or can I work on this ?\nThe problem is settled here:\nIs this the same as this issue: ?" ]
[]
lambda x: expr ``` <del> In the example above, `x` is a parameter to be use in the expression `expr`. Create a `test` variable and assign it a lambda function that takes an `x` parameter and returns `x * 2`. </del> <ins> In the example above, `x` is a parameter to be used in the expression `expr`. Create a `test` variable and assign it a lambda function that takes an `x` parameter and returns `x * 2`. </ins> # --hints--
[ "I noticed a typo in the instructions for Step 11 for The typo is in the line I think the word should be I know it's a bit pedantic, but this is so... N/A N/A No response Device: HP Laptop OS: Windows 10 Browser:Firefox Version: 122.0 No response" ]
[]
const challengeTitles = new ChallengeTitles(); const validateChallenge = challengeSchemaValidator(); <del> describe('Assert meta order', function () { /** This array can be used to skip a superblock - we'll use this * when we are working on the new project-based curriculum for * a superblock (because keeping those challenges in order is * tricky and needs cleaning up before deploying). */ const superBlocksUnderDevelopment = [ '2022/javascript-algorithms-and-data-structures' ]; const superBlocks = new Set([ ...Object.values(meta) .map(el => el.superBlock) .filter(el => !superBlocksUnderDevelopment.includes(el)) ]); superBlocks.forEach(superBlock => { const filteredMeta = Object.values(meta) .filter(el => el.superBlock === superBlock) .sort((a, b) => a.order - b.order); if (!filteredMeta.length) { return; } it(`${superBlock} should have the same order in every meta`, function () { const firstOrder = getSuperOrder(filteredMeta[0].superBlock, { showNewCurriculum: process.env.SHOW_NEW_CURRICULUM </del> <ins> if (!process.env.npm_config_block) { describe('Assert meta order', function () { /** This array can be used to skip a superblock - we'll use this * when we are working on the new project-based curriculum for * a superblock (because keeping those challenges in order is * tricky and needs cleaning up before deploying). */ const superBlocksUnderDevelopment = [ '2022/javascript-algorithms-and-data-structures' ]; const superBlocks = new Set([ ...Object.values(meta) .map(el => el.superBlock) .filter(el => !superBlocksUnderDevelopment.includes(el)) ]); superBlocks.forEach(superBlock => { const filteredMeta = Object.values(meta) .filter(el => el.superBlock === superBlock) .sort((a, b) => a.order - b.order); if (!filteredMeta.length) { return; } it(`${superBlock} should have the same order in every meta`, function () { const firstOrder = getSuperOrder(filteredMeta[0].superBlock, { showNewCurriculum: process.env.SHOW_NEW_CURRICULUM }); assert.isNumber(firstOrder); assert.isTrue( filteredMeta.every( el => getSuperOrder(el.superBlock, { showNewCurriculum: process.env.SHOW_NEW_CURRICULUM }) === firstOrder ), 'The superOrder properties are mismatched.' ); </ins> }); <del> assert.isNumber(firstOrder); assert.isTrue( filteredMeta.every( el => getSuperOrder(el.superBlock, { showNewCurriculum: process.env.SHOW_NEW_CURRICULUM }) === firstOrder ), 'The superOrder properties are mismatched.' ); }); filteredMeta.forEach((meta, index) => { it(`${meta.superBlock} ${meta.name} must be in order`, function () { assert.equal(meta.order, index); </del> <ins> filteredMeta.forEach((meta, index) => { it(`${meta.superBlock} ${meta.name} must be in order`, function () { assert.equal(meta.order, index); }); </ins> }); }); }); <del> }); </del> <ins> } </ins> describe(`Check challenges (${lang})`, function () { this.timeout(5000);
[ "The instructions are here: But, using for the practice projects will always result in a meta order error: <details<summaryOutput Testing Penguing Project</summary<pre<codeblock being tested: learn-css-transforms-by-building-a-penguin 1 passing (21ms) 1 failing 1) Check challenges Assert meta order 2022/responsive-web-design Learn CSS Transforms by Building a Penguin must be in order: expected 18 to equal +0 expected - actual -18 +0 </code</pre</details<details<summaryOutput testing Registration Form Practice Project</summary<pre<codeblock being tested: learn-html-forms-by-building-a-registration-form 1 passing (30ms) 1 failing 1) Check challenges Assert meta order 2022/responsive-web-design Learn HTML Forms by Building a Registration Form must be in order: expected 3 to equal +0 expected - actual -3 +0 </code</pre</details\nThis is the test that keeps failing: Specifically this: Where is consistently" ]
[]
## Here are some quick and fun ways you can help the community. <del> - <span class='cover-icon'><i class="fas fa-question-circle"></i></span> [Help by answering coding questions](https://forum.freecodecamp.org/c/help?max_posts=1) on our community forum. </del> <ins> - <span class='cover-icon'><i class="fas fa-question-circle"></i></span> [Help by answering coding questions](https://forum.freecodecamp.org) on our community forum. </ins> - <span class='cover-icon'><i class="fas fa-comments"></i></span> [Give feedback on coding projects](https://forum.freecodecamp.org/c/project-feedback?max_posts=1) built by campers. - <span class='cover-icon'><i class="fas fa-language"></i></span> [Help us translate](https://translate.freecodecamp.org) these Contributing Guidelines. - <span class='cover-icon'><i class="fab fa-github"></i></span> [Contribute to our open source codebase](/index?id=our-open-source-codebase) on GitHub.
[ "Describe your problem and how to reproduce it: There is a bad link on the page. The link to 'help by answering coding questions' takes you to which says \"Oops! That page doesn’t exist or is private.\" Add a Link to the page with the problem: Recommended fix, suggestions (how would you update it?): I tried looking around the forum for the page that that used to link to but I am not sure. I would say it could just go to the home page. If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): <img width=\"1679\" alt=\"Screen Shot 2020-11-20 at 8 48 48 AM\" src=\"https://user-\"<img width=\"1679\" alt=\"Screen Shot 2020-11-20 at 8 49 35 AM\" src=\"https://user-\"\nNice catch! This link broke when we restructured our subforum categories, I believe. The link is located in this file: , and could be updated to redirect to the base forum URL I think.\nWhen I click on the link from , it loads the forum in he Project Feedback category. There is not error. We did not change that category on the forum. It is still the same. Any thoughts?\nI get the Project Feedback category off the second link (\"Give feedback on coding projects\"), but on the \"Help by answering coding questions\" I'm getting a 404.\nI agree with adding a link to for . I have opened this issue up for ." ]
[]
<div> {/* Change code below this line */} <h1>Active Users: </h1> <del> {/* Change code below this line */} </del> <ins> {/* Change code above this line */} </ins> </div> ); }
[ "<!-- 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: Load challenge. Observe that there are two instances of \"{/ Change code below this line /}\". The second should be {/ Change code above this line /} Could lead to confusion with users unsure if there's more to do in the challenge after adding the correct code to the challenge. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: 87.0.4280.88 Operating System: MacOS If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): <img width=\"481\" alt=\"Screen Shot 2020-12-12 at 10 26 49 PM\" src=\"https://user-\"" ]
[]
<ins> import React from 'react'; const scripts = [ <script async='' src='https://www.googletagmanager.com/gtag/js?id=AW-795617839' /> ]; export default scripts; </ins>
[ "I can work on this. A little confused though, since it appears to be there already. Does the mission statement go here? Please provide instructions, thanks." ]
[]
}; function showCompletion() { <ins> ga('send', 'event', 'Bonfire', 'solved', bonfireName + ', Time: ' + (Math.floor(Date.now() / 1000) - started) +', Attempts: ' + attempts); </ins> $('#complete-bonfire-dialog').modal('show'); } No newline at end of file
[ "<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --In the challenge CSS Flexbox: Use the flex-wrap Property to Wrap a Row or Column, the value wrap-reverse is defined: wrap-reverse: \"wraps items from right-to-left if they are in a row, or bottom-to-top if they are in a column.\" This definition is not correct. Actually wrap-reverse wrap content changing de cross-axis direction, bottom to top in a row, and left to right in a column. Browser Name: Browser Version: Operating System:\nI'd like to take on this issue please\nSince the curriculum content is in the repo, I submitted the PR there.\nOk, thanks Simon." ]
[]
"tests": [ "assert(quotient === 2.2, 'message: The variable <code>quotient</code> should equal <code>2.2</code>');", "assert(/4.40*s*/s*2.*0*/.test(code), 'message: You should use the <code>/</code> operator to divide 4.4 by 2');", <del> "assert(code.match(/quotient/g).length === 3, 'message: The quotient variable should only be assigned once');" </del> <ins> "assert(code.match(/quotient/g).length === 1, 'message: The quotient variable should only be assigned once');" </ins> ], "type": "waypoint", "challengeType": 1,
[ "<!-- freeCodeCamp Issue Template --<!-- Please provide as much detail as possible for us to fix your issue --<!-- Remove any heading sections you did not fill out --<!-- NOTE: If your issue is CodePen Project / Test Suite related, please open it using the below URL instead --<!-- --Basic JavaScript: Divide one Decimal by Another with JavaScript Previous Issues: The issue is still happening even with suggested refresh and/or reset. Cannot pass this challenge states \"The quotient variable should only be assigned once\" I had other campers verify in case of a local issue, but they are reporting the same error on this challenge. <!-- Describe your workspace in which you are having issues--Browser Name, Version: Operating System: FireFox 57.0 (64-bit) and Chrome Version 63.0.3239.84 (Official Build) (64-bit) Mobile, Desktop, or Tablet: Laptop Windows 10 Professional 64-bit <!-- If relevant, paste all of your challenge code in here --<!-- Add a screenshot of your issue --!\nThanks for reporting this Previously, the code from the seed was included in the variable used in the tests. This was a new change in the beta that previously broke this test. This has been reverted, the is no longer included in the . Because of that, the test can also be reverted to what it was before. I opened a PR to fix this () and I'm opening an issue for the other instance that was found. There might be more of these, hopefully we can uncover them before the beta release." ]
[]
```js <del> const largestPrimeFactor = (number)=>{ </del> <ins> const largestPrimeFactor = (number) => { </ins> let largestFactor = number; <del> for(let i = 2;i<largestFactor;i++){ if(!(largestFactor%i)){ largestFactor = largestFactor/i; largestPrimeFactor(largestFactor); } </del> <ins> for (let i = 2; i <= Math.sqrt(largestFactor); i++) { if (!(largestFactor % i)) { let factor = largestFactor / i; let candidate = largestPrimeFactor(factor); return i > candidate ? i : candidate; } </ins> } return largestFactor; } ```
[ "<!-- 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 last test times out on the given problem and needs to either be removed or replaced with a smaller number. Add a Link to the page with the problem: If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !\nI think it's fair to require people to use efficient algorithms for this section, so I don't think that last test should be removed. Perhaps it's worth stressing (in the first few Euler challenges) that speed is a requirement. That said, the solution in the challenge is wrong: returns 4 when given 8. We should test for that. I think Is fast enough and (hopefully!) correct.\nYup. That works. I see the part about efficiency.\nCool, I think this is a good candidate for a first contribution.\nHello guys! Can I take this? as I understand the task is to update the solution block with a function that performs faster? Thank you!\nHi please do! If you could also add one more test that validates that that would be great, since the existing solution gets that wrong.\nCool, thank you! Will add that too" ]
[]
## Description <section id='description'> Besides GET, there is another common HTTP verb, it is POST. POST is the default method used to send client data with HTML forms. In REST convention, POST is used to send data to create new items in the database (a new user, or a new blog post). You don’t have a database in this project, but you are going to learn how to handle POST requests anyway. <del> In these kind of requests, the data doesn’t appear in the URL, it is hidden in the request body. This is a part of the HTML request, also called payload. Since HTML is text-based, even if you don’t see the data, it doesn’t mean that it is secret. The raw content of an HTTP POST request is shown below: </del> <ins> In these kind of requests, the data doesn’t appear in the URL, it is hidden in the request body. The body is a part of the HTTP request, also called the payload. Even though the data is not visible in the URL, this does not mean that it is private. To see why, look at the raw content of an HTTP POST request: </ins> ```http POST /path/subpath HTTP/1.0
[ "Describe your problem and how to reproduce it: The challenge says: It should be “HTTP request”, not “HTML request”. Also I don’t get the point in the third sentence “Since HTML is text-based, even if you don’t see the data, it doesn’t mean that it is secret”. What does HTML being text-based have to do with not seeing the data from a POST request? The response to an HTTP request doesn’t even necessarily have to be HTML, or even text-based. None of the examples up to this point has the response been HTML, but JSON. And how does HTML being text-based and not being able to see the data being sent in the request relate to the data being “secret” and why is that important? Add a Link to the page with the problem:\nAgreed, thanks for pointing that out. And, yes, the third sentence is misleading. The paragraph in question is I think what the challenge should say is the following: Basically it's a warning that POSTs may look more secure, but you still need encryption!\nHello! This is my first time contributing in the code. I would like to take up this issue if no one is working on it. Thank You!\nWelcome No one else seems to have taken this up yet, so please do." ]
[]
import ToolPanel from './Tool-Panel'; import TestSuite from './Test-Suite'; <del> import { challengeTestsSelector } from '../redux'; </del> <ins> import { challengeTestsSelector, isChallengeCompletedSelector } from '../redux'; </ins> import { createSelector } from 'reselect'; import './side-panel.css'; const mapStateToProps = createSelector( <ins> isChallengeCompletedSelector, </ins> challengeTestsSelector, <del> tests => ({ </del> <ins> (isChallengeCompleted, tests) => ({ isChallengeCompleted, </ins> tests }) );
[ "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.\nWe need a check mark in the title or a badge or to indicate the same?\nThe 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.\nThat would be a nice way to handle it. Please go forth if you are interested in this?" ]
[]
<br /> <br /> **Projects**: [Mean-Variance-Standard Deviation Calculator](https://www.freecodecamp.org/learn/data-analysis-with-python/data-analysis-with-python-projects/mean-variance-standard-deviation-calculator), [Demographic Data Analyzer](https://www.freecodecamp.org/learn/data-analysis-with-python/data-analysis-with-python-projects/demographic-data-analyzer), [Medical Data Visualizer](https://www.freecodecamp.org/learn/data-analysis-with-python/data-analysis-with-python-projects/medical-data-visualizer), [Page View Time Series Visualizer](https://www.freecodecamp.org/learn/data-analysis-with-python/data-analysis-with-python-projects/page-view-time-series-visualizer), [Sea Level Predictor](https://www.freecodecamp.org/learn/data-analysis-with-python/data-analysis-with-python-projects/sea-level-predictor) #### 9. Information Security Certification - [Information Security with HelmetJS](https://learn.freecodecamp.org/information-security/information-security-with-helmetjs)
[ "This is a broken link. <img width=\"1440\" alt=\"Screen Shot 2020-09-21 at 12 43 27 PM\" src=\"https://user-\"<img width=\"1148\" alt=\"Screen Shot 2020-09-21 at 12 43 55 PM\" src=\"https://user-\"Recommended fix, suggestions (how would you update it?): Two ideas for fixing this come to mind: In the , we want to change both links to match the current application. Here is the code that should be to fix the issue: Set up routes for the old paths to redirect to the current paths. I'm unsure of exactly how to do this." ]
[]
A <code>version</code> is one of the required fields of your package.json file. This field describes the current version of your project. Here's an example: ```json <del> "version": "1.2", </del> <ins> "version": "1.2.0", </ins> ``` </section>
[ "I noticed this while looking at another issue. Glitch is giving me an error when using version \"1.0\" in my file. It only seems to work when I use a third number: \"1.0.0\" - I'm not sure if this has always been the case since I don't think it threw this error in the past. But suggests to use a two digit version. It should probably be changed if this isn't allowed. EDIT: actually the project will still run with the invalid version - I thought it was causing the project not to run. But glitch does still give an error about it.\nmade a PR :+1:" ]
[]
"<code>});</code>" ], "tests":[ <del> "assert.deepEqual(array, [1,2,3,4], 'message: You should have removed all the values from the array that are greater than 4.');", </del> <ins> "assert.deepEqual(array, [1,2,3,4,5], 'message: You should have removed all the values from the array that are greater than 5.');", </ins> "assert(editor.getValue().match(/array.filters*(/gi), 'message: You should be using the filter method to remove the values from the array.');", "assert(editor.getValue().match(/[1,2,3,4,5,6,7,8,9,10]/gi), 'message: You should only be using <code>.filter</code> to modify the contents of the array.');" ],
[ "Assignment: Let's remove all the values greater than five Assert: You should have removed all the values from the array that are greater than 4. problem arises if user includes 5 in result set" ]
[]
Are you interested in contributing to our open source projects used by nonprofits? <del> Also, check out https://www.freecodecamp.org/contribute/ for some fun and convenient ways you can contribute to the community. </del> <ins> Also, check out https://contribute.freecodecamp.org/ for some fun and convenient ways you can contribute to the community. </ins> Happy coding,
[ "I got all the certs on .dev and got this email... ! The link should be updated to" ]
[]
```js var ourStr = "I come first. " + "I come second."; <del> // ourStr is "I come first. I come second." </del> <ins> // ourStr is "I come first. I come second." </ins> ``` </section>
[ "<!-- 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: Example on the page has a double space instead of a single. var ourStr = \"I come first.\" + \"I come second.\" // ourStr is \"I come first._I come second.\" Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Safari Browser Version: 13.1.1 Operating System: macOS If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): <img width=\"620\" alt=\"Skjermbilde 2020-06-04 kl 21 13 12\" src=\"https://user-\"\nI can confirm this. Thank you, for spotting it, and pointing it out.\nOkay, I believe I have corrected this error." ]
[]
<section id="description"> Sass中的<code>@if</code>指令对于测试特定情况很有用 - 它就像JavaScript中的<code>if</code>语句一样。 <blockquote> @mixin make-bold($ bool){ <br> @if $ bool == true { <br> font-weight:bold; <br> } <br> } </blockquote>就像在JavaScript中一样, <code>@else if</code>和<code>@else</code>测试更多条件: <blockquote> @mixin text-effect($ val){ <br> @if $ val == danger { <br>红色; <br> } <br> @else if $ val == alert { <br>颜色:黄色; <br> } <br> @else if $ val == success { <br>颜色:绿色; <br> } <br> @else { <br>颜色:黑色; <br> } <br> } </blockquote></section> ## Instructions <del> <section id="instructions">创建一个名为<code>border-stroke</code>的<code>mixin</code> ,它接受一个参数<code>$val</code> 。 <code>mixin</code>应使用<code>@if</code> , <code>@else if</code>和<code>@else</code>检查以下条件: <blockquote>光 - 1px纯黑色<br>中等 - 3px纯黑色<br>重 - 6px纯黑色<br>没有 - 没有边界</blockquote></section> </del> <ins> <section id="instructions">创建一个名为<code>border-stroke</code>的<code>mixin</code> ,它接受一个参数<code>$val</code> 。 <code>mixin</code>应使用<code>@if</code> , <code>@else if</code>和<code>@else</code>检查以下条件: <blockquote>光 - 1px纯黑色<br>中等 - 3px纯黑色<br>重 - 6px纯黑色 </blockquote> 如果<code>$val</code>不是<code>light</ code>,<code>medium</code>,或者<code>heavy</code>,则边框应该设置为<code>none</code>。 </section> </ins> ## Tests <section id='tests'>
[ "<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Issue Description Following the given instructions. The test will fail for the border-stroke($val) { $val === light { border: 1px solid black; } if $val === medium { border: 3px solid black; } if $val === heavy { border: 6px solid black; } { border: none; } } The checkmark at the bottom left says: \"Your mixin should have an statement to set the border to none.\" and it will pass if using \"none\" but not \"no border\" as suggested. My suggestion is to replace \"no border\" from the instructions with \"none\" Link to the page with the problem: browser and operating system: Browser Name: Chrome Browser Version: Version 71.0.3578.98 (Official Build) (64-bit) Operating System: MacOs Sierra Version 10.12.6\nAre you still facing this problem because on my end the code is working fine?\nHi yes. I still have the same issue. Following the instructions, the last test doesnt pass ! If I put 'border: none' in the statement it passes !\nI believe the instruction is little misleading. It should have been 'no border - none' instead of 'none - border' as border doesn't doesn't have a property called \"no border\" but does have a property called \"none\". I could change the description of it to reduce confusion. Please let me know if this clarifies your concern or if it is a completely different issue.\nyes, it has clarified my issue. Thank you for your help." ]
[]
overflow-y: auto; scrollbar-width: auto; /* lang menu should always be full height */ <del> height: 19.9rem; </del> } /* main menu must be at least as tall as lang menu (when displayed)
[ "The language selection menu is not intuitive about the no. of available options. It's a bit paradoxical at the moment: You will not notice additional options until you start scrolling while being on top of the options. You will not start scrolling until you know there are additional options. to '/learn' on 'Menu' down to 'Change Language' the cursor on the options Scrolling while being in the area of the listed options. menu should be very clean and intuitive. \"Cancel Change\" option should have some form of visual separation. https://user- Device: All Devices OS: All OS Browser: All Browsers Version: All Versions No response\nthis will start becoming evident with more languages on the list. The quickest and simplest way this can be handled is by slightly increasing the height of the list and decreasing the height of the hover-state highlight (each item). That will leave some space at the bottom of the last item, intuitively letting the user know there is more to be looked at. Currently, the perfect-sized (height) items and the overall height of the list make it difficult to notice more entries. Finally, that \"Cancel\" option should be a different color or have some form of visual separation.\nis this issue still being worked on? If not, I would like to take it.\nThat makes sense, I thought we fixed that. should be removed for and\nor anyone else interested, this is up for grabs.\nThis is what makes the language menu full length so no vertical scroll bar appears. Originally, I had the language menu set so that a vertical scroll bar would appear if it was taller than the main menu. But it was decided that there shouldn't be a vertical scroll bar, the language menu should be as tall as necessary so no scroll bar was needed. Is this what we still want? Even as we continue to add even more languages?\nthanks for bringing this up. Ideally we would need to show as many languages as possible in a viewport and display a minified scroll bar if the list exceeds the height viewport minus of the navigation. We could show a scrollbar initially as you recommended, but the dropdown needs expand further than the main menu if needed." ]
[]
"<div class='hidden-xs row media-stories'>" + "<div class='media'>" + "<div class='media-left'>" + <del> "<a href='/'" + data[i].author.username + "'>" + </del> <ins> "<a href='/" + data[i].author.username + "'>" + </ins> "<img class='img-news' src='" + data[i].author.picture + "'/>" + "</a>" + "</div>" +
[ "Task no. 7, says: \"You can view the portfolio pages of any camper who has posted links or comments on Camper News. Just click on their photo.\" However, clicking a photo simply licks back to the homepage. Clicking their username links to their profile. So the instruction needs to be updated.\nThank you for finding and reporting this! I went the other way and fixed the bug instead of the instructions, seemed more appropriate ;)\nNo problem. Glad I could help." ]
[]
Now you can start the code to fight monsters. To keep your code organized, your `fightDragon` function has been moved for you to be near the other `fight` functions. <del> Below your `weapons` array, define a `monsters` variable and assign it an array. Set that array to have three objects, each with a `name`, `level`, and `health` property. The first object's values should be `slime`, `2`, and `15`, in order. The second should be `fanged beast`, `8`, and `60`. The third should be `dragon`, `20`, and `300`. </del> <ins> Below your `weapons` array, define a `monsters` variable and assign it an array. Set that array to have three objects, each with a `name`, `level`, and `health` properties. The first object's values should be `slime`, `2`, and `15`, in order. The second should be `fanged beast`, `8`, and `60`. The third should be `dragon`, `20`, and `300`. </ins> # --hints--
[ "There is a typo in Step 108, the word is single while it should be . Here is the typo in step 102, there is a missing code block in this line it should be this in step 81, there are three missing code blocks in these line they should be 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. 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.\nI would like to work on this.\nfeel free to open a pull request, after you have read .\nI have opened a PR please let me know if there are any changes or improvements that needs to be done." ]
[]
Create a rule that targets both `.one` and `.two` and increase their `blur` effect by 1 pixel. <del> Here's an example of a rule that increases the `blur` of two elements: ```css h1, p { filter: blur(3px); } ``` </del> # --hints-- <del> You should have a `.one, .two` selector. </del> <ins> You should have a `.one, .two` selector list. </ins> ```js const oneTwo = new __helpers.CSSHelp(document).getStyle('.one, .two');
[ "It would make more sense for step 34 to have the filter syntax example, instead of it showing up in the next step. Explain and show the syntax. 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]\nYes, that totally needs to be done what about step 35? there I think the example is to remind people how to give same rules to multiple selectors. Should that be removed? double blur example?\nNot sure if we need a selector list example as long as the hint text shows the selector. But I would like for the hint text to actually specify it as a selector list." ]
[]
title, description, superBlock, <ins> block, </ins> translationPending } },
[ "Describe your problem and how to reproduce it: In the challenges/projects that don't use editor, link text at the top in the contain some additional text, for example Challenges that have editor on page don't seem to have this problem. Add a Link to the page with the problem: If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! !" ]
[]
<label>Do you have any questions:</label> </div> <div class="answer"> <del> <textarea rows="5" cols="24"> Who is flexbox... </textarea> </del> <ins> <textarea rows="5" cols="24" placeholder="Who is flexbox..."></textarea> </ins> </div> --fcc-editable-region-- </div>
[ "<!-- 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. -- The final instructions for this step say: \"Then, give the placeholder text describing an example answer.\" Since the instructions mention \"placeholder\" I think it is safe to assume that some people will think they should use the attribute on the to fulfill this requirement. But the code check test checks the of the : So using the attribute will result in the following hint: \"You should give the placeholder text describing an example answer.\" Which does not make it clear that the example answer should be embedded in the instead of using the attribute. Based on the current instructions I think most users will assume that the attribute should be used to complete this step and the test should be updated accordingly. <!-- Please complete the following information. --- Device: Desktop OS: Linux/Fedora 34 Browser: Firefox Version: 95.0.2\nOn\nI was going to fix this issue by updating the test in step 38 to check the placeholder attribute on the textarea but then I realized that if we make this change then the HTML in each step after 38 would also need to be updated to use the placeholder attribute as well. So the question is, do we want to use the placeholder attribute and update all of the remaining steps or do we want to reword the instructions in step 38 to make it clear that you should embed the question text in the textarea and not use the placeholder attribute?\nThat's a good question. The placeholder text matches wording from referring to the attribute. That would make me think, the intention is to use the attribute.\nAgreed, this should probably be updated to use the placeholder attribute. Looks like I've got a lot of updates to include in the PR.\nThank you, for opening this. When I wrote this, I vaguely remember reading a resource mentioning using the attribute on was not the recommended approach. However, as I cannot find that, I agree using the attribute in this case seems like the better option. Yes, this will require a rewrite for all subsequent lessons. However, this usually is a simple Find and Replace.\nPerfect. I'll submit a PR for this in just a bit." ]
[]
export default function hardGoToEpic(action$, _, { location }) { return action$.pipe( ofType(types.hardGoTo), <del> tap(({ payload = HOME_PATH }) => { </del> <ins> tap(({ payload }) => { </ins> location.href = payload; }), ignoreElements()
[ "While Gatsby allows us to create globals in we also make use of for that purpose. We should DRY this out and use one ( seems the best). See" ]
[]
"description": [ "<code>data structures</code> have <code>properties</code>. For example, <code>strings</code> have a property called <code>.length</code> that will tell you how many characters are in the string.", "For example, if we created a variable <code>var firstName = "Charles"</code>, we could find out how long the string "Charles" is by using the <code>firstName.length</code> property.", <del> "Use the <code>.length</code> property to count the number of characters in the <code>lastNameLength</code> variable." </del> <ins> "Use the <code>.length</code> property to count the number of characters in the <code>lastName</code> variable." </ins> ], "tests": [ "assert((function(){if(typeof(lastNameLength) !== "undefined" && typeof(lastNameLength) === "number" && lastNameLength === 8){return(true);}else{return(false);}})(), 'lastNameLength should be equal to eight.');",
[ "Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. The last paragraph: Should read:" ]
[]
assert.equal(allSongs[1].duration, "4:15"); ``` <del> The second object in your `allSongs` array should have an `src` property set to the string `"https://cdn.freecodecamp.org/curriculum/js-music-player/can't-stay-down.mp3"`. </del> <ins> The second object in your `allSongs` array should have a `src` property set to the string `"https://cdn.freecodecamp.org/curriculum/js-music-player/can't-stay-down.mp3"`. </ins> ```js assert.equal(allSongs[1].src, "https://cdn.freecodecamp.org/curriculum/js-music-player/can't-stay-down.mp3");
[ "I noticed that we are using both \"a attribute\" and \"an attribute\" in challenge descriptions. And we even use both in the same challenge (): <img width=\"596\" alt=\"Screenshot 2024-05-21 at 22 44 29\" src=\"\"I think both are acceptable, since the articles depend on how we pronounce \"src\" (\"es-ar-see\" vs \"source\"), but I think we should stick to one for consistency. I'll let native English speakers make the call\nI always pronounce it as , so I vote\nI'm with Jessica on this one. The second sentence should be changed to .\nThis issue is open to first-time code contributors to this repository. The files that you should be updating are: 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. 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.\nHi everyone. This is a great pick up! I am happy to help out there and will get a initial PR up for review today :)\nI have reviewed the changes made in PR, all the related file have been fixed correctly and checked locally.\nHello, This is my first Open source contribution so if you guys can give me feedback on what i did wrong and how i should correct it please guide me. from the seven files mentioned above, I have created pull request for each one which is as below. sorry if i messed up, as it is my first try. I am actively looking for any advice, suggestion, criticism. Thank You." ]
[]
// eval test string to actual JavaScript // This return can be a function // i.e. function() { assert(true, 'happy coding'); } <del> // eslint-disable-next-line no-eval const test = eval(testString); </del> <ins> const testPromise = new Promise((resolve, reject) => // To avoid race conditions, we have to run the test in a final // document ready: $(() => { try { // eslint-disable-next-line no-eval const test = eval(testString); resolve({ test }); } catch (err) { reject({ err }); } }) ); const { test, err } = await testPromise; if (err) throw err; </ins> if (typeof test === 'function') { await test(e.getUserInput); }
[ "<!-- 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: your code 'Run the Tests' it passes all your tests, again click on 'Run the Tests' time, it will show an error. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: 83.0.4103.61 Operating System: Windows 10 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): 1st-time click on 'Run the Tests' ! 2nd-time click on 'Run the Tests ' ! I would love to work on it. Please assign it to me Thank You\nHello there, This issue has been discussed on: And, if you are passing the tests, and returning to fail, it is not much of an issue. So, I will leave the same comment as I did in the forum: To solve, refresh the page. Perhaps, it might be useful to some, if the tests and seed code were rewritten, but refreshing the page, and ensuring the code is correct is a suitable fix. I will leave this issue open, but, seeing as this challenge has existed for a long time, this issue rarely arises, and the workaround is as simple as refreshing, I do not recommend a PR be opened for this.\nOkay\nWhile I agree that this isn't the highest priority (as there is a work around), it's still a bug. Someone should not have to refresh the page to reliably pass the tests. That said, it might not be easy to fix. It's possibly a case of re-writing the tests to be async and ing in the tests, but I'm not sure.\nI believe this should be fixed with the following assert:\nUnfortunately not, since that is basically which passes. needs to return an async function.\noh yeah, you are right, my bad. what about enclosing the assert inside the method?\nI am unable to reproduce this locally. Is there a chance that there is some cache reason for this behaviour?\nYes it cant be reproduced locally. I dont think its a cache issue.", "I believe the latency is too less - the document is loaded instantly whereas the actual environment is slower so we are able to get the mentioned behavior.\nI am curious as to what's going on here. My suspicion is that it's a timing issue, that for some runs the test gets evaluated before , but I'm not sure. Since document ready is asynchronous, the assert will be called at some point after the test has already passed. Take a look here: you can see if the test throws during the initial (synchronous) evaluation, the error is caught and the test fails. If instead it doesn't throw and returns a function, then that function should return a Promise. Finally that Promise is ed. If it doesn't throw, then the whole thing passes. The formulation you're talking about won't throw during the first evaluation and does not return a function to be awaited. It should (I think) always pass.\nGiven that this has been reported for several challenges, I think it's reasonable to assume that all the challenges that rely on could have the problem.\nagreed. It would be interesting to figure out a fix for this. I will try on my end but I hope other contributors are actively looking for ways to resolve this.\nYep, it would be good to understand why this is happening. That may not be easy to discover, though, so I'd be happy with a PR that just modifies the tests to wait for .\nSome observations: I have Disable Cache turned on under the network tab it always works for me. If I disable it, I can make the tests reliably fail. long as all the files have 0ms delay (memory cache) the test fails, the minute a vendors~chai js file has just a 1ms delay it passes the test (disk cache vs memory cache), . two challenges that are not using jQuery for the assert tests always pass for me. Not sure if it's simply the DOM querying that is the issue, or jQuery itself. How is the browser cache locally disabled? It always does a network fetch and is never fetching from disk or memory. Can that be disabled? As far as I can tell because there is always a fetch delay locally the tests never fail. Which makes it hard to test.\nNice QAing Presumably that tiny delay is enough for all the changes to appear in the DOM. Good question.", "I tried building the site () and serving it using , but it's still not cached. It might be getting cached when you use .org because of the cdn, but I'm not sure. If that's right, it's something that we will have to deploy to test.\nI'm pretty sure this is now fixed on .dev - I can no longer reproduce the problem. could take a quick look and confirm/deny?\nNice job, all the jQuery challenges pass for me now. Ran all of them in Chrome and a few in Firefox. Passed first try every time. :+1:\nNice. Thanks for all your help. Looks like we've got to the bottom of it." ]
[]
}; const StepPreview = ({ <del> disableIframe }: Pick<PreviewProps, 'disableIframe'>) => { </del> <ins> disableIframe, previewMounted }: Pick<PreviewProps, 'disableIframe' | 'previewMounted'>) => { </ins> return ( <Preview className='full-height'
[ "On the initial loading of a Step the preview is showing in the preview pane, but if you either open the preview in the pop-out window or toggle the preview pane off/on then the preview does not load again. All Steps in New RWD preview in pop-out window (preview does not load) page Preview button to toggle preview pane off/on (preview does not load) Preview should load in both pop-out window and after the preview pane has been toggled off/on. No response Verified with Chrome/Firefox on both Linux and Win11. Possibly related to issue , but I think this is newer and slightly different.\nJust discovered that if you make any change in the editor (such as adding a single space) then the preview will refresh and display again. But you have to do that every time you either open the pop-out window or toggle the preview pane.\nWhen the preview is blank the iframe attributes are not updated either (which makes sense I guess, it looks to be the default values). Blank before updating: After updating: It feels like a state issue.\nThe preview also disappears if you toggle the Instructions on any of the certification projects.\nYes, that's a separate issue. I dig around at this a bit, seems to have caused the problem. Before it, these issues aren't present." ]
[]
while (done !== count) { done++; rows.push(padRow(done, count)); <del> if (done === count) { </del> <ins> if (done === count) { </ins> continueLoop = false; } }
[ "In the JS Beta project to build a pyramid gen., steps 82 and 83 both show an if statement block in the code editor that is not correctly indented within the while loop it is in. This may confuse new learners if they are relying on the indents to understand the logic and should be fixed to keep the presented code in acceptable shape for learners. N/A the if statement should be indented within the while loops block ! ! N/A No response" ]
[]
When you use the `relative` value, the element is still positioned according to the normal flow of the document, but the `top`, `left`, `bottom`, and `right` values become active. <del> Instead of `static`, give you `.cat-head` a position of `relative`, and leave both `top` and `left` properties as they are. </del> <ins> Instead of `static`, give your `.cat-head` a position of `relative`, and leave both `top` and `left` properties as they are. </ins> # --hints--
[ "Here's the last paragraph in the instructions: Notice that where is says \"... give you .cat-head...\" should actually be \"... give your .cat-head ...\" N/A N/A ! Device: Laptop OS: Windows 10 Browser: Chrome Version: 116.0.5845.111 Didn't see a better way to report a spelling issue directly from the website.\nThanks 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: 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. 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.\nCan I Contribute on this issue?\nattempting\nHey We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labelled with or are open for contributions. Please make sure you read . We prioritize contributors following the instructions in our guide. Join us in or if you need help contributing - our community will be happy to assist you.\nplease check out the update.\nHey yout PR is targeting branch of your own fork, not the .\ni think its targeting the right one now.\nif you want to tackle some other grammatical errors I found, I know there is a missing space in a step somewhere, and missing punctuation in another. I've forgotten where, but I know they both happened prior to this step I reported here, but not before \"Learn the CSS Box Model by Building a Rothko Painting\". Both were on different steps." ]
[]
import { certMap } from '../../resources/cert-and-project-map'; import { completedChallengesSelector } from '..'; import { <ins> certTypes, certTypeIdMap } from '../../../../config/certification-settings'; import { </ins> updateUserFlagComplete, updateUserFlagError, validateUsernameComplete,
[ "Describe the bug I have completed the necessary requirements to get the Legacy Full Stack Certification, whenever I click on the claim certification button, it displays nothing, leaving the page as it is, I emailed the support team about this, they agreed i've fulfilled the requirements to get Legacy Full Stack certified and they said its a bug, and I should open a github case about it, so here I am. please help. Desktop (please complete the following information): OS: [Windows] Browser: [chrome] Version: [102.0.5005.115 (Official Build) (64-bit)] Additional context My username is muhammedctgr and my name is Popoola Muhammed\nto investigate\nhi pls whats the status on this?\nit needs to be investigated\nsays page not found....\nnoted, thank you. i'll wait.\nMany thanks to the dev team, I really appreciate the this mean its been fixed? Still unable to claim the cert tho.\nOnce the next production build is deployed, this fix should be in. We typically do 1 - 2 deployments each week.\nThis should be live now!\nappreciate this, I've been able to claim the full stack cert. Promise to make FCC proud." ]
[]
<section id='solution'> ```js <del> // solution required </del> <ins> const createPerson = (name, age, gender) => { "use strict"; return { name, age, gender }; }; </ins> ``` </section>
[ "<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --1) Add any code into the challenge field (other than a valid solution) that will not result in a syntax error. 2) Run the tests Expected result: The test should fail Actual result: The test passes Browser Name: Firefox Browser Version: 61.0 Operating System: 10.12.6 !\nThe problem is this test in the : It returns true if returns an object with no keys, or just not-an-object. I assume we should really be using something like to check the expected object and the user's output object are the same.\nWorking on a fix." ]
[]
This demonstrates an unusual property of 142857: it is a divisor of its right-rotation. <del> Find the last 5 digits of the sum of all integers $n$, $10 &lt; n &lt; 10100$, that have this property. </del> <ins> For integer number of digits $a$ and $b$, find the last 5 digits of the sum of all integers $n$, $10^a &lt; n &lt; 10^b$, that have this property. </ins> # --hints-- <del> `numberRotations()` should return `59206`. </del> <ins> `numberRotations(2, 10)` should return `98311`. </ins> ```js <del> assert.strictEqual(numberRotations(), 59206); </del> <ins> assert.strictEqual(numberRotations(2, 10), 98311); ``` `numberRotations(2, 100)` should return `59206`. ```js assert.strictEqual(numberRotations(2, 100), 59206); </ins> ``` # --seed--
[ "The 100 should be a superscript in the last line of this challenge. N/A Should say We may also consider better mathematical formatting? No response All No response\nSeems like it has been like this for a while: I will open this up to first timers. The expected fix is to use MathJax (KaTeX-like) to render the following: $$ n: 10 < n < 10^{100} $$ An issue with the 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\nI actually saw a way to roll this into a fix that expands the challenge so that won't work." ]
[]
} .video-quiz-options { <del> background-color: var(--tertiary-background); </del> <ins> background-color: var(--primary-background); </ins> } /* remove bootstrap margin here */
[ "<img width=\"492\" alt=\"Screen Shot 2020-05-28 at 1 29 28 PM\" src=\"https://user-\"<img width=\"511\" alt=\"Screen Shot 2020-05-28 at 1 28 37 PM\" src=\"https://user-\"<hr<img width=\"518\" alt=\"Screen Shot 2020-05-28 at 1 53 35 PM\" src=\"https://user-\"\nthanks for catching the code blocks in the answer section looking off. Didn't notice it at first -- maybe it required a refresh? But yeah, looks off with the darker background. Tested this locally and it seems like we can just remove the language (py or python) from the triple backticks: ! I also think it would be better to have all the code in markdown. It's a bit finicky in conjunction with YAML, but makes it much easier to control the formatting/spacing than tags.\nHow about something like this: ! this is with a background of and using to enable highlighting. I'm not sure what the best background is. This one looks a little better than white and is a bit better from a contrast perspective.\nI would like to see the same background color for answers like in Kris's photo, but the code highlighting, like in Oliver's. I think the only way to achieve this is to change some styles after the fact in the css.\nHere are some options: ! the first two being white and prism's default (#). The issue being they look progressively better, but get progressively harder to read. in particular starts to fade into the background. That's what got me thinking about this , so I think it's fine to go with the prettiest version as long as we address the a11y issues.\nwhat about changing the whole box to white... <img width=\"446\" alt=\"Screen Shot 2020-05-29 at 3 41 42 PM\" src=\"https://user-\"Kinda solves both issues\nMakes sense to me. They might look a little better with a dark border, but either way, I think the white background is the way to go." ]
[]
} button { <del> outline: none; </del> cursor: pointer; text-decoration: none; background-color: var(--light-yellow);
[ "The default CSS provided for the Calorie Counter in step 1 has the property set to for the element. I'm going to assume this was just an oversight, and not because you all are trying to cause me an early death by raising my blood pressure. Remove the property completely from the element. No response N/A No response" ]
[]
```js const meta = [...document.querySelectorAll('meta')]; <del> const target = meta?.find(m => !m?.getAttribute('name') && !m?.getAttribute('content') && m?.getAttribute('charset') === 'UTF-8'); </del> <ins> const target = meta?.find(m => !m?.getAttribute('name') && !m?.getAttribute('content') && m?.getAttribute('charset')?.toLowerCase() === 'utf-8'); </ins> assert.exists(target); ```
[ "The value for is case-insensitive. Not sure if I missed any, but here are case-sensitive ones I found. Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-accessibility-by-building-a-quiz Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-css-animation-by-building-a-ferris-wheel Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-intermediate-css-by-building-a-picasso-painting Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-responsive-web-design-by-building-a-piano Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-the-css-box-model-by-building-a-rothko-painting a lot Both are valid The value for should be case insensitive for all challenges. 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]" ]
[]
<del> require('dotenv').config(); </del> <ins> const env = require('../config/env'); </ins> const { createFilePath } = require('gatsby-source-filesystem');
[ "Is there any reason not to put the real and in ? I reflexively put in a dummy key when I set this up, but now that I revisit this, that seems like a mistake.\nYes, actually it broke the .dev build unsurprisingly , I think noticed it and reported in the team chat. My bad for not catching this previously. The real fix is to ignore and move ahead when the keys are not available are default. We do this with google application credentials.\nOh, I assume it broke the build because .dev isn't using I didn't think of that... So, we should implement the fix and add the public keys to , right?\nI was thinking something more along the lines of (example from api-server): I would try to avoid hundreds of contributors hitting the indexes locally. Ideally people should get their own keys. While the key and index is public, it's still not recommended to hit it?\nAs for the production keys, it's actually fine because the build should fail. I have since the keys in the build pipeline.\nOne thing: if we don't want contributors spamming search (fair enough!) I think there should be some docs that let people know what's what. Either that search isn't available in development or the steps they need to take to make it work.\nI agree. We should add some docs on getting keys, or perhaps creating a test index and sharing that instead" ]
[]
"Create an <code>ordered list</code> of the the top 3 things cats hate the most.", "HTML has a special element for creating ordered lists, or numbered-style lists.", "Ordered lists start with a <code>&#60;ol&#62;</code> element. Then they contain some number of <code>&#60;li&#62;</code> elements.", <del> "For example: <code>&#60;ol&#62;&#60;li&#62;hydrogen&#60;/li&#62;&#60;li&#62;helium&#60;/li&#62;&#60;ol&#62;</code> would create a numbered list of "hydrogen" and "helium"." </del> <ins> "For example: <code>&#60;ol&#62;&#60;li&#62;hydrogen&#60;/li&#62;&#60;li&#62;helium&#60;/li&#62;&#60;/ol&#62;</code> would create a numbered list of "hydrogen" and "helium"." </ins> ], "tests": [ "assert($('ul').length > 0, 'You should have an <code>ul</code> element on your webpage.')",
[ "Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. What I see: You can apply a class to an HTML element like this: <h2 class=\"blue-text\"CatPhotoApp<h2What I expected to see: You can apply a class to an HTML element like this: <h2 class=\"blue-text\"CatPhotoApp</h2\nMarkdown's getting in the way, see screenshot. !" ]
[]
"knip": "npx -y knip@1 --include files", "knip:all": "npx -y knip@1", "prelint": "pnpm run -F=client predevelop", <del> "lint": "npm-run-all create:shared -p lint:*", </del> <ins> "lint": "NODE_OPTIONS="--max-old-space-size=7168" npm-run-all create:shared -p lint:*", </ins> "lint:challenges": "cd ./curriculum && pnpm run lint", "lint:js": "eslint --cache --max-warnings 0 .", "lint:ts": "tsc && tsc -p shared && tsc -p api",
[ "Linting fails on local environment in some cases. Issue did not reproduce on GitPod. update-email to the root directory Execution fails with the message under Linting should be successful No response Device: Macbook Air M2 OS: MacOSThis issue was originally raised in Discord: Thread created with the full error log: A contributor also ran into this issue in the past: Note that the lint operation in this one ran against the entire project () rather than a single file.\nThanks for opening this issue. I'm not able to reproduce the issue locally, so I'll need your help with this: Add: after this line: Commit this change using the flag Make a change to and check if you can commit the change without the flag This is to check if those rules are the culprit as I did run into some performance issues with them in the past. Here is our eslint current performance, in case anyone is interested: <img width=\"521\" alt=\"Screenshot 2023-12-18 at 13 58 26\" src=\"\"\nThanks for your help I am still facing the issue. I the two lines after line 89, committed with --no-verify. I a space to and tried to commit without the flag. Attached the stack trace.\nIt seems like the memory allocation on your machine is capped at 2 GB. I tried reducing the limit to 512 MB using the following command, but could not reproduce the issue still: I'm wondering if it works if you increase the value on your end to . So please try this: In the root, add the following line to the \"scripts\" block: Then run in the terminal\nFixed it! I tried running but that did not seem to update the memory allocation when I ran Instead, I ran something similar to your command in the terminal - This fixed it. Thanks a lot! Should we add this in the documentation?" ]
[]
"description": [ "Sometimes you want to add <code>a</code> elements to your website before you know where they will link.", "This is also handy when you're changing the behavior of a link using <code>jQuery</code>, which we'll learn about later.", <del> "Replace your <code>a</code> element's <code>href</code> attribute with a <code>#</code>, also known as a hash symbol, to turn it into a dead link." </del> <ins> "Replace the value of your <code>a</code> element's <code>href</code> attribute with a <code>#</code>, also known as a hash symbol, to turn it into a dead link." </ins> ], "tests": [ "assert($("a").attr("href") === "#", 'Your <code>a</code> element should be a dead link with a <code>href</code> attribute set to "#".')"
[ "Says: Replace your a element's href attribute with a #, also known as a hash symbol, to turn it into a dead link. I think it is kind of unclear - would potentially be better as \"Replace the value of your a element's....\" Tripped me up at first. Submitting a pull request for the change" ]
[]
export function getGuideUrl({ forumTopicId, title = '' }) { title = encodeURIComponent(title); return forumTopicId <del> ? `${forumLocation}/t/${forumTopicId}` </del> <ins> ? `https://forum.freecodecamp.org/t/${forumTopicId}` </ins> : `${forumLocation}/search?q=${title}%20in%3Atitle%20order%3Aviews`; }
[ "Now it points to a Chinese forum post and shows nothing when people click \"Get a Hint\" button in the challenge of Chinese curriculum, for example, (). <!-- A clear and concise description of what you want to happen. --We may translate the hints into Chinese and other languages on Crowdin.\nIt should be possible to create something analogous to our current workflow, as long as the Discourse API allows it. i.e. GET the current articles for upload and then POST the translations once they're approved. Nick probably has a better idea about this than I do, though.\nThe biggest challenge is going to be figuring out how to update the front matter in the curriculum files to link the appropriate forum post.\nI think a really long time ago in one of our conversations with Randy, it was deliberated that the complexity & time involved in working on a way to translate the hint comments, vs working on the new editor & new curriculum was not worth it. But I could be wrong.\nThat's probably true, but what do we want to do with the \"Get a Hint\" button? Some options: Link to the English page Remove that button for the Chinese challenges\nI think linking to the English page is better~\nCan we just link them to English pages?\nThat should be fine, yeah" ]
[]
## Description <section id='description'> <del> Now you've seen all the basic operations for JavaScript objects. You can add, modify, and remove key-value pairs, check if keys exist, and iterate over all the keys in an object. As you continue learning JavaScript you will see even more versatile applications of objects. Additionally, the optional Advanced Data Structures lessons later in the curriculum also cover the ES6 <dfn>Map</dfn> and <dfn>Set</dfn> objects, both of which are similar to ordinary objects but provide some additional features. Now that you've learned the basics of arrays and objects, you're fully prepared to begin tackling more complex problems using JavaScript! </del> <ins> Now you've seen all the basic operations for JavaScript objects. You can add, modify, and remove key-value pairs, check if keys exist, and iterate over all the keys in an object. As you continue learning JavaScript you will see even more versatile applications of objects. Additionally, the Data Structures lessons located in the Coding Interview Prep section of the curriculum also cover the ES6 <dfn>Map</dfn> and <dfn>Set</dfn> objects, both of which are similar to ordinary objects but provide some additional features. Now that you've learned the basics of arrays and objects, you're fully prepared to begin tackling more complex problems using JavaScript! </ins> </section> ## Instructions
[ "<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --In \"\" it mentions: I do not see those lessons anywhere. Is there an hidden module somewhere I don't know of? Or is that text that is a legacy of the previous curriculum? Browser Name: Browser Version: Operating System:\nCheck under Coding Interview Prep (Thousands of hours of challenges)\nperhaps the title in there should be renamed to\nI think that now with the new curriculum, this is fixed?\nThe \"advanced\" section would be those challenge located in the Data Structure Questions in the Coding Interview Prep section. I am thinking the easiest solution this is to rewrite the following sentence from: to something like:\nYes. That should be fine.\nI'll take this up.\nGo for it. No one else has asked for it.\nI had the same question, so I came here, So the answer is Advanced Data Structures located in Coding Interview Prep (Thousands of hours of challenges) Data Structures , am I right ? Why doesn't any admin/mod rewrite as RandellDawson said so no one has this question and come here again ? Thanks\nWhat exactly are you trying to do?\nSame as OP, I cannot see the Advanced Data Structures lesson on FCC\nThey are not called Advanced Data Structures lessons. They are just called Data Structures and they are in the Coding Interview Prep section of the curriculum !\noh man, You didn't get me, I said above : Why doesn't any admin/mod rewrite as RandellDawson said so no one has this question and come here again ? Thanks I read completely this issues and got the answer, just ask why admin/mod doesn't change as you said, so no one will get confused like me or OP again,\nWe decided to just modify the text of the challenge to the following: Additionally, the Data Structures lessons located in the Coding Interview Prep section of the curriculum also cover the ES6 Map and Set objects, both of which are similar to ordinary objects but provide some additional features. This was done to minimize the need to update several other sections. We feel it does not make any difference if it is renamed or just remain section. We hope to have the changes made deployed to the production site very soon." ]
[]
.night .landing-page #top-right-nav li > a, .night #top-right-nav li > span { color: #fff; } <ins> .night .landing-page a { color: #006400; } .night .landing-page a:hover { color: #001800; } </ins> /* End night mode override */ .black-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: At the moment, the clickable area of footer links are spanning the full width of their parent div. I'm not sure if this is on purpose, but IMHO, they should fit to their content instead, since a user could get navigated to another page if they accidentally click somewhere within the clickable area. This issue is on , but it is down for maintenance at the moment. The screenshot is of my local fCC. !\nIs that actually a problem, though? I think having list items spread like that is pretty common. It could be a problem if you aimed for, say, Learn and got News, but there's a reasonable amount of space between them. How about if the box were subtly highlighted on hover?\nThanks for the threads\nTbh, this is the first time I have seen footer items spread like that, though it is common to me to see that on a navbar. I have no problem with leaving it as is, but adding background color on hover would be great.\nI, personally, would prefer if only the text was clickable - but it works either way.\nPersonally I like the wider boxes, because I'm lazy and click in the general vicinity of things. So, I've a PR for the highlight approach, since that was a really easy fix. If that doesn't seem right we can always shrink the links onto the text." ]
[]
# --description-- <del> Start your `HTMLString` with a new line, then create a `label` element. Give that element the text `Entry # Name`, using your template literal syntax to replace `#` with the value of `entryNumber`. </del> <ins> Inside your template literal, create a `label` element and give it the text `Entry # Name`. Using your template literal syntax, replace `#` with the value of `entryNumber`. </ins> # --hints-- <del> Your `HTMLString` variable should start with a new line. ```js assert.match(code, /HTMLStrings*=s*`n/); ``` You should add a `label` element on the new line. </del> <ins> You should have a `label` element inside your template literal. </ins> ```js assert.match(code, /HTMLStrings*=s*`ns*<label>.*</label>/);
[ "The test for Step 44 does not pass as it should when the user creates a newline with a newline literal, and not by pressing the enter key on their keyboard and making the string extend by a line. The challenge should report successful, as the created label has a newline before it. ! ! Device: Desktop, Arch linux, Firefox OS: 6.6.7-arch1-1 Browser: Firefox Version: 120.0.1 (64-bit) No response\nRan into this issue in the today.\nNot sure I understand why we care if there is a new line. If this requirement is meant as a code formatting requirement we shouldn't allow the use of and instead change the text to be more precise. Simply changing \"with\" to \"on\" might be enough.\nYeah I would improve the instruction as well, instead of changing the tests. The starting code of the subsequent steps have this line on a new line, so I think we should guide campers to follow the same format here.\nso it is not a parsing issue then but an instruction issue?\nI would say so. I can't imagine the text \"Start your with a new line\" in any way referring to using . I think it just needs to be clarified.\nI can easily imagine people interpreting that as using a at the beginning of the string. Also, this appears to be the first time a step uses multiple lines in a template literal, so it may not be obvious to the user that you can do that, and thus they might think that is their only option. I'm struggling to find a reason why we care whether they use or an actual hard return here? Maybe the point is to teach that template literals allow for multi-line strings? If that's the case then we need to explain that in the instructions. Otherwise, this restriction of not allowing seems rather capricious.\nWhich is why I said it should be clarified. As far as I'm concerned the new line asked for only serves as code formatting. It has no other importance. <sAllowing doesn't make sense as it does not produce the same code as going down on a new line before creating the element (also it doesn't do anything useful). </sEdit: never mind I thought they had a space as well. But as I said initially, I do not see the importance of testing for the new line.", "It seems fairly irrelevant.\nWhat about changing the seed code so the user does not need to do this at all? That seems like a good solution to me. Change the instructions to:\nIt looks like we are still getting users on the forum, getting stuck on this issue. I vote we move forward with 's suggestion of just updating the instructions and changing the editable regions to make it super clear where they need to write their code.\nThis is what I have and can't still move ahead: function addEntry() { const targetInputContainer = document.querySelector(); const entryNumber = targetInputContainer.querySelectorAll('input[type=\"text\"]').length; const HTMLString = `; HTMLString = <labelEntry ${entryNumber} Name</label`;\nHey Instead of asking for help here, please click the \"Help\" button on the challenge on freeCodeCamp, which will help you create a question in the right part of the forum. Volunteers on the forum usually respond to questions within a few hours and can help determine if there is an issue with your code or the challenge's tests. Thank you and happy coding." ]
[]
## --text-- <del> What Python library has the `.read_html()` method we can we use for parsing HTML documents and extracting tables? </del> <ins> What Python library has the `.read_html()` method we can use for parsing HTML documents and extracting tables? </ins> ## --answers--
[ "! the sentence needs to be fixed removing the second \"we\" 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: 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. 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.\nWow\nJust submitted a pull request after fixing this typo! This is my first time contributing to open source, so please let me know if there're things that I should've done. Thank you for providing this opportunity for first-time contributors." ]
[]
- Seed the database ```bash <del> pnpm run seed </del> <ins> pnpm run seed:certified-user </ins> ``` - Develop the server and client
[ "I had a facepalm moment when I was working on a set of Playwright tests. The tests passed locally but failed in CI, and turned out I was seeding my DB with demo user () while we seed CI with certified user (): The failure was expected then, because the tests were working with different user data. I'm now wondering if we should recommend developing with over in general. If we are okay with this, we will need to update the following section of the : <img width=\"1088\" alt=\"Screenshot 2023-11-09 at 17 12 23\" src=\"\"If we still recommend developing with , then we should add a note in the following section of the to ensure is run before tests are written and executed: <img width=\"1074\" alt=\"Screenshot 2023-11-09 at 17 15 49\" src=\"\"\nI think most people want to use the 'new' user and we do mention , so the setup docs seem fine. However, it's definitely not correct to recommend in the Playwright guide. Seems like a simple enough fix, though: the Playwright should say .\nI think updating the playwright guide would be enough - but we could add a note in the main area that says something like \"Use this if you are going to run playwright tests\"" ]
[]
## --text-- <del> Which of the following describes the affect of a `using` statement? </del> <ins> Which of the following statements is true about showing/removing the curly braces for code blocks associated with an `if` statement? </ins> ## --answers-- <del> Affects only the first code block in the code file. </del> <ins> The curly braces can't be removed from the code block for `else if` and `else` statements. </ins> --- <del> Affects only the current code block in the code file. </del> <ins> If the curly braces are removed from the code blocks of an `if-elseif-else`, the white space must also be removed. </ins> --- <del> Affects all of the code in the code file. </del> <ins> Always choose a style that improves readability. </ins> ## --video-solution--
[ "The \"Control Variable Scope and Logic Using Code Blocks in C#\" in the \"Add Logic to C# Console Applications\" has an question that doesn't really feel quite right for this section. The question is \"Which of the following describes the affect of a statement?\". The thing is statements aren't covered in the foundational MS Learn Path. It'd be a little unfair to new learners to answer this question with the given material. N/A When answering questions on the FreeCodeCamp foundational certification path, prior C# knowledge should not be required to answer questions. A question like the following might be better suited for this particular lesson. What is the scope of a local variable declared inside a method in C#? a) It's accessible only within the method where it's declared. b) It can be accessed from any method within the same class. c) It's accessible globally from any part of the program. d) It's only visible within the same class, but different methods can't access it. No response Device: Desktop OS: Windows 10 Browser: FireFox Version: 117 I only checked out this certification path for practice reasons.\nI came across the same issue. I had to read up on the using statement using different resources in order to answer the question and be able to continue my learning path.\nI've created a pull request to fix this issue. Since all the other questions are taken from the \"Knowledge Check\" portion of related tutorial, I just used the first question found here:" ]
[]
# --description-- <del> Arrays have a `.some()` method. Like the `.filter()` method, `.some()` accepts a callback function which should take an element of the array as the argument. The `.some()` method will return `true` if the callback function returns `true` for at least one element in the array. Here is an example of a `.some()` method call to check if any element in the array is an uppercase letter. ```js const arr = ["A", "b", "C"]; arr.some(letter => letter === letter.toUpperCase()); ``` </del> Add a `someeven` property to your `spreadsheetFunctions` - use the `.some()` method to check if any element in the array is even. # --hints--
[ "In the building a spam filter project's step 's instructions, we are told: \"Remember that arrays have a .some() method. \" However, we cannot remember as it was not taught. In fact it is not actually taught until step 100 of the building a spreadsheet project as far as I'm aware: I suggest that the part of lesson 100 that applies to teaching the some() method be moved into the spam filter project's step 12. N/A Adding the missing lesson for some() before or during step 12 of the building a spam filter project. No response N/A No response\nHello I am a first timer, can i take up this issue? because adding the .some() function explaination to step 12 will solve this issue and i think it will be pretty easy to do that.." ]
[]
"challenges": [ { "id": "bb000000000000000000001", <del> "title": "Trigger Click Events with jQuery", </del> <ins> "title": "Trigger Click Events with jQuery", </ins> "description": [ "In this section, we'll learn how to get data from APIs. APIs - or Application Programming Interfaces - are tools that computers use to communicate with one another.", "We'll also learn how to update HTML with the data we get from these APIs using a technology called Ajax.",
[ "[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\nTrabajando en esta" ]
[]
"lint:ts": "tsc && tsc -p config && tsc -p tools/ui-components && tsc -p utils && tsc -p api", "lint:prettier": "prettier --list-different .", "reload:server": "pm2 reload api-server/ecosystem.config.js", <ins> "preseed": "npm-run-all create:*", </ins> "seed": "cross-env DEBUG=fcc:* node ./tools/scripts/seed/seed-demo-user", "seed:certified-user": "cross-env DEBUG=fcc:* node ./tools/scripts/seed/seed-demo-user certified-user", "serve:client": "cd ./client && pnpm run serve",
[ "In chapter, we have files that run scripts when the is finished, it use and for this, we can do the same here to solve the issues related to installing needed files, copy and stuff a like, and provide a easier way to setup the curriculum for newer developers. This should stop issues which these PRs try to solve, like and , that are related to setting up freeCodeCamp. Here is the file in chapter , for more context.\nI dislike post/pre -install scripts a lot. Actually, I dislike most life-cycle scripts. However, I would be fine with adding a script. Essentially, what is missing with the seed step is:\ncan we not add to the npm script?\nAdding it to the postinstall script would duplicate the run in the CI and deployment pipelines, since it is also included in prebuild. I'd lean more toward Shaun's solution.\nI don't mind, as long as the issue is solved, one more agreement and we can open it for contribution.\nI see what you mean, it does add a bit of an overhead. It does solve this particular issue albeit with a bit of an overhead. I am not sure of the overall impact, but I'd presume it is minimal? I am happy to re-write it to what was suggested above. But does it make more sense for it to be part of the install lifecycle () script or the develop () lifecycle? let me know your thoughts. Thanks.\nI have no idea, I don't meddle with the config files, or scripting tools. This is outside my scope, I just hate that new contributors are facing issues installing the repo.\nIt should be as a script, like Shaun suggested:\nIf 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." ]
[]
return true; } }))).some(v => v); <ins> console.error = oldConsoleError; </ins> assert(fails, 'Test suit does not fail on the initial contents'); });
[ "Describe the bug Several warnings in the Travis CI builds: To Reproduce Steps to reproduce the behavior: a PR the output in Travis CI build Expected behavior Cleaner builds; maybe reduce build time(?) Screenshots ! Additional context Error references this documentation: Live Demo in doc:" ]
[]
## --seed-contents-- ```js ``` # --solutions--
[ "An empty solution seed with the following format does not parse correctly in Crowdin: ! Adding an empty new-line between the backtick lines will parse correctly in Crowdin: ! The following files have empty seeds with the first format and need a blank line : JavaScript / Basic JavaScript comment your javascript code declare javascript variables declare string variables initializing variables with the assignment operator passing values to functions with arguments return a value from a function with return write reusable javascript with functions JavaScript / ES6 create a javascript promise JavaScript / Object Oriented Programming define a constructor function Front End Libraries / Bootstrap Create a bootstrap headline Front End Libraries / React Create a complex jsx element Quality Assurance Projects metric imperial converter Coding Interview Prep / Data Structures Create an ES6 Javascript Map\nHi, I'll add those blank lines. It'll be my first time contributing to an open-source project, though.\nPlease visit to find all the info you will need to get started with contributing a fix for this issue.\nAlright. I'll go through the documentation.\nHi. First time contributor here. I have forked the free code camp files to my github page. I have cloned them locally, opened the appropriate folders into my VSCode editor and made the changes (though I was not able to find a # --seed-- in Quality Assurance Projects: metric imperial conversion) but now I have no idea of how to get the code back here. Is there some documentation with instructions on how to do that? Thanks in advance." ]
[]
# --solutions-- ```js <del> function countOnline(usersObj) { let online = 0; for(let user in usersObj){ if(usersObj[user].online) { online++; </del> <ins> function countOnline(allUsers) { let numOnline = 0; for(const user in allUsers){ if(allUsers[user].online) { numOnline++; </ins> } } <del> return online; </del> <ins> return numOnline; </ins> } ```
[ "This seed code can lead to a bit of confusion because the global variable name and parameter name are pretty similar What about isn't my favorite if someone has another idea. I just don't like when the type isn't strictly needed. No response All No response\ncan I work on this if anyone is not working?\nThis issue isn't ready for PRs yet\nOne idea for naming: -or -\nI went with something other than because 1) that's the example 2) at least one learner has has said was a little hard to grok at first We could change the example (and maybe we should in light of 2?)\nI can appreciate the idea behind it but I don't think the names should imply they are different things, and are not the same thing. Wouldn't just changing to for the parameter and leaving the object name as is work?\nWe can use that as the parameter name; I like it better than . This still doesn't fully handle the user complaint though. I see two problems 1) is a really awkward variable name. Swapping to fixes this. 2) Given the example, its an easy bug for users to write instead of the intended . Not sure if we want to address this or ignore this. Changing the global object name seems to be the best way to address this.\nMaybe what really needs to be done is to change the example to something else, like maybe or something like that?\nIf we change the parameter we should change the example as well. Either to something unrelated and change the text as needed, or it would need to use as well. I think we are, in part, trying to fix the underlying issue of campers not fully understanding parameters and arguments. Which I'm not sure how or where to address. I think the code highlighter isn't helping either. Usually, const and arguments are colored differently from parameters and reassignable variables. As an example (I changed the loop to use const as well) !\nNot sure how I feel about the parameter name but it might work.\nI like the direction. How about Instructions Sometimes you need to iterate through all the keys within an object. You can use a </dfnloop to do this. The </dfnloop looks like: This code logs and , with each value on its own line.", "We defined the variable in the loop head and this variable was set to each of the object's keys on each iteration, resulting in each food's name being printed to the console. We've defined a function which accepts one argument, . Use a </dfnstatement inside this function to loop through the object and return the number of users whose online property is set to . An example of an object which could be passed to is shown below. Each user will have an property set to either or . Seed Code I think this way we use your better parameter name and we swap the example for something that doesn't lead the learner to the bug.\nI think it looks good. As an aside, if we are documenting how works we should show how to access the properties on the object (in the example). I know we have taught how to use variables with objects and making them bridge the gap might force the learner to think about it more. But it feels a little wrong to me to teach without actually showing how to use it.\nSmall tweak for that: Instructions Sometimes you need to iterate through all the keys within an object. You can use a </dfnloop to do this. The </dfnloop looks like: This code logs and , with each key-value pair on its own line. We defined the variable in the loop head and this variable was set to each of the object's keys on each iteration, resulting in each food's name being printed to the console. We've defined a function which accepts one argument, . Use a </dfnstatement inside this function to loop through the object and return the number of users whose online property is set to . An example of an object which could be passed to is shown below. Each user will have an property set to either or . Seed Code" ]
[]
<ins> name: 'Unhide Specific String' description: "Updates a specific string to be not hidden" runs: using: 'node12' main: './index.js' inputs: filename: description: 'name of file with specific string to hide' required: true string-content: description: 'text content of string to unhide' required: true </ins>
[ "The challenge title of challenge Use && for a More Concise Conditional is not translatable on Crowdin ! (the greyed out text is for not translatable strings) An other challenge where the title is translatable ! this is the link for crowdin file: markdown file for the challenge:\nmind taking a look?\nI have manually marked the string as translatable today. After our workflows run tomorrow, I will confirm the string is still translatable - if it is not, I will investigate further.\nReopen if still and issue.\nthis actually happened again with last update\nJust to add that this is also happening in pt-BR. The entry is blocked for translation. I suspect this has to do with the double ampersand.\nHello, we are a group of researchers developing machine learning techniques to locate issues suitable for newcomers, and our model consider this issue as likely a \"good first issue\". May we recommend you to label it as \"good first issue\" so newcomers know where to choose? Thank you!\nthanks but it is not - this needs to be done through Crowdin pipeline, will need to do it, again" ]
[]
## Translate the File <del> ![Image - Editor View](./images/crowdin/editor.png) </del> <ins> ![Image - Editor View](https://contribute.freecodecamp.org/images/crowdin/editor.png) </ins> Crowdin separates a document into translatable "strings", usually sentences. Each string is translated individually. Referring to the image above:
[ "! Our local images currently do not render in the translated documentation views. This is due to the use of a relative link, which breaks with the new path generated for i18n pages. A couple of potential fixes: Use an absolute link (<filename). This, IMHO, is the most effective. Have translators fix the link in the translation flow. Host the images through our CDN and fetch them.\nWe should use the absolute path.\nSounds good. I'll get a PR up shortly." ]
[]
const addCodeOne = i18next.t('forum-help.add-code-one'); const addCodeTwo = i18next.t('forum-help.add-code-two'); const addCodeThree = i18next.t('forum-help.add-code-three'); <del> const altTextMessage = `### ${whatsHappeningHeading}nn### ${camperCodeHeading}nn${warning}nn${tooLongOne}nn${tooLongTwo}nn${tooLongThree}nn```textn${addCodeOne}n${addCodeTwo}n${addCodeThree}n```nn${endingText}`; </del> <ins> const altTextMessage = `### ${whatsHappeningHeading}nn${camperCodeHeading}nn${warning}nn${tooLongOne}nn${tooLongTwo}nn${tooLongThree}nn```textn${addCodeOne}n${addCodeTwo}n${addCodeThree}n```nn${endingText}`; </ins> const titleText = window.encodeURIComponent( `${i18next.t(
[ "The help post now has this header: ! which is It should have only one set of hashtags.\nCould you clarify where you see this? I don't seem to have this issue on my end.\nI did not specify, sorry, it's for posts that have the following message" ]
[]
Fulfill the user stories and pass all the tests below to complete this project. Give it your own personal style. Happy Coding! <ins> **Note:** Be sure to add `<link rel="stylesheet" href="styles.css">` in your HTML to link your stylesheet and apply your CSS </ins> # --hints-- You should have a `main` element with an `id` of `main`
[ "With the new format, a lot of people are not linking their css files to the HTML document. It is coming up a lot on the forum. Especially for those that are going through the Legacy curriculum. I think we should add a message underneath the sample projects, to remember to link the CSS file. Proposed change: Remember to link your CSS file in the HTML document. <img width=\"460\" alt=\"Screen Shot 2022-05-14 at 8 57 10 AM\" src=\"https://user-\"\nI had trouble fixing , because I didn't link To I hope this will be implemented\nI think we should do this." ]
[]
import Link from '../../../components/helpers/Link'; import './challenge-title.css'; <ins> import GreenPass from '../../../assets/icons/GreenPass'; </ins> const propTypes = { children: PropTypes.string,
[ "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.\nWe need a check mark in the title or a badge or to indicate the same?\nThe 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.\nThat would be a nice way to handle it. Please go forth if you are interested in this?" ]
[]
"For example, if you wanted to make a text input field required, you can just add the word "required" within your <code>input</code> element use: <code>&#60;input type='text' required&#62;</code>" ], "tests": [ <del> "assert($('input').prop('required'), 'Your text field have the property of being required.')", "assert($('[placeholder]').length > 0, 'Your text field should have the placeholder text of "cat photo URL".')" </del> <ins> "assert($('input').prop('required'), 'Your text field should have the property of being required.')", "assert(new RegExp('cat photo URL').test($('input').prop('placeholder')), 'Your text field should have the placeholder text of "cat photo URL".')" </ins> ], "challengeSeed": [ "<link href='http://fonts.googleapis.com/css?family=Lobster' rel='stylesheet' type='text/css'>",
[ "Spelling error: The waypoint requirements say, \"You should have three li elements on within your ol element.\" I think \"within\" is the better choice here.", "Typo on the first test \"your text field have the property of being required\". Also, the second test passes even if the placeholder text field is empty.\nThanks for the report, the copy has been updated.", "This isn't exactly a bug, but in the description for the challenge, there is an image that shows how bootstrap lays out elements on a page. This image is way too small to see or read any of the text in the image, and there doesn't seem to be a good way to get a larger version of the image.\nThanks, we've updated the copy to have the image link to the specific section of the bootstrap website!", "One of the requirements are not fulfilled (Wrap your all of your checkboxes inside one div with the class \"row\".) even though the codes have fulfilled the requirement. Per checking my code 3 times, I know I have fulfilled the requirement. Kindly check and see if this is just an error on my part. Thank you.", "<link href='' rel='stylesheet' type='text/css'<styleh2 { font-family: Lobster, Monospace; } .thick-green-border { border-color: green; border-width: 10px; border-style: solid; border-radius: 50%; } </style<div class='row'<div class='col-xs-8'<h2 class='text-primary text-center'CatPhotoApp</h2</div<div class='col-xs-4'<a href='#'<img class='img-responsive thick-green-border' src=''/</a</div</div<br<img src='' class='img-responsive'<br<div class='row'<div class='col-xs-4'<button class='btn btn-block btn-primary'<i class='fa fa-thumbs-up'</iLike</button</div<div class='col-xs-4'<button class='btn btn-block btn-info'<i class='fa fa-info-circle'</iInfo</button</div<div class='col-xs-4'<button class='btn btn-block btn-danger'<i class='fa fa-trash'</iDelete</button</div</div<pThings cats love:</p<ul<licat nip</li<lilaser pointers</li<lilasagna</li</ul<pTop 3 things cats hate:</p<ol<liflea treatment</li<lithunder</li<liother cats</li</ol<form action=\"/submit-cat-photo\"<br<div class='row'<div class='col-xs-6'<label<input type='radio' name='indoor-outdoor'Indoor</label</div<div class='col-xs-6'<label<input type='radio' name='indoor-outdoor'Outdoor</label</div</div<div class=\"row\"<div class='col-xs-4'<label<input type='checkbox' name='personality'Loving</label</div<div class='col-xs-4'<label<input type='checkbox' name='personality'Lazy</label</div<div class='col-xs-4'<label<input type='checkbox' name='personality'Crazy</label</div</div<br<div class='col-xs-7'<input type='text' class='form-control' placeholder='cat photo URL' required</div<div class='col-xs-5'<button type='submit' class='btn btn-primary'<i class='fa fa-paper-plane'</iSubmit</button</div</form!", "That test has a typo, it should tell you to wrap your input field and button in the div (like it does in the instruction text), not the checkboxes. Also, if you wanna show your html, .\nAlright! That worked! Thank you very much! :) Should I close this issue now? Newb in Github here.\nThe \"bug\" is still present so you can leave it open. If you want to fix it yourself, you can open a pull request. If you look it seems like an easy fix, and you can use the little pencil button at the top to do it all right from within GitHub.\nI'm actually lost with Github. Tried opening a pull request but I really don't know where to go. I guess I ll study Github first?\nThanks for bringing this issue up. We've cleaned up the copy!" ]
[]
"cheerio": "~0.20.0", "classnames": "^2.1.2", "compression": "^1.6.0", <del> "connect-mongo": "~1.3.2", </del> <ins> "connect-mongo": "^1.3.2", </ins> "cookie-parser": "^1.4.0", "csurf": "^1.8.3", "debug": "^2.2.0",
[ "A caret symbol, needs to be . So the result should look like this: . Please review before opening a PR, thank you!\nHi there - can I take this one? I'm new to contributing to FCC and this issue seems like a great way to get everything set up and working properly to help out more in the future." ]
[]
<h2 className='black-text'>D3.js</h2> </Col> </Row> <ins> <hr /> </ins> <Spacer /> <ins> <h3> freeCodeCamp is a donor-supported tax-exempt 501(c)(3) nonprofit organization (United States Federal Tax Identification Number: 82-0779546) </h3> <p className='large-p'> Our mission: to help people learn to code for free. We accomplish this by creating thousands of videos, articles, and interactive coding lessons - all freely available to the public. We also have thousands of freeCodeCamp study groups around the world. </p> <p className='large-p'> Donations to freeCodeCamp go toward our education initiatives, and help pay for servers, services, and staff. You can{' '} <a className='large-p underlined-link' href='https://donate.freecodecamp.org/' rel='noopener noreferrer' target='_blank' > make a tax-deductible donation here </a> </p> .<Spacer /> </ins> <BigCallToAction /> <Spacer /> <Spacer />
[ "I can work on this. A little confused though, since it appears to be there already. Does the mission statement go here? Please provide instructions, thanks." ]
[]
End of preview.

No dataset card yet

Downloads last month
14