{"query_id": "q-en-freeCodeCamp-041cba1b7cd3d5f997ec0136904192b242243dd171b490fed76db494c2396a4b", "query": "

Cat Form

--fcc-editable-region--
--fcc-editable-region--
--fcc-editable-region-- ", "positive_passages": [{"docid": "doc-en-freeCodeCamp-b2069b3c57a9b071d733e1e6e2c4d046c2011dfe13ff248c0c859beb27109278", "text": "In RWB, the placement of the instructions interrupts the code and makes indentation unclear, especially for a beginner that may not know what to look for yet. I noticed several instances where putting longer, uninterrupted part of the code in the highlighted editor might help with clarity.

Cat Form

--fcc-editable-region--
--fcc-editable-region--
--fcc-editable-region-- ", "positive_passages": [{"docid": "doc-en-freeCodeCamp-b0cf46839763ada4c682cd2d75858172e09be4772a7b94059a0e810521c2ce6c", "text": "There may be instances where rules like that don't work out so well. Like for the first steps of the Cat Photo project, we may want to be more specific about where to add code - and on later steps or projects, more vague. So I don't know.\nI did bring this up, but we were on the fence with:\nYeah it seems like something that's more of a case-by-case basis than to have hard and fast rules for. My proposed \"general\" approach would be to encapsulate anything the instructions mention. So if the instructions say \"write a h2 below your h1\", the h1 should be within the editable region.\nTo try and get this issue resolved, I vote for these changes: step 21: change the hint to \"There should be an img element right after the closing tag.\" step 23: use op's suggestion step 50: use op's suggestion\nThank you for reporting this issue. An easy fix would be to scroll the editor so the instructions are always almost at the top of the \"page\". That way the eyes know where to go on each challenge. (right now it scrolls to the center) I am interested in knowing more about this: \" it takes me a while to find and re-focus on the editor.\" Are you having difficulty locating the instructions? do also look around for the tests and the submit button? More context is appreciated. We ultimately need to usability test this with people who have not seen the curriculum.\nHello, sorry for the late reply. After seeing this notification, I opened the curriculum on a random step to see if I could provide you with more information. I mostly forgot how the page was structured and my eyes just ran across the page in no specific order. \"Check your code\" was the first text I read, as it draws the most attention, and then \"\". I believe that would be very helpful! (I think it would also be nice if the navigation breadcrumbs were more subtle, and if the buttons like \"\", \"\" and \"preview\" looked more like toggle buttons \u2013 now they remind me of tabs but disconnected from their sections, and they also draw more attention than is perhaps needed?) Thank you for checking in on this!\nThank you for your feedback.", "commid": "freeCodeCamp_issue_44827", "tokennum": 478}], "negative_passages": []} {"query_id": "q-en-freeCodeCamp-06dc9d56140e7db7b7cc39cef142b808078e99dfe8d4f1c4cba723a952109ecd", "query": "// eslint-disable-next-line max-len it('Worker executor should successfully execute 3 tasks and use 1 worker', async () => { mockWorker(); const testWorker = createWorker('test', { concurrency: 1 }); const testWorker = createWorker('test', { maxWorkers: 1 }); const task1 = testWorker.execute('test1'); const task2 = testWorker.execute('test2');", "positive_passages": [{"docid": "doc-en-freeCodeCamp-bc7b9b8a758504b5c8e59c4a936a443badbcc26126dc45781f483889454d9f25", "text": "Describe the bug Sass pages with invalid syntax occasionally timeout To Reproduce Steps to reproduce the behavior: to in in the console (sometimes) Expected behavior The following should appear in the console: Since this is intermittent, here's a gif to demonstrate: ! Additional Context When the error appears it does so very quickly, so it is unlikely that this is due to a genuine timeout.\nHey Oliver, When I clicked on the link, I reset the code, and completed the challenge as it should be completed. I came across a error, and was unable to run the tests. However, after resetting the code, refreshing the page, and pasting in the code you provided (missing ), the error you mention appeared, but does not disappear. So, I suspect it has to do with the page first load, because I can get the error only if I: 1) reset the code 2) Duplicate the tab 3) Input the incorrect code (missing ) !\nI tried method but that didn't produce the bug. I am able to reliably reproduce the bug on Chromium & Firefox with the following steps: the page (new tab & refresh can both produce bug). delete & re-add the character from line 9, fast enough that the new state does not display in the console. step 2 on deleting the . If done correctly the message will display instead of an error, even though the console input is incorrect. approximately 3-5 seconds for the timeout message to appear. Note: it can also be reproduced where by in step 2 you end on re-adding the but it's harder to tell if the bug has happened. It must have something to do with the console state change and the output error check conflicting.\nI worked on this issue on my old computer that is very slow and on my main PC (with a dual boot). On my old computer I have the same result as regurlaly timeouts. On the new one to have this issue I have to paste 3 times the piece of code to reproduce it. But everytimes, this is a real timeout (5ms, I put 'new Date()' on the code).", "commid": "freeCodeCamp_issue_39432", "tokennum": 454}], "negative_passages": []} {"query_id": "q-en-freeCodeCamp-06dc9d56140e7db7b7cc39cef142b808078e99dfe8d4f1c4cba723a952109ecd", "query": "// eslint-disable-next-line max-len it('Worker executor should successfully execute 3 tasks and use 1 worker', async () => { mockWorker(); const testWorker = createWorker('test', { concurrency: 1 }); const testWorker = createWorker('test', { maxWorkers: 1 }); const task1 = testWorker.execute('test1'); const task2 = testWorker.execute('test2');", "positive_passages": [{"docid": "doc-en-freeCodeCamp-c8789507c66999cca207524f16d1c267e9bce8e16ee622494734330875dff426", "text": "We can upgrade the source code one \"execute-challenge-\" with this kind of stuff to have a best message, but still the problem : import i18next from 'i18next'; const mapStateToProps = createStructuredSelector({ currentTab: currentTabSelector", "positive_passages": [{"docid": "doc-en-freeCodeCamp-919ddc19acc4dba1018af106a645ad52a7f5124c05632006b0bfbd171296c80a", "text": "Describe the bug When you enter a challenge using a mobile device, the tabs below the main header are displayed with untranslated text To Reproduce Steps to reproduce the behavior (mobile device): to untranslated tabs below the main header Expected behavior Tabs text should be translated. Screenshots Spanish site ! Chinese site ! Desktop (please complete the following information): OS: [Windows 10] Browser: [chrome] Version: [88] Additional context Those strings are not available yet on the Crowdin platform.", "commid": "freeCodeCamp_issue_41027", "tokennum": 108}], "negative_passages": []} {"query_id": "q-en-freeCodeCamp-08313f954e1cb9b1600d869a27a10a625520fa826a719b61cdc1e4aa12fd2933", "query": "\"workshop-blog-page\": { \"title\": \"Build a Cat Blog Page\", \"intro\": [ \"In this workshop, you will learn how to build an HTML only blog page using semantic elements including the main, nav, article and footer elements.\" \"In this workshop, you will learn how to build an HTML only blog page using semantic elements including the main, nav, article and footer elements.\" ] }, \"szcd\": { \"title\": \"13\", \"intro\": [] },", "positive_passages": [{"docid": "doc-en-freeCodeCamp-1cda39b0cf17a9d6add07c9f522b747fcb98ca9bcc31d7cb2beda8ce32210224", "text": "Keywords in the following sentence should be wrapped within . Update the file with this change:\nThis issue is open to first-time code contributors to this repository. The file that you should be updating is linked in the original post. We typically do not assign issues. Instead, we accept the most quality contribution followed by the one that is made first. Please make sure you read our as well as our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Happy contributing.\nI can work on this.\nAre you still working on this?\nI submitted a pull request () that is waiting to be reviewed.\nI would like to work on this.\nI can work on this.", "commid": "freeCodeCamp_issue_56033", "tokennum": 159}], "negative_passages": []} {"query_id": "q-en-freeCodeCamp-0a690555f4574a9f26f49e467599491aa1dcf99310e2acc182b846eb1cb3daa2", "query": "
style=\"padding: 15px 0px; height: 1px;\" style=\"padding: 15px 0px;\" />
style=\"padding: 15px 0px; height: 1px;\" style=\"padding: 15px 0px;\" />
style=\"padding: 15px 0px; height: 1px;\" style=\"padding: 15px 0px;\" />
style=\"padding: 15px 0px; height: 1px;\" style=\"padding: 15px 0px;\" />
function ChallengeDescription({ description, instructions, section }) { return (
{instructions && (
)}
); class ChallengeDescription extends Component { componentDidMount() { // Just in case 'current' has not been created, though it should have been. if (this.instructionsRef.current) { Prism.highlightAllUnder(this.instructionsRef.current); } } constructor(props) { super(props); this.instructionsRef = React.createRef(); } render() { const { description, instructions, section } = this.props; return (
{instructions && (
)}
); } } ChallengeDescription.displayName = 'ChallengeDescription';", "positive_passages": [{"docid": "doc-en-freeCodeCamp-4ef68b7872a6418004b20f92f7629078a450b2fdecfc229c19da06d381b11a7e", "text": "Related to . Once that's done, the code blocks will be written in blocks of into ! while the same code on the guide looks like ! I think this change would make the code blocks easier to read, make the guide and challenges feel more like parts of a unified whole and fit better with the code editor aesthetic discussed in the . I'd be happy to work on this, if this is useful feature What do you think?\nYou should look into for this sort of thing. Goodluck. this is something we would probably be needing and using across Guide and Learn. So, I'll let you chime in and guide on this.", "commid": "freeCodeCamp_issue_35999", "tokennum": 132}], "negative_passages": []} {"query_id": "q-en-freeCodeCamp-0baa0e4b137b9770de232b01a51cd1926089ff8dd639c25320dfb6c2634bb48a", "query": "# --description-- Add an `else` block to handle the current song's position in the playlist. Add an `else` block to handle the song's current playback time. This allows you to resume the current song at the point where it was paused. Within the `else` block, set the `currentTime` property of the `audio` object to the value stored in `userData?.songCurrentTime`.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-7742d5b906bce0f1ffb52b837fddbeba046261289ad4db79db8432293b520a1d", "text": "please clarify the instructions for step 39 of JS Beta Build a Music Player Currently they consist of 2 sentences: \"Add an else block to handle the current song\u2019s position in the playlist. Within the else block, set the currentTime property of the audio object to the value stored in userData?.songCurrentTime.\" The first sentence doesn't seem to relate to the second. It is not clear how 'the current song's position in the playlist\" is affected by the actions requested of setting the audio object's currentTime? This makes me think that there's a mistake in the first sentence (or maybe I've misunderstood what it is trying to say so it needs more clarification) N/A N/A No response N/A No response\nI don't think it has anything to do with the playlist order. The only thing is used for is pause/play (it gets reset everywhere else). Maybe it can just be:\nMy thoughts was that the else block was designed to continue playing the song at the place you stopped it. The current song has been chosen and it's same id of the song. In the block, we're setting the time to zero. In the else block, we're setting it at the old time.\nFYI: I attempted to test pausing and restarting the song but it always restarted from the beginning.\nIn what step did you test it? If you go to the last step, the play/pause should work as intended (or to whatever step has it implemented). Pausing saves the audio element's current time to , and playing restores it back to the element's current time when is available.\nI see, I thought I would be able to pause and play something else then come back to the original selection and it would start from where I stopped (but I don't think the code was created for that).\nNah. It only resumes and plays back for the current song. Once you switch songs, it forgets where you left off on the old one.\nI would be fine adding something like \"This allows you to resume the current song at the point where it was paused.\"\nThis looks like something that can be fixed by \"first time\" code contributors to this repository. Here is the file that you should be looking at to work on a fix: Change: To: Please make sure you read , we prioritize contributors following the instructions in our guides.", "commid": "freeCodeCamp_issue_55389", "tokennum": 511}], "negative_passages": []} {"query_id": "q-en-freeCodeCamp-0baa0e4b137b9770de232b01a51cd1926089ff8dd639c25320dfb6c2634bb48a", "query": "# --description-- Add an `else` block to handle the current song's position in the playlist. Add an `else` block to handle the song's current playback time. This allows you to resume the current song at the point where it was paused. Within the `else` block, set the `currentTime` property of the `audio` object to the value stored in `userData?.songCurrentTime`.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-9fa85a30ec2ddbaf736927fb0466d9f3c273dd712b32d25b6c74e3e871d6c7ea", "text": "Join us in our chat room or the forum 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.", "commid": "freeCodeCamp_issue_55389", "tokennum": 54}], "negative_passages": []} {"query_id": "q-en-freeCodeCamp-0c80847d2949356f8ccf83e602d8d52a37cada5cf93ebd46f437838662b7c23e", "query": "# --description-- Set `monsterHealth` to `monsterHealth` minus the power of the player's current weapon. Remember you have the `currentWeapon` variable and the `power` property. Set `monsterHealth` to `monsterHealth` minus the power of the player's current weapon. Remember that you can access the power of the player's current weapon using `weapons[currentWeapon].power`. # --hints--", "positive_passages": [{"docid": "doc-en-freeCodeCamp-1db1238151c9c444f5bb1bca550446df338bdfda6f68358dc812c4955455ff09", "text": "The instruction are not clear, right now it says Edit: This is actually step 120 in the main branch Set monsterHealth to monsterHealth minus the power of the player's current weapon. Remember you have the currentWeapon which is not initialized variable and the power property on weapons array. No response Device: Laptop OS: macOS Browser: Chrome I think it should be more detail about what and where is currentWeapon, power property and how to access it like in previous.\nIt looks like currentWeapon is initalized with the value of 0 here Then it is updated over time throughout the project. I think for that second sentence it should be clear about syntax on how to access those values since beginners are still struggling with that. Being more explicitly will help with confusion on the forum posts. Let's go with this change.\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", "commid": "freeCodeCamp_issue_53604", "tokennum": 250}], "negative_passages": []} {"query_id": "q-en-freeCodeCamp-0d53c2b93b86e82ad6f8e058af05ae9dd2b24205ecf304b24fbc80c81667979e", "query": "const propTypes = { canFocusEditor: PropTypes.bool, children: PropTypes.any, editorRef: PropTypes.object, executeChallenge: PropTypes.func, innerRef: PropTypes.any, introPath: PropTypes.string,", "positive_passages": [{"docid": "doc-en-freeCodeCamp-8e4542f91b669ae2b68b983782c1892864cd02b7f65829c964b78000553cf827", "text": "Is your feature request related to a problem? Please describe. It currently can take a several key presses to navigate to the editor if it does not have focus. Describe the solution you'd like It should be possible to focus on the editor with a hotkey, for example 'e'. The issue where this was mostly discussed will be closed soon, but some thoughts about implementing this appeared there:", "commid": "freeCodeCamp_issue_37186", "tokennum": 80}], "negative_passages": []} {"query_id": "q-en-freeCodeCamp-0dd8983e161f6a720c148073ab26651d1ed8bfce643c4aa965b7baea20f5a2e5", "query": "# --description-- In programming, it is standard practice to prefix a variable with `is` or `has` to indicate that the variable is a boolean. ```js let isRunning = true; let hasCompleted = false; ``` Declare an `isError` variable and set it to `false`, but use `let` so you can reassign it later. # --hints--", "positive_passages": [{"docid": "doc-en-freeCodeCamp-77146a36414f6764fb892d5b7c3ef1ea7f02dbd1fa36e4987ba1b72bef152033", "text": "Throughout the curriculum, we often have campers name variables that represent booleans with the prefix of or which follow standard convention. But we never really explain that to them. I think that step 17 would be a good place do that. js let isRunning = true; let hasCompleted = false; ` 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\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", "commid": "freeCodeCamp_issue_53451", "tokennum": 203}], "negative_passages": []} {"query_id": "q-en-freeCodeCamp-0dd95176ba2a05fa5fad495cb6b0d0b0b05176982f6192e59fd7a02dbbf9f752", "query": "\"difficulty\": 0.13, \"challengeSeed\": \"125671865\", \"description\": [ \"jQuery is a powerful tool for manipulating HTML elements.\", \"It's a lot easier to use than JavaScript itself, so we'll learn it first.\", \"jQuery is a powerful library built in Javascript for manipulating HTML elements.\", \"It's a lot easier to use than Javascript itself, so we'll learn it first.\", \"It's also extremely popular with employers, so we're going to learn it well.\", \"Codecademy has an excellent free course that will walk us through the basics of jQuery.\", \"Go to http://www.codecademy.com/courses/web-beginner-en-bay3D/0/1 and complete the first section.\"", "positive_passages": [{"docid": "doc-en-freeCodeCamp-ef25c32cbb98365a4e2f9d068fd3426122246a4e306436235b64cf14102a3749", "text": "The copy here seems misleading especially for those coming from no knowledge of javascript. It looks as though jQuery isn't also Javascript. ! [] 1) jQuery is a powerful tool for manipulating HTML elements. 2) It's a lot easier to use than JavaScript itself, so we'll learn it first. 1) jQuery is a powerful javascript framework for manipulating HTML elements. 2) It's a lot easier to use than plain JavaScript itself, so we'll learn it first.", "commid": "freeCodeCamp_issue_433", "tokennum": 110}], "negative_passages": []} {"query_id": "q-en-freeCodeCamp-12ca481e404b14f25313dd9e063726060520b3e1899034b9641b592d3ba78613", "query": "Three circles of equal radius are placed inside a larger circle such that each pair of circles is tangent to one another and the inner circles do not overlap. There are four uncovered \"gaps\" which are to be filled iteratively with more tangent circles. \"a \"a At each iteration, a maximally sized circle is placed in each gap, which creates more gaps for the next iteration. After 3 iterations (pictured), there are 108 gaps and the fraction of the area which is not covered by circles is 0.06790342, rounded to eight decimal places.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-354848720ae081f596015b05abd7038ec76bf14e0a952b8cfd2f8b33a60969e9", "text": " Read these guidelines in English \u4e2d\u6587 \u0440\u0443\u0441\u0441\u043a\u0438\u0439 \u0639\u0631\u0628\u064a Espa\u00f1ol \u4e2d\u6587 Portugu\u00eas \u0420\u0443\u0441\u0441\u043a\u0438\u0439 Espa\u00f1ol \u0395\u03bb\u03bb\u03b7\u03bd\u03b9\u03ba\u03ac ", "positive_passages": [{"docid": "doc-en-freeCodeCamp-597619ec3990f3729f030bb875de9982a398b37e83f1798cb88c24a0dcfdab5b", "text": "Describe your problem and how to reproduce it: When you try to change contibution guidelines language - you'll see how the languages table's order is desynchronized and in several languages you cannot find new Greek language. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: Version 74.0.3729.169 (Official Build) (64-bit) Operating System: Windows 10 Pro 1809 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !", "commid": "freeCodeCamp_issue_36248", "tokennum": 131}], "negative_passages": []} {"query_id": "q-en-freeCodeCamp-88d870c03f4b510a9fc91c5497ccfc62a7abc9f06fca5425acd87443abb72029", "query": "\"tests\": [ \"assert.deepEqual(chunk(['a', 'b', 'c', 'd'], 2), [['a', 'b'], ['c', 'd']], 'should return chunked arrays');\", \"assert.deepEqual(chunk([0, 1, 2, 3, 4, 5], 3), [[0, 1, 2], [3, 4, 5]], 'should return chunked arrays');\", \"assert.deepEqual(chunk([0, 1, 2, 3, 4, 5], 4), [[0, 1, 2, 3], [4, 5]], 'should return cthe last chunk as remaining elements');\" \"assert.deepEqual(chunk([0, 1, 2, 3, 4, 5], 4), [[0, 1, 2, 3], [4, 5]], 'should return the last chunk as remaining elements');\" ] }, {", "positive_passages": [{"docid": "doc-en-freeCodeCamp-071939cb05f6b34b77d786ee7f089bab734ec0cac8146f18aaf9d6f23247c71d", "text": "' : '*/'; return `n${startComment} User Editable Region ${endComment}n`; switch (fileExtension) { case 'html': return 'nn'; case 'css': return 'n/* User Editable Region */n'; case 'py': return 'n# User Editable Regionn'; case 'js': return 'n// User Editable Regionn'; default: return 'nUser Editable Regionn'; } }; const filesWithEditableRegions = challengeFiles.map(file => {", "positive_passages": [{"docid": "doc-en-freeCodeCamp-ab4171f89237b65a805ab0b1456dbefa7421edb7f804f8cc4048975c2f408035", "text": "The creation of the help wanted forum post should be changed to use correct Python comments for files. Right now the posts are created with the wrong type of comment. !\nI want to work on this issue\nWe 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.", "commid": "freeCodeCamp_issue_52721", "tokennum": 109}], "negative_passages": []} {"query_id": "q-en-freeCodeCamp-c4a63f5c0589d274c8662a1d99c3ed967ce98172344086a02cc3c20927eded6d", "query": "`bookList` should not change and still equal `[\"The Hound of the Baskervilles\", \"On The Electrodynamics of Moving Bodies\", \"Philosophi\u00e6 Naturalis Principia Mathematica\", \"Disquisitiones Arithmeticae\"]`. ```js add(bookList, \"Test\"); assert( JSON.stringify(bookList) === JSON.stringify([", "positive_passages": [{"docid": "doc-en-freeCodeCamp-8a41e2e10894adee0d7bb500f3fde822b43910cac613afffbb86c8645be0d1b5", "text": "