{"query": "Hello, On Firefox 34 on a Windows 7 32-bit PC, the link to download Google Chrome on challenge 14 is not working.\nNice catch! Yes, I simply neglected to add the link. I've it to and re-seeded the database. It now works. Thanks!", "pos": ["{ \"node\": true /* * ENVIRONMENTS * ================= */ // Define globals exposed by Node.js. \"node\": true, /* * ENFORCING OPTIONS * ================= */ // Force all variable names to use either camelCase style or UPPER_CASE // with underscores. \"camelcase\": true, // Prohibit use of == and != in favor of === and !==. \"eqeqeq\": true, // Suppress warnings about == null comparisons. \"eqnull\": true, // Enforce tab width of 2 spaces. \"indent\": 2, // Prohibit use of a variable before it is defined. \"latedef\": true, // Require capitalized names for constructor functions. \"newcap\": true, // Enforce use of single quotation marks for strings. \"quotmark\": \"single\", // Prohibit trailing whitespace. \"trailing\": true, // Prohibit use of explicitly undeclared variables. \"undef\": true, // Warn when variables are defined but never used. \"unused\": true, // Enforce line length to 80 characters \"maxlen\": 80 }", " { /* * ENVIRONMENTS * ================= */ // Define globals exposed by modern browsers. \"browser\": true, // Define globals exposed by jQuery. \"jquery\": true, /* * ENFORCING OPTIONS * ================= */ // Force all variable names to use either camelCase style or UPPER_CASE // with underscores. \"camelcase\": true, // Prohibit use of == and != in favor of === and !==. \"eqeqeq\": true, // Suppress warnings about == null comparisons. \"eqnull\": true, // Enforce tab width of 2 spaces. \"indent\": 2, // Prohibit use of a variable before it is defined. \"latedef\": true, // Require capitalized names for constructor functions. \"newcap\": true, // Enforce use of single quotation marks for strings. \"quotmark\": \"single\", // Prohibit trailing whitespace. \"trailing\": true, // Prohibit use of explicitly undeclared variables. \"undef\": true, // Warn when variables are defined but never used. \"unused\": true, // Enforce line length to 80 characters \"maxlen\": 80, // Enforce placing 'use strict' at the top function scope \"strict\": true' } "], "neg": []} {"query": "Hello, On Firefox 34 on a Windows 7 32-bit PC, the link to download Google Chrome on challenge 14 is not working.\nNice catch! Yes, I simply neglected to add the link. I've it to and re-seeded the database. It now works. Thanks!", "pos": ["\"Smallest Common Multiple\": \"https://www.mathsisfun.com/least-common-multiple.html\", \"Permutations\": \"https://www.mathsisfun.com/combinatorics/combinations-permutations.html\", \"HTML Entities\": \"http://dev.w3.org/html5/html-author/charref\", \"Symmetric Difference\": \"https://www.youtube.com/watch?v=PxffSUQRkG4\", // ========= GLOBAL OBJECTS \"Global Array Object\" : \"https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array\",", "\"assert.deepEqual(sym([1, 1]), [1], 'should return an array of unique values');\" ], \"MDNlinks\": [ \"Array.reduce()\" \"Array.reduce()\", \"Symmetric Difference\" ], \"challengeType\": 5, \"nameCn\": \"\","], "neg": []} {"query": "Hello, On Firefox 34 on a Windows 7 32-bit PC, the link to download Google Chrome on challenge 14 is not working.\nNice catch! Yes, I simply neglected to add the link. I've it to and re-seeded the database. It now works. Thanks!", "pos": ["], \"tests\": [ \"assert(editor.match(/json.map/gi), 'The message box should have something in it.')\" ], ], \"challengeSeed\": [ \"fccss\", \" $(document).ready(function() {\",", "\"id\": \"bb000000000000000000004\", \"title\": \"Render Images from Data Sources\", \"description\": [ \"In the JSON that we receive from Free Code Camp's Cat Photo API, each object has an attribute called \"imageLink\".\", \"When we're looping through these objects, let's check whether an object attribute (key) is imageLink. If it is, instead of outputing the image link, let's render the image.\", \"In the JSON that we receive data from Free Code Camp's Cat Photo API.\", \"When we're looping through these strings, let's check whether they are links. If it is, instead of outputing the image link, let's render the image.\", \"Here's the code that does this:\", \"if(val.match(\"http\")) {\", \"  html = html + '<img src = \"' + val + '\">';\", \"}\" ], \"tests\": [ \"assert(editor.match(/val.match/gi), 'You should have accessed the imageLink of each cat object.')\" \"assert(editor.match(/val.match/gi), 'You should have checked whether the strings contain links.')\" ], \"challengeSeed\": [ \"fccss\","], "neg": []} {"query": "It flashes the form fields for a second and then is blank between \"Update your profile here:\" and \"Actions\" headings. Here's the console error: TypeError: Cannot read property 'toLowerCase' of undefined at at at at l.$eval () at l.$digest () at l.$apply () at l () at O () at () That looks like it's on the $() on line 49. The JSON from my /account/api doesn't have a user.profile.username key. Maybe it would be a simple fix of piping? () '';\nWhich method did you use to sign up for freecodecamp? It's an issue of your username not existing.\nSigned up with email.\nHow long ago did you sign up for FCC? On Mon Jan 12 2015 at 11:40:50 AM Justin Rogers wrote:\nAround December 8th. Am I the only document without a username in the db?", "pos": ["User Story #14: My legend should contain rect elements. User Story #15: The rect elements in the legend should use at least 4 different fill colors. User Story #16: I can mouse over an area and see a tooltip with a corresponding id=\"tooltip\" which displays more information about the area. User Story #16: My tooltip should have a data-year property that corresponds to the data-year of the active area. User Story #17: My tooltip should have a data-year property that corresponds to the data-year of the active area. Here is the dataset you will need to complete this project: https://raw.githubusercontent.com/freeCodeCamp/ProjectReferenceData/master/global-temperature.json You can build your project by forking this CodePen pen. Or you can use this CDN link to run the tests in any environment you like: https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js Once you're done, submit the URL to your working project with all its tests passing."], "neg": []} {"query": "If I try to view a FCC user by entering a URL () and the user isn't found, an error is displayed when I return to the FCC page (\"We couldn't find a Code Camper with that username.\"). The error bubble pushes down the \"Fork me on GitHub\" ribbon so that it isn't flush with the top navbar of the page. !\nThanks for bringing this to our attention, we'll get a fix in shortly. On Mon Jan 12 2015 at 9:58:52 AM Adam Hollett wrote:\nThe fix would involve moving the ribbon into and conditionally showing it on the view (otherwise we'd have to move the flash notification element down into each individual view). But we've decided to remove this element from our forthcoming simplified landing page.", "pos": ["# --description-- 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. 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. # --hints--"], "neg": []} {"query": "When opening in chrome, the \"update your profile\" section does not load any fields underneath. !\nDatabase merge resolved the issue.", "pos": ["\u0627\u0644\u0622\u0646 \u060c \u0643\u064a\u0641 \u062a\u062e\u0628\u0631 \u0643\u0645\u0628\u064a\u0648\u062a\u0631 \u0644\u0644\u0639\u062b\u0648\u0631 \u0639\u0644\u064a\u0647. \u0644\u0627 \u064a\u0645\u0643\u0646 \u0644\u0644\u0643\u0645\u0628\u064a\u0648\u062a\u0631 \u0627\u0644\u0646\u0638\u0631 \u0625\u0644\u0649 \u0623\u0643\u062b\u0631 \u0645\u0646 \u0627\u0644\u0642\u064a\u0645\u0629 \u0641\u064a \u0648\u0642\u062a \u0645\u062d\u062f\u062f \u0645\u0646 \u0627\u0644\u0648\u0642\u062a. \u0644\u0630\u0644\u0643 \u064a\u0623\u062e\u0630 \u0639\u0646\u0635\u0631 \u0648\u0627\u062d\u062f \u0645\u0646 \u0627\u0644\u0635\u0641\u064a\u0641 \u0648\u0627\u0644\u062a\u062d\u0642\u0642 \u0645\u0645\u0627 \u0625\u0630\u0627 \u0643\u0627\u0646 \u0647\u0648 \u0646\u0641\u0633\u0647 \u0645\u0627 \u0643\u0646\u062a \u0623\u0628\u062d\u062b \u0639\u0646\u0647. \u0644\u0627 \u064a\u0645\u0643\u0646 \u0644\u0644\u0643\u0645\u0628\u064a\u0648\u062a\u0631 \u0627\u0644\u0646\u0638\u0631 \u0625\u0644\u0649 \u0623\u0643\u062b\u0631 \u0645\u0646 \u0642\u064a\u0645\u0629 \u0641\u064a \u0646\u0641\u0633 \u0627\u0644\u0648\u0642\u062a. \u0644\u0630\u0644\u0643 \u064a\u0623\u062e\u0630 \u0639\u0646\u0635\u0631 \u0648\u0627\u062d\u062f \u0645\u0646 \u0627\u0644\u0635\u0641\u064a\u0641 \u0648\u0627\u0644\u062a\u062d\u0642\u0642 \u0645\u0645\u0627 \u0625\u0630\u0627 \u0643\u0627\u0646 \u0647\u0648 \u0646\u0641\u0633\u0647 \u0645\u0627 \u0643\u0646\u062a \u0623\u0628\u062d\u062b \u0639\u0646\u0647. ![\u0628\u062d\u062b \u062e\u0637\u064a 3](https://i.imgur.com/ZOSxeZD.jpg) \u0627\u0644\u0639\u0646\u0635\u0631 \u0627\u0644\u0623\u0648\u0644 \u0644\u0645 \u064a\u062a\u0637\u0627\u0628\u0642. \u0644\u0630\u0644\u0643 \u0627\u0646\u062a\u0642\u0644 \u0625\u0644\u0649 \u0627\u0644\u0645\u0631\u062d\u0644\u0629 \u0627\u0644\u062a\u0627\u0644\u064a\u0629. \u0627\u0644\u0648\u0642\u062a ![\u0628\u062d\u062b \u062e\u0637\u064a 4](https://i.imgur.com/SwKsPxD.jpg) \u0648\u0645\u0627 \u0625\u0644\u0649 \u0630\u0644\u0643 \u0648\u0647\u0644\u0645 \u062c\u0631\u0627\u2026", "#### \u0645\u0648\u0627\u0631\u062f \u0622\u062e\u0631\u0649 [\u0628\u062d\u062b \u062e\u0637\u064a - CS50](https://www.youtube.com/watch?v=vZWfKBdSgXI) No newline at end of file [\u0628\u062d\u062b \u062e\u0637\u064a - CS50](https://www.youtube.com/watch?v=vZWfKBdSgXI) "], "neg": []} {"query": "When opening in chrome, the \"update your profile\" section does not load any fields underneath. !\nDatabase merge resolved the issue.", "pos": ["```javascript if (process.env.VAR_NAME === \"allCaps\") { resonse = \"Hello World\".toUpperCase(); response = \"Hello World\".toUpperCase(); } else { response = \"Hello World\"; }"], "neg": []} {"query": "Last paragraph - 'persevere' is spelled incorrectly as 'perservere' !\nGood catch, thanks! I've gone ahead and committed a fix correcting the typo. In the future, if you notice something small like this you can actually find the file in our repository (in this case it was in ) click the little icon in the top right of the window that looks like a pencil, and fix it yourself. Then just click on commit changes and submit a pull request.\nThanks Nathan I did fork the repo and tried to submit a pull request, but could not figure out how. Will save that for another day. Curious question (because I am interested in general in business models): How will freecodecamp make money? Or is it just pure open source all the way through to the business model? At first I thought perhaps the non profits were being charged something. Darren\nYou will have to ask Quincy that question, I don't really feel at liberty sharing the planning details. On Wed Jan 14 2015 at 10:58:23 AM Darren Burgess wrote:\nHi Darren, you can read about our plans here:", "pos": ["\u0648\u0647\u064a \u0645\u0642\u0633\u0645\u0629 \u0625\u0644\u0649 \u0627\u0644\u0641\u0626\u0627\u062a \u0627\u0644\u062a\u0627\u0644\u064a\u0629: * \u0627\u0644\u0623\u0639\u062f\u0627\u062f \u0627\u0644\u0635\u062d\u064a\u062d\u0629 * \u0623\u0631\u0642\u0627\u0645 \u0627\u0644\u0646\u0642\u0637\u0629 \u0627\u0644\u0639\u0627\u0626\u0645\u0629 * \u0627\u0644\u0634\u062e\u0635\u064a\u0627\u062a * \u0627\u0643\u062a\u0628 \u0645\u0646\u0637\u0642\u064a * \u0627\u0644\u0627\u0639\u062f\u0627\u062f \u0627\u0644\u0639\u0634\u0631\u064a\u0629 * \u0627\u0644\u0631\u0645\u0648\u0632 * \u0627\u0644\u0642\u064a\u0645 \u0627\u0644\u0645\u0646\u0637\u0642\u064a\u0629 \u062a\u0641\u0627\u0635\u064a\u0644 \u0643\u0644 \u0646\u0648\u0639 \u0645\u0646 \u0623\u0646\u0648\u0627\u0639 \u0627\u0644\u0628\u064a\u0627\u0646\u0627\u062a \u0645\u0630\u0643\u0648\u0631\u0629 \u0623\u062f\u0646\u0627\u0647: ## \u0627\u0644\u0623\u0639\u062f\u0627\u062f \u0627\u0644\u0635\u062d\u064a\u062d\u0629: \u0647\u0630\u0647 \u0647\u064a \u0645\u0646 \u0623\u0631\u0628\u0639\u0629 \u0623\u0646\u0648\u0627\u0639: `byte` \u060c `short` \u060c `int` \u060c `long` . \u0645\u0646 \u0627\u0644\u0645\u0647\u0645 \u0645\u0644\u0627\u062d\u0638\u0629 \u0623\u0646 \u0647\u0630\u0647 \u0627\u0644\u0642\u064a\u0645 \u0645\u0648\u062c\u0628\u0629 \u0648\u0633\u0627\u0644\u0628\u0629. \u064a\u062a\u0645 \u062a\u062e\u0632\u064a\u0646 \u0627\u0644\u0623\u0639\u062f\u0627\u062f \u0627\u0644\u0635\u062d\u064a\u062d\u0629 \u0641\u064a \u062c\u0647\u0627\u0632 \u0627\u0644\u0643\u0645\u0628\u064a\u0648\u062a\u0631 \u0628\u0627\u0633\u062a\u062e\u062f\u0627\u0645 [\u0645\u0643\u0645\u0644 2](http://www.ele.uri.edu/courses/ele447/proj_pages/divid/twos.html) . \u0648\u064a\u062a\u0643\u0648\u0646 \u0645\u0646 \u0642\u064a\u0645 \u0633\u0644\u0628\u064a\u0629 \u0648\u0625\u064a\u062c\u0627\u0628\u064a\u0629 \u0648\u0644\u0643\u0646 \u0628\u0635\u064a\u063a \u0645\u062e\u062a\u0644\u0641\u0629 \u0645\u062b\u0644 `(-1 to -128)` \u0623\u0648 `(0 to +127)` . \u064a\u0645\u0643\u0646 \u0623\u0646 \u064a\u062d\u062a\u0648\u0649 \u0639\u062f\u062f \u0635\u062d\u064a\u062d \u063a\u064a\u0631 \u0645\u0648\u0642\u0639\u0629 \u0639\u0644\u0649 \u0642\u064a\u0645\u0629 \u0645\u0648\u062c\u0628\u0629 \u0623\u0643\u0628\u0631 \u060c \u0648\u0644\u0627 \u062a\u0648\u062c\u062f \u0642\u064a\u0645\u0629 \u0633\u0627\u0644\u0628\u0629 \u0645\u062b\u0644 `(0 to 255)` . \u0639\u0644\u0649 \u0639\u0643\u0633 C ++ \u0644\u0627 \u064a\u0648\u062c\u062f \u0639\u062f\u062f \u0635\u062d\u064a\u062d \u063a\u064a\u0631 \u0645\u0648\u0642\u0639\u0629 \u0641\u064a Java. \u0647\u0630\u0647 \u0647\u064a \u0645\u0646 \u0623\u0631\u0628\u0639\u0629 \u0623\u0646\u0648\u0627\u0639: `byte` \u060c `short` \u060c `int` \u060c `long` . \u0645\u0646 \u0627\u0644\u0645\u0647\u0645 \u0645\u0644\u0627\u062d\u0638\u0629 \u0623\u0646 \u0647\u0630\u0647 \u0627\u0644\u0642\u064a\u0645 \u0645\u0648\u062c\u0628\u0629 \u0648\u0633\u0627\u0644\u0628\u0629. \u064a\u062a\u0645 \u062a\u062e\u0632\u064a\u0646 \u0627\u0644\u0623\u0639\u062f\u0627\u062f \u0627\u0644\u0635\u062d\u064a\u062d\u0629 \u0641\u064a \u062c\u0647\u0627\u0632 \u0627\u0644\u0643\u0645\u0628\u064a\u0648\u062a\u0631 \u0628\u0627\u0633\u062a\u062e\u062f\u0627\u0645 [\u0645\u0643\u0645\u0644 2](http://www.ele.uri.edu/courses/ele447/proj_pages/divid/twos.html) . \u0648\u064a\u062a\u0643\u0648\u0646 \u0645\u0646 \u0642\u064a\u0645 \u0633\u0627\u0644\u0628\u0629 \u0648\u0645\u0648\u062c\u0628\u0629 \u0648\u0644\u0643\u0646 \u0628\u0635\u064a\u063a \u0645\u062e\u062a\u0644\u0641\u0629 \u0645\u062b\u0644 `(-1 to -128)` \u0623\u0648 `(0 to +127)` . \u064a\u0645\u0643\u0646 \u0623\u0646 \u064a\u062d\u062a\u0648\u0649 \u0639\u062f\u062f \u0635\u062d\u064a\u062d \u063a\u064a\u0631 \u0645\u0648\u0642\u0639\u0629 \u0639\u0644\u0649 \u0642\u064a\u0645\u0629 \u0645\u0648\u062c\u0628\u0629 \u0623\u0643\u0628\u0631 \u060c \u0648\u0644\u0627 \u062a\u0648\u062c\u062f \u0642\u064a\u0645\u0629 \u0633\u0627\u0644\u0628\u0629 \u0645\u062b\u0644 `(0 to 255)` . \u0639\u0644\u0649 \u0639\u0643\u0633 C ++ \u0644\u0627 \u064a\u0648\u062c\u062f \u0639\u062f\u062f \u0635\u062d\u064a\u062d \u063a\u064a\u0631 \u0645\u0648\u0642\u0639\u0629 \u0641\u064a Java. ### \u0628\u0627\u064a\u062a: ### \u0628\u0627\u064a\u062a (byte): \u0646\u0648\u0639 \u0627\u0644\u0628\u064a\u0627\u0646\u0627\u062a \u0628\u0627\u064a\u062a \u0647\u0648 \u0639\u062f\u062f \u0635\u062d\u064a\u062d \u0645\u0643\u0645\u0644 8 \u0628\u062a \u0645\u0648\u0642\u0639\u0629 \u0627\u062b\u0646\u064a\u0646. `Wrapper Class: Byte `Wrapper Class (\u0627\u0644\u0641\u0626\u0629): Byte Minimum value: -128 (-2^7) Minimum value (\u0627\u0644\u0642\u064a\u0645\u0629 \u0627\u0644\u0627\u0635\u063a\u0631): -128 (-2^7) Maximum value: 127 (2^7 -1) Maximum value (\u0627\u0644\u0642\u064a\u0645\u0629 \u0627\u0644\u0642\u0635\u0648\u0649): 127 (2^7 -1) Default value: 0 Default value (\u0627\u0644\u0642\u064a\u0645\u0629 \u0627\u0644\u0627\u0641\u062a\u0631\u0627\u0636\u064a\u0629): 0 Example: byte a = 10 , byte b = -50; Example (\u0645\u062b\u0627\u0644): byte a = 10 , byte b = -50; ` ### \u0642\u0635\u064a\u0631\u0629: ### \u0642\u0635\u064a\u0631\u0629 (short): \u0646\u0648\u0639 \u0627\u0644\u0628\u064a\u0627\u0646\u0627\u062a \u0627\u0644\u0642\u0635\u064a\u0631 \u0647\u0648 \u0639\u062f\u062f \u0635\u062d\u064a\u062d \u0645\u0643\u0645\u0644 \u0645\u0646 16 \u0628\u062a \u0645\u0648\u0642\u0639\u0629 \u0627\u062b\u0646\u064a\u0646. `Wrapper Class: Short `Wrapper Class (\u0627\u0644\u0641\u0626\u0629): Short Minimum value: -32,768 (-2^15) Minimum value (\u0627\u0644\u0642\u064a\u0645\u0629 \u0627\u0644\u0635\u063a\u0631\u0649): -32,768 (-2^15) Maximum value: 32,767 (2^15 -1) Maximum value (\u0627\u0644\u0642\u064a\u0645\u0629 \u0627\u0644\u0642\u0635\u0648\u0649): 32,767 (2^15 -1) Default value: 0. Default value (\u0627\u0644\u0642\u064a\u0645\u0629 \u0627\u0644\u0627\u0641\u062a\u0631\u0627\u0636\u064a\u0629): 0. Example: short s = 10, short r = -1000; Example (\u0645\u062b\u0627\u0644): short s = 10, short r = -1000; ` ### \u0627\u0644\u0628\u0627\u062d\u062b: ### \u0627\u0644\u0639\u062f\u062f \u0627\u0644\u0635\u062d\u064a\u062d (integer): \u0646\u0648\u0639 \u0627\u0644\u0628\u064a\u0627\u0646\u0627\u062a IN \u0647\u0648 \u0639\u062f\u062f \u0635\u062d\u064a\u062d \u0645\u0643\u0645\u0644 32 \u0628\u062a \u0645\u0648\u0642\u0639\u0629 \u0627\u062b\u0646\u064a\u0646. \u064a\u062a\u0645 \u0627\u0633\u062a\u062e\u062f\u0627\u0645\u0647 \u0628\u0634\u0643\u0644 \u0639\u0627\u0645 \u0643\u0646\u0648\u0639 \u0628\u064a\u0627\u0646\u0627\u062a \u0627\u0641\u062a\u0631\u0627\u0636\u064a \u0644\u0644\u0642\u064a\u0645 \u0627\u0644\u0645\u062a\u0643\u0627\u0645\u0644\u0629 \u0625\u0644\u0627 \u0625\u0630\u0627 \u0643\u0627\u0646 \u0647\u0646\u0627\u0643 \u0642\u0644\u0642 \u062d\u0648\u0644 \u0627\u0644\u0630\u0627\u0643\u0631\u0629. `Wrapper Class: Integer `Wrapper Class (\u0627\u0644\u0641\u0626\u0629): Integer Minimum value: (-2^31) Minimum value (\u0627\u0644\u0642\u064a\u0645\u0629 \u0627\u0644\u0635\u063a\u0631\u0649): (-2^31) Maximum value: (2^31 -1) Maximum value (\u0627\u0644\u0642\u064a\u0645\u0629 \u0627\u0644\u0642\u0635\u0648\u0649): (2^31 -1) The default value: 0. The default value (\u0627\u0644\u0642\u064a\u0645\u0629 \u0627\u0644\u0627\u0641\u062a\u0631\u0627\u0636\u064a\u0629): 0. Example: int a = 50000, int b = -20 Example (\u0645\u062b\u0627\u0644): int a = 50000, int b = -20 ` ### \u0637\u0648\u064a\u0644: ### \u0637\u0648\u064a\u0644 (long): \u0646\u0648\u0639 \u0628\u064a\u0627\u0646\u0627\u062a \u0637\u0648\u064a\u0644 \u0647\u0648 \u0639\u062f\u062f \u0635\u062d\u064a\u062d \u0645\u0643\u0645\u0644 64 \u0628\u062a \u0645\u0648\u0642\u0639\u0629 \u0627\u062b\u0646\u064a\u0646. `Wrapper Class: Long `Wrapper Class (\u0627\u0644\u0641\u0626\u0629): Long Minimum value: (-2^63) Minimum value (\u0627\u0644\u0642\u064a\u0645\u0629 \u0627\u0644\u0635\u063a\u0631\u0649): (-2^63) Maximum value: (2^63 -1) Maximum value (\u0627\u0644\u0642\u064a\u0645\u0629 \u0627\u0644\u0642\u0635\u0648\u0649): (2^63 -1) Default value: 0L. Default value (\u0627\u0644\u0642\u064a\u0645\u0629 \u0627\u0644\u0627\u0641\u062a\u0631\u0627\u0636\u064a\u0629): 0L. Example: long a = 100000L, long b = -600000L; Example (\u0645\u062b\u0627\u0644): long a = 100000L, long b = -600000L; By default all integer type variable is \"int\". So long num=600851475143 will give an error. But it can be specified as long by appending the suffix L (or l) ` ## \u0646\u0642\u0637\u0629 \u0639\u0627\u0626\u0645\u0629: ## \u0627\u0639\u062f\u0627\u062f \u0639\u0634\u0631\u064a\u0629: \u062a\u0633\u0645\u0649 \u0647\u0630\u0647 \u0623\u064a\u0636\u064b\u0627 \u0623\u0631\u0642\u0627\u0645\u064b\u0627 \u062d\u0642\u064a\u0642\u064a\u0629 \u0648\u062a\u0633\u062a\u062e\u062f\u0645 \u0644\u0644\u062a\u0639\u0628\u064a\u0631\u0627\u062a \u0627\u0644\u062a\u064a \u062a\u062a\u0636\u0645\u0646 \u062f\u0642\u0629 \u0643\u0633\u0631\u064a\u0629. \u0647\u0630\u0647 \u0645\u0646 \u0646\u0648\u0639\u064a\u0646: `float` \u060c `double` . \u064a\u062a\u0645 \u062a\u062c\u0646\u0628 Float \u0641\u0639\u0644\u064a\u064b\u0627 \u0641\u064a \u062d\u0627\u0644\u0629 \u0627\u0644\u0628\u064a\u0627\u0646\u0627\u062a \u0627\u0644\u062f\u0642\u064a\u0642\u0629 \u0645\u062b\u0644 \u0628\u064a\u0627\u0646\u0627\u062a \u0627\u0644\u0639\u0645\u0644\u0627\u062a \u0623\u0648 \u0627\u0644\u0623\u0628\u062d\u0627\u062b. ### \u062a\u0637\u0641\u0648: ### \u062a\u0637\u0641\u0648 (float): \u0646\u0648\u0639 \u0628\u064a\u0627\u0646\u0627\u062a \u0639\u0627\u0626\u0645 \u0639\u0628\u0627\u0631\u0629 \u0639\u0646 [\u0646\u0642\u0637\u0629 \u0639\u0627\u0626\u0645\u0629 IEEE 754](http://steve.hollasch.net/cgindex/coding/ieeefloat.html) \u0630\u0627\u062a \u062f\u0642\u0629 \u0648\u0627\u062d\u062f\u0629 32 \u0628\u062a. `Wrapper Class: Float `Wrapper Class (\u0627\u0644\u0641\u0626\u0629): Float Float is mainly used to save memory in large arrays of floating point numbers. \u0627\u0633\u0627\u0633\u0627 \u062a\u0633\u062a\u062e\u062f\u0645 \u0644\u062d\u0641\u0638 \u0627\u0644\u0630\u0627\u0643\u0631\u0629 \u0641\u064a \u0627\u0644\u0645\u0635\u0641\u0648\u0641\u0627\u062a \u0627\u0644\u0645\u0643\u0648\u0646\u0629 \u0645\u0646 \u0627\u0644\u0627\u0631\u0642\u0627\u0645 \u0627\u0644\u0639\u0634\u0631\u064a\u0629 \u0630\u0627\u062a \u062f\u0642\u0629 \u0648\u0627\u062d\u062f\u0629(float) Default value: 0.0f. Default value (\u0627\u0644\u0642\u064a\u0645\u0629 \u0627\u0644\u0627\u0641\u062a\u0631\u0627\u0636\u064a\u0629): 0.0f. Example: float f1 = 24.5f; Example (\u0645\u062b\u0627\u0644): float f1 = 24.5f; The default data type of floating-point number is double. So float f = 24.5 will introduce an error. \u0646\u0648\u0639 \u0627\u0644\u0642\u064a\u0645\u0629 \u0627\u0644\u0627\u0641\u062a\u0631\u0627\u0636\u064a\u0629 \u0644\u0644\u0627\u0631\u0642\u0627\u0645 \u0627\u0644\u0639\u0634\u0631\u064a\u0629 \u0630\u0627\u062a \u062f\u0642\u0629 \u0648\u0627\u062d\u062f\u0629 \u0647\u0648 \u0645\u0632\u062f\u0648\u062c. \u0645\u062b\u0627\u0644: float f = 24.5 \u0633\u062a\u0638\u0647\u0631 \u062e\u0637\u0627 \u0644\u0644\u0645\u0633\u062a\u062e\u062f\u0645 However, we can append the suffix F (or f) to designate the data type as float. \u0644\u0643\u0646, \u0628\u0627\u0645\u0643\u0627\u0646\u0646\u0627 \u0627\u0633\u062a\u062e\u062f\u0627\u0645 F(or f) \u0644\u062a\u0639\u064a\u064a\u0646 \u062a\u0648\u0639 \u0627\u0644\u0628\u064a\u0627\u0646\u0627\u062a \u0643\u0631\u0642\u0645 \u0639\u0634\u0631\u064a \u0630\u0627\u062a \u062f\u0642\u0629 \u0648\u0627\u062d\u062f\u0629 (float) The default data type of floating-point number is double. So float f = 24.5 will introduce an error. However, we can append the suffix F (or f) to designate the data type as float. ` ### \u0645\u0632\u062f\u0648\u062c: ### \u0645\u0632\u062f\u0648\u062c (double): \u0646\u0648\u0639 \u0628\u064a\u0627\u0646\u0627\u062a \u0645\u0632\u062f\u0648\u062c \u0647\u0648 [\u0646\u0642\u0637\u0629 \u0639\u0627\u0626\u0645 IEEE 754](http://steve.hollasch.net/cgindex/coding/ieeefloat.html) \u0645\u0632\u062f\u0648\u062c\u0629 \u0627\u0644\u062f\u0642\u0629 64 \u0628\u062a. \u0639\u0627\u062f\u0629\u064b \u0645\u0627 \u064a\u0643\u0648\u0646 \u0646\u0648\u0639 \u0627\u0644\u0628\u064a\u0627\u0646\u0627\u062a \u0647\u0630\u0627 \u0647\u0648 \u0627\u0644\u062e\u064a\u0627\u0631 \u0627\u0644\u0627\u0641\u062a\u0631\u0627\u0636\u064a. \u064a\u062c\u0628 \u0639\u062f\u0645 \u0627\u0633\u062a\u062e\u062f\u0627\u0645 \u0646\u0648\u0639 \u0627\u0644\u0628\u064a\u0627\u0646\u0627\u062a \u0647\u0630\u0627 \u0645\u0637\u0644\u0642\u064b\u0627 \u0644\u0644\u0642\u064a\u0645 \u0627\u0644\u062f\u0642\u064a\u0642\u0629 \u060c \u0645\u062b\u0644 \u0627\u0644\u0639\u0645\u0644\u0629.", "``` 10198442 ``` No newline at end of file ``` "], "neg": []} {"query": "None of the FCC pages (logged in or out) has a footer bar or footer menu with relevant links for users to follow. Adding a footer bar with links to more info about FCC: Blog link (currently no link anywhere), Creative Commons/ Open Source License/ Copyright, Github and Social Media links, Privacy Policy, Forum and Chat links Not only will this make exploring FCC much easier but will be great for SEO as well.\nI agree but only on the logged in page, we don't want any distractions from our conversions.\nGood point\nClosing this as the footer is now integrated, and all links can be found either there or in the header. Please open a new issue to suggest changes to those elements.", "pos": ["## Byzantine Fault Tolerance Imagine the scenario where there is an empire and there are three generals with their respective armies at different positions. All of them must attack in order to win the fight or they can choose to retreat. Their only means of communications are through pigeon posts. But there is a problem, the generals can't trust each other or ensure that the message has not been corrupted along the way. How do they solve this problem? Blockchain essentially does so by listening to information broadcasted by other people, reaching to a consensus of which information is deemed true. As such, this model asssumes that the amount of \"traitors\" do not exceed more than 1/3 of the entire network. ## Modern Use Cases of Blockchain - Asset Tokenization : Using blockchain technology, previously illiquid assets can now be converted into its tokenized form and cheaply and efficiently fractionalized, traded and settled on chain (rather than go through the lengthy process of clearing and settlement process through third parties like clearing houses) - Supply Chain Management : Blockchains allow multiple parties to access a database to act as the single source of truth. Recorded transactions are immutable, are append only and provide a time stamped audit trail. - Digital Identity : A self sovereign ID can be used to verify identity without needing an individual to produce numerous documents and paperwork each time they need their identity verified. This could be done with a single key that can be matched against an immutable ledger. The digital ID can also collect other online information about a user\u2019s identity like social security information, medical records and social media credentials and have that stored securely on the blockchain. - Energy Market : Blockchain technology can enable the smart metering of electricity generated through an individual\u2019s solar panels to be recorded, traded and settled on a ledger. - Healthcare : Using blockchain technology to record patient information on a distributed ledger can allow different stakeholders conditional access to a single source of truth where each interaction with a patient\u2019s health data can be recorded on a ledger as a transaction with a time stamped audit trail. ## Issues Whilst blockchain technology is undoubtedly elegant, there are several problems that its presence brings, the main one being use my malicious third parties. Due to the extremely secure nature of blockchain, its technologies are often used by criminals to carry out transactions, which are impossible for governments to track."], "neg": []} {"query": "originally reported: Each time I log in with Twitter, I still have to authorize the app to allow FCC access to my profile.\nPR resolves this issue successfully.\nTwitter API documentation for GET oauth/authenticate distinguishes the difference between authorize and authenticate in paragraph four .\nI believe this is still an issue. I've already authorized FCC to interact with my twitter account, yet every time I attempt sign-in with twitter it still wants permission to authorize account interaction. Rather than just logging in.\nAngelica, The pull request hasn't been merged into the main branch and pushed live to the servers. As soon as the team has a chance to review my changes we'll get it going live for you to enjoy the ease of use! On Sat Jan 17 2015 at 6:07:48 PM Angelica Ferdinand < :", "pos": ["The positive aspect is that you don't have to limit your moodboard to images in magazine. The negative aspect is that it might be hard to find the right images, since you have all internet to search from. The places to start look for images and ideas: - google. Goole Images can be chosen according to colour, shape or form, so if you can search it, then it is possible that you find it. - google. Google Images can be chosen according to colour, shape or form, so if you can search it, then it is possible that you find it. - Pinterest. Same as for google, yet different. - free images. Such as Pixabay, Pexels, or free images sites, you can find tons of inspiration already in one picture. - go outside with a camera. There might be the exact item for your moodboard waiting for you to take that picture."], "neg": []} {"query": "I've had to reenter many of the challenges after pressing 'Take me to the next challenge.' Also, on several of the challenges the test console output show errors (e.g. Unexpected Token) with no output concerning the test, but it still passes. I'll get a screenshot shot the next time it happens.\nThanks for the report. This is caused by the user not entering a test correctly. We'll work on hardening it up.\nI don't believe I changed test text provided, but I could be wrong. But now that you mention that, if I change the test text I get the 'is not defined' error. It still gives the 'Take me to my next challenge' modal, but it will bring me back to the same challenge. If I do the same thing once more, it brings me to the next challenge.\nBoth of these issues have been addressed in pull request .", "pos": ["To learn more about installation, see the [Installation Appendix](./src/articles/typescript/appendix-installation/index.md). In case you need just a type checker and don't want to compile your programm, read about Flux. In case you need just a type checker and don't want to compile your program, read about Flux. - Quick Start - Documentation"], "neg": []} {"query": "In the following test-case expected ['TWENTY', 80.00], but only ['TWENTY', 60.00] available. I'm going to fix it and make a pull request.", "pos": ["\"expect(drawer(19.50, 20.00, [['PENNY', 0.01], ['NICKEL', 0], ['DIME', 0], ['QUARTER', 0], ['ONE', 0], ['FIVE', 0], ['TEN', 0], ['TWENTY', 0], ['ONE HUNDRED', 0]])).to.be.a('string');\", \"expect(drawer(19.50, 20.00, [['PENNY', 0.50], ['NICKEL', 0], ['DIME', 0], ['QUARTER', 0], ['ONE', 0], ['FIVE', 0], ['TEN', 0], ['TWENTY', 0], ['ONE HUNDRED', 0]])).to.be.a('string');\", \"assert.deepEqual(drawer(19.50, 20.00, [['PENNY', 1.01], ['NICKEL', 2.05], ['DIME', 3.10], ['QUARTER', 4.25], ['ONE', 90.00], ['FIVE', 55.00], ['TEN', 20.00], ['TWENTY', 60.00], ['ONE HUNDRED', 100.00]]), [['QUARTER', 0.50]], 'return correct change');\", \"assert.deepEqual(drawer(3.26, 100.00, [['PENNY', 1.01], ['NICKEL', 2.05], ['DIME', 3.10], ['QUARTER', 4.25], ['ONE', 90.00], ['FIVE', 55.00], ['TEN', 20.00], ['TWENTY', 60.00], ['ONE HUNDRED', 100.00]]), [['TWENTY', 80.00], ['TEN', 10.00], ['FIVE', 5], ['ONE', 1], ['QUARTER', 0.50], ['DIME', 0.20], ['PENNY', 0.04] ], 'return correct change with multiple coins and bills');\", \"assert.deepEqual(drawer(3.26, 100.00, [['PENNY', 1.01], ['NICKEL', 2.05], ['DIME', 3.10], ['QUARTER', 4.25], ['ONE', 90.00], ['FIVE', 55.00], ['TEN', 20.00], ['TWENTY', 60.00], ['ONE HUNDRED', 100.00]]), [['TWENTY', 60.00], ['TEN', 20.00], ['FIVE', 15], ['ONE', 1], ['QUARTER', 0.50], ['DIME', 0.20], ['PENNY', 0.04] ], 'return correct change with multiple coins and bills');\", \"assert.deepEqual(drawer(19.50, 20.00, [['PENNY', 0.01], ['NICKEL', 0], ['DIME', 0], ['QUARTER', 0], ['ONE', 0], ['FIVE', 0], ['TEN', 0], ['TWENTY', 0], ['ONE HUNDRED', 0]]), 'Insufficient Funds', 'insufficient funds');\", \"assert.deepEqual(drawer(19.50, 20.00, [['PENNY', 0.50], ['NICKEL', 0], ['DIME', 0], ['QUARTER', 0], ['ONE', 0], ['FIVE', 0], ['TEN', 0], ['TWENTY', 0], ['ONE HUNDRED', 0]]), \"Closed\", 'cash-in-drawer equals change');\" ]"], "neg": []} {"query": "On first render, camper see's an unstyled textarea. After, codemirror takes over and hides textarea and adds it's own box. This initial flash is hideous and makes puppies cry.\nThis has not been fixed on the Reactify branch. And I would prefer styling to be to match codemirror instead of just hiding the text area, as this does not prevent flash to the user.\nDoes styling it like that really not stop the flash? Everything I'm seeing online says it should. I'm only an amateur though. My thought process on the fix was that codemirror is hiding the textarea through javascript and that the flash is be caused by the script running late/slow/delayed/ and is hiding it after the page has already displayed. So I thought since codemirror is hiding it anyway, why not just hide it from the start to prevent the flash.\nThere are really two flashes, first the text area is shown then hidden by codemirror. The second flash is happening because codemirror does not render until it is loading in the DOM, which is intentional as codemirror relies heavily on DOM manipulation. While hiding the textarea does stop it from showing to the user on initial load, codemirror still needs to load and the user will see codemirror appear from nowhere, ie flash. After thinking about it, hiding the text area might be the best route on the reactify branch as well. If we were to add classes to mimic the styling of codemirror in the text box, the text box is not codemirror and React will still need to re-render that section of the view which will cause a flash. Ultimately what I would like to get done is to completely rewrite codemirror into a self contained React component so that it can pre-render on the server. But that is neither here nor there. I am willing to close this issue when the same styling is applied to the reactify branch that is currently on master. Would you like to give it a try? You can get some exposure to React at the same time. We are all amateurs until we are not. My philosophy is\nJust to make sure, this is the branch your referring to? I tried to edit the .jade files in server/views/bonfire/ but nothing happened. Finally found that changes were being done from common/components/bonfires/ so it looks like the easiest way would just be to apply the style in under bonfire styling? I don't want to submit anything because I'm not sure if I would be submitting changes to the correct file.\nYes I think that should work just fine. Test locally to make sure it is hidden then submit the PR.\nI messed up and commited directly to the repo. Sorry about that. Tested code locally and it worked.\nLooks like the text area hide is working! Thanks.", "pos": ["#mainEditorPanel form.code .form-group.codeMirrorView textarea#codeEditor(autofocus=true) textarea#codeEditor(autofocus=true, style='display: none;') script(src='/js/lib/bonfire/bonfireFramework_v0.1.2.js')"], "neg": []} {"query": "When FreeCodeCamp/freecodecamp was closed by updating the link from Trello to the text of the next sentence wasn't updated on\nThanks for point that out. Would you like to create a PR?\nThanks for pointing this out. I fixed and merged.", "pos": ["We welcome pull requests from Free Code Camp \"campers\" (our students) and seasoned JavaScript developers alike! 1) Check our [public Waffle Board](https://waffle.io/freecodecamp/freecodecamp) 2) If your issue or feature isn't on the board, either open an issue on this GitHub repo or message Quincy Larson to request to be added to the Trello board. 2) If your issue or feature isn't on the board, open an issue and if you think you can fix it yourself, start working on it. 3) Once your code is ready, submit the pull request. We'll do a quick code review and give you feedback, and iterate from there. This project uses [Airbnb JavaScript Style Guide](https://github.com/airbnb/javascript) with a few minor exceptions. If you are submitting a pull request that involves Jade templates, please make sure you are using *spaces*, not tabs. License -------"], "neg": []} {"query": "! In Firefox 36.0.1 on OS X 10.9.5 Link:\nFirefox appears to be jamming the comment-list on top of the display area for the main story.\nThose elements are floating left because of .col-xs-12 on the h3.", "pos": ["var image = !{JSON.stringify(image)}; .spacer h3.row.col-xs-12 h3.row .row.text-left.negative-10 .col-xs-3.col-sm-1.text-center .row.negative-5"], "neg": []} {"query": "Creating a new account via email you can enter an email such as mrrenter This should be checked for a .com/org/etc Also once this account is created it is bricked as well. If you log out of it you cannot log back in because the server says its not a valid email address. There is still an entry in the table Solution: Update the regex used for email validation\nThe decision was made to allow this behavior if a user so desired. Unless Quincy wants to enforce valid emails (through confirmation, not regex imo) I'm going to close this.\nIf the user uses this type of email though they will not be able to log back in. This will just fill the database with unusable accounts. If this an accepted format I suggest changing the login to accept this format as well\nIdeally we should verify that it conforms to a legal email address pattern. I can't remember why we didn't do this originally (I'm sure we discussed it). I think Angular validation didn't allow for it.\nThe sign up form checks /api/checkUniqueEmail/[email-text-typed] to see if the email is unique. If the client side validation doesn't work couldn't we use checkUniqueEmail to validate the email server side?\nI've fixed this. It will now send the user back to the form with a flash notification upon submission of an invalid email. I tested it and it will accept good emails. I'm using , which was already included, to do this.", "pos": ["*/ exports.postEmailSignup = function(req, res, next) { var errors = req.validationErrors(); req.assert('email', 'valid email required').isEmail(); var errors = req.validationErrors(); if (errors) { req.flash('errors', errors); return res.redirect('/email-signup');"], "neg": []} {"query": "Bonfires show completely done, but not all points were accounted for. This could have stemmed from using Bonfires when it was first live and the bug at and fixed in . I doubt this is a pervasive issue. It could just be isolated to me.\nThere's a good chance this is already fixed on our UX-improvement branch. There were a number of issues with our old point system that we've since remedied.", "pos": ["} ]); profileValidation.controller('nonprofitFormController', ['$scope', function($scope) { } ]); profileValidation.directive('uniqueUsername', function($http) { return { restrict: 'A',", "li • Understand that they will build your project using JavaScript frameworks (as opposed to older or proprietary tools) li • Keep your expectations high. Our students' goal is to produce work that's up to your standards h3 If you're OK with these terms, great! We'd love to help you! Fill in this form and we'll get right back to you. form.form-horizontal(role='form', action=\"/nonprofits/\", method='POST') form.form-horizontal(role='form', action=\"/nonprofits/\", method='POST', novalidate='novalidate', name='nonprofitForm') input(type='hidden', name='_csrf', value=_csrf) .form-group label(class='col-sm-2 control-label', for='name') Your name label(class='col-sm-2 control-label', for='name') Your name * .col-sm-8 input.form-control(type='text', name='name', id='name') input.form-control(type='text', name='name', id='name', autocomplete=\"off\", ng-model='name', required='required') .col-sm-8.col-sm-offset-2(ng-show=\"nonprofitForm.name.$invalid && nonprofitForm.name.$error.required && !nonprofitForm.name.$pristine\") alert(type='danger') span.ion-close-circled(id='#name-error') | Your name is required. .form-group label(class='col-sm-2 control-label', for='email') Your email label(class='col-sm-2 control-label', for='email') Your email * .col-sm-8 input.form-control(type='text', name='email', id='email') input.form-control(type='text', name='email', id='email', autocomplete=\"off\", ng-model='email', required='required') .col-sm-8.col-sm-offset-2(ng-show=\"nonprofitForm.email.$invalid && nonprofitForm.email.$error.required && !nonprofitForm.email.$pristine\") alert(type='danger') span.ion-close-circled(id='#email-error'). Your email is required. .form-group label(class='col-sm-2 control-label', for='message') Briefly describe what problem you need to solve, and for whom. label(class='col-sm-2 control-label', for='message') Briefly describe what problem you need to solve, and for whom. * .col-sm-8 textarea.form-control(type='text', name='message', id='message', rows='7') textarea.form-control(type='text', name='message', id='message', rows='7', autocomplete=\"off\", ng-model='message', required='required') .col-sm-8.col-sm-offset-2(ng-show=\"nonprofitForm.message.$invalid && nonprofitForm.message.$error.required && !nonprofitForm.message.$pristine\") alert(type='danger') span.ion-close-circled(id='#message-error') | Your message is required. .form-group .col-sm-offset-2.col-sm-8 button.btn.btn-primary(type='submit') button.btn.btn-primary(type='submit', ng-disabled='nonprofitForm.$invalid') span.ion-paper-airplane | Submit | Submit No newline at end of file"], "neg": []} {"query": "Bonfires show completely done, but not all points were accounted for. This could have stemmed from using Bonfires when it was first live and the bug at and fixed in . I doubt this is a pervasive issue. It could just be isolated to me.\nThere's a good chance this is already fixed on our UX-improvement branch. There were a number of issues with our old point system that we've since remedied.", "pos": ["transform: translateY(-50%); } .landing-skill-icon { color: #215f1e; font-size: 150px; } .black-text { color: #333; font-weight: 400; font-size: 40px; } .font-awesome-padding { margin-top: 45px; margin-bottom: 20px; } .background-svg { width: 220px; height: 220px;", "background-position: center; } .testimonial-image { border-radius: 5px; height: 200px; width: 200px; } .testimonial-copy { font-size: 20px; text-align: center; @media (min-width: 991px) and (max-width: 1199px) { height: 120px; } @media (min-width: 1200px) { height: 90px; } } //uncomment this to see the dimensions of all elements outlined in red //* { // border-color: red;", "extends layout block content .hidden-xs a(href='https://github.com/freecodecamp/freecodecamp') img(style='position: absolute; top: 40; right: 0; border: 0; margin-top: -30px;', src='https://camo.githubusercontent.com/e7bbb0521b397edbd5fe43e7f760759336b5e05f/68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f6769746875622f726962626f6e732f666f726b6d655f72696768745f677265656e5f3030373230302e706e67', alt='Fork me on GitHub', data-canonical-src='https://s3.amazonaws.com/github/ribbons/forkme_right_green_007200.png') .jumbotron .text-center h1.hug-top Code with Us", "br br a.btn.nonprofit-cta.btn-success(href=\"/nonprofits\") I'm with a nonprofit and want help coding something include partials/about include partials/faq No newline at end of file .big-break h2 Campers you'll hang out with: .row .col-xs-12.col-sm-12.col-md-4 img.img-responsive.testimonial-image.img-center(src=\"https://s3.amazonaws.com/freecodecamp/testimonial-jen.jpg\", alt=\"@jenthebest's testimonial image\") .testimonial-copy Getting back on track with Free Code Camp and committing to a new career in 2015! h3 - @jenthebest .col-xs-12.col-sm-12.col-md-4 img.img-responsive.testimonial-image.img-center(src=\"https://s3.amazonaws.com/freecodecamp/testimonial-tate.jpg\", alt=\"@TateThurston's testimonial image\") .testimonial-copy Just built my company's website with skills I've learned from Free Code Camp! h3 - @TateThurston .col-xs-12.col-sm-12.col-md-4 img.img-responsive.testimonial-image.img-center(src=\"https://s3.amazonaws.com/freecodecamp/testimonial-cynthia.jpg\", alt=\"@cynthialanel's testimonial image\") .testimonial-copy I'm currently working through Free Code Camp to improve my JavaScript. The community is very welcoming! h3 - @cynthialanel .big-break h2 Skills you'll learn: .text-center .col-xs-12.col-sm-12.col-md-3 .landing-skill-icon.ion-social-html5 .black-text HTML5 .col-xs-12.col-sm-12.col-md-3 .landing-skill-icon.ion-social-css3 .black-text CSS3 .col-xs-12.col-sm-12.col-md-3 .landing-skill-icon.ion-social-javascript .black-text JavaScript .col-xs-12.col-sm-12.col-md-3 .landing-skill-icon.fa.fa-database.font-awesome-padding .black-text Databases .col-xs-12.col-sm-12.col-md-3 .landing-skill-icon.ion-social-chrome .black-text DevTools .col-xs-12.col-sm-12.col-md-3 .landing-skill-icon.ion-social-nodejs .black-text Node.js .col-xs-12.col-sm-12.col-md-3 .landing-skill-icon.ion-social-angular .black-text Angular.js .col-xs-12.col-sm-12.col-md-3 .landing-skill-icon.ion-ios-loop-strong .black-text Agile .big-break h2   h2 Fast facts about our community: h3.col-xs-offset-0.col-sm-offset-1.col-md-offset-2 ul.text-left li.ion-code   We're 100% free and open source li.ion-code   We're thousands of professionals who are learning to code li.ion-code   We're building projects for dozens of nonprofits li.ion-code   We share one goal: to boost our careers with code .big-break a.btn.btn-cta.signup-btn(href=\"/login\") Start learning to code (it's free) No newline at end of file"], "neg": []} {"query": "Bonfires show completely done, but not all points were accounted for. This could have stemmed from using Bonfires when it was first live and the bug at and fixed in . I doubt this is a pervasive issue. It could just be isolated to me.\nThere's a good chance this is already fixed on our UX-improvement branch. There were a number of issues with our old point system that we've since remedied.", "pos": ["failureRedirect: '/login' }; app.get('/auth/twitter', passport.authenticate('twitter')); app.get('/auth/twitter', passport.authorize('twitter')); app.get( '/auth/twitter/callback', passport.authenticate('twitter', {", "); }; // prepares the string to be printed on the terminal var escape = function(msg) { return msg. replace(/&/g,'&'). replace(//g,'>'). replace(/n/g, '
'). replace(/ /g, ' '); };
// puts the message on the terminal var print = function(cls, msg) { codeOutput.setValue(msg);", "// interface provided to the plugin var api = { output: function(data) { if (!--requests) { endLoading(); } // print('separator'); print('input', data.input); if (data.error) { print('message', data.error); } else { print('output', data.output); } endLoading(); print('input', data.input); if (data.error) { print('message', data.error); } else { print('output', data.output); } } };", "setTimeout( function() { endLoading(); codeOutput.setValue('Infinite loop detected!'); // print('message', 'Your code took too long to execute. Check for an infinite loop or recursion.'); // console.log('infinite loop'); // $('#codeOutput.setValue('Infinite loop detected')') reset(); }, 10); });", "var editor = myCodeMirror; myCodeMirror.setValue('2*2'); myCodeMirror.setSize(\"100%\", 500); var codeOutput = CodeMirror.fromTextArea(document.getElementById(\"codeOutput\"), { lineNumbers: false,"], "neg": []} {"query": "In the ux-improvements branch: Looks like this is an issue with the seed data here:\nThanks! I've fixed the copy for all of these waypoints.\nNo problem. You may already know this, but it's still showing the Mongo video...", "pos": ["\"Return the provided string with the first letter of each word capitalized.\", \"For the purpose of this exercise, you should also capitalize connecting words like 'the' and 'of'.\" ], \"challengeEntryPoint\": \"titleCase(\"I'm a little tea pot\")\", \"challengeEntryPoint\": \"titleCase(\"I'm a little tea pot\");\", \"challengeSeed\": \"function titleCase(str) {n return str;rn}\", \"tests\": [ \"expect(titleCase(\"I'm a little tea pot\")).to.be.a('String');\","], "neg": []} {"query": "It would be really helpful for each bonfire solution on a user's profile to include a link to the original exercise, esp. for non-FCC users.\nGreat point. I'm doing so. Thanks!", "pos": ["\"Return the provided string with the first letter of each word capitalized.\", \"For the purpose of this exercise, you should also capitalize connecting words like 'the' and 'of'.\" ], \"challengeEntryPoint\": \"titleCase(\"I'm a little tea pot\")\", \"challengeEntryPoint\": \"titleCase(\"I'm a little tea pot\");\", \"challengeSeed\": \"function titleCase(str) {n return str;rn}\", \"tests\": [ \"expect(titleCase(\"I'm a little tea pot\")).to.be.a('String');\","], "neg": []} {"query": "One of the tests for that bonfire is : , which is supposed to give : . And another test is the same bonfire is : , which is supposed to give : . This doesn't make sense. If it can be inferred, based on the difference being one month apart, that it's the next year, for the second case, then it should also be possible for the first case too. March and May are one month apart, so the output should be just like the second case.\nWe're a little backlogged right now so if you can submit a PR to clean this up it would be much appreciated.", "pos": ["\"assert.deepEqual(friendly(['2015-07-01', '2015-07-04']), ['July 1st','4th'], 'ending month should be omitted since it is already mentioned');\", \"assert.deepEqual(friendly(['2015-12-01', '2016-02-03']), ['December 1st','February 3rd'], 'two months apart can be inferred if it is the next year');\", \"assert.deepEqual(friendly(['2015-12-01', '2017-02-03']), ['December 1st, 2015','February 3rd, 2017']);\", \"assert.deepEqual(friendly(['2016-03-01', '2016-05-05']), ['March 1st','May 5th, 2016']);\", \"assert.deepEqual(friendly(['2016-03-01', '2016-05-05']), ['March 1st','May 5th'], 'one month apart can be inferred it is the same year');\", \"assert.deepEqual(friendly(['2017-01-01', '2017-01-01']), ['January 1st, 2017'], 'since we do not duplicate only return once');\", \"assert.deepEqual(friendly(['2022-09-05', '2023-09-04']), ['September 5th, 2022','September 4th, 2023']);\" ],"], "neg": []} {"query": "The description does not specify to preserve the title case of the word replaced. Although the tests somehow expect the title case to be preserved if the word is getting replaced. We should either: A. change the test B. Add a note in the description about this quirk.", "pos": ["\"Return the provided string with the first letter of each word capitalized.\", \"For the purpose of this exercise, you should also capitalize connecting words like 'the' and 'of'.\" ], \"challengeEntryPoint\": \"titleCase(\"I'm a little tea pot\")\", \"challengeEntryPoint\": \"titleCase(\"I'm a little tea pot\");\", \"challengeSeed\": \"function titleCase(str) {n return str;rn}\", \"tests\": [ \"expect(titleCase(\"I'm a little tea pot\")).to.be.a('String');\","], "neg": []} {"query": "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.", "pos": ["\"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.\""], "neg": []} {"query": "for step 38 here: the new user needs to set up an SSH key to push to github. the key is given by C9, but it's not clear to me how to add it to github, a simple copy /paste to my SSH keys in my account isn't working. This should be clarified for new users of c9. Not sure if it's needed for every c9 workspace or just once, but I guess github is seeing c9 as a new computer?\nHere is a set of instructions that worked for me: In the bottom left of your C9 dashboard is a section called \u201cAdd-on Services\u201d. Click \u201cactivate\u201d next to the \u201cGitHub\u201d icon (if you haven\u2019t already). When the pop up appears, tell it to allow access to your account. This should complete the link between GitHub account and your C9 account. While still on the dashboard, look to the right under \u201cAccount Settings\u201d for the link \u201cShow your SSH key\u201d. Click on it, and copy the value which appears. Go to the GitHub SSH settings page, and click \u201cAdd SSH Key\u201d Enter the title \u201cC9\u2033, paste the SSH Key into the \u201cKey\u201d box, and click \u201cAdd Key\u201d.\nExcellent. Thank you for pointing this out. I'll add this.", "pos": ["\"Return the provided string with the first letter of each word capitalized.\", \"For the purpose of this exercise, you should also capitalize connecting words like 'the' and 'of'.\" ], \"challengeEntryPoint\": \"titleCase(\"I'm a little tea pot\")\", \"challengeEntryPoint\": \"titleCase(\"I'm a little tea pot\");\", \"challengeSeed\": \"function titleCase(str) {n return str;rn}\", \"tests\": [ \"expect(titleCase(\"I'm a little tea pot\")).to.be.a('String');\","], "neg": []} {"query": "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. \"Now it's time to tackle our Bonfires.\", \"Go to http://freecodecamp.com/bonfires and start working through our Bonfire challenges.\", \"Now it's time to tackle our Bonfires. You can begin them by advancing to the next challenge.\", \"Once you you finish pair programming, end the session in Screen Hero session.\", \"Congratulations! You have completed your first pair programming session.\", \"Pair program as much as possible with different campers until you've completed all the Bonfire challenges. This is a big time investment, but the JavaScript practice you get will be well worth it!\",", "\"tests\": [ \"assert($('ul').length > 0, 'You should have an ul element on your webpage.')\", \"assert($('ol').length > 0, 'You should have an ol element on your webpage.')\", \"assert($('li').length > 5, 'You should have three li elements on within your ul element.')\", \"assert($('li').length > 5, 'You should have three li elements on within your ol element.')\" \"assert($('li').length > 5, 'You should have three li elements within your ul element.')\", \"assert($('li').length > 5, 'You should have three li elements within your ol element.')\" ], \"challengeSeed\": [ \"\",", "\"For example, if you wanted to make a text input field required, you can just add the word \"required\" within your input element use: <input type='text' required>\" ], \"tests\": [ \"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\".')\" \"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\".')\" ], \"challengeSeed\": [ \"\",", "\"Put the \"like\", \"Info\" and \"Delete\" buttons side-by-side by wrapping all three of them within one <div class=\"row\"> element, then each of them within a <div class=\"col-xs-4\"> element.\", \"Bootstrap uses a responsive grid system, which makes it easy to put elements into rows and specify each element's relative width. Most of Bootstrap's classes can be applied to a div element.\", \"Here's a diagram of how Bootstrap's 12-column grid layout works:\", \"\", \"\", \"Note that in this illustration, we use the col-md-* class. Here, \"md\" means \"medium\", and \"*\" is a number specifying how many columns wide the element should be. In this case, we're specifying how many columns wide an element should be on a medium-sized screen, such as a laptop.\", \"In the Cat Photo App that we're building, we'll use col-xs-*, where \"*\" is the number of columns wide the element should be, and \"xs\" means \"extra small\", like an extra-small mobile phone screen.\", \"The row class is applied to a div, and the buttons themselves can be wrapped within it.\"", "\"name\": \"Waypoint: Line up Form Elements Responsively with Bootstrap\", \"difficulty\" : 0.062, \"description\": [ \"Wrap both your form's text input field and submit button within a div with the class \"row\". Wrap your form's text input field within a div with the class of \"col-xs-7\". Wrap your form's submit button the in a div with the class \"col-xs-5\".\", \"Now let's get your form input and your submission button on the same line. We'll do this the same way we have previously: by using a \"row\" element with \"col-xs-*\" elements withing it.\", \"Wrap both your form's text input field and submit button within a div with the class \"row\". Wrap your form's text input field within a div with the class of \"col-xs-7\". Wrap your form's submit button the in a div with the class \"col-xs-5\".\", \"This is the last challenge we'll do for our Cat Photo App for now. We hope you've enjoyed learning Font Awesome, Bootstrap, and responsive design!\" ], \"tests\": [ \"assert($('.row').length > 4, 'Wrap your all of your checkboxes inside one div with the class \"row\".')\", \"assert($('.row').length > 4, 'Wrap your form submission button and text area in a div with class \"row\".')\", \"assert($('.col-xs-5').length > 0, 'Wrap your form submission button in a div with the class \"col-xs-5\".')\", \"assert($('.col-xs-7').length > 0, 'Wrap your form text area in a div with the class \"col-xs-7\".')\" ],"], "neg": []} {"query": "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.", "pos": ["\"Add them as a new contact in Screen Hero, then click the monitor-looking button to attempt to share your screen with them.\", \"Once the Screen Hero session starts, your screen's margins will glow orange. You are now sharing your screen.\", \"Your pair will have their own cursor, and will be able to type text on his or her and keyboard.\", \"Now it's time to tackle our Bonfires.\", \"Go to http://freecodecamp.com/bonfires and start working through our Bonfire challenges.\", \"Now it's time to tackle our Bonfires. You can begin them by advancing to the next challenge.\", \"Once you you finish pair programming, end the session in Screen Hero session.\", \"Congratulations! You have completed your first pair programming session.\", \"Pair program as much as possible with different campers until you've completed all the Bonfire challenges. This is a big time investment, but the JavaScript practice you get will be well worth it!\",", "\"tests\": [ \"assert($('ul').length > 0, 'You should have an ul element on your webpage.')\", \"assert($('ol').length > 0, 'You should have an ol element on your webpage.')\", \"assert($('li').length > 5, 'You should have three li elements on within your ul element.')\", \"assert($('li').length > 5, 'You should have three li elements on within your ol element.')\" \"assert($('li').length > 5, 'You should have three li elements within your ul element.')\", \"assert($('li').length > 5, 'You should have three li elements within your ol element.')\" ], \"challengeSeed\": [ \"\",", "\"For example, if you wanted to make a text input field required, you can just add the word \"required\" within your input element use: <input type='text' required>\" ], \"tests\": [ \"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\".')\" \"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\".')\" ], \"challengeSeed\": [ \"\",", "\"Put the \"like\", \"Info\" and \"Delete\" buttons side-by-side by wrapping all three of them within one <div class=\"row\"> element, then each of them within a <div class=\"col-xs-4\"> element.\", \"Bootstrap uses a responsive grid system, which makes it easy to put elements into rows and specify each element's relative width. Most of Bootstrap's classes can be applied to a div element.\", \"Here's a diagram of how Bootstrap's 12-column grid layout works:\", \"\", \"\", \"Note that in this illustration, we use the col-md-* class. Here, \"md\" means \"medium\", and \"*\" is a number specifying how many columns wide the element should be. In this case, we're specifying how many columns wide an element should be on a medium-sized screen, such as a laptop.\", \"In the Cat Photo App that we're building, we'll use col-xs-*, where \"*\" is the number of columns wide the element should be, and \"xs\" means \"extra small\", like an extra-small mobile phone screen.\", \"The row class is applied to a div, and the buttons themselves can be wrapped within it.\"", "\"name\": \"Waypoint: Line up Form Elements Responsively with Bootstrap\", \"difficulty\" : 0.062, \"description\": [ \"Wrap both your form's text input field and submit button within a div with the class \"row\". Wrap your form's text input field within a div with the class of \"col-xs-7\". Wrap your form's submit button the in a div with the class \"col-xs-5\".\", \"Now let's get your form input and your submission button on the same line. We'll do this the same way we have previously: by using a \"row\" element with \"col-xs-*\" elements withing it.\", \"Wrap both your form's text input field and submit button within a div with the class \"row\". Wrap your form's text input field within a div with the class of \"col-xs-7\". Wrap your form's submit button the in a div with the class \"col-xs-5\".\", \"This is the last challenge we'll do for our Cat Photo App for now. We hope you've enjoyed learning Font Awesome, Bootstrap, and responsive design!\" ], \"tests\": [ \"assert($('.row').length > 4, 'Wrap your all of your checkboxes inside one div with the class \"row\".')\", \"assert($('.row').length > 4, 'Wrap your form submission button and text area in a div with class \"row\".')\", \"assert($('.col-xs-5').length > 0, 'Wrap your form submission button in a div with the class \"col-xs-5\".')\", \"assert($('.col-xs-7').length > 0, 'Wrap your form text area in a div with the class \"col-xs-7\".')\" ],"], "neg": []} {"query": "i am suspecting another small bug, the next challenge after succesful code run in Bonfire: Chunky Monkey actually points to itself", "pos": ["'*.ionicframework.com', 'https://syndication.twitter.com', '*.youtube.com', 'cdn.jsdelivr.net/' ]; app.use(helmet.contentSecurityPolicy({", "\"passport-local\": \"^1.0.0\", \"passport-oauth\": \"^1.0.0\", \"passport-twitter\": \"^1.0.2\", \"ramda\": \"^0.10.0\", \"request\": \"^2.49.0\", \"sitemap\": \"^0.7.4\", \"uglify-js\": \"^2.4.15\",", "// (re)initializes the plugin var reset = function() { requests = 0; plugin = new jailed.Plugin(path+'plugin_v0.1.2.js', api); plugin = new jailed.Plugin(path+'plugin_v0.1.3.js', api); plugin.whenDisconnected( function() { // give some time to handle the last responce setTimeout( function() {", " // executes the given code and handles the result var run = function(code) { var result = { input: code, output: null, error: null, type: null }; try { var codeExec = runHidden(code); result.type = typeof codeExec; result.output = stringify(codeExec); } catch(e) { result.error = e.message; } application.remote.output(result); }; // protects even the worker scope from being accessed var runHidden = function(code) { var indexedDB = null; var location = null; var navigator = null; var onerror = null; var onmessage = null; var performance = null; var self = null; var webkitIndexedDB = null; var postMessage = null; var close = null; var openDatabase = null; var openDatabaseSync = null; var webkitRequestFileSystem = null; var webkitRequestFileSystemSync = null; var webkitResolveLocalFileSystemSyncURL = null; var webkitResolveLocalFileSystemURL = null; var addEventListener = null; var dispatchEvent = null; var removeEventListener = null; var dump = null; var onoffline = null; var ononline = null; var importScripts = null; return eval(code); } // converts the output into a string var stringify = function(output) { var result; if (typeof output == 'undefined') { result = 'undefined'; } else if (output === null) { result = 'null'; } else { result = JSON.stringify(output) || output.toString(); } return result; } application.setInterface({run:run}); ", " // executes the given code and handles the result var run = function(code) { var result = { input: code, output: null, error: null, type: null }; try { var codeExec = runHidden(code); result.type = typeof codeExec; result.output = stringify(codeExec); } catch(e) { result.error = e.message; } application.remote.output(result); }; // protects even the worker scope from being accessed var runHidden = function(code) { var importScript = function(url) { var error = null; try { importScripts(url); } catch (e) { error = e; console.log('Unable to load ramda!'); } }; var indexedDB = null; var location = null; var navigator = null; var onerror = null; var onmessage = null; var performance = null; var self = null; var webkitIndexedDB = null; var postMessage = null; var close = null; var openDatabase = null; var openDatabaseSync = null; var webkitRequestFileSystem = null; var webkitRequestFileSystemSync = null; var webkitResolveLocalFileSystemSyncURL = null; var webkitResolveLocalFileSystemURL = null; var addEventListener = null; var dispatchEvent = null; var removeEventListener = null; var dump = null; var onoffline = null; var ononline = null; importScript(\"https://cdn.jsdelivr.net/ramda/0.10.0/ramda.min.js\"); var _ = R; return eval(code); } // converts the output into a string var stringify = function(output) { var result; if (typeof output == 'undefined') { result = 'undefined'; } else if (output === null) { result = 'null'; } else { result = JSON.stringify(output) || output.toString(); } return result; } application.setInterface({run:run}); ", " /** * Created by nathanleniz on 2/21/15. */ var R = require('ramda'); No newline at end of file", " // Ramda v0.10.0 // https://github.com/ramda/ramda // (c) 2013-2015 Scott Sauyet and Michael Hurley // Ramda may be freely distributed under the MIT license. (function(){\"use strict\";var n={ramda:\"placeholder\"},t=function(n,t){return n+t},r=function(n,t){for(var r=-1;++r0){for(var e,u=0,i=r[u],o=t(i);++ut},g=function(n,t,r){var e=0,u=n.length;for(\"number\"==typeof r&&(e=0>r?Math.max(0,u+r):r);u>e;){if(n[e]===t)return e;++e}return-1},p=Array.isArray||function(n){return null!=n&&n.length>=0&&\"[object Array]\"===Object.prototype.toString.call(n)},m=Number.isInteger||function(n){return n<<0===n},y=function(n){return null!=n&&n===Object(n)&&\"function\"==typeof n.then},v=function(n,t,r){var e=n.length;for(\"number\"==typeof r&&(e=0>r?e+r+1:Math.min(e,r+1));--e>=0;)if(n[e]===t)return e;return-1},d=function(n,t){return t>n},w=function(n,t){for(var r=-1,e=t.length,u=new Array(e);++rn?t[t.length+n]:t[n]},x=function(n){return function(t){return w(function(n){return[n,t[n]]},n(t))}},A=function(n,t){var r,e=-1,u=n.length;if(null!=t){for(r=t;null!=r&&++e0?n.hasOwnProperty(0)&&n.hasOwnProperty(n.length-1):!1:!1},D=function(n){return 0===Object(n).length},U=function(n){return null==n},_=function(n){for(var t=n.length,r=-1;++r=0)return!1;return!0},$=function(n){var t,r=[];for(t in n)r[r.length]=t;return r},G=function(n,t){switch(n){case 0:return function(){return t.call(this)};case 1:return function(n){return t.call(this,n)};case 2:return function(n,r){return t.call(this,n,r)};case 3:return function(n,r,e){return t.call(this,n,r,e)};case 4:return function(n,r,e,u){return t.call(this,n,r,e,u)};case 5:return function(n,r,e,u,i){return t.call(this,n,r,e,u,i)};case 6:return function(n,r,e,u,i,o){return t.call(this,n,r,e,u,i,o)};case 7:return function(n,r,e,u,i,o,c){return t.call(this,n,r,e,u,i,o,c)};case 8:return function(n,r,e,u,i,o,c,a){return t.call(this,n,r,e,u,i,o,c,a)};case 9:return function(n,r,e,u,i,o,c,a,f){return t.call(this,n,r,e,u,i,o,c,a,f)};case 10:return function(n,r,e,u,i,o,c,a,f,l){return t.call(this,n,r,e,u,i,o,c,a,f,l)};default:throw new Error(\"First argument to nAry must be a non-negative integer no greater than ten\")}},H=function(n){return function(){return!n.apply(this,arguments)}},J=function(n){return function(){return j(n,arguments)}},K=function(n){return[n]},Q=function(n){var t,r=!1;return function(){return r?t:(r=!0,t=n.apply(this,arguments))}},V=C(E),X=function(n,t){switch(arguments.length){case 0:throw O();case 1:return function(t){return t[n]}}return t[n]},Y=C(X),Z=function(n){return P(n).reverse()},nt=x($),tt=function(){var n=\"\tn\u000bfr \u00a0\u1680\u180e\u2000\u2001\u2002\u2003\u2004\u2005\u2006\u2007\u2008\u2009\u200a\u202f\u205f\u3000u2028u2029\ufeff\",t=\"\u200b\",r=\"function\"==typeof String.prototype.trim;return r&&!n.trim()&&t.trim()?function(n){return n.trim()}:function(t){var r=new RegExp(\"^[\"+n+\"][\"+n+\"]*\"),e=new RegExp(\"[\"+n+\"][\"+n+\"]*$\");return t.replace(r,\"\").replace(e,\"\")}}(),rt=function(n){return null===n?\"Null\":void 0===n?\"Undefined\":Object.prototype.toString.call(n).slice(8,-1)},et=function(n){if(0===arguments.length)throw O();return function(){return n(P(arguments))}},ut=function(n){return G(1,n)},it=function(n){var t,r=[];for(t in n)r[r.length]=n[t];return r},ot=T(!1),ct=F,at=T(!0),ft=function(n,t){return i(t,[n])},lt=function Cu(n,t,r){var e=function(e){for(var u=t.length,i=-1;++i=0},pt=function(n){return function(){switch(arguments.length){case 0:throw O();case 1:return arguments[0];default:for(var t=arguments.length-1,r=arguments[t],e=r.length;t--;)r=n(arguments[t],r);return S(e,r)}}},mt=function(n,t){return function(r){if(0===arguments.length)throw O();for(var e,u=-1,i=t;++u=n?t.apply(this,u):r(u)})}([])}),Bt=xt(-1),Ft=vt(function(n,t){return null==t?n:t}),zt=vt(function(n,t){for(var r=[],e=-1,u=n.length;++e=0?n:r.length,i(ft(t,P(r,0,n)),P(r,n))}),hr=dt(function(n,t,r){return n=n=0?n:r.length,i(i(P(r,0,n),t),P(r,n))}),gr=function(n,t){var r=P(arguments,2),e=n-r.length;return Lt(e+1,function(){var n=arguments[e],u=r.concat(P(arguments,0,e));return n[t].apply(n,u)})},pr=vt(function(n,t){return null!=t&&t.constructor===n||t instanceof n}),mr=gr(1,\"join\"),yr=function(){var n=!{toString:null}.propertyIsEnumerable(\"toString\"),t=[\"constructor\",\"valueOf\",\"isPrototypeOf\",\"toString\",\"propertyIsEnumerable\",\"hasOwnProperty\",\"toLocaleString\"];return function(r){if(Object(r)!==r)return[];if(Object.keys)return Object.keys(r);var e,u,i=[];for(e in r)or(e,r)&&(i[i.length]=e);if(n)for(u=t.length;u--;)e=t[u],or(e,r)&&!gt(e,i)&&(i[i.length]=e);return i}}(),vr=vt(function(n,t){return v(t,n)}),dr=function(n){return null!=n&&pr(Number,n.length)?n.length:0/0},wr=vt(function(n,t){var r=function(t){return n(t)};return r.set=vt(t),r.map=vt(function(r,e){return t(r(n(e)),e)}),r}),br=vt(st(\"map\",w)),Or=dt(function(n,t,r){for(var e=-1,u=r.length,i=new Array(u),o=[t];++e=t)return[];for(var r=0,e=new Array(Math.floor(t)-Math.ceil(n));t>n;)e[r++]=n++;return e}),Zr=dt(k),ne=dt(function(n,t,r){for(var e=-1,u=r.length;++ee?-1:e>u?1:0})}),se=gr(1,\"split\"),he=vt(function(n,t){return t.indexOf(n)}),ge=vt(function(n,t){return t.lastIndexOf(n)}),pe=gr(2,\"substring\"),me=C(pe)(void 0),ye=pe(0),ve=Zr(t,0),de=st(\"tail\",function(n){return P(n,1)}),we=vt(st(\"take\",function(n,t){return P(t,0,Math.min(n,t.length))})),be=vt(st(\"takeWhile\",function(n,t){for(var r=-1,e=t.length;++r1?r.apply(null,P(arguments,1)):S(kr(jt(\"length\",t)),r)}},De=ze(r),Ue=ze(e),_e=vt(Le),$e=dt(function(n,t,r){return Fe(L(w(function(n){return[n,r[n]]},$(r))),Ct(n,t))}),Ge=function(){var n=function(t,r,e){if(1===t.length)return $e(t[0],r,e);var u=e[t[0]];return $e(t[0],n(P(t,1),r,pr(Object,u)?u:{}),e)};return function(t,r,e){var u=arguments.length;if(0===u)throw O();var i=se(\".\",t),o=vt(function(t,r){return n(i,t,r)});switch(u){case 1:return o;case 2:return o(r);default:return o(r,e)}}}(),He=vt(st(\"chain\",function(n,t){return Pe(w(n,t))})),Je=gr(1,\"charAt\"),Ke=gr(1,\"charCodeAt\"),Qe=dt(function(n,t,r){function e(t,r){return Le(w(kt,n(r)),t)}return k(e,t([]),r)}),Ve=vt(function(n,t){for(var r={},e=t.length,u=-1;++u10)throw new Error(\"Constructor with greater than ten arguments\");return 0===n?function(){return new t}:Xe(G(n,function(n,r,e,u,i,o,c,a,f,l){switch(arguments.length){case 1:return new t(n);case 2:return new t(n,r);case 3:return new t(n,r,e);case 4:return new t(n,r,e,u);case 5:return new t(n,r,e,u,i);case 6:return new t(n,r,e,u,i,o);case 7:return new t(n,r,e,u,i,o,c);case 8:return new t(n,r,e,u,i,o,c,a);case 9:return new t(n,r,e,u,i,o,c,a,f);case 10:return new t(n,r,e,u,i,o,c,a,f,l)}}))}),Ou=lu(gt),ju=lu(function(n,t){return n/t}),xu=lu(h),Au=lu(function(n,t){return n>=t}),Iu=function(n){if(0===arguments.length)throw O();return fu(n.length,n)},Eu=lu(d),ku=lu(function(n,t){return t>=n}),Mu=lu(function(n,t){return m(n)?!m(t)||1>t?0/0:(n%t+t)%t:0/0}),Pu=lu(function(n,t){return Fe(Fe({},n),t)}),Tu=Zr(Pu,{}),Su=lu(function(n,t){return n%t}),Wu=vu(w,_r,F),Nu=function(n){return bu(n.length,n)},Ru={F:ot,I:ct,T:at,__:n,add:xt,all:At,allPass:De,always:T,and:It,any:Et,anyPass:Ue,ap:_e,append:kt,appendTo:Mt,apply:Pt,arity:S,assoc:$e,assocPath:Ge,binary:Tt,bind:St,call:W,chain:He,charAt:Je,charCodeAt:Ke,clone:Wt,commute:du,commuteMap:Qe,comparator:N,compose:Nt,composeP:Rt,concat:wu,cond:R,construct:Nu,constructN:bu,contains:Ou,containsWith:qt,converge:q,countBy:Ve,createMapEntry:Ct,curry:Xe,curryN:Lt,dec:Bt,defaultTo:Ft,difference:zt,differenceWith:Dt,dissoc:Ut,divide:ju,drop:_t,dropWhile:$t,empty:Gt,eq:Ht,eqDeep:Ye,eqProps:Jt,evolve:Ze,filter:Kt,filterIndexed:Qt,find:Vt,findIndex:Xt,findLast:Yt,findLastIndex:Zt,flatten:nr,flip:C,forEach:tr,forEachIndexed:rr,fromPairs:L,func:B,functions:nu,functionsIn:er,get:ur,groupBy:ir,gt:xu,gte:Au,has:or,hasIn:cr,head:tu,identity:F,ifElse:ar,inc:fr,indexOf:lr,init:ru,insert:sr,insertAll:hr,installTo:eu,intersection:uu,intersectionWith:iu,invert:ou,invertObj:cu,invoker:gr,is:pr,isArrayLike:z,isEmpty:D,isNil:U,isSet:_,join:mr,keys:yr,keysIn:$,last:au,lastIndexOf:vr,length:dr,lens:wr,lift:Iu,liftN:fu,lt:Eu,lte:ku,map:br,mapAccum:Or,mapAccumRight:jr,mapIndexed:xr,mapObj:Ar,mapObjIndexed:Ir,match:Er,mathMod:Mu,max:kr,maxBy:Mr,memoize:Pr,merge:Pu,mergeAll:Tu,min:Tr,minBy:Sr,modulo:Su,multiply:Wr,nAry:G,negate:Nr,not:H,nth:Rr,nthArg:J,of:K,omit:qr,once:Q,op:lu,or:Cr,partial:Lr,partialRight:Br,partition:Fr,path:su,pathEq:zr,pathOn:Dr,pick:Ur,pickAll:_r,pickBy:$r,pipe:Gr,pipeP:Hr,pluck:Jr,prepend:Kr,prependTo:V,product:hu,project:Wu,prop:X,propEq:Qr,propOf:Y,propOr:Vr,props:Xr,range:Yr,reduce:Zr,reduceIndexed:ne,reduceRight:te,reduceRightIndexed:re,reject:ee,rejectIndexed:ue,remove:ie,repeat:gu,replace:oe,reverse:Z,scan:ce,slice:ae,sort:fe,sortBy:le,split:se,strIndexOf:he,strLastIndexOf:ge,substring:pe,substringFrom:me,substringTo:ye,subtract:pu,sum:ve,tail:de,take:we,takeWhile:be,tap:Oe,times:je,toLower:xe,toPairs:Ae,toPairsIn:nt,toUpper:Ie,trim:tt,type:rt,unapply:et,unary:ut,unfold:Ee,union:mu,unionWith:yu,uniq:ke,uniqWith:Me,unnest:Pe,useWith:vu,values:Te,valuesIn:it,where:Se,wrap:We,xprod:Ne,zip:Re,zipObj:qe,zipWith:Ce};\"object\"==typeof exports?module.exports=Ru:\"function\"==typeof define&&define.amd?define(function(){return Ru}):this.R=Ru}).call(this); No newline at end of file", "script(src='/js/lib/codemirror/mode/javascript/javascript.js') script(src='/js/lib/jailed/jailed.js') script(src='/js/lib/bonfire/bonfireInit.js') script(src=\"https://cdn.jsdelivr.net/ramda/0.10.0/ramda.min.js\") .row", "var passedBonfireHash = !{JSON.stringify(bonfireHash)}; var challengeName = !{JSON.stringify(name)}; var started = Math.floor(Date.now() / 1000); var _ = R; .col-xs-12.col-sm-12.col-md-8 #mainEditorPanel form.code"], "neg": []} {"query": "There's a minor, minor typo in the title of this waypoint: \"Waypoint: Responsively Style a Radio Buttons\" should be \"Waypoint: Responsively Style Radio Buttons\"\nThanks, commit addresses this", "pos": ["} ]); profileValidation.controller('nonprofitFormController', ['$scope', function($scope) { } ]); profileValidation.directive('uniqueUsername', function($http) { return { restrict: 'A',", "li • Understand that they will build your project using JavaScript frameworks (as opposed to older or proprietary tools) li • Keep your expectations high. Our students' goal is to produce work that's up to your standards h3 If you're OK with these terms, great! We'd love to help you! Fill in this form and we'll get right back to you. form.form-horizontal(role='form', action=\"/nonprofits/\", method='POST') form.form-horizontal(role='form', action=\"/nonprofits/\", method='POST', novalidate='novalidate', name='nonprofitForm') input(type='hidden', name='_csrf', value=_csrf) .form-group label(class='col-sm-2 control-label', for='name') Your name label(class='col-sm-2 control-label', for='name') Your name * .col-sm-8 input.form-control(type='text', name='name', id='name') input.form-control(type='text', name='name', id='name', autocomplete=\"off\", ng-model='name', required='required') .col-sm-8.col-sm-offset-2(ng-show=\"nonprofitForm.name.$invalid && nonprofitForm.name.$error.required && !nonprofitForm.name.$pristine\") alert(type='danger') span.ion-close-circled(id='#name-error') | Your name is required. .form-group label(class='col-sm-2 control-label', for='email') Your email label(class='col-sm-2 control-label', for='email') Your email * .col-sm-8 input.form-control(type='text', name='email', id='email') input.form-control(type='text', name='email', id='email', autocomplete=\"off\", ng-model='email', required='required') .col-sm-8.col-sm-offset-2(ng-show=\"nonprofitForm.email.$invalid && nonprofitForm.email.$error.required && !nonprofitForm.email.$pristine\") alert(type='danger') span.ion-close-circled(id='#email-error'). Your email is required. .form-group label(class='col-sm-2 control-label', for='message') Briefly describe what problem you need to solve, and for whom. label(class='col-sm-2 control-label', for='message') Briefly describe what problem you need to solve, and for whom. * .col-sm-8 textarea.form-control(type='text', name='message', id='message', rows='7') textarea.form-control(type='text', name='message', id='message', rows='7', autocomplete=\"off\", ng-model='message', required='required') .col-sm-8.col-sm-offset-2(ng-show=\"nonprofitForm.message.$invalid && nonprofitForm.message.$error.required && !nonprofitForm.message.$pristine\") alert(type='danger') span.ion-close-circled(id='#message-error') | Your message is required. .form-group .col-sm-offset-2.col-sm-8 button.btn.btn-primary(type='submit') button.btn.btn-primary(type='submit', ng-disabled='nonprofitForm.$invalid') span.ion-paper-airplane | Submit | Submit No newline at end of file"], "neg": []} {"query": "Adding placeholder tag to the <input type='text' placeholder='this is placeholder text'>\" ], \"tests\": [ \"assert($('[placeholder]').length > 0, 'Your text field should have a placeholder attribute.')\", \"assert(/url/gi.test($('input').attr('placeholder')), 'Your placeholder field should have the value of \"cat photo URL\".')\" \"assert($('input[placeholder]').length > 0, 'Your text field should have a placeholder attribute.')\", \"assert($('input').attr('placeholder') === 'cat photo URL', 'Your placeholder field should have the value of \"cat photo URL\".')\" ], \"challengeSeed\": [ \"\","], "neg": []} {"query": "This challenge has the additional requirement of \"Your text field should have the placeholder text of \"cat photo URL\".\", when this placeholder text was before, then removed again arbitrarily in this lesson. Assuming this is a bug since it doesn't match the tutorial flow.", "pos": ["\"For example, if you wanted to make a text input field required, you can just add the word \"required\" within your input element use: <input type='text' required>\" ], \"tests\": [ \"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\".')\" \"assert($('input').prop('required'), 'Your text field should have the property of being required.')\" ], \"challengeSeed\": [ \"\",", "\"
  • other cats
  • \", \"\", \"
    \", \" \", \" \", \" \", \"
    \" ],"], "neg": []} {"query": "Challenge: Just for reference, I am using Firefox 38 and Windows 8.1, without additional fonts or MS Office installed. As such, the font does not render in the exercise. Instead, it produces Serif. Interestingly enough, the dev tools show the correct font family. (See attached screenshot) In my Firefox settings, I have the default monospace font as \"Lucida Console\", so I am not sure why that font is not displaying, in place of \"Monospace\" !\nWhich version of Firefox are you running? Have you tried just refreshing the page? I've seen a lot of issues caused by the browser that got \"blamed\" on FCC itself.\nThat's likely because you have the font-family surrounded in quotes. Monospace isn't an actual font-family, it's a keyword that represents the browser's default monospaced font (as you point out, Lucida Console in your case). When you surround the font-family value in quotes, the browser is attempting to load a font actually called \"Monospace\" and failing since that doesn't exist on your system. Try the following code and see if it's fixed:\nThe instructions are as follows: Maybe, the lesson should be changed to ask for the family ? Beause I see family as a type (monospace, sans-serif, etc), or a group of fonts (\"Sans-Serif, Arial, Helvetica\") EDIT: Your suggestion of changing to the type monospace worked. It renders as the default monospace set by my browser\nUPDATE - I am noticing that when you begin a new exercise, the code changes slightly to show best practices and ideal answer. This is what FCC considered to be correct: Notice the capitalized \"Monospace\", without quotes. In my opinion, when FCC refers to a phrase to enter, it should wrap it in a code tag, as I assumed the quotation marks to be included.\nThe issue seems to be that I originally put the example in quotes. I'm going to fix that. Thanks for catching this,\nThank you for such a quick response!", "pos": ["} ]); profileValidation.controller('nonprofitFormController', ['$scope', function($scope) { } ]); profileValidation.directive('uniqueUsername', function($http) { return { restrict: 'A',", "li • Understand that they will build your project using JavaScript frameworks (as opposed to older or proprietary tools) li • Keep your expectations high. Our students' goal is to produce work that's up to your standards h3 If you're OK with these terms, great! We'd love to help you! Fill in this form and we'll get right back to you. form.form-horizontal(role='form', action=\"/nonprofits/\", method='POST') form.form-horizontal(role='form', action=\"/nonprofits/\", method='POST', novalidate='novalidate', name='nonprofitForm') input(type='hidden', name='_csrf', value=_csrf) .form-group label(class='col-sm-2 control-label', for='name') Your name label(class='col-sm-2 control-label', for='name') Your name * .col-sm-8 input.form-control(type='text', name='name', id='name') input.form-control(type='text', name='name', id='name', autocomplete=\"off\", ng-model='name', required='required') .col-sm-8.col-sm-offset-2(ng-show=\"nonprofitForm.name.$invalid && nonprofitForm.name.$error.required && !nonprofitForm.name.$pristine\") alert(type='danger') span.ion-close-circled(id='#name-error') | Your name is required. .form-group label(class='col-sm-2 control-label', for='email') Your email label(class='col-sm-2 control-label', for='email') Your email * .col-sm-8 input.form-control(type='text', name='email', id='email') input.form-control(type='text', name='email', id='email', autocomplete=\"off\", ng-model='email', required='required') .col-sm-8.col-sm-offset-2(ng-show=\"nonprofitForm.email.$invalid && nonprofitForm.email.$error.required && !nonprofitForm.email.$pristine\") alert(type='danger') span.ion-close-circled(id='#email-error'). Your email is required. .form-group label(class='col-sm-2 control-label', for='message') Briefly describe what problem you need to solve, and for whom. label(class='col-sm-2 control-label', for='message') Briefly describe what problem you need to solve, and for whom. * .col-sm-8 textarea.form-control(type='text', name='message', id='message', rows='7') textarea.form-control(type='text', name='message', id='message', rows='7', autocomplete=\"off\", ng-model='message', required='required') .col-sm-8.col-sm-offset-2(ng-show=\"nonprofitForm.message.$invalid && nonprofitForm.message.$error.required && !nonprofitForm.message.$pristine\") alert(type='danger') span.ion-close-circled(id='#message-error') | Your message is required. .form-group .col-sm-offset-2.col-sm-8 button.btn.btn-primary(type='submit') button.btn.btn-primary(type='submit', ng-disabled='nonprofitForm.$invalid') span.ion-paper-airplane | Submit | Submit No newline at end of file"], "neg": []} {"query": "! This effects longer lines of codes by making it impossible to select code when trying to insert the cursor with the mouse. I saw where a commit to make the iphone stand out over footer by adding a z-index of 9999 but 9999 is too high. I'm doing a pull request right now that fixes the cover up issue on the code editor and still keeps the iphone above the footer as Quincy wanted. Thanks, Charles\nThanks, I didn't even think about the modal when I set the z-index that high. I'm taking a look at your pull request now.", "pos": [".iframe-scroll { position: fixed !important; margin-top: 75px; z-index: 9999; z-index: 1; } } @media only screen and (max-width: 992px) {"], "neg": []} {"query": "Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. I passed the test, but I should not, because I did not wrapped all my buttons within the same div element with the class \"row\". Screenshot:", "pos": ["\"The \"row\" class is applied to a div, and the buttons themselves can be wrapped within it.\" ], \"tests\": [ \"assert($('div.row:has(button)'), 'Your buttons should all be wrapped within the same div element with the class \"row\".')\", \"assert($('div.row:has(button)').length > 0, 'Your buttons should all be wrapped within the same div element with the class \"row\".')\", \"assert($('div.col-xs-4:has(button)').length > 2, 'Each of your Bootstrap buttons should be wrapped within its own a div element with the class \"col-xs-4\".')\", \"assert(editor.match(//g) && editor.match(/\", \" \", \" \", \" \", \" \", \"
    \", \"

    #right-well

    \", \"
    \", \" \", \" \", \" \", \"\", \"
    \", \"

    jQuery Playground

    \", \"
    \", \"
    \", \"

    #left-well

    \", \"
    \", \" \", \" \", \" \", \"
    \", \"
    \", \"
    \", \"

    #right-well

    \", \"
    \", \" \", \" \", \" \", \"
    \", \"
    \", \"
    \", \"
    \", \"
    \" \"\" ], \"type\": \"waypoint\", \"challengeType\": 0"], "neg": []} {"query": "Challenge has an issue. User Agent is: \"Compare two arrays and return a new array with any items not found in both of the original arrays.\", \"Compare two arrays and return a new array with any items only found in one of the original arrays.\", \"Remember to use Read-Search-Ask if you get stuck. Try to pair program. Write your own code.\" ], \"challengeSeed\": [", "], \"tests\": [ \"assert(typeof(diff([1, 2, 3, 5], [1, 2, 3, 4, 5])) === \"object\", 'message: diff() should return an array.');\", \"assert.deepEqual(diff([\"diorite\", \"andesite\", \"grass\", \"dirt\", \"pink wool\", \"dead shrub\"], [\"diorite\", \"andesite\", \"grass\", \"dirt\", \"dead shrub\"]), [\"pink wool\"], 'message: [\"diorite\", \"andesite\", \"grass\", \"dirt\", \"pink wool\", \"dead shrub\"], [\"diorite\", \"andesite\", \"grass\", \"dirt\", \"dead shrub\"] should return [\"pink wool\"].');\", \"assert.includeMembers(diff([\"andesite\", \"grass\", \"dirt\", \"pink wool\", \"dead shrub\"], [\"diorite\", \"andesite\", \"grass\", \"dirt\", \"dead shrub\"]), [\"diorite\", \"pink wool\"], 'message: [\"andesite\", \"grass\", \"dirt\", \"pink wool\", \"dead shrub\"], [\"diorite\", \"andesite\", \"grass\", \"dirt\", \"dead shrub\"] should return [\"diorite\", \"pink wool\"].');\", \"assert.deepEqual(diff([\"andesite\", \"grass\", \"dirt\", \"dead shrub\"], [\"andesite\", \"grass\", \"dirt\", \"dead shrub\"]), [], 'message: [\"andesite\", \"grass\", \"dirt\", \"dead shrub\"], [\"andesite\", \"grass\", \"dirt\", \"dead shrub\"] should return [].');\", \"assert.deepEqual(diff([1, 2, 3, 5], [1, 2, 3, 4, 5]), [4], 'message: [1, 2, 3, 5], [1, 2, 3, 4, 5] should return [4].');\", \"assert.includeMembers(diff([1, \"calf\", 3, \"piglet\"], [1, \"calf\", 3, 4]), [\"piglet\", 4], 'message: [1, \"calf\", 3, \"piglet\"], [1, \"calf\", 3, 4] should return [\"piglet\", 4].');\", \"assert.deepEqual(diff([], [\"snuffleupagus\", \"cookie monster\", \"elmo\"]), [\"snuffleupagus\", \"cookie monster\", \"elmo\"], 'message: [], [\"snuffleupagus\", \"cookie monster\", \"elmo\"] should return [\"snuffleupagus\", \"cookie monster\", \"elmo\"].');\", \"assert.includeMembers(diff([1, \"calf\", 3, \"piglet\"], [7, \"filly\"]), [1, \"calf\", 3, \"piglet\", 7, \"filly\"], 'message: [1, \"calf\", 3, \"piglet\"], [7, \"filly\"] should return [1, \"calf\", 3, \"piglet\", 7, \"filly\"].');\" \"assert.sameMembers(diff([\"diorite\", \"andesite\", \"grass\", \"dirt\", \"pink wool\", \"dead shrub\"], [\"diorite\", \"andesite\", \"grass\", \"dirt\", \"dead shrub\"]), [\"pink wool\"], 'message: [\"diorite\", \"andesite\", \"grass\", \"dirt\", \"pink wool\", \"dead shrub\"], [\"diorite\", \"andesite\", \"grass\", \"dirt\", \"dead shrub\"] should return [\"pink wool\"].');\", \"assert.sameMembers(diff([\"andesite\", \"grass\", \"dirt\", \"pink wool\", \"dead shrub\"], [\"diorite\", \"andesite\", \"grass\", \"dirt\", \"dead shrub\"]), [\"diorite\", \"pink wool\"], 'message: [\"andesite\", \"grass\", \"dirt\", \"pink wool\", \"dead shrub\"], [\"diorite\", \"andesite\", \"grass\", \"dirt\", \"dead shrub\"] should return [\"diorite\", \"pink wool\"].');\", \"assert.sameMembers(diff([\"andesite\", \"grass\", \"dirt\", \"dead shrub\"], [\"andesite\", \"grass\", \"dirt\", \"dead shrub\"]), [], 'message: [\"andesite\", \"grass\", \"dirt\", \"dead shrub\"], [\"andesite\", \"grass\", \"dirt\", \"dead shrub\"] should return [].');\", \"assert.sameMembers(diff([1, 2, 3, 5], [1, 2, 3, 4, 5]), [4], 'message: [1, 2, 3, 5], [1, 2, 3, 4, 5] should return [4].');\", \"assert.sameMembers(diff([1, \"calf\", 3, \"piglet\"], [1, \"calf\", 3, 4]), [\"piglet\", 4], 'message: [1, \"calf\", 3, \"piglet\"], [1, \"calf\", 3, 4] should return [\"piglet\", 4].');\", \"assert.sameMembers(diff([], [\"snuffleupagus\", \"cookie monster\", \"elmo\"]), [\"snuffleupagus\", \"cookie monster\", \"elmo\"], 'message: [], [\"snuffleupagus\", \"cookie monster\", \"elmo\"] should return [\"snuffleupagus\", \"cookie monster\", \"elmo\"].');\", \"assert.sameMembers(diff([1, \"calf\", 3, \"piglet\"], [7, \"filly\"]), [1, \"calf\", 3, \"piglet\", 7, \"filly\"], 'message: [1, \"calf\", 3, \"piglet\"], [7, \"filly\"] should return [1, \"calf\", 3, \"piglet\", 7, \"filly\"].');\" ], \"MDNlinks\": [ \"Comparison Operators\","], "neg": []} {"query": "Challenge has an issue. User Agent is: .jumbotron .col-sm-8.col-sm-offset-2 form(method='POST') .col-sm-8.col-sm-offset-2.jumbotron form(method='POST', action=\"/forgot\") h1 Forgot Password input(type='hidden', name='_csrf', value=_csrf) .form-group", "button.btn.btn-primary(type='submit') i.fa.fa-key | Reset Password"], "neg": []} {"query": "Since the code is included in the URL after every change, once the user has made any code changes the back button will not work as expected as the browser history gets filled up with entries pointing to the same page but with different code in the URL. !", "pos": ["if (!codeUri.enabled) { return null; } location.hash = '?solution=' + codeUri.encode(encodeFcc(solution)); if (history && typeof history.replaceState === 'function') { history.replaceState( history.state, null, '?solution=' + codeUri.encode(encodeFcc(solution)) ); } else { location.hash = '?solution=' + codeUri.encode(encodeFcc(solution)); } return solution; },"], "neg": []} {"query": "Challenge has an issue. User Agent is: end(\"Bastian\", \"n\") should return true.');\", \"assert(end(\"Connor\", \"n\") === false, 'message: end(\"Connor\", \"n\") should return false.');\", \"assert(end(\"Walking on water and developing software from a specification are easy if both are frozen\", \"specification\") === false, '\"Walking on water and developing software from a specification are easy if both are frozen\", \"specification\") should return false.');\", \"assert(end(\"Walking on water and developing software from a specification are easy if both are frozen\", \"specification\") === false, 'message: end(\"Walking on water and developing software from a specification are easy if both are frozen\", \"specification\") should return false.');\", \"assert(end(\"He has to give me a new name\", \"name\") === true, 'message: end(\"He has to give me a new name\", \"name\") should return true.');\", \"assert(end(\"He has to give me a new name\", \"me\") === true, 'message: end(\"He has to give me a new name\", \"me\") should return true.');\", \"assert(end(\"If you want to save our world, you must hurry. We dont know how much longer we can withstand the nothing\", \"mountain\") === false, 'message: end(\"If you want to save our world, you must hurry. We dont know how much longer we can withstand the nothing\", \"mountain\") should return false.');\""], "neg": []} {"query": "I tried submitting a URL to camper news and somehow it got as a blank URL. The link I tried to add was but it just links to http:// I also can't edit or delete it, so I can't try fixing it.\nYup, I confirmed this with that URL. Did you make a change to disallow blank URLs that might affect this?\nNope. Didn't realize this was possible.\nI see the mistake I made, I clicked \"Submit\" then typed in the url and hit \"Submit\" again. Then on the next page the title is auto-filled out but the URL is not copied over so I hit submit again, which let it be a blank URL. URL should copy from previous page into the new textbox.\nI think I may have done the same thing.\nFor some reason the url value is not copied from the page URL. This requires some adjustments in the jade template. I will fix that.", "pos": [".col-xs-12.col-md-1 label.control-label.control-label-story-submission(for='name') Link .col-xs-12.col-md-11 input#story-url.form-control(placeholder='Paste your link here', name='Link') input#story-url.form-control(name='Link', ng-model='submitStory.url', disabled=\"disabled\", ng-init='submitStory.url=\"#{storyURL}\"') .form-group .col-xs-12.col-md-1 label.control-label.control-label-story-submission(for='name') Title"], "neg": []} {"query": "Hi, Now, once the myCar instance is created it can be used like any other object and can have its properties accessed and modified the same way you would usually. For example: var myCar.turboType = \"twin\"; we don't need var it should be myCar.turboType = \"twin\";\nWow, I can't believe I missed this in the proofreading pass! Thanks for pointing this out!", "pos": ["\"}\", \"Note that it is important to use the new keyword when calling a constructor. This is how javascript knows to create a new object and that all the references to this inside the constructor should be referring to this new object.\", \"Now, once the myCar instance is created it can be used like any other object and can have its properties accessed and modified the same way you would usually. For example:\", \"var myCar.turboType = \"twin\";\", \"myCar.turboType = \"twin\";\", \"Our myCar variable now has a property turboType with a value of \"twin\".\", \"In the editor, use the Car constructor to create a new instance and assign it to myCar.\", \"Then give myCar a nickname property with a string value.\""], "neg": []} {"query": "The Waypoint description says: It seems to me that the first paragraph should be the last, i.e., the assignment was given before the Waypoint's description.", "pos": ["\"id\": \"bad87fee1248bd9aedf08824\", \"title\": \"Add Different Margins to Each Side of an Element\", \"description\": [ \"Give the green box a margin of 40px on its top and left side, but only 20px on its bottom and right side.\", \"Sometimes you will want to customize an element so that it has a different margin on each of its sides.\", \"CSS allows you to control the margin of an element on all four sides with margin-top, margin-right, margin-bottom, and margin-left properties.\" \"CSS allows you to control the margin of an element on all four sides with margin-top, margin-right, margin-bottom, and margin-left properties.\", \"Give the green box a margin of 40px on its top and left side, but only 20px on its bottom and right side.\" ], \"tests\": [ \"assert($(\".green-box\").css(\"margin-top\") === \"40px\", 'Your green-box class should give the top of elements 40px of margin.')\","], "neg": []} {"query": "Challenge has an issue. User Agent is: \"For example, where([1,2,3,4], 1.5) should return 1 because it is greater than 1 (index 0), but less than 2 (index 1).\", \"Likewise, where([20,3,5], 19) should return 2 because it is less than 20 (index 2) and greater than 5 (index 1).\", \"For example, where([1,2,3,4], 1.5) should return 1 because it is greater than 1 (index 0), but less than 2 (index 1).\", \"Likewise, where([20,3,5], 19) should return 2 because once the array has been sorted it will look like [3,5,20] and 19 is less than 20 (index 2) and greater than 5 (index 1).\", \"Remember to use Read-Search-Ask if you get stuck. Write your own code.\" ], \"challengeSeed\": ["], "neg": []} {"query": "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", "pos": ["\"description\": [ \"Sometimes you want to add a 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 jQuery, which we'll learn about later.\", \"Replace your a element's href attribute with a #, also known as a hash symbol, to turn it into a dead link.\" \"Replace the value of your a element's href attribute with a #, also known as a hash symbol, to turn it into a dead link.\" ], \"tests\": [ \"assert($(\"a\").attr(\"href\") === \"#\", 'Your a element should be a dead link with a href attribute set to \"#\".')\""], "neg": []} {"query": "Challenge has an issue. User Agent is: 0, 'Create a ul element.')\", \"assert($(\"ul li\").length > 2, 'You should have three li elements within your ul element.')\", \"assert(editor.match(//g) && editor.match(/
      /g).length === editor.match(/
        ul element has a closing tag.')\", \"assert(editor.match(//g) && editor.match(/]/g) && editor.match(//g).length === editor.match(/]/g).length, 'Make sure your li elements have closing tags.')\" \"assert(editor.match(/
      /gi) && editor.match(/
        /gi).length === editor.match(/
          ul element has a closing tag.')\", \"assert(editor.match(//gi) && editor.match(/]/gi) && editor.match(//gi).length === editor.match(/]/gi).length, 'Make sure your li elements have closing tags.')\" ], \"challengeSeed\": [ \"\","], "neg": []} {"query": "here \"giving it a i element with the classes fa and fa-thumbs-up.\" shoud be \"an i\" and not \"a i\" Challenge has an issue. User Agent is: .svg file format. These icons are treated just like fonts. You can specify their size using pixels, and they will assume the font size of their parent HTML elements.\", \"The i element was originally used to make other elements italic, but is now commonly used for icons. You add the Font Awesome classes to the i element to turn it into an icon, for example:\", \"<i class=\"fa fa-info-circle\"></i>\", \"Use Font Awesome to add a thumbs-up icon to your like button by giving it a i element with the classes fa and fa-thumbs-up.\" \"Use Font Awesome to add a thumbs-up icon to your like button by giving it an i element with the classes fa and fa-thumbs-up.\" ], \"tests\": [ \"assert($(\"i\").hasClass(\"fa fa-thumbs-up\"), 'Add an i element with the classes fa and fa-thumbs-up.')\","], "neg": []} {"query": "Challenge [Bonfire: Validate US Telephone Numbers] This actually returns false as the test says it should, but the test does not pass. The rest of the tests pass in my actual telephoneCheck() function.\nThanks for the report! It looks like that test was actually testing against the string rather than like the message said. I have submitted a PR to correct this.\nok good so i'm not insane. just mental. +1:", "pos": ["\"assert(telephoneCheck(\"(555)555-5555\") === true, 'message: telephoneCheck(\"(555)555-5555\") should return true.');\", \"assert(telephoneCheck(\"1(555)555-5555\") === true, 'message: telephoneCheck(\"1(555)555-5555\") should return true.');\", \"assert(telephoneCheck(\"1 555 555 5555\") === true, 'message: telephoneCheck(\"1 555 555 5555\") should return true.');\", \"assert(telephoneCheck(\"555-555-5555\") === true, 'message: telephoneCheck(\"555-555-5555\") should return true.');\", \"assert(telephoneCheck(\"1 456 789 4444\") === true, 'message: telephoneCheck(\"1 456 789 4444\") should return true.');\", \"assert(telephoneCheck(\"123**&!!asdf#\") === false, 'message: telephoneCheck(\"123**&!!asdf#\") should return false.');\", \"assert(telephoneCheck(\"55555555\") === false, 'message: telephoneCheck(\"55555555\") should return false.');\",", "\"assert(telephoneCheck(\"(275)76227382\") === false, 'message: telephoneCheck(\"(275)76227382\") should return false.');\", \"assert(telephoneCheck(\"2(757)6227382\") === false, 'message: telephoneCheck(\"2(757)6227382\") should return false.');\", \"assert(telephoneCheck(\"2(757)622-7382\") === false, 'message: telephoneCheck(\"2(757)622-7382\") should return false.');\", \"assert(telephoneCheck(\"555)-555-5555\") === false, 'message: telephoneCheck(\"555)555-5555\") should return false.');\", \"assert(telephoneCheck(\"555)-555-5555\") === false, 'message: telephoneCheck(\"555)-555-5555\") should return false.');\", \"assert(telephoneCheck(\"(555-555-5555\") === false, 'message: telephoneCheck(\"(555-555-5555\") should return false.');\" ], \"challengeSeed\": ["], "neg": []} {"query": "Ever since we the last test case to , there have been questions about it. We either need to add several additional test cases which have a later number which does not meet the test criteria retained, or alter earlier test cases to have that same condition. Relevant Text (Emphasis ): < Drop the elements of an array (first argument), starting from the front, until the predicate (second argument) returns true. Existing Test Case: We do believe that this \"early exit\" solution is important and should be supported by test cases.\nRef: for an example of the sort of issue we see.\nI'll do this. Note I've never actually made a PR before, anywhere.", "pos": ["\"drop([1, 2, 3], function(n) {return n < 3; });\" ], \"tests\": [ \"assert.deepEqual(drop([1, 2, 3, 4], function(n) {return n>= 3;}), [3, 4], 'message: drop([1, 2, 3, 4], function(n) {return n >= 3;}) should return [3, 4].');\", \"assert.deepEqual(drop([1, 2, 3, 4], function(n) {return n >= 3;}), [3, 4], 'message: drop([1, 2, 3, 4], function(n) {return n >= 3;}) should return [3, 4].');\", \"assert.deepEqual(drop([0, 1, 0, 1], function(n) {return n === 1;}), [1, 0, 1], 'message: drop([0, 1, 0, 1], function(n) {return n === 1;}) should return [1, 0, 1].');\", \"assert.deepEqual(drop([1, 2, 3], function(n) {return n > 0;}), [1, 2, 3], 'message: drop([1, 2, 3], function(n) {return n > 0;}) should return [1, 2, 3].');\", \"assert.deepEqual(drop([1, 2, 3, 4], function(n) {return n > 5;}), [], 'message: drop([1, 2, 3, 4], function(n) {return n > 5;}) should return [].');\", \"assert.deepEqual(drop([1, 2, 3, 7, 4], function(n) {return n > 3;}), [7, 4], 'message: drop([1, 2, 3, 7, 4], function(n) {return n > 3;}) should return [7, 4].');\","], "neg": []} {"query": "I the \"thumbs-up\" icon to the \"Info\" button and I still passed the challenge. I don't know if this was intended to help. Cheers! :D Challenge has an issue. User Agent is: i element with the classes fa and fa-thumbs-up.')\", \"assert($(\"i.fa-thumbs-up\").parent().text().match(/Like/gi), 'Your fa-thumbs-up icon should be located within the Like button.')\", \"assert($(\"button\").children(\"i\").length > 0, 'Nest your i element within your button element.')\", \"assert(editor.match(//g), 'Make sure your i element has a closing tag.')\" ],"], "neg": []} {"query": "Challenge has an issue. User Agent is: \"In the JSON that we receive data from Free Code Camp's Cat Photo API.\", \"We've seen from the last two lessons that each object in our JSON array contains an imageLink key with a value that is the url of a cat's image.\", \"When we're looping through these objects, let's use this imageLink property to display this image in an img element.\", \"Here's the code that does this:\","], "neg": []} {"query": "Anywhere from 1000px width to when the UI goes into responsive mode the numbers on the check list move into it's respective check box. Image posted bellow \"screen .col-xs-3.col-sm-1.col-md-2.padded-ionic-icon.text-center .col-xs-2.col-sm-1.col-md-2.padded-ionic-icon.text-right input(type='checkbox' class='challenge-list-checkbox') .col-xs-9.col-sm-11.col-md-10 .col-xs-10.col-sm-11.col-md-10 li.step-text.wrappable!= step .col-xs-12.col-sm-12.col-md-8 .embed-responsive.embed-responsive-16by9", "extends ../layout-wide block content .row .col-md-4.bonfire-top .col-md-4 h4.text-center= name hr ol for step, index in description .row.checklist-element(id=\"#{dashedName + index}\") .col-xs-3.col-sm-1.col-md-2.padded-ionic-icon.text-center .col-xs-2.col-sm-1.col-md-2.padded-ionic-icon.text-right input(type='checkbox' class='challenge-list-checkbox') .col-xs-9.col-sm-11.col-md-10 .col-xs-10.col-sm-11.col-md-10 li.step-text.wrappable!= step .col-xs-12.col-sm-12.col-md-8 .embed-responsive.embed-responsive-16by9"], "neg": []} {"query": "Challenge has an issue. User Agent is: p.negative-10 \"I'm a massage therapist and Stay-at-home-dad. I learned Hypercard, then Rails, but now I feel at home with JavaScript.\" p.negative-10 \"Cookbook author and stay-at-home-dad. Started coding as a kid, got distracted, but now I'm back in full JavaScript force!\" .col-xs-12.col-sm-4.col-md-3.team-member h3.negative-10.text-nowrap Michael Johnson h4.negative-10.text-nowrap Nonprofit Coordinator", "h4.negative-10.text-nowrap Live Content Manager img.profile-image(src='https://s3.amazonaws.com/freecodecamp/jason-rueckert.jpg' alt=\"Jason Rueckert's picture\") h4.text-nowrap Seattle, Washington p.negative-10 \"My high school job was testing basketball shoes for Nike. I learned code to work smarter, not harder. I have no thyroid.\" No newline at end of file p.negative-10 \"My high school job was testing basketball shoes for Nike. I learned code to work smarter, not harder. I have no thyroid.\" "], "neg": []} {"query": "Challenge has an issue. User Agent is: \"challengeEntryPoint\": \"titleCase(\"I'm a little tea pot\")\", \"challengeEntryPoint\": \"titleCase(\"I'm a little tea pot\");\", \"challengeSeed\": \"function titleCase(str) {n return str;rn}\", \"tests\": [ \"expect(titleCase(\"I'm a little tea pot\")).to.be.a('String');\","], "neg": []} {"query": "Return statement Issue: JS Line 3: Return statement text should be \"Greater than 10\" instead of \"10 or bigger\" Challenge Link : Browser Version : v47.0.2526.106 (64-bit) Operating System Version : Mac OS X 10.11.2 Steps to reproduce: to the above challenge link and check the text. (Optional)Read/Run the below test case in the above waypoint challenge page myTest(10) should return \"Between 5 and 10\" Screenshot 1: ! Screenshot 2: !\n:+1: yes \"10 or bigger\" means\nThis same waypoint has some more minor bugs associated with it (in the test cases). They are : To save PR Reviewer time, I am merging this very minor issues in one and creating one commit to fix this.", "pos": ["\"challengeSeed\": [ \"function myTest(val) {\", \" if(val > 10) {\", \" return \"10 or Bigger\";\", \" return \"Greater than 10\";\", \" }\", \" \", \" if(val < 5) {\",", "\"\" ], \"solutions\": [ \"function myTest(val) {n if(val > 10) {n return \"10 or Bigger\";n } else if(val < 5) {n return \"Smaller than 5\";n } else {n return \"Between 5 and 10\";n }n}\" \"function myTest(val) {n if(val > 10) {n return \"Greater than 10\";n } else if(val < 5) {n return \"Smaller than 5\";n } else {n return \"Between 5 and 10\";n }n}\" ], \"tests\": [ \"assert(code.match(/else/g).length > 1, 'message: You should have at least two else statements');\", \"assert(code.match(/if/g).length > 1, 'message: You should have at least two if statements');\", \"assert(myTest(0) === \"Smaller than 5\", 'message: myTest(4) should return \"Smaller than 5\"');\", \"assert(myTest(5) === \"Between 5 and 10\", 'message: myTest(5) should return \"Smaller than 5\"');\", \"assert(myTest(0) === \"Smaller than 5\", 'message: myTest(0) should return \"Smaller than 5\"');\", \"assert(myTest(5) === \"Between 5 and 10\", 'message: myTest(5) should return \"Between 5 and 10\"');\", \"assert(myTest(7) === \"Between 5 and 10\", 'message: myTest(7) should return \"Between 5 and 10\"');\", \"assert(myTest(10) === \"Between 5 and 10\", 'message: myTest(10) should return \"Between 5 and 10\"');\", \"assert(myTest(12) === \"10 or Bigger\", 'message: myTest(12) should return \"10 or Bigger\"');\" \"assert(myTest(12) === \"Greater than 10\", 'message: myTest(12) should return \"Greater than 10\"');\" ], \"type\": \"waypoint\", \"challengeType\": \"1\","], "neg": []} {"query": "With the the new year now recently 2016... The test still stays: friendly([\"2015-07-01\", \"2015-07-04\"]) should return [\"July 1st\",\"4th\"]. But shouldn't both years be ommited only if first year is the current year (which is 2016, not 2015). However, the test also says: friendly([\"2016-03-01\", \"2016-05-05\"]) should return [\"March 1st\",\"May 5th\"] which implies it is following the rule that the current year is 2016. Am I missing something here?\nThis is for Bonfire: Friendly Dates.\nSounds like we need to update the tests on this one . . . or maybe make them more generic.\nI incremented the year in every test except the last one in , some of the tests didn't need to be updated but I did it anyways. That should be enough for passing the tests during 2016, but I think those tests could be more generic\nI think this issue can be closed now.", "pos": ["\" return str;\", \"}\", \"\", \"friendly(['2015-07-01', '2015-07-04']);\" \"friendly(['2016-07-01', '2016-07-04']);\" ], \"tests\": [ \"assert.deepEqual(friendly(['2015-07-01', '2015-07-04']), ['July 1st','4th'], 'message: friendly([\"2015-07-01\", \"2015-07-04\"]) should return [\"July 1st\",\"4th\"].');\", \"assert.deepEqual(friendly(['2015-12-01', '2016-02-03']), ['December 1st','February 3rd'], 'message: friendly([\"2015-12-01\", \"2016-02-03\"]) should return [\"December 1st\",\"February 3rd\"].');\", \"assert.deepEqual(friendly(['2015-12-01', '2017-02-03']), ['December 1st, 2015','February 3rd, 2017'], 'message: friendly([\"2015-12-01\", \"2017-02-03\"]) should return [\"December 1st, 2015\",\"February 3rd, 2017\"].');\", \"assert.deepEqual(friendly(['2016-03-01', '2016-05-05']), ['March 1st','May 5th'], 'message: friendly([\"2016-03-01\", \"2016-05-05\"]) should return [\"March 1st\",\"May 5th\"]');\", \"assert.deepEqual(friendly(['2017-01-01', '2017-01-01']), ['January 1st, 2017'], 'message: friendly([\"2017-01-01\", \"2017-01-01\"]) should return [\"January 1st, 2017\"].');\", \"assert.deepEqual(friendly(['2016-07-01', '2016-07-04']), ['July 1st','4th'], 'message: friendly([\"2016-07-01\", \"2016-07-04\"]) should return [\"July 1st\",\"4th\"].');\", \"assert.deepEqual(friendly(['2016-12-01', '2017-02-03']), ['December 1st','February 3rd'], 'message: friendly([\"2016-12-01\", \"2017-02-03\"]) should return [\"December 1st\",\"February 3rd\"].');\", \"assert.deepEqual(friendly(['2016-12-01', '2018-02-03']), ['December 1st, 2016','February 3rd, 2018'], 'message: friendly([\"2016-12-01\", \"2018-02-03\"]) should return [\"December 1st, 2016\",\"February 3rd, 2018\"].');\", \"assert.deepEqual(friendly(['2017-03-01', '2017-05-05']), ['March 1st','May 5th'], 'message: friendly([\"2017-03-01\", \"2017-05-05\"]) should return [\"March 1st\",\"May 5th\"]');\", \"assert.deepEqual(friendly(['2018-01-01', '2018-01-01']), ['January 1st, 2018'], 'message: friendly([\"2018-01-01\", \"2018-01-01\"]) should return [\"January 1st, 2018\"].');\", \"assert.deepEqual(friendly(['2022-09-05', '2023-09-04']), ['September 5th, 2022','September 4th, 2023'], 'message: friendly([\"2022-09-05\", \"2023-09-04\"]) should return [\"September 5th, 2022\",\"September 4th, 2023\"].');\" ], \"MDNlinks\": ["], "neg": []} {"query": "Challenge has an issue. User Agent is: \"(function(t) { if(typeof t !== 'undefined') { return \"Total = \" + t; } else { return \"Total is undefined\";}})(total);\" \"(function(){if(typeof total !== 'undefined') { return \"total = \" + total; } else { return \"total is undefined\";}})()\" ], \"solutions\": [ \"var myArr = [ 2, 3, 4, 5, 6];nvar total = 0;nnfor (var i = 0; i < myArr.length; i++) {n total += myArr[i];n}\""], "neg": []} {"query": "I really do like the SideCar (I'm assuming that's what your using) Map menu! It gives really quick access to previous challenges. It would cool if the \"collapse all challenges\" area was fixed to top and everything would slide under it. That way, users wouldn't have to scroll all the way up or down if they're looking for something specific - they would just collapse everything and go to the specific component they're looking for.\nI agree. Totally makes sense to have it fixed to the top somehow.\nI'm going to start working on this now, should have a PR open shortly.", "pos": ["* based off of https://github.com/gitterHQ/sidecar * license: MIT */ .map { display: flex; flex-direction: column; max-height: 90vh; } .map-aside { z-index: 20000;", "z-index: 100; } .map-fixed-header { background: white; z-index: 1; flex: 1; padding-bottom: 25px; } .map-accordion { flex: 9; overflow-y: auto; } .map-aside-action-item { display: flex; /* main axis */", "}); if (lastChallenge.length) { lastChallenge = lastChallenge[lastChallenge.length - 1]; var scrollTo = $(lastChallenge).offset().top - 250; $('html, body').scrollTop(scrollTo); var scrollTo = $(lastChallenge).offset().top - 400; $('.map-accordion').scrollTop(scrollTo); } }", "extends ../layout-wide block content .text-center h1 Challenge Map p Required challenges are marked with a * .row .col-xs-10.col-xs-offset-1.col-sm-6.col-sm-offset-3.col-md-4.col-md-offset-4 .btn.btn-primary.btn-block.active#showAll Collapse all challenges hr #accordion for superBlock, index in superBlocks h2 i.fa.fa-caret-down |   a(data-toggle='collapse', data-parent='#accordion', href='#collapse'+superBlock.name.split(' ').join('-')) | #{superBlock.name} div.margin-left-10(id = 'collapse'+superBlock.name.split(' ').join('-') class = \"collapse in map-collapse no-transition\") #nested for challengeBlock in superBlock.blocks h3 i.fa.fa-caret-down |   a(data-toggle='collapse', data-parent='#nested', href='#nested-collapse'+challengeBlock.name.replace(/(W)/gi, '').split(' ').join('-')) | #{challengeBlock.name} (#{challengeBlock.time}) div.margin-left-10(id = \"nested-collapse\"+challengeBlock.name.replace(/W/gi, '').split(' ').join('-') class = \"collapse in map-collapse no-transition\") .button-spacer for challenge in challengeBlock.challenges if challenge.completed p.text-primary.ion-checkmark-circled.padded-ionic-icon.negative-15(name=\"#{challenge.dashedName}\")     a(href=\"/challenges/#{challenge.dashedName}\" target='_parent') = challenge.title span.sr-only= \" Complete\" else if challenge.isRequired p.slightly-faded.ion-ios-circle-outline.padded-ionic-icon.negative-15(name=\"#{challenge.dashedName}\")     a(name=\"#{challenge.dashedName}\" target='_parent' href=\"/challenges/#{challenge.dashedName}\" class=challenge.isComingSoon ? 'disabled' : '') span= challenge.title span.sr-only= \" Incomplete\" if challenge.markNew span.text-success.small     strong em New if challengeBlock.isComingSoon span.text-success.small     strong em Coming Soon span.text-primary     strong * else p.slightly-faded.ion-ios-circle-outline.padded-ionic-icon.negative-15(name=\"#{challenge.dashedName}\")     a(name=\"#{challenge.dashedName}\" target='_parent' href=\"/challenges/#{challenge.dashedName}\" class=challenge.isComingSoon ? 'disabled' : '') span= challenge.title span.sr-only= \" Incomplete\" if challenge.markNew span.text-success.small     strong em New if challengeBlock.isComingSoon span.text-success.small     strong em Coming Soon .spacer .map .map-fixed-header.text-center h1 Challenge Map p Required challenges are marked with a * .row .col-xs-10.col-xs-offset-1.col-sm-6.col-sm-offset-3.col-md-4.col-md-offset-4 .btn.btn-primary.btn-block.active#showAll Collapse all challenges hr #accordion.map-accordion for superBlock, index in superBlocks h2 i.fa.fa-caret-down |   a(data-toggle='collapse', data-parent='#accordion', href='#collapse'+superBlock.name.split(' ').join('-')) | #{superBlock.name} div.margin-left-10(id = 'collapse'+superBlock.name.split(' ').join('-') class = \"collapse in map-collapse no-transition\") #nested for challengeBlock in superBlock.blocks h3 i.fa.fa-caret-down |   a(data-toggle='collapse', data-parent='#nested', href='#nested-collapse'+challengeBlock.name.replace(/(W)/gi, '').split(' ').join('-')) | #{challengeBlock.name} (#{challengeBlock.time}) div.margin-left-10(id = \"nested-collapse\"+challengeBlock.name.replace(/W/gi, '').split(' ').join('-') class = \"collapse in map-collapse no-transition\") .button-spacer for challenge in challengeBlock.challenges if challenge.completed p.text-primary.ion-checkmark-circled.padded-ionic-icon.negative-15(name=\"#{challenge.dashedName}\")     a(href=\"/challenges/#{challenge.dashedName}\" target='_parent') = challenge.title span.sr-only= \" Complete\" else if challenge.isRequired p.slightly-faded.ion-ios-circle-outline.padded-ionic-icon.negative-15(name=\"#{challenge.dashedName}\")     a(name=\"#{challenge.dashedName}\" target='_parent' href=\"/challenges/#{challenge.dashedName}\" class=challenge.isComingSoon ? 'disabled' : '') span= challenge.title span.sr-only= \" Incomplete\" if challenge.markNew span.text-success.small     strong em New if challengeBlock.isComingSoon span.text-success.small     strong em Coming Soon span.text-primary     strong * else p.slightly-faded.ion-ios-circle-outline.padded-ionic-icon.negative-15(name=\"#{challenge.dashedName}\")     a(name=\"#{challenge.dashedName}\" target='_parent' href=\"/challenges/#{challenge.dashedName}\" class=challenge.isComingSoon ? 'disabled' : '') span= challenge.title span.sr-only= \" Incomplete\" if challenge.markNew span.text-success.small     strong em New if challengeBlock.isComingSoon span.text-success.small     strong em Coming Soon .spacer "], "neg": []} {"query": "Challenge has an issue. User Agent is: Hello Paragraph

          \" ], \"tests\": [ \"assert.isTrue((/Kitty(s)+ipsum(s)+dolor/gi).test($(\"p\").text()), 'message: Your p element should contain the first few words of the provided kitty ipsum text.');\" \"assert.isTrue((/Kitty(s)+ipsum/gi).test($(\"p\").text()), 'message: Your p element should contain the first few words of the provided kitty ipsum text.');\" ], \"challengeType\": 0, \"nameEs\": \"Llena espacios con texto de relleno\","], "neg": []} {"query": "Challenge has an issue. User Agent is: font-size CSS property, like this:\", \"
          h1 {
            font-size: 30px;
          }
          \", \"Create a second p element with the following kitty ipsum text: Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.\", \"Inside the same <style> tag that we created for your red-text class, set the font-size of all p elements to 16 pixels (16px).\" \"Inside the same <style> tag that we created for your red-text class, set the font-size of all p elements to 16 pixels (16px).\", \"Note
          Due to browser implementation differences, you may need to be at 100% zoom to pass the tests on this challenge.\"
          ], \"challengeSeed\": [ \"\", \"CatPhotoApp\" \"CatPhotoApp\" ], \"tests\": [ \"assert($('a').css('color') == 'rgb(0, 0, 0)', 'message: The color of the anchor tag text should be black.')\"", "\" \", \" \", \"\", \"CatPhotoApp\" \"CatPhotoApp\" ], \"tests\": [ \"assert($('a').css('color') == 'rgb(0, 0, 0)', 'message: The anchor tag color should remain black, only add CSS rules for the :hover state.');\","], "neg": []} {"query": "There should be a test case for a target ending that appears anywhere else other than the end of the string. The purpose of the function is to determine whether the 'target' string appears at the end of the given string (str). The issue is that the code below will pass when it shouldn't. It looks for the first appearance of the target in the string (str), creates a substring from that to the end, and returns if it's equal to the target string. There are no test cases for the case when the target appears anywhere else than the end. \"screenconfirmEnding(\"Bastian\", \"n\") should return true.');\", \"assert(confirmEnding(\"Congratulation\", \"on\") === true, 'message: confirmEnding(\"Congratulation\", \"on\") should return true.');\", \"assert(confirmEnding(\"Connor\", \"n\") === false, 'message: confirmEnding(\"Connor\", \"n\") should return false.');\", \"assert(confirmEnding(\"Walking on water and developing software from a specification are easy if both are frozen\", \"specification\") === false, 'message: confirmEnding(\"Walking on water and developing software from a specification are easy if both are frozen\", \"specification\") should return false.');\", \"assert(confirmEnding(\"He has to give me a new name\", \"name\") === true, 'message: confirmEnding(\"He has to give me a new name\", \"name\") should return true.');\","], "neg": []} {"query": " 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; } ``` "], "neg": []} {"query": " 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 "], "neg": []} {"query": "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): !", "pos": [" \u0639\u0631\u0628\u064a \u4e2d\u6587 Portugu\u00eas \u0440\u0443\u0441\u0441\u043a\u0438\u0439 \u0420\u0443\u0441\u0441\u043a\u0438\u0439 Espa\u00f1ol \u0395\u03bb\u03bb\u03b7\u03bd\u03b9\u03ba\u03ac "], "neg": []} {"query": "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): !", "pos": ["
          \u6b64\u6307\u5357\u53ef\u9605\u8bfb\u7684\u8bed\u8a00\u7248\u672c 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
          "], "neg": []} {"query": "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): !", "pos": [" \u0639\u0631\u0628\u064a \u4e2d\u6587 Portugu\u00eas \u0440\u0443\u0441\u0441\u043a\u0438\u0439 \u0420\u0443\u0441\u0441\u043a\u0438\u0439 Espa\u00f1ol \u0395\u03bb\u03bb\u03b7\u03bd\u03b9\u03ba\u03ac "], "neg": []} {"query": "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): !", "pos": [" \u0639\u0631\u0628\u064a \u4e2d\u6587 Portugu\u00eas \u0440\u0443\u0441\u0441\u043a\u0438\u0439 \u0420\u0443\u0441\u0441\u043a\u0438\u0439 Espa\u00f1ol \u0395\u03bb\u03bb\u03b7\u03bd\u03b9\u03ba\u03ac "], "neg": []} {"query": "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): !", "pos": [" \u0639\u0631\u0628\u0649 \u4e2d\u6587 Portugu\u00eas \u0440\u0443\u0441\u0441\u043a\u0438\u0439 \u0420\u0443\u0441\u0441\u043a\u0438\u0439 Espa\u00f1ol \u0395\u03bb\u03bb\u03b7\u03bd\u03b9\u03ba\u03ac "], "neg": []} {"query": "Describe the bug If the user's code does not build there are no logs informing them of this. To Reproduce Steps to reproduce the behavior: locally, to (a); ('a'); postResult postResult, oldLog }; })();", "`); } catch (err) { if (__userCodeWasExecuted) { // rethrow error, since test failed. throw err; } else { // report errors to dev console (not the editor console, since the test // may still pass) __utils.oldLog(err); } testResult = eval(e.data.testString); }"], "neg": []} {"query": "Describe your problem: Paragraph breaks in challenge descriptions that are present in production are missing in the master branch. The blocks of text that are paragraphs in production are only separated by single newline characters in the source markdown (on the master branch). This is not enough to push them into paragraphs - they need to be separated by an entire empty line. Add a Link to the page with the problem: The problem is ubiquitous, but a good example is the which looks like this on live: ! and master: ! From , live: ! and master: !\nI don't think this problem can be solved by changing the parser, since it's behaving correctly when given blocks of text are separated by an empty line. The markdown itself will need changing, but it isn't as simple as globally replacing -since that will mess up any code blocks and any embedded html. However, as long as it's restricted to text, it should be safe. Edit: 'safe' assuming the challenge was well formatted in the first case. The Project Euler challenges are a bit messy and will need dealing with separately.\nThis used to not be a problem. Something has changed recently.\nAny idea when it was working? I couldn't find any obvious changes in the parser or in the challenges, and the first challenge has (probably) been wrong since .\nTurns out I wasn't looking hard enough. My PR, caused it, so I'll just revert that if I can't come up with a better solution.", "pos": ["\"@commitlint/cli\": \"^7.0.0\", \"@commitlint/config-conventional\": \"^7.0.1\", \"@commitlint/travis-cli\": \"^7.0.0\", \"@freecodecamp/challenge-md-parser\": \"^1.0.0\", \"@freecodecamp/challenge-md-parser\": \"^0.0.1\", \"@semantic-release/changelog\": \"^2.0.2\", \"@semantic-release/git\": \"^5.0.0\", \"babel-cli\": \"^6.3.17\","], "neg": []} {"query": " "], "neg": []} {"query": "Describe the bug The PayPal sdk gets called by the local site, even when there are no keys specified in .env To Reproduce Steps to reproduce the behavior: to any page with a donation component the console a 400 error Expected behavior If the keys are missing, PayPal should not be contacted. Screenshots !\n/cc\nHello guys! Does this happen on page or somewhere else too? Can't recreate it anymore, happend only once. I'd like to help with that issue if you don't mind Also, I noticed PaypalButton has a typo -in props, example:\nit should happen if you hard refresh on donation page. (and on donation modal) That script loads the button. A solution would be to check for paypalClientId in the render of PaypalButton component and return PayPalButtonScriptLoader only if paypalClientId is truthy.\nPR is ready. Could you please take a look? Also about the Stripe issue. I'm not sure if it's expected/known but if I don't configure the key for stripe, the page isn't loading for me at all. \"CleanShot let queries = `?client-id=${this.props.clinetId}&disable-funding=credit,card`; let queries = `?client-id=${this.props.clientId}&disable-funding=credit,card`; if (subscription) queries += '&vault=true'; scriptLoader(", "} const propTypes = { clinetId: PropTypes.string, clientId: PropTypes.string, createOrder: PropTypes.func, createSubscription: PropTypes.func, donationAmount: PropTypes.number,", "render() { const { duration, planId, amount } = this.state; const isSubscription = duration !== 'onetime'; if (!paypalClientId) { return null; } return ( clinetId={paypalClientId} clientId={paypalClientId} createOrder={(data, actions) => { return actions.order.create({ purchase_units: ["], "neg": []} {"query": "", "Select which project you want to contribute to, and you will see a list of available languages for translation. ![Image - List of available languages](./images/crowdin/languages.png) ![Image - List of available languages](https://contribute.freecodecamp.org/images/crowdin/languages.png) Select the language you want to work on, and you will see the complete file tree. ![Image - List of available files](./images/crowdin/file-tree.png) ![Image - List of available files](https://contribute.freecodecamp.org/images/crowdin/file-tree.png) Each file and folder will show a progress bar. The **blue** portion of the progress bar indicates what percentage of the file has been translated, while the **green** portion of the progress bar indicates what percentage of the file has been approved by the proofreading team.", "## Translate the File ![Image - Editor View](./images/crowdin/editor.png) ![Image - Editor View](https://contribute.freecodecamp.org/images/crowdin/editor.png) Crowdin separates a document into translatable \"strings\", usually sentences. Each string is translated individually. Referring to the image above:", "When you attempt to save a translation, you may see a warning message appear with a notification regarding your proposed translation. ![Image - QA Warning Message](./images/crowdin/qa-message.png) ![Image - QA Warning Message](https://contribute.freecodecamp.org/images/crowdin/qa-message.png) This message appears when Crowdin's QA system has identified a potential error in the proposed translation. In this example, we have modified the text of a `` tag and Crowdin has caught that."], "neg": []} {"query": "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): ! !", "pos": ["description, instructions, translationPending, superBlock superBlock, block } }, isChallengeCompleted,", "title, description, superBlock, block, translationPending } },", " block={blockName} block={block} isCompleted={isChallengeCompleted} superBlock={superBlock} translationPending={translationPending}", "challengeType helpCategory superBlock block translationPending fields { blockName"], "neg": []} {"query": "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.", "pos": ["## --seed-contents-- ```html ``` # --solutions--", "## --seed-contents-- ```jsx ``` # --solutions--", "You can `GET` `/api/convert` with a single parameter containing an accepted number and unit and have it converted. (Hint: Split the input by looking for the index of the first character which will mark the start of the unit) ```js ``` You can convert `'gal'` to `'L'` and vice versa. (1 gal to 3.78541 L)", "## --seed-contents-- ```js ``` # --solutions--"], "neg": []} {"query": "

          Click here to view more cat photos.

          \"A --fcc-editable-region-- "], "neg": []} {"query": "Describe the bug A clear and concise description of what the bug is. In this string, we are missing code tags around the word . We can change it to this string Here is the file If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this.\nHey, I can do it\nHey ! Could you please assign it to me. I would be glad to start contributing in open-source with freeCodeCamp.\nThere is no assignment, you can open a PR, after you have read out our guidelines", "pos": ["# --description-- JavaScript is a powerful language which allows you to build websites that are interactive. To get started, create your standard HTML boilerplate with a `DOCTYPE`, `html`, `head`, and `body`. Include a `title` element and a `link` for your stylesheet, and your `meta` tag for the `charset`. Then, create a `div` element with the id `game` within your `body`. Use the text `RPG - Dragon Repeller` for your `title` element. JavaScript is a powerful language which allows you to build websites that are interactive. To get started, create your standard HTML boilerplate with a `DOCTYPE`, `html`, `head`, and `body`. Include a `title` element and a `link` for your stylesheet, and your `meta` tag for the `charset`. Then, create a `div` element with `id` set to `game` within your `body`. Use the text `RPG - Dragon Repeller` for your `title` element. # --hints--"], "neg": []} {"query": "Creating a new issue specifically to track discussion for the tag system - spinning off of . This also follows up on\nHere's some notes I wrote down from our meeting: Make a \"tags\" dropdown or something expandable in the block descriptions. When expanded, it would list all the tags that are used in steps within that block. When you click on a tag, it filters the steps in the grid display to only show steps with that tag.\nJust throwing out some more requirements/suggestions/questions on what we would need to do to enhance accessibility. The user would need to know what tag the grid is currently filtered on (or if not filtered at all), even if the tags dropdown is contracted. It might be helpful to include a \"clear filter\" button so that keyboard users don't have to navigate through the tags in order to undo a filter. This button could be displayed only when the list is filtered. The previous/next step keyboard shortcuts will come in handy here to allow users to quickly go through the filtered steps until they find what they are looking for. I've heard remarks in the past that these particular shortcuts are intended for power users and thus discoverability isn't a big concern. But with this functionality I think they are now intended for everyone and we should make sure that everyone knows they are available. If we are going to list all of the possible tags in the dropdown then the tags themselves would need to be implemented with an element that can communicate its state (i.e. whether it is the current filter). A would work using the attribute (this is probably my preferred suggestion at this point). A checkbox would work, although a group of checkboxes usually allows for multiple checkboxes to be selected, so we might be going against expected behavior in this case. Another option would be to use a for the tags. Then we wouldn't need a separate dropdown for this (or a clear button), but we would most likely need to add a button since we wouldn't want the filter to apply when the user is merely scrolling through list to view the filters.\nFor this design, the goal was to create tags with topics that will show up under the \"Start Project\" button. When clicked, they will highlight the blocks of steps that are connected to the tag\u2019s subject. While designing, I had the following considerations in mind: People with visual impairments should be able to use this feature like everyone else, therefore we shouldn\u2019t rely solely on color or contrast to differentiate the relevant numbersOne posible option could be to have a small text somewhere explaining what the tags do for those who are not familiar enough with technology and don\u2019t understand that these are linksIf there could potentially be like 50 tags, we need to come up with a way to make them look easy on the eye so the users will want to interact with them and not be intimidated or confused, otherwise if they look cluttered users will ignore them due to how difficult they are to read. This is why I made the tags a bit bigger, especially because the tag section can be hidden as you'll see in the design The final draft I made today can be found on the lower right side of the figma file, the frame where the flow starts is called \"Second iteration\". If you choose this frame you can interact with the prototype, here's a screenshot for reference: \"Screen \"node\": true /* * ENVIRONMENTS * ================= */ // Define globals exposed by Node.js. \"node\": true, /* * ENFORCING OPTIONS * ================= */ // Force all variable names to use either camelCase style or UPPER_CASE // with underscores. \"camelcase\": true, // Prohibit use of == and != in favor of === and !==. \"eqeqeq\": true, // Suppress warnings about == null comparisons. \"eqnull\": true, // Enforce tab width of 2 spaces. \"indent\": 2, // Prohibit use of a variable before it is defined. \"latedef\": true, // Require capitalized names for constructor functions. \"newcap\": true, // Enforce use of single quotation marks for strings. \"quotmark\": \"single\", // Prohibit trailing whitespace. \"trailing\": true, // Prohibit use of explicitly undeclared variables. \"undef\": true, // Warn when variables are defined but never used. \"unused\": true, // Enforce line length to 80 characters \"maxlen\": 80 }", " { /* * ENVIRONMENTS * ================= */ // Define globals exposed by modern browsers. \"browser\": true, // Define globals exposed by jQuery. \"jquery\": true, /* * ENFORCING OPTIONS * ================= */ // Force all variable names to use either camelCase style or UPPER_CASE // with underscores. \"camelcase\": true, // Prohibit use of == and != in favor of === and !==. \"eqeqeq\": true, // Suppress warnings about == null comparisons. \"eqnull\": true, // Enforce tab width of 2 spaces. \"indent\": 2, // Prohibit use of a variable before it is defined. \"latedef\": true, // Require capitalized names for constructor functions. \"newcap\": true, // Enforce use of single quotation marks for strings. \"quotmark\": \"single\", // Prohibit trailing whitespace. \"trailing\": true, // Prohibit use of explicitly undeclared variables. \"undef\": true, // Warn when variables are defined but never used. \"unused\": true, // Enforce line length to 80 characters \"maxlen\": 80, // Enforce placing 'use strict' at the top function scope \"strict\": true' } "], "neg": []} {"query": "In the certification project pages, the tab on the left is \"Instructions\". However, if you resize the browser and the page switches to the mobile layout, the tab name changes to \"Info\". The \"Console\" on the desktop layout changes to \"Tests\" too. and other certification projects with built in editor to the browser Use the same name for the same content. ! ! Device: Laptop OS: Windows 10 Browser: Chrome Version: 108.0.5359.125 No response_\nTechnically, I don't think this is a WCAG failure. does address consistent identification of functional components. In this scenario, in wide view they are HTML buttons but in narrow view they are tabs, so technically they are not the same component and thus don't fall under 3.2.4. But for usability I would tend to agree that it would be best if they could use the same terminology since they basically do the same thing.\nWe can use \"Console\" for both mobile and desktop. Do we use \"info\" for the desktop layout and call it ?\nI agree with using \"Console\" for both. For the panel showing user stories I would prefer using \"Instructions\" since the word \"Info\" seems too vague.\nTo solve this issue: use \"Console\" and \"Instructions\" for both layout. 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.\nWe might want to keep in mind that is much longer than . We do not have much real-estate on mobile.\nHere are words that I can think of are \"details\", \"step\", \"story\", \"task\", \"manual\", \"guide\", and \"briefing\". Is any of them good enough, or do we change the console for now and come back for \"instructions\" later?\nMy initial thought is: keep everything consistent, and just use the current mobile-naming for desktop as well. However, I am not entirely happy with the word for what it denotes. might be one option, but I also like your suggestion of .\nI find or interesting . I vote for too, if no one else has issue with it, we can go with it, otherwise we go with .\nI think is a term in agile development so I'm not sure if we can call it just . I would vote for or if is too long. However, my main concern was that the word changes as the user resizes the window. So, I'm okay with either of them as long as we use the same word for both layouts.\nWe decided to go with the desktop terms for both, \"Instructions\" and \"Console\". The file that needs to be changed is We are going to make another issue about improving the mobile UX to potentially use icons or another solution.\nI think that should remain for responsive design issues on cell phones and since it is the appropriate term when the student goes to vsCode or another IDE", "pos": ["{!hasEditableBoundaries && ( title={i18next.t('learn.editor-tabs.info')} title={i18next.t('learn.editor-tabs.instructions')} tabIndex={0} > {instructions}", " title={i18next.t('learn.editor-tabs.tests')} title={i18next.t('learn.editor-tabs.console')} {...editorTabPaneProps} > {testOutput}"], "neg": []} {"query": "In crowdin, I noticed that step 48 of the new JS course, build an rpg, uses a sentence that may need a grammar correction. Instead of \u201cyour button innerText\u201d it should say \u201cyour buttons\u2019 innerText\u201d? Full sentence was: Grammar correction. No response N/A No response\nHello , Can you assign me this?\nShould be changed to:\nThanks for opening this issue. This looks like something that can be fixed by \"first-time\" code contributors to this repository. Please make sure you read 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.", "pos": ["# --description-- In your `goTown` function, update your button `innerText` properties to be `Go to store`, `Go to cave`, and `Fight dragon`. Update your `onclick` properties to be `goStore`, `goCave`, and `fightDragon`, respectively. Finally, update your text's `innerText` property to be `You are in the town square. You see a sign that says Store.`. In your `goTown` function, update your `button` elements' `innerText` properties to be `Go to store`, `Go to cave`, and `Fight dragon`. Update your `onclick` properties to be `goStore`, `goCave`, and `fightDragon`, respectively. Finally, update your text's `innerText` property to be `You are in the town square. You see a sign that says Store.`. # --hints--"], "neg": []} {"query": "The updated topic banner on the is covering up a couple of the table headers here \"Screen | lodash | Handy JavaScript utlities library. | | lodash | Handy JavaScript utilities library. | | uglify-js | Dependency for connect-assets library to minify JS. | | mocha | Test framework. | | chai | BDD/TDD assertion library. |"], "neg": []} {"query": "Describe the bug Having special character in the slug, title, or heading of the challenges lead to broken structure as shown in the image below. Originally reported by ! These challenges are the translation of these. ! Although we can not add them in the Arabic translation, this is a fix to the side effect, because Arabic isn't the only RTL language with translation efforts. I think it's better to not include special characters in the heading, if they aren't wrapped in spaced, example 'the Logical And Operator &&'. So I suggest two solutions: Delete special character, if they aren't wrapped around spaces, like change \"push()\" to \"push\". Add code block around functions and methods, to be something like .\nWould it be acceptable to spell these out a little more? Instead of We could do Not only do we get rid of the special characters but it possibly makes it a little clearer for people listening to the page.\nIn translation, that's perfectly fine . Good call.", "pos": ["--- id: 56bbb991ad1ed5201cd392cc title: Manipulate Arrays With pop() title: Manipulate Arrays With pop Method challengeType: 1 videoUrl: 'https://scrimba.com/c/cRbVZAB' forumTopicId: 18236", "--- id: 56bbb991ad1ed5201cd392cb title: Manipulate Arrays With push() title: Manipulate Arrays With push Method challengeType: 1 videoUrl: 'https://scrimba.com/c/cnqmVtJ' forumTopicId: 18237", "--- id: 56bbb991ad1ed5201cd392cd title: Manipulate Arrays With shift() title: Manipulate Arrays With shift Method challengeType: 1 videoUrl: 'https://scrimba.com/c/cRbVETW' forumTopicId: 18238", "--- id: 56bbb991ad1ed5201cd392ce title: Manipulate Arrays With unshift() title: Manipulate Arrays With unshift Method challengeType: 1 videoUrl: 'https://scrimba.com/c/ckNDESv' forumTopicId: 18239"], "neg": []} {"query": "The instructions state \"In your fourth tr element, add a th element with the text Total Liabilities.\" However it is not really clear that the user should or should not include a period. Users will have failed previous tasks if the period was omitted (periods are required on previous exercises) , therefore they will most likely add the period which will result in a failed test case. Also, if the period is included after \"Liabilities\", the error message gives \"Your th element should have the text Total Liabilities.\" Which does not highlight the actual issue. Maybe making a different test case message that looks for the period would make it more understandable? The code above should highlight the issue of the period being present. The test case that is currently in place can confuse users that they have a spelling issue/spacing instead of the actual issue being the period at the end of \"Liabilities\". No response Device: Desktop OS: Windows 10 Browser: Chrome Version: Version 108.0.5359.125 No response\nI was thinking, that we could change to But this doesn't make a coherent sentence. I am in favor of adding a new test.\nI also think a new test case would be good.\nHi! We just opened a to fix it, but it was not accepted . Could you please kindly inform us some feedback about what was going wrong and what else we need to do? So that we can know where to focus. We appreciate any help, thank you!!\nHi Thanks for reaching out and creating a pull request. For reasons of sanity, we can't accept PRs from forks that organizations maintain. You should make a PR from your own personal GitHub account. You can collaborate with others and have commits made by multiple people, but one person needs to create the PR, and then others may push to the same PR should they wish. It is OK if you want to use the draft mode while collaborating. The person making the PR is responsible for ensuring the checklist is followed, tests are working, and so on. You can also commit on someone's behalf. See: Also, please create good, small, and succinct commit messages and PR titles. Keep your commits clean and avoid any merge commits unless you have conflicts to resolve. The final PR should not have dirty commits from collaborating on an organization fork like the previous PR. The reason is the maintainers of this project will need to validate your changes and the source of the commits. Keeping it clean makes everyone's lives easy. Thanks and happy coding!\nHi Mrugesh! Thank you for your precious feedback! I've switched back to my personal GitHub account, and made a pull request . This time the commits are clean and the messages are concise. Thank you for taking time reviewing! I appreciate any feedback. :D", "pos": ["assert(document.querySelectorAll('table')?.[1]?.querySelector('tbody')?.querySelectorAll('tr')?.[3]?.querySelector('th')); ``` Your text `Total Liabilities` should not include period `.`. ```js assert(document.querySelectorAll('table')?.[1]?.querySelector('tbody')?.querySelectorAll('tr')?.[3]?.querySelector('th')?.innerText !== 'Total Liabilities.'); ``` Your `th` element should have the text `Total Liabilities`. ```js"], "neg": []} {"query": "Users often delete the text or include it inside of the anchor text. Could we add a line to the instructions preventing this error? Common errors: Target solution: There should be a way to prevent these common errors. No response All No response\nI'm happy to work on and fix this issue\nWhile we are at it, I move that we include the opening and closing tags in the active editor region. I've see several people add these tags because they don't realize they are already there since they are in the gray area, far removed from the white editor region.\n+1 to adding the p to the editable region\nJust helped someone in the forums who extra tags on this step. Definitely need to put them in the editable region.\nI am down to test moving them to the editor area first, if the issue persists, we can add new line After all, this looks like it's cased by a confusion If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this.\nI think I tried everything and it doesnt work\nThis isn't a location for help. You should use the Ask for Help button or go to the forum at", "pos": ["

          --fcc-editable-region-- No Copyright - freeCodeCamp.org

          No Copyright - freeCodeCamp.org

          --fcc-editable-region--

          "], "neg": []} {"query": "I think we can clarify this step with one small tweak. Currently the instructions say Students seem to often miss what is going on here and try to make a combo img-anchor element. We could modify it to add a brief bit of context No response All No response\nI'm happy to work on and fix this issue if that's alright with you?\nI like what you've proposed here I think I might have proposed something similar for this step a while ago, but I'm getting old so my memory may not be as good as it used to be.\nThanks for creating an issue about this That should help cut down on the confusion in this step quite a bit. I vaguely recall mentioning something similar before, so it's great you opened up an issue so we can improve this step. feel free to open up a PR for this. We don't typically assign issues. Instead, we look for comments in issues like yours expressing interest, and the first comprehensive PR that's submitted is reviewed and merged.\nIs this issue still open?\nI see a \"first timers only\" tag and a \"help wanted\" tag on this issue. Are we just waiting on a couple of fixes to be chosen from, or can I work on this issue since I am a first timer?\nHey the first pull request that solves issue, while following contribution guidelines, will be merged.", "pos": ["# --description-- In previous steps you used an anchor element to turn text into a link. Other types of content can also be turned into a link by wrapping it in anchor tags. Turn the image into a link by surrounding it with necessary element tags. Use `https://freecatphotoapp.com` as the anchor's `href` attribute value. # --hints--"], "neg": []} {"query": "The challenge is using the method which hasn't been introduced yet. I believe it is an artifact of the current section order (ES6 now comes before functional programming). You don't really need to understand how works to solve the challenge but just to avoid any confusion it might be better to change it to use a simple for loop. The guide post will need to be updated as well if this change is made. Should not contain code that is unfamiliar to the student. No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] Forum post: Guide post:\nhey i have fix this issue let you check PR", "pos": ["```js const sum = (x, y, z) => { const args = [x, y, z]; return args.reduce((a, b) => a + b, 0); let total = 0; for (let i = 0; i < args.length; i++) { total += args[i]; } return total; } ```", "```js const sum = (...args) => { return args.reduce((a, b) => a + b, 0); let total = 0; for (let i = 0; i < args.length; i++) { total += args[i]; } return total; } ```"], "neg": []} {"query": "The phrase \"because we are using flexbox\" is not clear here. There was no flexbox for table or tr or td. It is not clear why setting width to 100vw works in such way It will be cool to have clear explanation about setting td width to 100vw in table No response Device: MacBook Pro OS: Ventura 13.0.1 Browser: Chrome Version: 109.0.5414.119 No response\nWhere is the code of this issue?\nI believe it's in the folder, written in one of its files.\nHave you fixed the issue yet ?\nI am waiting for the issue to be triaged by a maintainer.\nThis issue is related and might lead to a different code solution for step 52:\nThe phrase needs to be removed from the challenge description. An issue with the or label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the The file to be changed is:", "pos": ["# --description-- Create a selector to target your `td` elements within your table body. Give them a width to fill the viewport, with a minimum and maximum of `4rem`. This approach ensures that the width is fixed, whereas setting `width` specifically would allow the elements to shrink to the container (because we are using flexbox). Create a selector to target your `td` elements within your table body. Give them a width to fill the viewport, with a minimum and maximum of `4rem`. This approach ensures that the width is fixed, whereas setting `width` specifically would allow the elements to shrink to the container. # --hints--"], "neg": []} {"query": "in the odin project, there is a sentence that is worded like it should be worded like Here is the file If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this.\ncan I solve this?", "pos": ["The `` element is where you put important meta-information about your webpages, and stuff required for your webpages to render correctly in the browser. Inside the ``, you should not use any element that displays content on the webpage. ## The Charset Meta Element You should always have the `meta` tag for the charset encoding of the webpage in the head element: ``. You should always have the `meta` tag for the `charset` encoding of the webpage in the `head` element: ``. Setting the encoding is very important because it ensures that the webpage will display special symbols and characters from different languages correctly in the browser."], "neg": []} {"query": "When adding a new node ( or element ) to a binary search tree, I was supposed to compare the value supplied method with that of current node. But it seems odd to me that, despite not doing it at all, the testing script somehow ignored it. Here's the code I wrote I expect the unit test case to fail instead of to succeed. Also, if I slightly edit this LOC here: to Then I expect the said unit test case to pass. No response Device: Dell Latitude 5580 OS: Ubuntu 22.04 Browser: Brave Browser Version: 1.45.127 No response\nis taking a look and this and will create a PR if a fix is identified.\nThe reason the \"The add method should add elements according to the binary search tree rules.\" test passes is because the test does not test for adding duplicate keys. I've a pr that changes the test so it adds a duplicate key, and the solution in the docs still works. The code you wrote now fails (correctly). Your intended fix of changing to does not work, as if cr[direction] is null, you can't get its .value", "pos": ["} test.add(4); test.add(1); test.add(1); test.add(7); test.add(87); test.add(34);"], "neg": []} {"query": "In the step: We see the text: \"You can use a callback function in the style() method to change the styling for different elements.\" Which is a repetition in part of the later sentence \"You can use a callback function in the style() method and include the conditional logic.\" I feel the first sentence can be skipped entirely and make for a better step overall. Instead of the current step text, we could rewrite as follows: No response N/A No response\nopened pr that gets rid of first sentence", "pos": ["# --description-- D3 is about visualization and presentation of data. It's likely you'll want to change the styling of elements based on the data. You can use a callback function in the `style()` method to change the styling for different elements. D3 is about visualization and presentation of data. It's likely you'll want to change the styling of elements based on the data. For example, you may want to color a data point blue if it has a value less than 20, and red otherwise. You can use a callback function in the `style()` method and include the conditional logic. The callback function uses the `d` parameter to represent the data point: ```js"], "neg": []} {"query": "In the sentence: \"There are several ways to add a tooltip to a visualization, this challenge uses the SVG A tooltip shows more information about an item on a page when the user hovers over that item. There are several ways to add a tooltip to a visualization, this challenge uses the SVG `title` element. A tooltip shows more information about an item on a page when the user hovers over that item. There are several ways to add a tooltip to a visualization. This challenge uses the SVG `title` element. `title` pairs with the `text()` method to dynamically add data to the bars."], "neg": []} {"query": "Someone in the forums pointed out that adding the property just to will not have the intended effect since the property is not inherited. It appears to me that removing this property completely from in the final product does not seem to make any difference to the layout. Do we need ? If so, if the intent is to apply it to all elements then it should probably be moved to the rule set. Either remove completely or move it into the ruleset. No response N/A No response\nPretty sure I saw this in another challenge too and it got fixed. The CSS used looks like the of setting the but with the actual inheriting missing from the code. It should be fixed, but I would not suggest we remove , setting that (in my opinion) is pretty much a best pratice.\nI'm guessing it would be easier and take less explaining to update step 26 to add the on that selector and then remove the mention of it in step 27. Then update all the seed code.\nJust a heads up, if lasjorg PR merged without issue, balance sheet project suffer the same issue, we can open a PR or issue for it, if the PR is merged. Except that the balance sheet project , doesn't do much and moving it break the layout.", "pos": ["# --description-- To start your CSS, normalize the CSS rules by targeting all elements with `*`, including the `::before` and `::after` pseudo-selectors. Set the `padding` property and `margin` property both to `0`. To start your CSS, normalize the CSS rules by targeting all elements with `*`, including the `::before` and `::after` pseudo-selectors. Set the `padding` and `margin` properties both to `0` and set the `box-sizing` property to `border-box`. # --hints--", "assert(new __helpers.CSSHelp(document).getStyle('*, ::before, ::after')?.margin === '0px'); ``` Your `*, ::before, ::after` selector should have a `box-sizing` property set to `border-box`. ```js assert(new __helpers.CSSHelp(document).getStyle('*, ::before, ::after')?.boxSizing === 'border-box'); ``` # --seed-- ## --seed-contents--", "This will make it easier for you to work with `rem` units later, as `2rem` would be 20px. Also, set the `box-sizing` property to `border-box`. # --hints-- You should create an `html` selector.", "assert(new __helpers.CSSHelp(document).getStyle('html')?.fontSize === '62.5%'); ``` Your `html` selector should have a `box-sizing` property set to `border-box`. ```js assert(new __helpers.CSSHelp(document).getStyle('html')?.boxSizing === 'border-box'); ``` # --seed-- ## --seed-contents--", "*, ::before, ::after { padding: 0; margin: 0; box-sizing: border-box; } --fcc-editable-region--", "*, ::before, ::after { padding: 0; margin: 0; box-sizing: border-box; } html { font-size: 62.5%; box-sizing: border-box; } --fcc-editable-region--", "*, ::before, ::after { padding: 0; margin: 0; box-sizing: border-box; } html { font-size: 62.5%; box-sizing: border-box; } body {", "::after { padding: 0; margin: 0; box-sizing: border-box; } html { font-size: 62.5%; box-sizing: border-box; } body {"], "neg": []} {"query": "In the 5 certification projects for the Data Visualization certificate, the phrase \"(non-virtual) DOM elements\" is used without any prior explanation (I checked the Data Visualization curriculum and no such phrase was introduced at any point). It is not clear therefore to the learner what the requirement \"Required (non-virtual) DOM elements are queried on the moment of each test.\" could actually mean. Now, maybe it means \"actual DOM' vs \"virtual DOM\" from the React curriculum. But requiring that a priori knowledge to understand a Data Visualization project requirement seems like overkill? I propose that this requirement in all 5 projects be stated simply as \"Required DOM elements...\" The chance of someone not understanding that we mean 'actual DOM elements' seems miniscule to me in the context of these challenges, but I'm not a web developer, so if there is a valid reason to use the term 'non-virtual DOM elements', it would be very interesting for me to learn/hear of it. ps. should this issue be accepted, please also fix the phrasing \"on the moment\" to be \"at the moment\" which I believe is what was actually meant. update all 5 certification project statements referring to (non-virtual) DOM elements as per the above discussion. No response N/A No response\nI think this is more of a note for advanced campers, similar to mentioning that the tests might not work with a framework like Vue.\nYes I think so too, but it is too confusing to someone who is not that advanced. If we didn't say it, what is the chance an advanced camper will run into a problem?\nIt likely wouldn't - though I also haven't seen much mention of beginners who do have confusion.\nI agree that I haven't seen questions on this either but since the rule-of-thumb is to not include undefined technical terms in the challenges and projects, we should do something about this one. (Either define it or drop it)\nThanks for opening this issue. 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: In these files, the text should be updated to . Please make sure you read 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.", "pos": ["Fulfill the below user stories and get all of the tests to pass. Use whichever libraries or APIs you need. Give it your own personal style. You can use HTML, JavaScript, CSS, and the D3 svg-based visualization library. The tests require axes to be generated using the D3 axis property, which automatically generates ticks along the axis. These ticks are required for passing the D3 tests because their positions are used to determine alignment of graphed elements. You will find information about generating axes at . Required (non-virtual) DOM elements are queried on the moment of each test. If you use a frontend framework (like Vue for example), the test results may be inaccurate for dynamic content. We hope to accommodate them eventually, but these frameworks are not currently supported for D3 projects. You can use HTML, JavaScript, CSS, and the D3 svg-based visualization library. The tests require axes to be generated using the D3 axis property, which automatically generates ticks along the axis. These ticks are required for passing the D3 tests because their positions are used to determine alignment of graphed elements. You will find information about generating axes at . Required DOM elements are queried on the moment of each test. If you use a frontend framework (like Vue for example), the test results may be inaccurate for dynamic content. We hope to accommodate them eventually, but these frameworks are not currently supported for D3 projects. **User Story #1:** My chart should have a title with a corresponding `id=\"title\"`.", "Fulfill the below user stories and get all of the tests to pass. Use whichever libraries or APIs you need. Give it your own personal style. You can use HTML, JavaScript, CSS, and the D3 svg-based visualization library. Required (non-virtual) DOM elements are queried on the moment of each test. If you use a frontend framework (like Vue for example), the test results may be inaccurate for dynamic content. We hope to accommodate them eventually, but these frameworks are not currently supported for D3 projects. You can use HTML, JavaScript, CSS, and the D3 svg-based visualization library. Required DOM elements are queried on the moment of each test. If you use a frontend framework (like Vue for example), the test results may be inaccurate for dynamic content. We hope to accommodate them eventually, but these frameworks are not currently supported for D3 projects. **User Story #1:** My choropleth should have a title with a corresponding `id=\"title\"`.", "Fulfill the below user stories and get all of the tests to pass. Use whichever libraries or APIs you need. Give it your own personal style. You can use HTML, JavaScript, CSS, and the D3 svg-based visualization library. Required (non-virtual) DOM elements are queried on the moment of each test. If you use a frontend framework (like Vue for example), the test results may be inaccurate for dynamic content. We hope to accommodate them eventually, but these frameworks are not currently supported for D3 projects. You can use HTML, JavaScript, CSS, and the D3 svg-based visualization library. Required DOM elements are queried on the moment of each test. If you use a frontend framework (like Vue for example), the test results may be inaccurate for dynamic content. We hope to accommodate them eventually, but these frameworks are not currently supported for D3 projects. **User Story #1:** My heat map should have a title with a corresponding `id=\"title\"`.", "Fulfill the below user stories and get all of the tests to pass. Use whichever libraries or APIs you need. Give it your own personal style. You can use HTML, JavaScript, CSS, and the D3 svg-based visualization library. The tests require axes to be generated using the D3 axis property, which automatically generates ticks along the axis. These ticks are required for passing the D3 tests because their positions are used to determine alignment of graphed elements. You will find information about generating axes at . Required (non-virtual) DOM elements are queried on the moment of each test. If you use a frontend framework (like Vue for example), the test results may be inaccurate for dynamic content. We hope to accommodate them eventually, but these frameworks are not currently supported for D3 projects. You can use HTML, JavaScript, CSS, and the D3 svg-based visualization library. The tests require axes to be generated using the D3 axis property, which automatically generates ticks along the axis. These ticks are required for passing the D3 tests because their positions are used to determine alignment of graphed elements. You will find information about generating axes at . Required DOM elements are queried on the moment of each test. If you use a frontend framework (like Vue for example), the test results may be inaccurate for dynamic content. We hope to accommodate them eventually, but these frameworks are not currently supported for D3 projects. **User Story #1:** I can see a title element that has a corresponding `id=\"title\"`.", "Fulfill the below user stories and get all of the tests to pass. Use whichever libraries or APIs you need. Give it your own personal style. You can use HTML, JavaScript, CSS, and the D3 svg-based visualization library. The tests require axes to be generated using the D3 axis property, which automatically generates ticks along the axis. These ticks are required for passing the D3 tests because their positions are used to determine alignment of graphed elements. You will find information about generating axes at . Required (non-virtual) DOM elements are queried on the moment of each test. If you use a frontend framework (like Vue for example), the test results may be inaccurate for dynamic content. We hope to accommodate them eventually, but these frameworks are not currently supported for D3 projects. You can use HTML, JavaScript, CSS, and the D3 svg-based visualization library. The tests require axes to be generated using the D3 axis property, which automatically generates ticks along the axis. These ticks are required for passing the D3 tests because their positions are used to determine alignment of graphed elements. You will find information about generating axes at . Required DOM elements are queried on the moment of each test. If you use a frontend framework (like Vue for example), the test results may be inaccurate for dynamic content. We hope to accommodate them eventually, but these frameworks are not currently supported for D3 projects. **User Story #1:** My tree map should have a title with a corresponding `id=\"title\"`."], "neg": []} {"query": "CSS Learn Typography/Nutrition Label: Step 31 \u201cCreate an .small-text selector and set the font-size to\u201d the \u201can\u201d should actually be an \u201ca\u201d. Windows 11/ Chrome browser Version 110.0.5481.78 (Official Build) (64-bit)\nIt helps if you use the New Issue template. ! Link to challenge: Suggested correction:\nWould you like to solve this issue? Or shall I go for it? Feel free to try\niam new to opensource i love to work on this issue.\nAn issue with the or label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the\nTo solve this issue, change this line from to Here is the file If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our prolific contributors will guide you through this.", "pos": ["The `rem` unit stands for `root em`, and is relative to the font size of the `html` element. Create an `.small-text` selector and set the `font-size` to `0.85rem`, which would calculate to be roughly `13.6px` (remember that you set your `html` to have a `font-size` of `16px`). Create a `.small-text` selector and set the `font-size` to `0.85rem`, which would calculate to roughly `13.6px` (remember that you set your `html` to have a `font-size` of `16px`). # --hints--"], "neg": []} {"query": "In the multi-file editor, if the preview pane is toggled off and then on again, any output in the console will be cleared. Granted, the user can always check their code again to get the console output back. But I'm assuming this is not intended behavior? Any page using the multi-file editor the Survey Form in the new RWD the Console button so it is showing below the preview. the tests. the Preview button to hide the preview. the Preview button again to show the preview. that the console output resets. Console output should not reset if the preview pane is toggled off/on. No response N/A No response\nHere is what I tried, so anyone in the future save time: Changing lowerJaw to JSX didn't help. TabPane change display to , but React doesn't care and preserve the state. if you turn to JSX, so react preserve the state, it won't render at all. monaco wants it to be an element. I don't know if this helps, but I personally think if become JSX, then React can do its thing and preserve the state. I have no idea how to make monaco accept JSX instead of Element, so I am going to stop there, maybe someone else the same issue. Here is the file with the issue Here is the react-wrapper for the monaco, maybe it does have a way to do it\nI have looked it more up And I don't think, it is possible to inject JSX element inside the editor. I am maybe wrong, but the easiest solution, is to have the editor in instruction and lowerjaw in different tab, is that possible?\nI think the console output is not related to the editor per say. We just need to investigate output, consoleOutputSelector, and consoleOut state in redux store and see at what point it gets reset.", "pos": ["return [ takeLatest(types.executeChallenge, executeCancellableChallengeSaga), takeLatest( [ types.updateFile, types.previewMounted, types.challengeMounted, types.resetChallenge ], [types.updateFile, types.challengeMounted, types.resetChallenge], previewChallengeSaga ), takeLatest(types.previewMounted, previewChallengeSaga, { flushLogs: false }), takeLatest(types.projectPreviewMounted, previewProjectSolutionSaga) ]; }"], "neg": []} {"query": "The test fails to catch the difference between an element and class selector The hint is But the first hint should be displayed instead: The regex fails to tell the difference between an element and class selector. No response All No response\nWe should just use the method on the class to look for . Examples of this can be seen in other tests. An issue with the or label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the\nHi My name is Om Bansal and this is my first time contributing to open source can i work on this issue?\nGo for it - we will accept the first fully correct PR that fixes the issue.", "pos": ["You should use the `body` element selector. ```js assert.match(code, /bodys*{/); assert.exists(new __helpers.CSSHelp(document).getStyle('body')); ``` You should use the `background` property in the `body` selector."], "neg": []} {"query": "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: \"Screen showCodeAllySelector, userFetchStateSelector } from '../../redux/selectors';", "isOnlineSelector, isServerOnlineSelector, userFetchStateSelector, showCodeAllySelector, userSelector, ( isSignedIn,", "isOnline: boolean, isServerOnline: boolean, fetchState: UserFetchState, showCodeAlly: boolean, user: User ) => ({ isSignedIn,", "isServerOnline, fetchState, theme: user.theme, showCodeAlly, user }) );", "showFooter?: boolean; isChallenge?: boolean; block?: string; showCodeAlly: boolean; superBlock?: string; t: TFunction; }", "superBlock, t, theme = Themes.Default, showCodeAlly, user, fetchUser, updateAllChallengesInfo", "/> ) : null} {isChallenge && ( {isChallenge && !showCodeAlly && (
          challenge.id === challengeId ); const breadcrumbs = document.querySelector('.breadcrumbs-demo'); showCodeAlly && breadcrumbs?.remove(); return showCodeAlly ? ( "], "neg": []} {"query": "This should be a relatively easy fix for a first-time contributor :) This challenge says the first two numbers are 1 and 1 when in fact the first two numbers are 0 and 1. The first few numbers are: 0, 1, 1, 2, 3, 5 and 8 So when you update the text to also check the tests and make sure this doesn't change any of the expected test outcomes. The text should correctly state the first numbers as 0, 1, 1, 2, 3, 5 and 8 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\nAn issue with the label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the The affected file can be found here:\nHello! I'm a rookie software developer and I'm looking for a \"good first issue\" to start contributing to open-source projects. So could I be assigned to fix this issue please?", "pos": ["Given a positive integer `num`, return the sum of all odd Fibonacci numbers that are less than or equal to `num`. The first two numbers in the Fibonacci sequence are 1 and 1. Every additional number in the sequence is the sum of the two previous numbers. The first six numbers of the Fibonacci sequence are 1, 1, 2, 3, 5 and 8. The first two numbers in the Fibonacci sequence are 0 and 1. Every additional number in the sequence is the sum of the two previous numbers. The first seven numbers of the Fibonacci sequence are 0, 1, 1, 2, 3, 5 and 8. For example, `sumFibs(10)` should return `10` because all odd Fibonacci numbers less than or equal to `10` are 1, 1, 3, and 5."], "neg": []} {"query": "Currently, the instructions in the module, which happens to be a part of the module ( of the course ), suggest the following as the value of the variable: For the sake of more clarity, I think the value of the variable should be as follows: NOTE: There should a forward slash ( ) before the and should be enclosed within quotes because that particular part is supposed to be a string. The value of the variable should be as follows: NOTE: There should a forward slash ( ) before the and should be enclosed within quotes because that particular part is supposed to be a string. \"image\" absolutePath = __dirname + relativePath/file.ext absolutePath = __dirname + '/relativePath/file.ext' ``` # --instructions--"], "neg": []} {"query": "Originally reported by the editor region doesn't render when camper submits a challenge. https://user- This hide the instruction and lowerJaw, whenever this bug occurs\nWhat browser/OS were you using to trigger this? I'm not able to replicate with either FF or Chrome on Windows/Linux. Or perhaps there is some trick to this that I'm not seeing in the video?\nTo be honest, I don't think this is a browser specific. she mentioned that chrome was used, my guess is that somewhere in the JavaScript files, it has if statement that stop editor region from rendering, because old PRs do account for this failing. The true solution is to findout, what changed and what isn't pleased. Otherwise, we can add , that fallback to a basic component with instruction and submit button. Or we can add another tab in the upperJaw, for instruction if editor region is It won't have editor region, but it's better than the current nothing. Sorry, I can't include all of it, but here is the discord discussion.\nmy user agent info (on Windows 11) User Agent is: { const { updateFile, fileKey } = props; const { updateFile, fileKey, isResetting } = props; if (isResetting) return; // TODO: now that we have getCurrentEditableRegion, should the overlays // follow that directly? We could subscribe to changes to that and redraw if // those imply that the positions have changed (i.e. if the content height"], "neg": []} {"query": "Similar to issue Please also update another step that has the same issue and should get a similar fix: The sentence: \"will only return Yes if num is greater than 5 and less than 10. The same logic can be written as:\" should be changed to: \"This will only...\" (adding This is enough to fix it as a reference to the previous code block) And similarly for this step as well: Multiple As described above No response N/A No response\nProposed change: Question - do we use or for string literals?\n\"yes\" i think\nPlease assign this issue to me i think can fix this and make my first contribution to open source\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.\nI have created a pull request, what should i do next ?(It's my first contribution, don't mind my stupid questions please)", "pos": ["Sometimes you will need to test more than one thing at a time. The logical and operator (`&&`) returns `true` if and only if the operands to the left and right of it are true. The same effect could be achieved by nesting an if statement inside another if: The same effect could be achieved by nesting an `if` statement inside another `if`. ```js if (num > 5) {", "return \"No\"; ``` will only return `Yes` if `num` is greater than `5` and less than `10`. The same logic can be written as: This code will return `Yes` if `num` is greater than `5` and less than `10`. The same logic can be written with the logical and operator. ```js if (num > 5 && num < 10) {", "The logical or operator is composed of two pipe symbols: (`||`). This can typically be found between your Backspace and Enter keys. The pattern below should look familiar from prior waypoints: The pattern below should look familiar from prior waypoints. ```js if (num > 10) {", "return \"Yes\"; ``` will return `Yes` only if `num` is between `5` and `10` (5 and 10 included). The same logic can be written as: This code will return `Yes` if `num` is between `5` and `10` (`5` and `10` included). The same logic can be written with the logical or operator. ```js if (num > 10 || num < 5) {"], "neg": []} {"query": "In the build a bike shop interactive project, the term \"subshell\", also \"sub shell\" (1 instance) is first used in step 1450 as an instruction without any definition of what a sub shell / subshell is. The challenge has been using subshells since much earlier in the tutorial as well as in the prior coding challenges where bash is used to access a PSQL database, but the term is never explained. This creates cognitive friction during this step and doesn't allow for the \"interactive video game flow state\" that is desired in the FCC curriculum. I'd suggestion a simple sentence that explains what a subshell is before using the term as part of a coding instruction step. It would probably be best to introduce this term back in the Build a student database project since that is the first occurence of using the syntax NA - for instructions issue NA - for instructions issue No response Device: [Laptop] OS: [e.g. iOS 12.6.1] Browser: [Chrome] Version: [e.g. 109] Address how the wording interferes with the flow state described here: .\nWhere should I add the definition of subshell ? can you tell me the name of the file and path of the file ? Definition of Subshell : A subshell is a child process launched by a shell (or shell script). A subshell is a separate instance of the command processor. Also, is above definition of subshell correct ?\nHey do you mind taking a look and triage this?\nI really didn't think anything needed to be here. Campers have been using subshells quite a few times before this course. It's never thoroughly explained exactly what it is, but it's explained how it behaves... step in OP: next step: A forum search yields no results of people asking about this: I decided to add a small snippet in the course before this where that syntax is first used to hopefully ease campers into the terminology.", "pos": ["1: \"Move the .target element from #location1 to #location2.\", 2: \"Change the background color of .target to red.\", 3: \"Change the background color of the even-numbered targets to red.\", 4: \"Change the background color of the target4 to red.\", 5: \"Clone the target2 in #location1 so that it also exists in #location2.\", 6: \"Remove the target3 from element from #location1.\", 4: \"Change the background color of target4 to red.\", 5: \"Clone target2 in #location1 so that it also exists in #location2.\", 6: \"Remove the target3 element from #location1.\", 7: \"Check the following checkboxes using jQuery.\", 8: \"Make the text input field read-only.\", 9: \"Select the target2 option in the select box.\", 9: \"Select target2 option in the select box.\", 10: \"Add the following css classes to .target: 'animated' and 'hinge'.\", 11: \"Use jQuery to read the data of .target.\", 12: \"Use 'length' to count the number of child elements in #location1, then display that value in #location2.\","], "neg": []} {"query": "When I learned the JavaScript,I saw this expression \"Nearly every object in JavaScript has a prototype property which is part of the constructor function that created it.\", I give me a vibe that \"All objects in JavaScript have prototype property\". I don't know if this is my misunderstanding, If not , correct it It will bring great misleading to novices. Correct it into below \u201cNearly every object in JavaScript has a constructor that created it ,and this constructor function has a prototype property.\u201d No response Device: [Laptop] OS: [MacOs 13.2] Browser: [Chrome] Version: [110.0.5481.177] No response\nThank you for taking the time to open this. I am not sure what you mean by this. I am not sure how you interpret \"all objects\" from the words \"nearly every object\" Aside from that, I suggest we remove the sentence completely. It does not do much, and is incorrect: I believe the sentence is referring to some primitives like which do not have a property . However, these are not objects, unless referring to the . man, js is confusing\nSorry, I am not good at English.I didn't expect MDN to have a similar expression, because I didn't read the English version before.By the way, you just said that this expression is incorrect and gave you your thoughts I remember that not only some primitives like number do not have a property prototype, but also an object like this does not have a property prototype too. \"image\" Since all instances automatically have the properties on the `prototype`, think of a `prototype` as a \"recipe\" for creating objects. Note that the `prototype` for `duck` and `canary` is part of the `Bird` constructor as `Bird.prototype`. Nearly every object in JavaScript has a `prototype` property which is part of the constructor function that created it. Since all instances automatically have the properties on the `prototype`, think of a `prototype` as a \"recipe\" for creating objects. Note that the `prototype` for `duck` and `canary` is part of the `Bird` constructor as `Bird.prototype`. # --instructions--"], "neg": []} {"query": "It isn't a huge deal, but I do think the camper has a point, see the forum thread for more info. I think updating the example code with something less ambiguous wouldn't be a horrible idea. Current example New example (I can't think of anything better right now, you get the point). Less ambiguous example code that does not involve letter case logic or identifiers with the word in it when teaching about and . 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]\nI agree, the example is unnecessarily confusing. I have submitted a pull request that uses a classic fruit example. The console log is also more explicit on what is being selected. Additionally, may I suggest that we also change the instructions to be more explicit? So instead of: it'll be something like:Additionally, additionally, may I also suggest we expand the explanation on strict equality testing? So add a simple sentence like: \"Strings with different cases will be treated as different values\"\nI guess the conditions can be clarified, but I don't remember seeing this being a problem. That isn't how strict equality works. It has to do with type coercion. Letters with different casings always have different values.\nYes I get that, but for this specific example, I just thought it would be good to keep it simple. On second thought, the explanations / instructions are good enough. Lets leave it as it is.\nhello can you please tell me why my pull requests are getting blocked when I am trying to close an issue", "pos": ["Here is an example of a `switch` statement: ```js switch (lowercaseLetter) { case \"a\": console.log(\"A\"); switch (fruit) { case \"apple\": console.log(\"The fruit is an apple\"); break; case \"b\": console.log(\"B\"); case \"orange\": console.log(\"The fruit is an orange\"); break; } ```"], "neg": []} {"query": "It would be nice if we allowed the camper to log out the result without having the last test fail because of it. One option might be to use code comments as delimiters to help make the regex more targeted. The camper should be allowed to log out the result without failing with the correct code. 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]\nWe could update the test to check for the assignment operator, instead of just a variable reference:\nTo fix the issue change the third test: To what Naomi suggested Here is the file for the challenge: If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our prolific contributors will guide you through this.\nCan I work on this issue ? It would mean a lot\nGo for it.\nCan I work on this issue?", "pos": ["The quotient variable should only be assigned once ```js assert(code.match(/quotient/g).length === 1); assert(code.match(/quotients*=/g).length === 1); ``` # --seed--"], "neg": []} {"query": "For me, both in Chrome and Edge (without any extensions) the cursor position is off by some characters (a tab?). It seems to happen after reloading the page (hard refresh) or even directly navigating to a challenge URL. to and complete the step. to the next challenge and check the cursor position, it should be fine. the page (hard refresh) and check the cursor position again, it is now off. ! Doesn't seem to happen in Firefox or when I tried it in the JS curriculum. Is this reproducible for anyone else? The only PR I found briefly looking at the commits for the editor is Might be causing this? Edit: I tried reverting the code from the PR and it didn't seem to help so I'm guessing that isn't it. Honestly not sure what is causing it but it seems to have happened between the Feb 28 build and the later production build. Edit 2: For anyone reading this looking for a fix. A normal (soft) page refresh should fix it. Firefox seems unaffected. The cursor position should not be borked after a page reload. No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] Forum:\ncouldn't replicate on edge version 111.0.1661.44 on chrome version 111.0.5563.65, I did have the issue tho, with some area isn't formatted correctly This picture from step 4 on cafe menu !\nMake sure it is a hard refresh. I didn't think it would matter but it seems like it does. I will update the repro steps.\nForum report\nYeab, still show sometime in chrome , couldn't replicate on edge Don't need to reload btw, Edit: I forgot to mute system sounds\nAdded another forum report on this bug. I'm actually surprised we have not yet seen more reports of this bug. But I'm guessing it is because it doesn't seem to trigger when just going through the curriculum using the normal ways of advancing between challenge steps. But man when this bug hits you it makes helping with challenges on the forum an absolute nightmare. I pretty much have to use Firefox (which I don't mind).\nThanks for opening this issue, and for all of the helpful details you provided to reproduce the issue. We've had one report of this issue in the support inbox so far. I wasn't able to reproduce the issue in Chrome on macOS, or in Chromium on an Ubuntu 22.04 VM. But I was able to reproduce the issue with your steps in Chrome on a Windows 11 VM. Once I did opened a challenge in Chrome on Windows and did a hard reload, the cursor position was off when I clicked into the editor or used the arrow keys to move around. The only fix I found is to do a regular reload of the page. Clicking the reset button in the UI, doing a hard reload, or right clicking on the reload button and selecting \"Empty Cache and Hard Reload\" didn't work on my end. Granted the VMs are ARM versions of Ubuntu and Windows running through Parallels, so that might have some effect on reproducing the issue and the workaround. if you do a regular reload of the page, is the cursor position fixed? Or is the position still off?\nYou are right, a normal reload does seem to fix it, at least 99% of the time (sometimes it takes two reloads). I guess because the opposite is usually the case I didn't even check it. I didn't think to look before, but the offset of the cursor position in the CSS is different and if you navigate using the arrow keys it doesn't jump the same amount of pixels between keyboard inputs (bugged cursor vs normal).\nWow, this is a weird bug. Just confirming as well that the only time I can trigger this is by doing a hard refresh (Shift + Reload button) using either Chrome or Edge on Win11. Firefox does not seem to be affected on Win11. None of these browsers seem to be affected on Linux. A soft refresh fixes the problem.\nHad this happen to me too. Refreshing didn't help, had to move to Firefox for a while.\nCould you give us more details about your setup, What browser were you using when you experienced this issue, and what version was it? Also, which OS are you running?\nChrome, latest version, Windows 10", "pos": ["accessibilitySupport: accessibilityMode ? 'on' : 'auto' }); document.fonts.ready .then(() => monaco.editor.remeasureFonts()) .catch(err => console.error(err)); // Focus should not automatically leave the 'Code' tab when using a keyboard // to navigate the tablist. if (!isMobileLayout || !isUsingKeyboardInTablist) {"], "neg": []} {"query": "Step 96Passed Give wave four waypoints starting at 10%, and incrementing by 10%. tests allow duplicate waypoints for the four required percentages. tests allow other waypoint values not specified in the instructions. wave { 10% { } 20% { } 10% { } 30% { } 10% { } 40% { } 10% { } 50% { } } When I read the instructions, I thought it said do four wave points starting at ten and add ten to each one. Once I failed. I calculated it to do each ten and add ten percent to each one after. I guess even though I did not read the instructions the way they were adviced I found a bug. I passed and when I went to next step it automatically fixed my mistake and removed the 50% also. 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] The instructions from what I read confused me to do four tens and add ten percent under each one. I was able to find the bug due to this so yay I am pleased to help. By doing a total of four I was able to add 50 percent, on the last one too. My suggestion to fix the sentence on instructions, would be to not say make four waves starting at ten. Instead maybe you could say make four waves start at 10 percent and then for the rest add ten percent to each one for a total of four waves only.\nWe should add new test with hint as following Here is the test If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our prolific contributors will guide you through this.\nCan I work on this ?\ngo for it. Edit: btw if you solve one of the two issue, leave the other for first timer.\nThis test should be at the last of the other tests right? I mean after completing the other tests. Checking for 4 wavepoints should be the last one right? like this : !\nGood point , if it's earlier it would trigger before the other, and wouldn't provide coherent hints for different issues.\n, I am a first-timer so I do not really know where to make these changes . Also do I need to add the logic using jest or can I just add it to the call-back function of the event listener of that button which submits the user input for that challenge. can i assist you ?\nIm working on this. Find another issue.\nI have made the changes (addition of code which is mentioned in the above screenshot) in this file : ! This should work now right?\nyeah you can work since obviously you got it assigned to yourself first . I am just here to learn . I just want to get familiar with the workflow that's it .", "pos": ["assert([...[...new __helpers.CSSHelp(document).getCSSRules('keyframes')].find(rule => rule?.name === 'wave')?.cssRules].some(css => css?.keyText === '40%')); ``` You should have 4 waypoints in your keyframe. ```js assert([...[...new __helpers.CSSHelp(document).getCSSRules('keyframes')].find(rule => rule?.name === 'wave')?.cssRules].length === 4); ``` # --seed-- ## --seed-contents--"], "neg": []} {"query": "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.", "pos": ["}; const StepPreview = ({ disableIframe }: Pick) => { disableIframe, previewMounted }: Pick) => { return ( executeChallenge executeChallenge, previewMounted }: ShowClassicProps) { const { t } = useTranslation(); const [resizing, setResizing] = useState(false);", "showToolPanel: false })} notes={} preview={} preview={ } testOutput={ }", "isFirstStep={isFirstStep} layoutState={layout} notes={} preview={} preview={ } resizeProps={resizeProps} testOutput={ "], "neg": []} {"query": "I've come across two forum posts from Safari users in the past few days saying that they can't pass step 47 even though their CSS is correct. Based on the hint they are getting, the test that is not passing is: I'm wondering if Safari has recently changed the string being returned for the border properties when set to ? I don't have a mac so I can't test this for myself. Opening this issue with the hopes that a Safari user can figure out what is going on here. Should be tested on a very recent version of Safari. This is the correct CSS but it is apparently not passing for Safari users. Correct CSS should pass. No response For both posters, user agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.4 Safari/605.1.15 No response", "pos": ["```js const borderBottom = new __helpers.CSSHelp(document).getStyle('fieldset:last-of-type')?.borderBottom; assert(borderBottom === 'none' || borderBottom === 'medium none'); assert(borderBottom === 'none' || borderBottom === 'medium none' || borderBottom === 'medium'); ``` # --seed--"], "neg": []} {"query": "When the user uses FreeCodeCamp on narrow screens like the Samsung galaxy fold, the FreeCodeCamp logo overlaps with the drop-down menu button and profile picture at the top of the page. to '' the developer tools dimensions select \"Galaxy fold\". the .png example in the screenshots section As a suggestion in this type of screens <= 280px * 653px we could remove the FCC fire logo or remove the profile picture to follow the responsive design rules. ! Device: [Laptop, Samsung Galaxy Fold, Pc] OS: [Android 12L ,Windows 11] Browser: [Chrome, OperaGx] No response\nBruce mentioned the possibility of changing the logo in this PR too I am kinda in favor, because of how many people started to associate freeCodeCamp with fCC, so change in logo may be possible. Note: that screens with size lower than aren't required to be supported as mentioned in his comment as well.\nbtw, the logo is on higher stack above the menu, so it isn't possible to click the menu. If we aren't changing the logo, changing the layout is the other option.\nHi What do you think about leaving only the \"FreeCodeCamp\" logo and removing the symbol? I think it would look more aesthetic xD and all the space would be fixed.\nI think a part of the menu will still be blocked , but I hope I am wrong. Your suggestion may be better than fCC, but I don't know the workflow on removing and how important it's. Another dev or prolific contributor with more experience can indicate how important is the glyph.\nI have solved this issue by dropping the fire icon. This is how it looks like. https://user-\nHey If you are working from a mobile Android device we recommend downloading the freeCodeCamp mobile app, which has a good mobile experience for the Responsive Web design certification.\nHey Thank you for making this change, although this works, it is in violation of our style guidelines. Please see them here: https://design-style-\nyeah, I was thinking that it will go against the guidelines. I think putting the \"sign in\" button inside the \"hamburger menu\" for small screens can be a possible solution.\nIf I am reading the guidelines correctly then just the glyph can be used. I'm sure the app is fine, but the web-based version should provide just as good an experience as the mobile app or we are doing something wrong. Also, just to be clear, since I might have started this in the first place, I am not insisting in any way that we adjust the header for very small widths. It was just an offhand suggestion in another PR that was somewhat related.\nYes. It probably wouldn't hurt to have a breakpoint that switched to the glyph, though I feel like this has been brought up (and turned down) before? might have more insight.\nHello, I am available to work on this issue. I believe I can solve this up you can Assignees the issue to me\nI have resolved the Navbar logo responsiveness bug in the Galaxy Fold This is how it looks like.And i can Make a PR !\ndiff my name is vivek\ndiff my name is vivek my name is vivek yadav\nWe could go with the glyph or make the logo a bit more responsive. Either way would work.\nBecause there are 4 PRs opened doing the same thing, I want to clear the requirement to close this issue. The CSS solution, the issue is cased by the existing property of in , removing it and refactoring the layout of the navbar, will sort the issue as shown below, without the need to add another break point. Why am I against adding a break point? because it's a solution to a side effect and not the solution to the real cause of the issue The HTML solution, use element with fallback to glyph SVG. You can find the glyph in the .\nFor context, either solution is an enhancement to the navbar, so if a PR is fixing the CSS, while the other is changing the picture element, I wouldn't mind approving both, as both will be an enhancement to the current navbar. But maybe it's better to choose one option, before opening this for contribution so I am pushing it to triage again.\nShouldn't the element be conditionally rendered using the component instead of just being empty? That way it won't push the logo and the logo doesn't have to be position absolute. Code we have now wrapping the element instead. I only looked at this briefly so I will admit I might have missed something. Edit: I made a PR just to show what I mean.\nYeab, you are correct.", "pos": ["} #universal-nav-logo { display: flex; position: absolute; padding-top: 0.2em; top: 0; } .expand-nav {", "className={`universal-nav${displayMenu ? ' expand-nav' : ''}`} id='universal-nav' >
          {search}
          {search}
          "], "neg": []} {"query": "The wording on this step is a bit awkward. Based on , the wording isn't quite accurate. This resulted in the camper writing the following code: I'm not sure how to better describe this, tbh. No response System info isn't relevant for a verbiage issue (: No response\nAgreed, that is clunky. Just to get the ball rolling.\nis anyone working on this, but i can take this up\nHey there, This issue is still under discussion and has not been opened up for contribution yet.\nHi there, I read through the issue related to the wording in step 5 of the 'Learn CSS Colors by Building a Set of Colored Markers' challenge, and I think I might have a suggestion for how to improve the wording. Here's a revised version of the step that I came up with: 'Add a new meta element for each attribute that you want to specify. To specify the viewport attributes, add the following meta element to the head of your HTML document: You can have multiple self-closing `meta` elements on a web page. What distinguishes one `meta` element from the other is the attribute. You should add a new meta element for each attribute you want to specify. You can have multiple self-closing `meta` elements on a web page. Each `meta` element adds information about the page that cannot be expressed by other HTML elements. Add another self-closing `meta` element within the `head`. Give it a `name` attribute set to `viewport` and a `content` attribute set to `width=device-width, initial-scale=1.0` so your page looks the same on all devices."], "neg": []} {"query": "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.", "pos": ["\"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\", \"preseed\": \"npm-run-all create:*\", \"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\","], "neg": []} {"query": "Please check this commit: There is a missing }) on line 524! Should look like this: ! 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\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: The intended change appears to be: 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 is anyone working on this issue? If not can I fix it?\nThanks for mentioning the issue. Its seems really easy to fix and I see some pull requests are already there. I am also looking for my first contribution but as per the ethics I should not create pull request for this issue.\nHi, is it still open can i work on it", "pos": ["date: new Date().toLocaleDateString(\"en-US\", { timeZone: \"UTC\", weekday: \"short\", month: \"short\", day: \"2-digit\", year: \"numeric\" }).replaceAll(',', '') }; const addRes = await fetch(url + `/api/users/${_id}/exercises`, { method: 'POST',"], "neg": []} {"query": "Currently, the instructions within the module happen to be as follows: Newer CSS features take time before they are fully adopted and ready to use in all browsers. As features are to browsers, CSS rules using them may need vendor prefixes. Consider : For the sake of clarity, the above instructions should also explicitly point out which bits within the given code snippet are vendor prefixes, instead of just simply mentioning the word vendor prefixes within the instructions and expecting the users to figure out themselves as in which parts within the given code snippet are vendor prefixes. The instructions within the module should be as follows: Newer CSS features take time before they are fully adopted and ready to use in all browsers. As features are to browsers, CSS rules using them may need vendor prefixes ( , , etc ). Consider the property below: In Sass, a mixin is a group of CSS declarations that can be reused throughout the style sheet. Newer CSS features take time before they are fully adopted and ready to use in all browsers. As features are added to browsers, CSS rules using them may need vendor prefixes. Consider `box-shadow`: In Sass, a mixin is a group of CSS declarations that can be reused throughout the style sheet. The definition starts with the `@mixin` at-rule, followed by a custom name. You apply the mixin using the `@include` at-rule. ```scss div { -webkit-box-shadow: 0px 0px 4px #fff; -moz-box-shadow: 0px 0px 4px #fff; -ms-box-shadow: 0px 0px 4px #fff; box-shadow: 0px 0px 4px #fff; @mixin reset-list { margin: 0; padding: 0; list-style: none; } nav ul { @include reset-list; } ``` Compiles to: ```css nav ul { margin: 0; padding: 0; list-style: none; } ``` It's a lot of typing to re-write this rule for all the elements that have a `box-shadow`, or to change each value to test different effects. Mixins are like functions for CSS. Here is how to write one: Your mixins can also take arguments, which allows their behavior to be customized. The arguments are required when using the mixin. ```scss @mixin box-shadow($x, $y, $blur, $c){ -webkit-box-shadow: $x $y $blur $c; -moz-box-shadow: $x $y $blur $c; -ms-box-shadow: $x $y $blur $c; box-shadow: $x $y $blur $c; @mixin prose($font-size, $spacing) { font-size: $font-size; margin: 0; margin-block-end: $spacing; } p { @include prose(1.25rem, 1rem); } h2 { @include prose(2.4rem, 1.5rem); } ``` The definition starts with `@mixin` followed by a custom name. The parameters (the `$x`, `$y`, `$blur`, and `$c` in the example above) are optional. Now any time a `box-shadow` rule is needed, only a single line calling the mixin replaces having to type all the vendor prefixes. A mixin is called with the `@include` directive: You can make arguments optional by giving the parameters default values. ```scss div { @include box-shadow(0px, 0px, 4px, #fff); @mixin text-color($color: black) { color: $color; } p { @include text-color(); /* color: black */ } nav a { @include text-color(orange); } ``` # --instructions-- Write a mixin for `border-radius` and give it a `$radius` parameter. It should use all the vendor prefixes from the example. Then use the `border-radius` mixin to give the `#awesome` element a border radius of `15px`. Write a mixin named `shape` and give it 3 parameters: `$w`, `$h`, and `$bg-color`. Use the `shape` mixin to give the `#square` element a width and height of `50px`, and the color `red`. For the `#rect-a` element add a width of `100px`, a height of `50px`, and the color `blue`. Finally, for the `#rect-b` element add a width of `50px`, a height of `100px`, and the color `orange`. # --hints-- Your code should declare a mixin named `border-radius` which has a parameter named `$radius`. You should declare a mixin named `shape` with 3 parameters: `$w`, `$h`, and `$bg-color`. ```js assert(code.match(/@mixins+?border-radiuss*?(s*?$radiuss*?)s*?{/gi)); assert.match(code, /@mixins+shapes*(s*$w,s*$h,s*$bg-colors*)s*{/gi); ``` Your code should include the `-webkit-border-radius` vendor prefix that uses the `$radius` parameter. Your mixin should include a `width` property that uses the `$w` parameter. ```js assert( __helpers.removeWhiteSpace(code).match(/-webkit-border-radius:$radius;/gi) ); assert.match(__helpers.removeWhiteSpace(code), /width:$w;/gi); ``` Your code should include the `-moz-border-radius` vendor prefix that uses the `$radius` parameter. Your mixin should include a `height` property that uses the `$h` parameter. ```js assert( __helpers.removeWhiteSpace(code).match(/-moz-border-radius:$radius;/gi) ); assert.match(__helpers.removeWhiteSpace(code), /height:$h;/gi); ``` Your code should include the `-ms-border-radius` vendor prefix that uses the `$radius` parameter. Your mixin should include a `background-color` property that uses the `$bg-color` parameter. ```js assert(__helpers.removeWhiteSpace(code).match(/-ms-border-radius:$radius;/gi)); assert.match(__helpers.removeWhiteSpace(code), /background-color:$bg-color;/gi); ``` Your code should include the general `border-radius` rule that uses the `$radius` parameter. You should replace the styles inside the `#square` selector with a call to the `shape` mixin using the `@include` keyword. Setting a width and height of `50px`, and the color `red`. ```js assert( __helpers.removeWhiteSpace(code).match(/border-radius:$radius;/gi).length == 4 ); assert.match(code, /#squares*{s*@includes+shape(s*50px,s*50px,s*reds*)s*;s*}/gi); ``` Your code should call the `border-radius mixin` using the `@include` keyword, setting it to `15px`. You should replace the styles inside the `#rect-a` selector with a call to the `shape` mixin using the `@include` keyword. Setting a width of `100px`, a height of `50px`, and the color `blue`. ```js assert(code.match(/@includes+?border-radius(s*?15pxs*?)s*;/gi)); assert.match(code, /#rect-as*{s*@includes+shape(s*100px,s*50px,s*blues*)s*;s*}/gi); ``` You should replace the styles inside the `#rect-b` selector with a call to the `shape` mixin using the `@include` keyword. Setting a width of `50px`, a height of `100px`, and the color `orange`. ```js assert.match(code, /#rect-bs*{s*@includes+shape(s*50px,s*100px,s*oranges*)s*;s*}/gi); ``` # --seed--", "```html
          ``` # --solutions-- ```html
          ```"], "neg": []} {"query": "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 Sometimes you may need to iterate through all the keys within an object. This requires a specific syntax in JavaScript called a for...in statement. For our `users` object, this could look like: Sometimes you need to iterate through all the keys within an object. You can use a for...in loop to do this. The for...in loop looks like: ```js for (let user in users) { console.log(user); ```javascript const refrigerator = { 'milk': 1, 'eggs': 12, }; for (const food in refrigerator) { console.log(food, refrigerator[food]); } ``` This would log `Alan`, `Jeff`, and `Sarah` - each value on its own line. This code logs `milk 1` and `eggs 12`, with each key-value pair on its own line. In this statement, we defined a variable `user`, and as you can see, this variable was reset during each iteration to each of the object's keys as the statement looped through the object, resulting in each user's name being printed to the console. We defined the variable `food` 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. **NOTE:** Objects do not maintain an ordering to stored keys like arrays do; thus a key's position on an object, or the relative order in which it appears, is irrelevant when referencing or accessing that key. # --instructions-- We've defined a function `countOnline` which accepts one argument (a users object). Use a for...in statement within this function to loop through the users object passed into the function and return the number of users whose `online` property is set to `true`. An example of a users object which could be passed to `countOnline` is shown below. Each user will have an `online` property with either a `true` or `false` value. We've defined a function `countOnline` which accepts one argument, `allUsers`. Use a for...in statement inside this function to loop through the `allUsers` object and return the number of users whose online property is set to `true`. An example of an object which could be passed to `countOnline` is shown below. Each user will have an `online` property set to either `true` or `false`. ```js {", "} } function countOnline(usersObj) { function countOnline(allUsers) { // Only change code below this line // Only change code above this line", "# --solutions-- ```js function countOnline(usersObj) { let online = 0; for(let user in usersObj){ if(usersObj[user].online) { online++; function countOnline(allUsers) { let numOnline = 0; for(const user in allUsers){ if(allUsers[user].online) { numOnline++; } } return online; return numOnline; } ```"], "neg": []} {"query": "A lot of campers do not understand they have to use the parameters and keep creating an object inside the function. I know this is verbose. Not sure if we need an example that uses a function as well: We might also want to add a call to the function in the seed code Campers should understand the function signature with its parameters and use them properly. 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]\nI would be fine changing the description to what you have suggested. Might as well. But, this is after many lessons teaching/involving arguments and parameters. Did we not recently spend time removing a bunch of these?\nI think so but I'm not entirely sure why? Seeing the function invocation can help in understanding the function definition. I think we are taking it for granted that they should look at the test output to see the invocation when in fact it is just the test status people look at. Yes, they should know better by now, but they don't. In fact, not understanding parameters/arguments is an overall issue we see. It can not have been reinforced properly because we see it all the time. My best guess is that too many of the challenges have premade functions and in not forcing people to write the function definition and invocation campers are left not fully understanding it.\nI think they were confusing Campers . Campers would write their function as though only the example call was what was being tested - they hard-coded based on the seed example call.\nI guess that makes some sense but that too points to the same issue. There is a disconnect between writing and running the code.\nI like the more explicit instructions. I'm not sure if the sample function call is the right band-aid for learners not understanding what a function call does?\nDo you mean the example function or adding the function call to the seed code? I believe it can help with pattern recognition. Seeing the definition and invocation in close proximity can help connect the dots between the parameters and arguments.\nThere's a non-insignificant number of learners who don't seem to understand much about how a function call works. I'm not sure that giving more examples of the thing they don't understand will target the underlying reason of why they don't understand it. The problem is though, I'm not sure why the idea of a function call's arguments giving values to the parameters is such a mysterious idea for some of the learners.\nBecause not having the definition and invocation in close proximity throughout the course is part of the underlying problem. The pattern isn't getting reinforced correctly (both through seeing and writing). Not enough functions are written from scratch and we (almost) never require the camper to execute the function with the correct arguments. One exception would be the recursion challenges. The TDD setup is creating a disconnect for beginners and I believe the way the test runner is implemented isn't helping. I have said this before, but I would prefer if the test running was embedded and exposed better in the UI, for example, the way it is on Codewars. It would require explaining the interface in the beginning as it is a bit technical. But the function getting called for the camper is a detail that often is lost until we explain it.", "pos": ["# --description-- Sometimes it is useful to check if the property of a given object exists or not. We can use the `.hasOwnProperty(propname)` method of objects to determine if that object has the given property name. `.hasOwnProperty()` returns `true` or `false` if the property is found or not. To check if a property on a given object exists or not, you can use the `.hasOwnProperty()` method. `someObject.hasOwnProperty(someProperty)` returns `true` or `false` depending on if the property is found on the object or not. **Example** ```js const myObj = { top: \"hat\", bottom: \"pants\" }; function checkForProperty(object, property) { return object.hasOwnProperty(property); } myObj.hasOwnProperty(\"top\"); myObj.hasOwnProperty(\"middle\"); checkForProperty({ top: 'hat', bottom: 'pants' }, 'top'); // true checkForProperty({ top: 'hat', bottom: 'pants' }, 'middle'); // false ``` The first `hasOwnProperty` returns `true`, while the second returns `false`. The first `checkForProperty` function call returns `true`, while the second returns `false`. # --instructions-- Modify the function `checkObj` to test if an object passed to the function (`obj`) contains a specific property (`checkProp`). If the property is found, return that property's value. If not, return `\"Not Found\"`. Modify the function `checkObj` to test if the object passed to the function parameter `obj` contains the specific property passed to the function parameter `checkProp`. If the property passed to `checkProp` is found on `obj`, return that property's value. If not, return `Not Found`. # --hints--"], "neg": []} {"query": "Some users are encountering the error in the linked video. See the forum for more discussion. All Console error messages should clear so users can run code No response various No response\nIf I revert the change from it seems to fix it.\nI am also facing this issue while doing javascript datastructures and algorithms course. The console errors are stuck and the solution is to refresh the page everysingle time.\nI also face this issue while doing a JavaScript data structures and algorithms course. The console errors are stuck and the solution is to refresh the page every single time.\nThanks for tracking that down, it was defintiely the culprit.", "pos": ["challengeFile.fileKey === fileKey ? { ...challengeFile, ...updates } : { ...challengeFile } ) ), isBuildEnabled: true }; }, [actionTypes.storedCodeFound]: (state, { payload }) => ({"], "neg": []} {"query": "Describe the bug When you try to make api call in the setting page, to change your subscription to Quincy newsletter, you will see a failed API call before the new one. To Reproduce Steps to reproduce the behavior: to 'Email Settings' in on unsubscribe from Quincy news-letter alert show before the success alert shown. Expected behavior Wait until the api fail before showing the alert", "pos": ["
          e.preventDefault()}> import { deprecatedEndpoints } from './routes/deprecated-endpoints'; import { auth0Routes, devLoginCallback } from './routes/auth'; import { testMiddleware } from './middleware'; import prismaPlugin from './db/prisma';", "void fastify.register(devLoginCallback, { prefix: '/auth' }); } void fastify.register(settingRoutes); void fastify.register(deprecatedEndpoints); return fastify; };", " import request from 'supertest'; import { build } from '../app'; import { endpoints } from './deprecated-endpoints'; describe('Deprecated endpoints', () => { let fastify: undefined | Awaited>; beforeAll(async () => { fastify = await build(); await fastify.ready(); }, 20000); afterAll(async () => { await fastify?.close(); }); endpoints.forEach(([endpoint, method]) => { test(`${method} ${endpoint} returns 410 status code with \"info\" message`, async () => { const response = await request(fastify?.server)[ method.toLowerCase() as 'get' | 'post' ](endpoint); expect(response.status).toBe(410); expect(response.body).toStrictEqual({ message: { type: 'info', message: 'Please reload the app, this feature is no longer available.' } }); }); }); }); ", " import { FastifyPluginCallbackTypebox, Type } from '@fastify/type-provider-typebox'; type Endpoints = [string, 'GET' | 'POST'][]; export const endpoints: Endpoints = [ ['/refetch-user-completed-challenges', 'POST'], ['/certificate/verify-can-claim-cert', 'GET'], ['/api/github', 'GET'] ]; export const deprecatedEndpoints: FastifyPluginCallbackTypebox = ( fastify, _options, done ) => { endpoints.forEach(([endpoint, method]) => { fastify.route({ method, url: endpoint, schema: { response: { 410: Type.Object({ message: Type.Object({ type: Type.Literal('info'), message: Type.Literal( 'Please reload the app, this feature is no longer available.' ) }) }) } }, handler: async (_req, reply) => { void reply.status(410); return { message: { type: 'info', message: 'Please reload the app, this feature is no longer available.' } } as const; } }); }); done(); }; "], "neg": []} {"query": "A user can fail with correct code because the tests secretly rely upon global variables accessible to the user. This code fails because the user has the correct solution but deleted the instantiation of the object. Tests should instantiate any data they need. We should update the seed code to We should then add and modify the test suite to use instead of . No response All No response\nHello, Just to clarify, did you want to add in the user code block? Because I noticed when I attempted to reproduce the bug you encountered that two test cases still passed, despite not being initialized in the user's code. I checked the lesson's markdown file and found out that those two test cases did have their own initialized. I was thinking of adding to all the test cases instead. For reference, here's the code for one of the test cases that still passed, despite the bug.\nThose tests initiate their own values so they are fine. I'm talking about the tests that fail if users modify their seed code to not have the object initialization. The new variable would go into a new --after-user-code-- part; that's not currently present. Just adding this new variable inside of the seed creates the exact same problem. Note - this issue isn't marked as ready for contributions yet. Maybe we should review if the tests logic too to see if they are independent\nOpening this up for contribution.\nHi assign this issue for branch bugfix/. I have resolved it, need to create PR for same\nWe don't assign issues. The first PR that fully covers the issue will be accepted.\nHi ok !! I have raised PR . thanks for reply.", "pos": ["`bob instanceof Person` should return `true`. ```js assert.deepEqual(bob instanceof Person, true); assert.deepEqual(_test_bob instanceof Person, true); ``` `bob.firstName` should return `undefined`. ```js assert.deepEqual(bob.firstName, undefined); assert.deepEqual(_test_bob.firstName, undefined); ``` `bob.lastName` should return `undefined`. ```js assert.deepEqual(bob.lastName, undefined); assert.deepEqual(_test_bob.lastName, undefined); ``` `bob.getFirstName()` should return the string `Bob`. ```js assert.deepEqual(bob.getFirstName(), 'Bob'); assert.deepEqual(_test_bob.getFirstName(), 'Bob'); ``` `bob.getLastName()` should return the string `Ross`. ```js assert.deepEqual(bob.getLastName(), 'Ross'); assert.deepEqual(_test_bob.getLastName(), 'Ross'); ``` `bob.getFullName()` should return the string `Bob Ross`. ```js assert.deepEqual(bob.getFullName(), 'Bob Ross'); assert.deepEqual(_test_bob.getFullName(), 'Bob Ross'); ``` `bob.getFullName()` should return the string `Haskell Ross` after `bob.setFirstName(\"Haskell\")`.", "```js assert.strictEqual( (function () { bob.setFirstName('Haskell'); return bob.getFullName(); _test_bob.setFirstName('Haskell'); return _test_bob.getFullName(); })(), 'Haskell Ross' );", "```js assert.strictEqual( (function () { bob.setFullName('Haskell Curry'); return bob.getFullName(); _test_bob.setFullName('Haskell Curry'); return _test_bob.getFullName(); })(), 'Haskell Curry' );", "```js assert.strictEqual( (function () { bob.setFullName('Haskell Curry'); return bob.getFirstName(); _test_bob.setFullName('Haskell Curry'); return _test_bob.getFirstName(); })(), 'Haskell' );", "```js assert.strictEqual( (function () { bob.setFullName('Haskell Curry'); return bob.getLastName(); _test_bob.setFullName('Haskell Curry'); return _test_bob.getLastName(); })(), 'Curry' );", "# --seed-- ## --after-user-code-- ```js const _test_bob = new Person('Bob Ross'); ``` ## --seed-contents-- ```js const Person = function(firstAndLast) { // Only change code below this line // Complete the method below and implement the others similarly this.getFullName = function() { return \"\"; };"], "neg": []} {"query": "Course: Front End Development Libraries Certification Section: Bootstrap Lesson: Add Font Awesome Icons to all of our Buttons The wording is as follows: \"Note: The span element is an acceptable alternative to the i element for the directions below.\" The word \"below\" is wrong. The instructions are above, not below. Switch word \"below\" with \"above\". None/ not applicable to issue. N/A, not applicable to issue Issue is found within the text of the instructions N/a, not applicable This is only a grammatical error found in the instructions for the challenge.\nI think the directions mentioned here is the tests.\nYes, this is referring to the instructions in the test text, which is where the element is requested.\nMaybe something like this would be clearer\nThe challenge will accept span elements.\nAhh. So we should probably say something more like\nThat one works for me. Thanks for opening this issue. 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: You should update the instruction text to replace: With: Please make sure you read 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.\nI would like to work on this issue could you please assign it to me\nWe don't assign issues. We accept the first complete pull request that fully addresses the issue\nVery excited", "pos": ["Use Font Awesome to add an `info-circle` icon to your info button and a `trash` icon to your delete button. **Note:** The `span` element is an acceptable alternative to the `i` element for the directions below. **Note:** You can use either `i` or `span` elements to complete this challenge. # --hints--"], "neg": []} {"query": "Looking forward for reporting a security issue: Please report security issues by following our security policy: Describe the bug I don't know if fcc is paying for CI runs so maybe this doesn't matter. While waiting for CI to run, I noticed that both and run . What actually takes the longest is which is only linting .md files so that probably doesn't need to run twice eh? To Reproduce Steps to reproduce the behavior: output of pnpm run lint Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Desktop (please complete the following information): n/a Smartphone (please complete the following information): n/a Additional context Add any other context about the problem here.", "pos": [" name: CI - Node.js Test Upcoming env: NODE_OPTIONS: '--max_old_space_size=6144' on: # Run on push events, but only for the below branches push: branches: - 'main' - 'prod-**' # Run on pull requests, but only for the below targets pull_request: branches: - 'main' - 'next-**' schedule: # run this Action every 14 days - cron: '0 * */14 * *' # Run on demand workflow_dispatch: permissions: contents: read jobs: lint: name: Lint runs-on: ubuntu-20.04 strategy: matrix: node-version: [18.x] fail-fast: false steps: - name: Checkout Source Files uses: actions/checkout@8e5e7e5ab8b370d6c329ec480221332ada57f0ab # v3 - name: Setup pnpm uses: pnpm/action-setup@v2 with: version: 8 - name: Use Node.js ${{ matrix.node-version }} uses: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c # v3 with: node-version: ${{ matrix.node-version }} cache: pnpm - name: Set Environment variables run: | cp sample.env .env echo 'SHOW_UPCOMING_CHANGES=true' >> .env echo 'SHOW_NEW_CURRICULUM=true' >> .env cat .env - name: Lint Source Files run: | pnpm install pnpm run create:config npm i --prefix=curriculum-server npm i --prefix=web pnpm run build:curriculum pnpm run lint test: name: Test needs: lint runs-on: ubuntu-20.04 strategy: fail-fast: false matrix: node-version: [18.x] steps: - name: Checkout Source Files uses: actions/checkout@8e5e7e5ab8b370d6c329ec480221332ada57f0ab # v3 - name: Setup pnpm uses: pnpm/action-setup@v2 with: version: 8 - name: Use Node.js ${{ matrix.node-version }} uses: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c # v3 with: node-version: ${{ matrix.node-version }} cache: pnpm - name: Set Environment variables run: | cp sample.env .env echo 'SHOW_UPCOMING_CHANGES=true' >> .env echo 'SHOW_NEW_CURRICULUM=true' >> .env cat .env - name: Start MongoDB uses: supercharge/mongodb-github-action@d26215f71b2ce60420a2a3776a25893d11a65f85 # 1.9.0 with: mongodb-version: 6.0 mongodb-replica-set: test-rs mongodb-port: 27017 - name: Install Dependencies run: | pnpm install pnpm run create:config pnpm run build:curriculum - name: Run Tests run: pnpm test ", "- name: Run Tests run: pnpm test test-new: name: Test New Curriculum needs: lint runs-on: ubuntu-20.04 strategy: fail-fast: false matrix: node-version: [18.x] steps: - name: Checkout Source Files uses: actions/checkout@8e5e7e5ab8b370d6c329ec480221332ada57f0ab # v3 - name: Setup pnpm uses: pnpm/action-setup@v2 with: version: 8 - name: Use Node.js ${{ matrix.node-version }} uses: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c # v3 with: node-version: ${{ matrix.node-version }} cache: pnpm - name: Set Environment variables run: | cp sample.env .env echo 'SHOW_UPCOMING_CHANGES=true' >> .env echo 'SHOW_NEW_CURRICULUM=true' >> .env cat .env - name: Start MongoDB uses: supercharge/mongodb-github-action@d26215f71b2ce60420a2a3776a25893d11a65f85 # 1.9.0 with: mongodb-version: 6.0 mongodb-replica-set: test-rs mongodb-port: 27017 - name: Install Dependencies run: | echo pnpm version $(pnpm -v) pnpm install pnpm run create:config pnpm run build:curriculum - name: Run Tests run: pnpm test test-localization: name: Localize needs: lint"], "neg": []} {"query": "This is a a health check endpoint\nCheck the issue of internet ping, connect with network [ ]way run of tickettttttttt....... thank", "pos": ["} from './utils/env'; import { userRoutes } from './routes/user'; import { donateRoutes } from './routes/donate'; import { statusRoute } from './routes/status'; export type FastifyInstanceWithTypeProvider = FastifyInstance< RawServerDefault,", "void fastify.register(donateRoutes); void fastify.register(userRoutes); void fastify.register(deprecatedEndpoints); void fastify.register(statusRoute); return fastify; };", " import { setupServer, superRequest } from '../../jest.utils'; describe('/status', () => { setupServer(); test('GET returns 200 status code with pong', async () => { const response = await superRequest('/status/ping', { method: 'GET' }); expect(response.body).toStrictEqual({ msg: 'pong' }); expect(response.status).toBe(200); }); }); ", " import { type FastifyPluginCallbackTypebox } from '@fastify/type-provider-typebox'; export const statusRoute: FastifyPluginCallbackTypebox = ( fastify, _options, done ) => { fastify.get('/status/ping', async (_req, _reply) => { return { msg: 'pong' }; }); done(); }; "], "neg": []} {"query": "In module, the users are supposed to add their code after the provided code snippet. Keeping that in mind, the comment ( within the provided code snippet ) should be changed from to . In module, the provided code snippet should look as follows: ! Device: Laptop OS: macOS 13.0.1 Browser: Chrome Version: 107.0.5304.110", "pos": ["

          Lets render this to the DOM

          ); // Change code below this line // Add your code below this line ``` # --solutions--", "

          Lets render this to the DOM

    ); // Change code below this line // Add your code below this line ReactDOM.render(JSX, document.getElementById('challenge-node')); ```"], "neg": []} {"query": "On , the task is to use the spread operator to copy an array. JS semantics allow the spread operator to have whitespace between it and the object it is being applied to. The following is valid: However, in the challenge, any whitespace between the operator and the value will cause the test to fail. The issue is with the test regex here: Which should probably be amended to: NOTE: this issue was , I am submitting it on their behalf. Whitespace between the spread operator and the object it is being applied to should not cause the test to fail. 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\nLooks like a good beginner friendly fix to me\nThanks for opening this issue. 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 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.", "pos": ["The `copyMachine` function should utilize the `spread operator` with array `arr` ```js assert(code.match(/...arr/)); assert(code.match(/...s*arr/)); ``` # --seed--"], "neg": []} {"query": "Looking forward for reporting a security issue: Please report security issues by following our security policy: Describe the bug A clear and concise description of what the bug is. Gitpod can't be used to develop right now. Or maybe it's possible but someone new wouldn't know what steps they need to take. Should i add a note in how-to-setup-freecodecamp- so that new people know? To Reproduce Steps to reproduce the behavior: instructions in how-to-setup-freecodecamp-locally to develop with gitpod, fails with message\nThanks for letting us know On the pnpm side this should be resolved by any idea why our .gitpod.Dockerfile isn't already using the latest version of pnpm?\nBecause I have forsaken the local config to focus on: For this repo, I have just been manually running . Personally, I do not like everything running from the get-go, but realise many like the one-button setup. This is so quick to fix, I will just PR it before the long-term fix is ready.", "pos": ["RUN bash -c 'VERSION=\"18\" && source $HOME/.nvm/nvm.sh && nvm install $VERSION && nvm use $VERSION && nvm alias default $VERSION && npm i -g pnpm@8' && npm i -g pnpm@8.6' RUN echo \"nvm use default &>/dev/null\" >> ~/.bashrc.d/51-nvm-fix"], "neg": []} {"query": "I've run into this enough in the forums that it might be time to fix it. A lot of people leave off the closing tag when turning the image into a link. The hint they get is: \"You should only add one opening anchor (a) tag. Please remove any extras.\" Which is confusing since the objective of the step is to add a second link to the page and the hint makes it sound like there should only be one. Instead, the hint should probably remind them that an anchor element needs both an opening and closing tag. Whether we want to spell it out even further by telling them that they are missing the closing tag I will leave up to the hive mind. If we don't want to be too explicit we could do something like: \"Hint: Creating a link with the anchor element requires both an opening and closing tag.\" Or: \"Hint: You must use both an opening and closing tag to create a link.\" Or if we want to be more direct: \"Hint: You are missing a closing tag after the image.\" No response N/A No response\nI think being explicit about a closing tag being needed is the way to go this early in the curriculum\nLet us go with this.\nYeah I read through your Issue and it is quite confusing to get this hint. The explicit hint you mentioned is the way to go.\nCan I make that change ? I just did this locally and works.\nThis has a help wanted tag, so anyone is free to open a PR for this.\nI think that we need to decide exactly what to change - just changing the text of the hint without changing the associated test will cause more problems\nIs this designed just to discourage newbies like me? Over an hour on this step. No previously posted code nor clarifications helped... just sent me down new rabbit holes. You need to know code to decipher the clarifications. Must be part of a hazing process. THIS code works as of the date of this posting: = 2); ``` You should only add one opening anchor (`a`) tag. Please remove any extras. You are missing a closing (`a`) tag after the image. ```js assert(document.querySelectorAll('a').length === 2);"], "neg": []} {"query": "Currently, the instructions in module happens to be as follows: The instructions tell the users that instead of setting the font size property to a number ( i.e. 72 ), they can optionally set the font size property to but don't inform the user that needs to be enclosed within quotes i.e. needs to be a string value. Furthermore, the word units in the second sentence should be changed to unit because in this particular case, we are just referring to a single unit i.e. . Considering this, I think the instructions of module should be reworded as follows: The instructions in module should be as follows: \"image\" Note that you can optionally set the font size to be a number, omitting the units `px`, or write it as `72px`. Note that you can optionally set the font size to be a number, omitting the units `px`, or write it as `\"72px\"`. # --hints-- The component should render a `div` element."], "neg": []} {"query": "Some steps are placing unnecessary horizontal scrollbars on plain text content. The content is being treated as a code example and thus is not line wrapping normally. Also, the content is coded as one continuous line with no newlines, thus causing a very long horizontal scroll and making it more difficult to copy. There are exceptions for having horizontal scrollbars in WCAG, but those exceptions are for content \"which require two-dimensional layout for usage or meaning\" (). Actual code examples can fall under this exception, but I think it would be much harder to argue that pure text content like this \"requires\" that it not line wrap normally in order to be understood. There are several instances of this in the CSS Magazine course: Steps 11, 12, 13, 15, 16, 17. These are the ones I know of. N/A Present this non-code content on the page in a way that it is allowed to line wrap normally. I am able to do this by removing from the element. I'm noticing we are using to code this in the challenge files: markup Soon the freeCodeCamp curriculum will be 100% project-driven learning... This causes the element to have the class . If we are only using for these types of non-code examples then perhaps we can use that class to remove the property. No response N/A No response\nHello can I work on this issue", "pos": ["text-shadow: none !important; } /* remove horizontal scrollbars for text-only code */ code[class='language-markup'] { white-space: normal !important; } /* a11y color adjustments */ :not(.dark-palette) .token.comment, :not(.dark-palette) .token.prolog,"], "neg": []} {"query": "Currently, the second paragraph in module, happens to be as follows: The first line of the second paragraph seems to be a bit incomplete. Considering that, I believe the first line of the second paragraph should be as follows: The first line of the second paragraph of module, should be as follows: \"image\" Recall that action creators return an object with a type property that specifies the action that has occurred. Then the method dispatches an action object to the Redux store. Based on the previous challenge's example, the following lines are equivalent, and both dispatch the action of type `LOGIN`: Recall that action creators return an object with a type property that specifies the type of action that has occurred. Then the method dispatches an action object to the Redux store. Based on the previous challenge's example, the following lines are equivalent, and both dispatch the action of type `LOGIN`: ```js store.dispatch(actionCreator());"], "neg": []} {"query": "Currently, the instructions in module, mention about subsection, which is a subsection of a completely different course ( i.e. course ). At the moment, those instructions in module, only mention the name of the \"Managing Packages with NPM\" subsection and no link has been provided to that particular subsection. Keeping that in mind, I believe to make it easier for the user to navigate to the subsection from within the instructions of module, a link to the subsection should be provided within the module. Hence, taking the above point into consideration, I believe the last line in the first paragraph of module, should be changed from: To The last line in the first paragraph of module, should be changed to: \"image\" Congratulations! You finished the lessons on React and Redux. There's one last item worth pointing out before you move on. Typically, you won't write React apps in a code editor like this. This challenge gives you a glimpse of what the syntax looks like if you're working with npm and a file system on your own machine. The code should look similar, except for the use of `import` statements (these pull in all of the dependencies that have been provided for you in the challenges). The \"Managing Packages with npm\" section covers npm in more detail. Congratulations! You finished the lessons on React and Redux. There's one last item worth pointing out before you move on. Typically, you won't write React apps in a code editor like this. This challenge gives you a glimpse of what the syntax looks like if you're working with a file system on your own machine. The code should look similar, except for the use of `import` statements (these pull in all of the dependencies that have been provided for you in the challenges). Finally, writing React and Redux code generally requires some configuration. This can get complicated quickly. If you are interested in experimenting on your own machine, the Create React App comes configured and ready to go."], "neg": []} {"query": "Unnecessary borders are displayed around each line in the solution code of certification projects. For example: to someone's certification page on 'View' ('View Code') to see the solution code Each line in the solution code should not have borders around it ! Device: Laptop OS: Windows 10 Browser: Chrome Version: 114.0.5735.199 (Official Build) (64-bit) The border seems to be in\nHi the borders on the code doesnt seem to be a good UX. I would like to take up this issue.\nHello! I would like to work on this issue. Seems to be a quick fix.\nHey. Contributions are very welcome. Please take a look at to get started.\n! Would this sample look better ?\nI have fixed the issue and created a pull request . Please review it and let me know if there are any concerns.\nTo solve the issue move the properties in , to CSS selector that affects the challenges' layout, or doesn't affect the setting layout.\nSimply removing the border property in fixes the issue ! ! Is it fine if done this way? I have reverted the changes I made to the bootstrap file back to its original form.\nHow can we find those code files from the repo ? If the particular link to the file is not provided in the issue.\nHello I would like to request to be assigned to fix this\nHi! I would like to take up this issue", "pos": ["border-color: var(--tertiary-color); } code { border: 1px solid var(--secondary-color); padding: 1px 4px; background-color: var(--quaternary-background); color: var(--tertiary-color);", "overflow-wrap: anywhere; } :not(pre) > code { border: 1px solid var(--secondary-color); } .challenge-instructions code { white-space: break-spaces; }", "code[class*='language-'], pre[class*='language-'] { border-radius: 0; border: none; } pre {"], "neg": []} {"query": "This code has the comments, but really we shouldn't be using variables in the user code for tests. Rewrite test to use private variable. No response All No response", "pos": ["assert(!code.match(/.?[sS]*?splice/g)); ``` The `inputCities` array should not change. You should not mutate the original array passed to the function. ```js assert( JSON.stringify(inputCities) === JSON.stringify(['Chicago', 'Delhi', 'Islamabad', 'London', 'Berlin']) ); assert.deepEqual(_inputCities, [\"Chicago\", \"Delhi\", \"Islamabad\", \"London\", \"Berlin\"]); ``` `nonMutatingSplice([\"Chicago\", \"Delhi\", \"Islamabad\", \"London\", \"Berlin\"])` should return `[\"Chicago\", \"Delhi\", \"Islamabad\"]`. ```js assert( JSON.stringify( nonMutatingSplice(['Chicago', 'Delhi', 'Islamabad', 'London', 'Berlin']) ) === JSON.stringify(['Chicago', 'Delhi', 'Islamabad']) ); assert.deepEqual(nonMutatingSplice(_inputCities), [\"Chicago\", \"Delhi\", \"Islamabad\"]); ``` # --seed--", "```js function nonMutatingSplice(cities) { // Only change code below this line return cities.splice(3); // Only change code above this line return cities.splice(3); } ``` const inputCities = [\"Chicago\", \"Delhi\", \"Islamabad\", \"London\", \"Berlin\"]; nonMutatingSplice(inputCities); ## --after-user-code-- ```js const _inputCities = [\"Chicago\", \"Delhi\", \"Islamabad\", \"London\", \"Berlin\"]; ``` # --solutions--", "function nonMutatingSplice(cities) { return cities.slice(0,3); } const inputCities = [\"Chicago\", \"Delhi\", \"Islamabad\", \"London\", \"Berlin\"]; ```"], "neg": []} {"query": "There appears to be a slight typo in the English instructions on Step 41 of \"Learn Typography by Building a Nutrition Label\". The instructions are displayed on the file and read as: The typo is with the text: . The and

    The text `* Daily Value %` should be aligned to the right. Create a `.right` selector and use the `justify-content` property to do it. The text `% Daily Value *` should be aligned to the right. Create a `.right` selector and use the `justify-content` property to do it. # --hints--"], "neg": []} {"query": "We got a report that the current test for Step 23 of the Learn CSS Animation by Building a Ferris Wheel project fails in the latest version of Safari. The test works as expected in Firefox and Chrome. This test should pass with the above code like it does in Firefox and Chrome. No response Device: Macbook Air OS: macOS Browser: Safari Version: 16.5.2 In of this project, the CSS helper () returns the string when the correct code is submitted in both Chrome and Firefox. In the latest version of Safari, the CSS helper returns . The test in the should be updated to check for both strings so learners using all supported browsers can complete this step. If this is an issue for other people running Safari, this would be a good candidate for someone's first PR.\nAnother arguably more verbose option is to look at each individual property. I suspect they will never change values or be different between browsers so that might be more future-proof than looking at the shorthand value.\nThanks for sharing that, I agree \u2013 it would be much more future-proof to test those properties / values individually. I'm not sure what our CSS Helper library returns for each individual property in the browsers we support. But if they're consistent across Chrome, Firefox, and Safari, testing each one would be a much better approach.", "pos": ["Your `.cabin` selector should have an `animation` property set to `cabins 10s linear infinite`. ```js assert(new __helpers.CSSHelp(document).getStyle('.cabin')?.animation === '10s linear 0s infinite normal none running cabins'); const cabinElementStyles = new __helpers.CSSHelp(document).getStyle('.cabin'); assert( cabinElementStyles?.animationName === \"cabins\" && cabinElementStyles?.animationDuration === \"10s\" && cabinElementStyles?.animationTimingFunction === \"linear\" && cabinElementStyles?.animationIterationCount === \"infinite\" ); ``` # --seed--"], "neg": []} {"query": "The hint text for one of the tests in step 54 of the Learn Typography By Building a Nutrition Label project has a minor typo. This typo isn't visible unless a learner fails a specific test. The hint text currently reads \"A element should wrap the text \". It should be updated to \"A element should wrap the text \" to match the instructions for this step, and the test itself. This would be a great first PR for new contributors.\nI will be working on it.\nwhy cloning the repo is throwing errors? I have been trying for 52 minutes\nAdd Newly generated SSH key from your device to your github account then clone\nThe problem is not with SSH key as half of the repo gets cloned and other gets skipped or deleted. The repo is too large to get cloned, I tried increasing buffer size but it didn't worked. Have you tried cloning it? Cloning depth wise might help but problem could be different if it is only appearing in my machine.\nI just forked the main branch of the repository on my account and then git cloned that repository on to my local machine.", "pos": ["assert(document.querySelector('.daily-value.small-text')?.lastElementChild?.querySelectorAll('span')?.length === 3); ``` A `span` element should wrap the text `Sodium 360mg`. A `span` element should wrap the text `Sodium 160mg`. ```js assert(document.querySelector('.daily-value.small-text')?.lastElementChild?.firstElementChild?.innerText?.match(/Sodium[s|n]160mg/));"], "neg": []} {"query": "The instructions for the JS challenge Seek and Destroy clearly say \"Note: You have to use the object.\" But yet you can pass this challenge without using the object by modifying the function to use a rest parameter to capture the additional arguments. In addition, there is also a solution in the hints that uses this exact technique. This code passes: Unless we have a specific reason for wanting the user to use the object, I think the rest parameter version is the more acceptable approach and we should be pushing that one, or at the least we should not be telling the user that they have to use the object if they really don't have to. The question is, how helpful do we want to be setting up the function? Do we want to add a rest parameter to the function definition? Or do we want to keep it as is (with just the argument) and then the note can say that you can use either the object or you can add a rest parameter to the arguments list? No response N/A No response\nP.S. I just realized that maybe we aren't making updates to these JS challenges any more because we will be switching to the new format soon. If so, let me know and I'll close this.\nI'd be good with either dropping the hint or saying that either arguments parameter or rest parameter is needed. I think I have a mild preference for the first. We are still making updates to these challenges, but only small updates.\nYeah, I think dropping the instruction is fine. Given that this is the intermediate algorithm section, we should be less concerned with the implementation and more concerned that it works. Since we test with variadic arguments, any implementation should be fine.\nI think it's just meant as a hint and its age is why it only talks about the object. I'm not sure we can't have a hint and just call it that. I updated the hint page on the forum a bit.\nI like the idea of changing the current note in the instructions to let them know that they can modify the function by adding a rest parameter. I would word it something like the following: My concern is that since we seed the function with only the argument, some people might not think they are allowed to add a rest parameter.\nThat works for me. I might suggest switching the order so the bit about the arguments object comes last (to give the rest parameter higher priority). It does feel to me like the information can be integrated as part of the main challenge description and requirements without it needing a note section. But I guess I'm fine with either way.\nI like that, yes.", "pos": ["# --description-- You will be provided with an initial array (the first argument in the `destroyer` function), followed by one or more arguments. Remove all elements from the initial array that are of the same value as these arguments. You will be provided with an initial array as the first argument to the `destroyer` function, followed by one or more arguments. Remove all elements from the initial array that are of the same value as these arguments. **Note:** You have to use the `arguments` object. The function must accept an indeterminate number of arguments, also known as a variadic function. You can access the additional arguments by adding a rest parameter to the function definition or using the `arguments` object. # --hints--"], "neg": []} {"query": "instructions state -10px failed test done incorrectly. error states that it must be -1degerror instruction bug proven. please be grateful free testing again to your company. I would like to one day do corrections to updated things like this on github, step 78 new responsive web design did not pass with clear instructions. error says -1deg ! 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\nThanks for opening this issue. 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: The test text should be updated to . Please make sure you read 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.\nOpen Source is based upon free contributions. We're always grateful for efforts that move the codebase forward.", "pos": ["# --hints-- Your `.cat-whisker-right-top` selector should have a `transform` property set to `rotate(-1deg)`. Your `.cat-whisker-right-top` selector should have a `transform` property set to `rotate(-10deg)`. ```js assert(new __helpers.CSSHelp(document).getStyle('.cat-whisker-right-top')?.transform === 'rotate(-10deg)')"], "neg": []} {"query": "Uploads: Everyday Downloads: Twice a week This should suffice our deployment targets which are usually Tuesdays? and Thursdays (optional) at around UTC+3 We can shake it up so that PRs can be merged on Mondays and Wednesdays?\nSo downloads should be triggered on Mondays and Wednesdays?\nYes, or a day before, for all we care. As long as they are: a week only on Mondays and Wednesdays for deployments on Tuesdays and Thursdays", "pos": ["on: workflow_dispatch: schedule: # runs every weekday at 12:15 PM UTC - cron: '15 12 * * 1-5' # runs Monday and Wednesday at 12:15 PM UTC - cron: '15 12 * * 1,3' env: GITHUB_TOKEN: ${{ secrets.CROWDIN_CAMPERBOT_PAT }}", "on: workflow_dispatch: schedule: # runs every weekday at 12:30 PM UTC - cron: '30 12 * * 1-5' # runs Monday and Wednesday at 12:15 PM UTC - cron: '15 12 * * 1,3' env: GITHUB_TOKEN: ${{ secrets.CROWDIN_CAMPERBOT_PAT }}", "on: workflow_dispatch: schedule: # runs every weekday at 12:00 noon UTC - cron: '0 12 * * 1-5' # runs Monday and Wednesday at 12:15 PM UTC - cron: '15 12 * * 1,3' env: GITHUB_TOKEN: ${{ secrets.CROWDIN_CAMPERBOT_PAT }}"], "neg": []} {"query": "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.", "pos": ["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. Instead of `static`, give you `.cat-head` a position of `relative`, and leave both `top` and `left` properties as they are. Instead of `static`, give your `.cat-head` a position of `relative`, and leave both `top` and `left` properties as they are. # --hints--"], "neg": []} {"query": "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:", "pos": ["## --text-- Which of the following describes the affect of a `using` statement? Which of the following statements is true about showing/removing the curly braces for code blocks associated with an `if` statement? ## --answers-- Affects only the first code block in the code file. The curly braces can't be removed from the code block for `else if` and `else` statements. --- Affects only the current code block in the code file. If the curly braces are removed from the code blocks of an `if-elseif-else`, the white space must also be removed. --- Affects all of the code in the code file. Always choose a style that improves readability. ## --video-solution--"], "neg": []} {"query": "We see this every so often and it might warrant a note. See the examples for more context. Warn the user so they do not waste time debugging something that is out of their control. 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] Examples:\nThanks for opening this. I forgot this was still a thing. An issue with the 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: To Close This Issue Change this file: Add the following to the description: If you have any issues with contributing, be sure to join us on the , or on the\nI hope this message finds you well. I am writing to seek your advice and assistance regarding a minor issue I've encountered with a project I am working on. As a beginner, your guidance and support would be greatly appreciated. In the course of my work, I've noticed that the tests for this project do not function properly when using To ensure transparency and clarity, I believe it would be beneficial to add a note in the project documentation, specifically under the \"Note\" section, stating the following: Note: This project's tests do not work when using I believe that adding this note would help inform other contributors and users about this limitation, ensuring a smoother development and testing process for everyone involved. Furthermore, I would like to seek your opinion on whether it would be appropriate to raise a Pull Request (PR) to implement this change. Your guidance on this matter would be invaluable to me as a newcomer to the project. I genuinely believe that your expertise could help me navigate this process more effectively. Your mentorship has been an inspiration to me, and I am truly grateful for any assistance you can provide. If adding the mentioned note is indeed the appropriate action to take, I would be thrilled to have the opportunity to submit a PR for this purpose. Your approval and support in merging the PR would be an incredible motivation for me to continue contributing to the project. I would be grateful for your thoughts and guidance on this matter. Your expertise and mentorship are highly regarded, and I look forward to your response. Thank you for your time and consideration. Sincerely, K S Sai Teja\nI have raised PR. Regarding this issue.. Please review my PR.", "pos": ["When you are done, make sure a working demo of your project is hosted somewhere public. Then submit the URL to it in the Solution Link field. Optionally, also submit a link to your project's source code in the GitHub Link field. **Note:** This project's tests do not work when using `glitch.com`. # --instructions-- - Complete the necessary conversion logic in `/controllers/convertHandler.js`"], "neg": []} {"query": "Challenge can be passed with solution that will serve files from the root folder, not just directory. Ref By using as a path serving static assets, and not giving explicit path to the , the static assets will be served from (root folder in this case) at the (root) path. Since folder is then served where it is expected to be served, this fulfills test requirements: However, using just serves also other files and directories, starting from the root folder. Ie. or . Reasonable solution seems to be adding test that will check if one of the files from root folder (ie. are not served as static assets. To reproduce: replit starter from to , below line : replit on passes works, so is or . Files outside of folder should not be served as static assets. Otherwise the test should fail. No response No response_\nThanks for opening this. This does sound like a reasonable fix. An issue with the 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", "pos": ["); ``` Your app should not serve files from any other folders except from `/public` directory ```js (getUserInput) => $.get(getUserInput('url') + '/server.js').then( (data) => { assert.equal( data?.status + '', 404 + '', 'Your app must serve files only from \"public\" directory' ); }, (xhr) => { assert.equal( xhr?.status + '', 404 + '', 'Your app must serve files only from \"public\" directory' ); } ); ``` # --solutions-- ```js"], "neg": []} {"query": "Hello FreeCodeCamp team, I found a minor typo in the JavaScript learning module. In the lesson titled \"Use getters and setters to Control Access to an Object,\" there is a small error in the instruction related to creating a getter and setter for temperature conversion. Here's the specific portion of the instruction that needs correction: Incorrect Line: \"In the class, create a getter to obtain the temperature in Celsius and a setter to set the temperature in Celsius.\" Suggested Correction: \"In the class, create a getter to obtain the temperature in Celsius and a setter to set the temperature in Fahrenheit.\" This correction is necessary to maintain clarity and accuracy in the learning material. The correct units (Celsius and Fahrenheit) should align with the given problem statement and the intended outcome of the exercise. Thank you for your attention to detail and dedication to improving the learning experience on FreeCodeCamp. Navigate to the javascript algorithms and data structures learning module. Go to ES6 course. Locate the lesson titled \"Use getters and setters to Control Access to an Object.\" Read the relevant portion of the instruction mentioned. To correct the mentioned typo and ensure clarity in the instruction, the line should be modified as follows: Original: \"In the class, create a getter to obtain the temperature in Celsius and a setter to set the temperature in Celsius.\" Suggested Correction: \"In the class, create a getter to obtain the temperature in Celsius and a setter to set the temperature in Fahrenheit.\" This change aligns with the problem statement and maintains consistency with the intended temperature units. !\nI'm not sure I see the problem here. How do we know that the intent is for the setter to set the temp in Fahrenheit? Maybe I'm missing something. The seed code seems to indicate that it should be set in Celsius:\nno, in the last line It also runs the getter function, which means that it takes Celsius as Fahrenheit and tries to convert it into Celsius that's why we have to set the temperature in Fahrenheit. Here is the working code. `\nYa, I'm not seeing a problem here either. The getter spits out a Celsius temp and the setter takes a Celsius temp. How you actually store the temp internally in the class is not a consideration here. You don't have to store the internal temp in Fahrenheit. You can solve this by storing the temp internally in Celsius:\nYes, I agree with you, we can solve this by storing temp internally. \"The constructor accepts a Fahrenheit temperature. In the class, create a getter to obtain the temperature in Celsius and a setter to set the temperature in Celsius.\" I could be wrong but the above lines clearly mention that we have to use the getter function to get the temperature in Celsius and the constructor has to accept temperature in Fahrenheit. I feel that these lines are a bit confusing.\nI guess I can see how it could be confusing - but I don't think your suggestion here is the way to go. It's setting the temp in Celsius: So saying that the setter function should set the temp in Fahrenheit doesn't seem to make sense to me. What about or something.\nYes, we have to make this line more clear so students won't get confused.\nThis line makes a requirement to use temperature as a parameter for the constructor and also the name of the getter and setter function to be temperature. So, for better user understanding we can user this line: like this: . So that final code becomes like this:\nAlso the assert functions also requires temperature to be set\nand standard says the getter and setter function should have the same name as the property with _ removed for which property the getter and setter are working\nI think In the class, create a to obtain the temperature in Celsius and a that accepts a temperature in Celsius. is the way to go. We do not need to specify the parameter name of the constructor.\nYes I agree with you. Knowing what to put in the parameter in the constructor looking will be a task that requires good understanding for the students.\nI the first timer label. The We want to change it to the suggestion: If you would like to contribute, and have not read the contributors docs, please do so here:\nI have raised a PR for this change . This is my first ever PR on an open-source project.", "pos": ["Use the `class` keyword to create a `Thermostat` class. The `constructor` accepts a Fahrenheit temperature. In the class, create a `getter` to obtain the temperature in Celsius and a `setter` to set the temperature in Celsius. In the class, create a `getter` to obtain the temperature in Celsius and a `setter` that accepts a temperature in Celsius. Remember that `C = 5/9 * (F - 32)` and `F = C * 9.0 / 5 + 32`, where `F` is the value of temperature in Fahrenheit, and `C` is the value of the same temperature in Celsius."], "neg": []} {"query": "I've run into this several times in the forum in the past week. The active editor is placed within the existing rule set and apparently people don't notice that and instead create a new rule set and add the there. This is what I'm seeing in the forum: I think the active editor should include the entire existing rule set so that it is clear it already exists and that that is where the property should be . We can add an empty line at the bottom of the rule set to indicate where the property should go. No response N/A No response\nI definitely agree. I went ahead and made a PR that moves the editable region to include the full selector.", "pos": ["background-color: #c9d2fc; } --fcc-editable-region-- .cat-head { width: 205px; height: 180px; border: 1px solid #000; border-radius: 46%; --fcc-editable-region-- --fcc-editable-region-- } --fcc-editable-region-- ```"], "neg": []} {"query": "when mongodb is off at dev environment and someone trying to run seed script 'connected successfully to mongo' message displayed 'pnpm run seed' mongo down to run 'pnpm run seed' will see errror message at the terminal but still at the begining - 'connected successfully to mongo' message displayed in case mongodb is not running - you should see Failed to connect to mongo message ! 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\nhi i would like to work on this issue\nThanks for the report, and thanks for the offer of help, Anyone is free to work on this, but we recommend new contributors read our contribution guide first:\nHI I WOULD LIKE TO WORK ON THIS ISSUE\nHey the is up, can you help me take a look at it? Thanks.", "pos": ["const client = new MongoClient(MONGOHQ_URL, { useNewUrlParser: true }); log('Connected successfully to mongo'); const db = client.db('freecodecamp'); const user = db.collection('user');", "}; const run = async () => { await client.connect(); log('Connected successfully to mongo'); await dropUserTokens(); await dropUsers(); if (args.includes('certified-user')) {"], "neg": []} {"query": "In the , we say that: But IMHO, test IDs should be used sparingly in cases where we can't use any other locators as an alternative. The issue with test IDs is that it doesn't guarantee the page has the correct text or the page / section of the page has proper element usages (which is important to ensure that our pages are accessible). Here is an example, let's pretend we have the following HTML: If our test only checks for the test ID, the test would pass while this is not a valid implementation of a button and will cause a severe accessibility issue: But if we write the assertion with , the test would fail, which enables us to ensure the validity of the DOM: https://testing- N/A Update the guide and recommend using and instead of . We can also add the link to the for other recommended locators. No response\nI agree. Recently, I've opened two PRs with E2E tests, and although I followed the guide and used , it just doesn't feel right to do it this way.\ncan you assign to me\nI've created to update the guide with the new recommendation. For Hacktoberfest PRs that have already been using test IDs, I think we should still respect the authors' efforts and accept their code addition, and we can always improve the tests later on.", "pos": ["Alternatively you can follow official documentation referenced below: To install and configure Playwright on your machine check out this [documentation](https://playwright.dev/docs/intro#installing-playwright) To install and configure Playwright on your machine check out this [documentation](https://playwright.dev/docs/intro#installing-playwright). To learn how to write Playwright tests, or 'specs', please see Playwright's official [documentation](https://playwright.dev/docs/writing-tests).", "- Playwright test files are always with a `.spec.ts` extension. ## Best Practices for writing e2e tests ## Best Practices for writing E2E tests This section will explain in detail about best practices for writing and documenting E2E tests based on playwright documentation and our community code-style. This section will explain in detail about best practices for writing and documenting E2E tests based on Playwright documentation and our community code-style. ### - Identifying a DOM element Always use the `data-playwright-test-label` attribute to identify DOM elements. This attribute is used to identify elements in the DOM for testing with playwright only. It is not used for styling or any other purpose. Playwright comes with [multiple built-in locators](https://playwright.dev/docs/locators#quick-guide), but we recommend priritizing the following locators: - `getByRole` for querying semantic elements, whose role is important and allows assistive technology to perceive the page correctly. - `getByText` for querying non-semantic elements such as `div`, `span`, or `p`. For example: For example: ```ts await expect(page.getByRole('heading', { name: 'Sign up' })).toBeVisible(); await expect(page.getByText('Hello World')).toBeVisible(); ``` In cases where the elements cannot be queried using the above-mentioned locators, you can use the `data-playwright-test-label` attribute as the last resort. This attribute is used to identify elements in the DOM for testing with playwright only. It is not used for styling or any other purpose. ```html

    \"...\"
    ``` For example: ```html
    \"...\"
    ```
    Make sure you use the getByTestId method to identify the element in the test file. In the test file, you can use the `getByTestId` method to identify the element. For example: For example: ```ts const landingPageFigure = page.getByTestId('landing-page-figure'); ``` ```ts await expect(page.getByTestId('landing-page-figure')).toBeVisible(); ``` ### - Imports Always start with necessary imports at the beginning of the file. Always start with necessary imports at the beginning of the file. For example: For example: ```ts import { test, expect, type Page } from '@playwright/test'; ``` ```ts import { test, expect, type Page } from '@playwright/test'; ``` ### - Constants Define any constant elements, data sets, or configurations used throughout your tests for easy reference. Define any constant elements, data sets, or configurations used throughout your tests for easy reference. For example: For example: ```ts const landingPageElements = { ... }; const superBlocks = [ ... ]; ``` ```ts const landingPageElements = { ... }; const superBlocks = [ ... ]; ``` ### - Shared Context If tests depend on a shared context (like a loaded web page), use beforeAll and afterAll hooks to set up and tear down that context. If tests depend on a shared context (like a loaded web page), use beforeAll and afterAll hooks to set up and tear down that context. For example: For example: ```ts let page: Page; ```ts let page: Page; beforeAll(async ({ browser }) => { page = await browser.newPage(); }); beforeAll(async ({ browser }) => { page = await browser.newPage(); }); afterAll(async () => { await page.close(); }); ``` afterAll(async () => { await page.close(); }); ``` ### - Descriptive test names Each test block should have a clear and concise name describing exactly what it's testing. Each test block should have a clear and concise name describing exactly what it's testing. For example: For example: ```ts test('The component landing-top renders correctly', async ({ page }) => { ... }); ``` ```ts test('The component landing-top renders correctly', async ({ page }) => { // ... }); ``` ### - Human readable assertions Each assertion should be as human readable as possible. This makes it easier to understand what the test is doing and what it's expecting. Each assertion should be as human readable as possible. This makes it easier to understand what the test is doing and what it's expecting. For example: For example: ```ts await expect(landingHeading1).toHaveText('Learn to code \u2014 for free.'); ``` ```ts await expect(landingHeading1).toHaveText('Learn to code \u2014 for free.'); ``` ### - Keep it DRY Make sure that the tests are not repeating the same code over and over again. If you find yourself repeating the same code, consider refactoring it as a loop or a function. Make sure that the tests are not repeating the same code over and over again. If you find yourself repeating the same code, consider refactoring it as a loop or a function. For example: For example: ```ts for (const logo of await logos.all()) { await expect(logo).toBeVisible(); } ``` ```ts for (const logo of await logos.all()) { await expect(logo).toBeVisible(); } ``` ### - Tests for mobile screens Use the 'isMobile' argument to run tests that incude logic that varies for mobile screens. Use the `isMobile` argument to run tests that incude logic that varies for mobile screens. For example: For example: ```ts test('The campers landing page figure is visible on desktop and hidden on mobile view', async ({isMobile}) => { const landingPageImage = page.getByTestId('landing-page-figure'); ```ts test('The campers landing page figure is visible on desktop and hidden on mobile view', async ({ isMobile }) => { const landingPageImage = page.getByTestId('landing-page-figure'); if (isMobile) { await expect(landingPageImage).toBeHidden(); } else { await expect(landingPageImage).toBeVisible(); } }); if (isMobile) { await expect(landingPageImage).toBeHidden(); } else { await expect(landingPageImage).toBeVisible(); } }); ``` ### - Group related tests Group related tests together using describe blocks. This makes it easier to understand what the tests are doing and what they're testing. Group related tests together using describe blocks. This makes it easier to understand what the tests are doing and what they're testing. For example: For example: ```ts describe('The campers landing page', () => { test('The campers landing page figure is visible on desktop and hidden on mobile view', async ({isMobile}) => { ... }); test('The campers landing page figure has the correct image', async () => { ... }); ```ts describe('The campers landing page', () => { test('The campers landing page figure is visible on desktop and hidden on mobile view', async ({ isMobile }) => { // ... }); ``` test('The campers landing page figure has the correct image', async () => { // ... }); }); ``` ## How to Run Tests"], "neg": []} {"query": "The current instructions say: But they don't specifically say where the new text should be within the . If you add the text before the (with the anchor correctly to the text) then you get the following hint: This creates even more confusion since the anchor was correctly. I think these instructions are relying on the fact that the text for the radio buttons was after the and thus the assumption is that the text for the check box should also be after the . And I agree that usually the text for radio buttons/check boxes is placed after the , but this is not a requirement. Also, in step 26 when we have them add the text for the radio buttons, we explicitly say \"immediately after the element\", so it seems like this is important information to add. N/A Change the instructions to: I should have done better testing :slightlysmilingface: The tests don't care if there is a space between the and the text. We might also want to update the tests so it gives a better hint if they put the text before the . No response N/A No response\nI like the proposed change in wording.\nPlease let me know if there are any other changes needed.\nthe issue is not marked as ready for contribution yet.\nThis issue has been around for a while and I'm still seeing it come up in the forums. Do we need any more discussion on this? Two things to fix in this PR: Update instructions to make it clear that the text comes after the Fix the test that is erroneously telling the user they need to add an anchor element when it is already there.\nI don't think so, no. The requirements are nice and clear, thanks!", "pos": ["# --description-- Add `I accept the terms and conditions` text to the newly added label, then link the text `terms and conditions` to the following location: Add the text `I accept the terms and conditions` immediately after the `input` element in the newly added label. Then link the text `terms and conditions` to the following location: ```md https://www.freecodecamp.org/news/terms-of-service/", "assert.equal(document.querySelector('fieldset:nth-child(3) + label')?.innerText.trim(), 'I accept the terms and conditions'); ``` You should use an `a` element to link to the terms and conditions. You should use an `a` element to link to the terms and conditions. ```js assert.exists(document.querySelector('fieldset:nth-child(3) + label a')); ``` You should put the new text immediately after the `input` element in the `label`. ```js assert.exists(document.querySelector('fieldset:nth-child(3) + label > input + a'));"], "neg": []} {"query": "A camper managed to fail the challenge despite having a close enough correct solution for the challenge. It even displays correctly in the browser. I do not believe the tests should be failing if there are spaces around the words \"cat photos\" in the anchor element. The user should be proceeding to another challenge. No response Device: Desktop OS: Windows 10 Browser: FireFox Version: 118.0.2 No response\nI think here we should actually expect correct whitespace.\nThey shouldn't be messing with that element in the first place in step 13. I think step 12 is more relevant for this issue. And yes, a lot of people add extra spaces in the link text and get bit by this. This was mentioned in issue and I think the consensus is that a test should be specifically to check for the extra white space. I would normally agree that extra white space should not be an issue and the tests should not be so strict about it. But for link text I can see the reasoning. If you add extra white space after \"photos\" then you will see the underline on the link extend past the word \"photos\" into the white space after the word. This is one of those few instances where white space actually does make a difference.\nHey, I am a first-timer and I would like to solve this issue\nPlease read our contributing guide. This issue is not marked as ready for contributions and we do not assign issues.\nThere is a test where the user is prompted for typos. So instead of writing a test for just detecting whitespaces can't we just mention to avoid whitespaces in that prompt? !\nI think it would probably be better to mention whitespace separately since it's early in the curriculum\nSorry if I am wrong about this but do you mean we should make the test less strict and allow whitespaces?\nNope. I think we should check whitespace and typos separately.\ndoes this work then?\nThe link's text should be . You have either whitespaces before or after the text javascript const nestedAnchor = $('p a')[0]; const hasWhiteSpaceBeforeCat = /^(nestedAnchor ); const hasWhiteSpaceAfterPhotos = /s+$/.test(nestedAnchor ); assert( hasWhiteSpaceBeforeCat hasWhiteSpaceAfterPhotos );\nThe test for the p element content probably also needs an adjustment to be agnostic to whitespace? And then this test for whitespace would follow?\nThis regex pattern tests true for sentences with single whitespace between words and no whitespaces before and after the starting and ending word respectively. You can try below code for verifying that So I can write a single test to verify if there are no extra whitespaces between words and no whitespaces before and after the first and last word. So if I get the innerText of the tag then I can just run the test on that to verify the text inside the nestedAnchor tag.\nI'm talking about modifying the current test that checks forboth typos and spaces at the same time.\nThis is the current test for only typos.\nThe link's text should be cat photos. You have either omitted the text or have a typo. As far as I can understand you want this modification to the test right? javascript const nestedAnchor = $('p a')[0]; const pText = document.querySelector('p').innerText.toLowerCase(); //get the inner text which includes text inside anchor tag const typoCheck = nestedAnchor.innerText.toLowerCase().replace(/s+/g, ' ') === 'cat photos'; //checking for typos const whiteSpacesCheck = /^(S+sS+)+$/.test(pText); assert( typoCheck whiteSpacesCheck ); //if either is false then it will fail\nI'm saying that test needs to be two tests.\nI have three options of writing the test: telling the users to avoid whitespaces when the typo test fails and this text is prompted to the user 'The link's text should be cat photos. You have either omitted the text or have a typo or have extra whitespaces.' and not adding a new test. separate tests for checking typos and whitespaces. The link's text should be cat photos. You have either omitted the text or have a typo. AND The link text seems to contain extra whitespaces. both the tests into one single test. The link's text should be cat photos. You have either omitted the text or have a typo or have extra whitespaces. Please tell me which option solves the issue. If none of them are correct then please elaborate more on the proper solution I am unable to understand the proposed solution. Also sorry if this is causing you inconvenience.\nYour option 2 is almost correct, but those two tests cannot be quite like that. First we should check if the contents of the a element match the correct text with or without spaces. So ' cat photos ' or 'cat photos ' or ' cat photos ' or 'cat photos' should all pass while 'foo bar' would not. Then we should check if the contents of the a element are exactly 'cat photos'. The tests have to be in order.\nI found another challenge that deals with the same anchor and spacing issue. I'd like to try to come up with some regex myself for the tests. I'll add an additional comment with some ideas.\nI was thinking a little something for the I mentioned right before the last test You should not have extra spaces around the .\nIs this the correct way now? The link's text should be cat photos. You have either omitted the text or have a typo. NEXT TEST The link's text should be cat photos. You either have leading or ending whitespaces.\nThe second test doesn't need to be that complicated. It should match for the string literal without extra spaces.\nyeah sorry I was too engrossed in learning regex xD You can check the second test I have updated it.\nshould I raise a PR then? or is this issue not open for PRs?\nI think the actual implementation details of the tests are better suited in a PR. I will open this up to contribution. If other challenges need the same change we can collect them in this issue and make it more general. An issue with the help wanted or first timers only label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the\nI will repeat what I posted in the PR here as well. If we are really concerned about the anchor element content we shouldn't be lowercasing it or removing anything and we should use or and not . Something about this I didn't realize is the spacing inside only happens if the element is followed by outside text (which seems bizarre). and will always show the actual element content. We should replace jQuery for any test we see that is using it.\nhey everyone i think that when it comes to whitespaces - the user includes whitespaces before or after or in both sides of the anchor text - if we want to ignore whitespaces i think a regex should just be included in the source code and replaces it with an empty string ''\" like showed in a code earlier. So that wouldn't be a big issue later on. And about typos normally they shouldn't be allowed. Like if the user is supposed to type 'cat photos' and instead they type 'cat photo' that obviously shouldn't pass and they shouldn't be able to go to the next challenge until they enter the exact anchor text asked. Hope this was understandable.\nI think we agreed above that we don't want to ignore the whitespaces\noh ok i get it\nI did the last instruction to delete the entire anchor element below the p element and it passed.", "pos": ["The link's text should be `cat photos`. You have either omitted the text or have a typo. ```js const nestedAnchor = document.querySelector(`p > a`); assert( nestedAnchor.innerText.toLowerCase().replace(/s+/g, ' ') === 'cat photos' ); const nestedAnchor = document.querySelector('p > a'); const innerContent = nestedAnchor.innerHTML; assert.isTrue(innerContent.trim() === 'cat photos'); ``` The text inside your anchor element has extra leading or trailing whitespace. The only space in the anchor text should be between the word `cat` and the word `photos`. ```js const nestedAnchor = document.querySelector('p > a'); const innerContent = nestedAnchor.innerHTML; assert.isNotTrue(/^s+|s+$/.test(innerContent)); ``` After nesting the anchor (`a`) element, the only `p` element content visible in the browser should be `See more cat photos in our gallery.` Double check the text, spacing, or punctuation of both the `p` and nested anchor element."], "neg": []} {"query": "Describe the bug if you type something in searchbar while using the dark mode, and hover over the produced links, it will hide the link. To Reproduce Steps to reproduce the behavior: to '' something over it how the hover is hiding the result Screenshots ! Browser: chrome\nCan you please assign this to me\nHi I've been looking into the issue you reported regarding dark mode and hover behavior on the search results. I'd like to contribute a fix, but I'm having trouble locating the exact code or files that need modification. Could you please provide more specific details about the file or code that's related to this issue? A direct link to the relevant code or even just the file path would be immensely helpful. Your guidance would ensure that I'm making the correct changes to address this problem effectively. Thank you!", "pos": ["padding: 0; } .sidebar ul li a { .sidebar ul li a, .search a { color: var(--quaternary-color); } .sidebar ul li > a:hover { .sidebar ul li > a:hover, .search a:hover { color: var(--primary-color); }"], "neg": []} {"query": "Right now we have multiple tests that shouldn't be needed. We speculated that it might be leftover tests from a step getting split up into two steps (I didn't check). I suggest we keep tests 1 and 6 and replace 2-5 with a single test. Related issue/PR Replace granular tests with a single \"do not touch this\" test. 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", "pos": ["# --hints-- Your code should only have one anchor (`a`) element. ```js assert(document.querySelectorAll('a').length === 1); ``` The `p` element should still have the anchor (`a`) element inside of it. ```js assert($('p > a').length); ``` The link's `href` value should be `https://freecatphotoapp.com`. You have either omitted the `href` value or have a typo. Your code should only have one paragraph (`p`) element. ```js const nestedAnchor = $('p > a')[0]; assert( nestedAnchor.getAttribute('href') === 'https://freecatphotoapp.com' ); assert.isTrue(document.querySelectorAll('p').length === 1); ``` The link's text should be `cat photos`. You have either omitted the text or have a typo. Your code should only have one anchor (`a`) element. ```js const nestedAnchor = $('p > a')[0]; assert( nestedAnchor.innerText.toLowerCase().replace(/s+/g, ' ') === 'cat photos' ); assert.isTrue(document.querySelectorAll('a').length === 1); ``` The `p` element content visible in the browser should be `See more cat photos in our gallery.` Double check the text, spacing, or punctuation of both the `p` and nested anchor element. Do not make any changes to the elements you created in the previous step. ```js const pText = document .querySelector('p') .innerText.toLowerCase() .replace(/s+/g, ' '); assert(pText.match(/see more cat photos in our gallery.?$/)); assert.strictEqual(document.querySelector('p').innerHTML, 'See more cat photos in our gallery.') ``` There should not be `cat photos` text below the `p` element."], "neg": []} {"query": "The active editor for step 9 is currently one empty line placed within the ruleset. Since the instructions above the editor are relatively long it makes it hard to see the selector, which has the potential to confuse people and cause them to unnecessarily add it again (I just dealt with a forum post that did this exact thing). In step 8 we have the active editor include the entire ruleset and leave a blank line for the new property to be . I would suggest we do the same thing for step 9, and leave three blank lines if possible since we are asking for three new properties to be . Step 10 and 11 also have a similar issue, but they are only changing the values of existing properties, so perhaps this is not as big an issue for those steps? I'm fine with keeping them as they are now. In the forum post the selector was again resulting in the following CSS: Have the active editor encompass the entire ruleset and leave three empty lines for the three new properties. No response N/A No response\nHey ! This change makes sense. I have looked through the forum and have seen the issue with campers getting confused. So it would be easy enough to fix. I will do a quick write up with the suggested changes and open it up for contribution I vote to leave steps 10 and 11 as they are for now, just because I haven't seen that pop up to much on the forum.\nI am opening this up for first timer contributors since it is small fix. Please make sure to read the and first. Here is the file you will be working with You will need to change the editable region to include the entire ruleset It should produce this result which will make it clearer for campers what changes they will need to add. \"Screenshot --fcc-editable-region-- .cat-head { --fcc-editable-region-- --fcc-editable-region-- background: linear-gradient(#5e5e5e 85%, #45454f 100%); width: 205px; height: 180px; border: 1px solid #000; border-radius: 46%; } --fcc-editable-region-- ```"], "neg": []} {"query": "I've seen CI failing with the following error multiple times: \"Screenshot function countingFractionsInARange(limit) { let result = 0; const stack = [[3, 2]]; while (stack.length > 0) { const [startDenominator, endDenominator] = stack.pop(); const curDenominator = startDenominator + endDenominator; if (curDenominator <= limit) { result++; stack.push([startDenominator, curDenominator]); stack.push([curDenominator, endDenominator]); class PrimeSeive { constructor(num) { const seive = Array(Math.floor((num - 1) / 2)).fill(true); const upper = Math.floor((num - 1) / 2); const sqrtUpper = Math.floor((Math.sqrt(num) - 1) / 2); for (let i = 0; i <= sqrtUpper; i++) { if (seive[i]) { // Mark value in seive array const prime = 2 * i + 3; // Mark all multiples of this number as false (not prime) const primeSquaredIndex = 2 * i ** 2 + 6 * i + 3; for (let j = primeSquaredIndex; j < upper; j += prime) { seive[j] = false; } } } this._seive = seive; } isPrime(num) { return num === 2 ? true : num % 2 === 0 ? false : this.isOddPrime(num); } isOddPrime(num) { return this._seive[(num - 3) / 2]; } }; const primeSeive = new PrimeSeive(12001); function countingFractionsInARange(num) { const moebius = Array(num + 1).fill(1) // Generate Moebis function terms for (let i = 2; i <= num; i++) { if (!primeSeive.isPrime(i)) continue; for (let j = i; j <= num; j += i) moebius[j] *= -1; for (let j = i * i; j <= num; j += i * i) moebius[j] = 0; } // Evaluate totient sum let sum = 0; for (let i = 1; i <= num; i++) { const coeff = Math.floor(num / i - 2); sum += moebius[i] * Math.floor(coeff * coeff / 12 + 0.5); } return result; return sum; } ```"], "neg": []} {"query": "I was looking at and I wonder if we should improve the legibility of that heading text as well. The default Bootstrap isn't great here. The font used with makes it harder to read in my opinion. Here is the Modal with and the default for the heading. ! And here is the original ! Any challenge with \"Get Help\" Open the Modal Better legibility of the heading text. 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\n! Isn't it already correct?\nI don't know what you mean by correct. I'm suggesting changing the and to make it easier to read. I'm talking about the with the Read-Search-Ask link in it to be clear. It is less of an issue in light mode than dark mode but I still think the legibility can be improved by the suggested changes.\nI don't think it's hard to read, but it does feel a little condensed and I do think it looks better with a little more space. With the space, we may not need to make the adjustments to the link underlines.\nIf the text \"looks better\" chances are it \"reads better\". And yes, the line height should also help with the underline issue.", "pos": ["padding-bottom: 10px; } .help-modal-heading { line-height: 1.5; font-weight: 400; word-spacing: -0.4ch; } @media screen and (max-width: 767px) { .help-modal .btn-lg { font-size: 16px;", "

    - [Start MongoDB and seed the database](how-to-setup-freecodecamp-locally.md#step-3-start-mongodb-and-seed-the-database) - [Start MongoDB and seed the database](how-to-setup-freecodecamp-locally.md#step-3-start-mongodb-and-seed-the-database). In order for Playwright tests to work, be sure that you use the `pnpm run seed:certified-user` command. - [Start the freeCodeCamp client application and API server](how-to-setup-freecodecamp-locally.md#step-4-start-the-freecodecamp-client-application-and-api-server)", "- Seed the database ```bash pnpm run seed pnpm run seed:certified-user ``` - Develop the server and client", "pnpm run seed ``` By default, you will be signed in as a new user without any completed certifications. Run the following commands if you need to develop with completed certifications: By default, you will be signed in as a new user without any completed certifications. Run the following command if you need to develop with completed certifications or write Playwright tests: ```bash pnpm run seed:certified-user"], "neg": []} {"query": "\"image\" import { Button, Panel } from '@freecodecamp/react-bootstrap'; import React from 'react'; import { connect } from 'react-redux'; import { bindActionCreators, Dispatch } from 'redux'; import { useTranslation } from 'react-i18next'; import { Panel, Button } from '@freecodecamp/ui'; import { openModal } from '../../redux/actions'; import Spacer from '../../../../components/helpers/spacer'; import SurveyModal from './survey-modal';", "const { t } = useTranslation(); return ( {t('survey.foundational-c-sharp.title')}

    {t('survey.misc.two-questions')}

    );"], "neg": []} {"query": "I consistently got the following error when running Cypress locally: Run Run either or Cypress attempts to run, but will fail with the above errorOS: MacOS Sonoma I was able to resolve the issue by adding to the command and re-run . I've been having some strange issues lately with localhost so I think this is due to my local setup, but I'm reporting still, to check if anyone was/is experiencing the same problem. We can add a note to the Cypress guide if I'm not the only one ran into it.\nSolution: Remove Cypress\nSo the victim count is 2 now as Sem joined the club. I'll go ahead and add a note to the doc. I've also created to kick off the Cypress removal.", "pos": ["- When prompted in the terminal, select your keyboard layout by language/area Now, [Cypress can be run](how-to-add-cypress-tests.md#_2-run-the-cypress-tests) ## Troubleshooting ### Unable to Connect to Port 8000 If Cypress fails to run with the following error: ``` CypressError: `cy.visit()` failed trying to load: http://localhost:3000/signin We attempted to make an http request to this URL but the request failed without a response. We received this error at the network level: > Error: connect ECONNREFUSED 127.0.0.1:8000 Common situations why this would fail: - you don't have internet access - you forgot to run / boot your web server - your web server isn't accessible - you have weird network configuration settings on your computer This error occurred while creating the session. Because the session setup failed, we failed the test. ``` You can resolve the issue by: - Going to the root `package.json` file and adding `--host 0.0.0.0` to the `develop:client` command: ```json \"scripts\": { \"develop:client\": \"cd ./client && pnpm run develop --host 0.0.0.0\" } ``` - Then, re-running `pnpm run develop` "], "neg": []} {"query": "Need to document the rename challenge tool and the i18n sync tool. Sometime later this week. Not urgent.\nI can take this on?\nGo for it, Thanks!\nI will start with the rename challenge tool, for the i18n sync, I will wait news if it works now", "pos": ["\"difficulty\": \"1.06\", \"description\": [ \"Return an array consisting of the largest numbers in the provided array. The array will contain 4 sub-arrays.\", \"Remember, you an iterate through an array with a simple for loop, and access each member with array syntax arr[i] .\", \"Remember, you can iterate through an array with a simple for loop, and access each member with array syntax arr[i] .\", \"If you are writing your own Chai.js tests, be sure to use a deep equal statement instead of an equal statement when comparing arrays.\" ], \"challengeEntryPoint\": \"largestOfFour([[4, 5, 1, 3], [13, 27, 18, 26], [32, 35, 37, 39], [1000, 1001, 857, 1]]);\",", "\"name\": \"Sum All Odd Fibonacci Numbers\", \"difficulty\": \"2.09\", \"description\": [ \"Return the sum of all odd fibonacci numbers up to and including the passed number if it is a fibonacci number.\", \"Return the sum of all odd Fibonacci numbers up to and including the passed number if it is a Fibonacci number.\", \"The first few numbers of the Fibonacci sequence are 1, 1, 2, 3, 5 and 8, and each subsequent number is the sum of the previous two numbers.\", \"As an example, passing 4 to the function should return 5 because all the odd fibonacci numbers under 4 are 1, 1, and 3.\" \"As an example, passing 4 to the function should return 5 because all the odd Fibonacci numbers under 4 are 1, 1, and 3.\" ], \"challengeEntryPoint\": \"sumFibs(4);\", \"challengeSeed\": \"function sumFibs(num) {n return num;rn}\",", "\"difficulty\": \"2.10\", \"description\": [ \"Sum all the prime numbers up to and including the provided number.\", \"A prime number is defined as having only two divisors, 1 and itself. For example, 2 is a prime number because it's only divisible by 1 and 2. 1 isn't a prime number, because it's only divisible by itself.\", \"A prime number is defined as having only two divisors, 1 and itself. For example, 2 is a prime number because it's only divisible by 1 and 2. 1 isn't a prime number, because it's only divisible by itself.\", \"The provided number may not be a prime.\" ], \"challengeEntryPoint\": \"sumPrimes(10);\",", "\"Fill in the object constructor with the methods specified in the tests.\", \"Those methods are getFirstName(), getLastName(), getFullName(), setFirstName(), setLastName(), and setFullName().\", \"These methods must be the only available means for interacting with the object.\", \"There will be some linting errors on the tests, you may safely ignore them. You should see undefined in the console output.\" \"There will be some linting errors on the tests. You may safely ignore them. You should see undefined in the console output.\" ], \"challengeEntryPoint\": \"var bob = new Person('Bob Ross');\", \"challengeSeed\": \"var Person = function(firstAndLast) {n return firstAndLast;rn};\",", "\"Return true if the passed string is a valid US phone number\", \"The user may fill out the form field any way they choose as long as it is a valid US number. The following are all valid formats for US numbers:\", \"555-555-5555, (555)555-5555, (555) 555-5555, 555 555 5555, 5555555555, 1 555 555 5555\", \"For this challenge you will be presented with a string such as \"800-692-7753\" or \"8oo-six427676;laskdjf\". Your job is to validate or reject the US phone number based on any combination of the formats provided above. The area code is required. If the country code code is provided, you must confirm that the country code is \"1\". Return true if the string is a valid US phone number; otherwise false.\" \"For this challenge you will be presented with a string such as \"800-692-7753\" or \"8oo-six427676;laskdjf\". Your job is to validate or reject the US phone number based on any combination of the formats provided above. The area code is required. If the country code is provided, you must confirm that the country code is \"1\". Return true if the string is a valid US phone number; otherwise false.\" ], \"tests\": [ \"expect(telephoneCheck(\"555-555-5555\")).to.be.a(\"boolean\");\","], "neg": []} {"query": "I was helping a with in the new JS curriculum and they weren't able to pass the tests because of the way they formatted their answer. Here was their code We should allow for that code to pass because they got it right. Here are the current tests For all of the tests that use we should instead update it to use a regex solution with instead. That will make it possible for campers to submit answers with different spacing. All of the tests with the to make sure they have a or element should stay the same though. For those, interested in working on this issue, please read through the first. There will be no assignment for this issue. If you are interested in working on it, then you can submit a PR The following code should pass regardless of different formatting with spaces. 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", "pos": ["```js const stat = document.querySelectorAll('.stat')[0]; assert.equal(stat.innerText, 'XP: 0'); assert.equal(stat.innerText.trimEnd(), 'XP: 0'); ``` You should add a `strong` element in your second `.stat` element.", "```js const stat = document.querySelectorAll('.stat')[1]; assert.equal(stat.innerText, 'Health: 100'); assert.equal(stat.innerText.trimEnd(), 'Health: 100'); ``` You should add a `strong` element in your third `.stat` element.", "```js const stat = document.querySelectorAll('.stat')[2]; assert.equal(stat.innerText, 'Gold: 50'); assert.equal(stat.innerText.trimEnd(), 'Gold: 50'); ``` # --seed--"], "neg": []} {"query": "No need to use here since the array is not re-assigned in later steps. We used for other arrays in this project that aren't reassigned. No response All No response\nHello, I fixed this by doing the following: 1) went to 2) found the ID of step-162 () 3) went to the repositories code and searched for the markdown file through ID. 4) the markdown file 5) Updated the markdown file to use 'const' instead of 'let' ! After this commit is approved, this should be able to be closed.\nAll of the seed code for subsequent challenges would also be changed.\nI am not sure what you mean by this. Is there anything I can do to learn this? Are you referring to all references of 'let' initialization to be changed to 'const' in future steps?\nNot quite - the answer to this step becomes part of the starting code for all future steps. If we change the instructions to use here, then then starting code on all future steps needs to be swapped to reflect that.\nHi, I raised a PR to fix this", "pos": ["# --description-- Inside `pick`, use `let` to initialize a variable named `numbers` and set it to an empty array. Inside `pick`, use `const` to initialize a variable named `numbers` and set it to an empty array. # --hints--", "--fcc-editable-region-- function pick(guess) { let numbers = []; const numbers = []; } --fcc-editable-region--", "--fcc-editable-region-- function pick(guess) { let numbers = []; const numbers = []; while (numbers.length < 10) { }", "--fcc-editable-region-- function pick(guess) { let numbers = []; const numbers = []; while (numbers.length < 10) { numbers.push(Math.floor(Math.random() * 11)); }", "} function pick(guess) { let numbers = []; const numbers = []; while (numbers.length < 10) { numbers.push(Math.floor(Math.random() * 11)); }"], "neg": []} {"query": "The test is expecting to use 49 in the slice. Which seems like could have been an error\u2026.It should be 50 The test is expecting to use 49 in the slice. Which seems like could have been an error\u2026.It should be 50 No response Device: [Laptop] OS: [Windows 10] Browser: [ Chrome] No response\nYes, you are correct. The test is incorrect. I will go ahead and open this up for contribution for the community. Please read through the guidelines first. We do not assign issues. If you are interested in working on this, then work on the issue and create a PR. Several changes need to be made Here is the first file that needs to be updated For step , you will need to update these two tests here to use the correct value of 50 for the slice method. You will also need to update the seed code for steps 28 and 29. Remember that step 29 also has the complete solution which needs to be updated as well Happy coding", "pos": ["If the `bio` text is greater than `50` characters, you should extract the first 50 characters with `slice()` and replace the rest with `...`. Don't forget that indexes are zero-based. ```js assert.match(code, /${s*bio.lengths*>s*50s*?s*bio.slice(s*0,s*49s*)s*+s*(\"|')...2s*:/) assert.match(code, /${s*bio.lengths*>s*50s*?s*bio.slice(s*0,s*50s*)s*+s*(\"|')...2s*:/) ``` If the `bio` text is less than 50 characters, use the `bio` text directly. ```js assert.match(code, /${s*bio.lengths*>s*50s*?s*bio.slice(s*0,s*49s*)s*+s*(\"|')...2s*:s*bios*}

    /)
    assert.match(code, /${s*bio.lengths*>s*50s*?s*bio.slice(s*0,s*50s*)s*+s*(\"|')...2s*:s*bios*}

    /)
    ```", "

    ${author}

    \"${author}

    ${bio.length > 50 ? bio.slice(0, 49) + '...' : bio}

    ${bio.length > 50 ? bio.slice(0, 50) + '...' : bio}

    ${author} author page `;", "

    ${author}

    \"${author}

    ${bio.length > 50 ? bio.slice(0, 49) + '...' : bio}

    ${bio.length > 50 ? bio.slice(0, 50) + '...' : bio}

    ${author} author page `;"], "neg": []} {"query": "For , the answer is already provided for them. The starting seed code needs to just be the button element without the onclick. Here is the file that needs changing If you are interested in working on this please read through the first We do not assign issues. If you are interested, work on the issue and then create a PR for the fix. Happy coding! incorrect start code This should be the correct starting seed code 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", "pos": ["return `
  • --fcc-editable-region-- ')", "# --hints-- Yous should remove the code toggling the class `hidden` on `taskForm`. You should remove the code toggling the class `hidden` on `taskForm`. ```js const splitter = code.split(\"confirmCloseDialog.close();\")"], "neg": []} {"query": "We are still getting a lot of people on the forum confused on how to do step 146 of RPG project. They are looking to the current example and returning strings when the directions say to return the variable and the number . In order to clear up confusion, we should chose a different example. I know that this is updated code example is very similar to what they need to do in the step. But I think that is what they need at this stage. js // if-else statement if (score 0) { return score } else { return defaultscore } // ternary operator score 0 ? score : defaultscore ` 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", "pos": ["Here is an example of returning a value using an `if-else` statement and a refactored example using a ternary operator: ```js if (num > 5) { return 'num is greater than 5'; // if-else statement if (score > 0) { return score } else { return 'num is smaller than or equal to 5'; return default_score } return num > 5 ? 'num is greater than 5' : 'num is smaller than or equal to 5'; // ternary operator score > 0 ? score : default_score ``` In `getMonsterAttackValue`, change `return hit` to a ternary operator that returns `hit` if `hit` is greater than `0`, or returns `0` if it is not."], "neg": []} {"query": "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!", "pos": ["If your ternary is falsy, it should display the string `N/A`. ```js assert.match(code, /s*s*Nickname:s*${s*nicknames*(?:!==s*null)?s*?s*nicknames*:s*('|\"|`)N/A1}s*

    s*/)
    assert.match(code, /s*s*Nickname:s*${s*nicknames*(?:!==s*null)?s*?s*nicknames*:s*('|\"|`)N/A1s*}s*

    s*/)
    ``` # --seed--"], "neg": []} {"query": "The course currently only supports binary gender, he and she, they is excluded. -Advance to 3rd chapter, task 41 -oberserve the text all platforms, all fw Please make this course more inclusive, with something like: What do/does (he/she/they) look like? !\nThe string \"What is (he/she) like?\" also appears in Task 42.\n\"they\" is taught in task 43. Even if it is discussed in task43, it can still be used in respective string from Task 41 onwards.\nI have updated the issue as asked . Please review it .\nHi there, Thanks for your interest in contributing. This issue has not been triaged yet, and a solution has not been agreed upon. Once the issue is open for contribution, you are welcome to create a pull request to reflect the issue consensus. Please also note that we typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue.\nHmmmmmm, While I am always advocating for inclusivity, in this case it may not make sense. Specifically because in English, even when using the singular \"they\", plural verb conjugations are used. \"What does (he/she) look like?\" -\"What do they look like?\" \"What is (he/she) like?\" -\"What are they like?\"\nI have made the changes as said .\nThe following tasks need to be updated with these texts.", "pos": ["# --description-- When you are curious about someone's physical appearance, such as their hair color, height, or general appearance, you could use the sentence `What does (he/she) look like?` `To look like` is used to describe someone's or something's appearance, often implying a comparison. For example: If you hear that a new programmer joined your team but you haven't met them, you can ask your colleague, `What does (he/she) look like?` When you're curious about someone's physical characteristics, such as their hair color, height, or overall look, you might use expressions like: You want to know if they are tall, have short hair, or wear glasses, so you can recognize them in the office. `What does (he/she) look like?` or `What do they look like?` The choice between these depends on the number and gender of the person you're asking about. Use `does` with singular pronouns `(he, she)` when referring to one person and `do` with `they` when referring to someone whose gender might not be known or if referring to people in a non-binary or plural sense. **Note:** Remember that questions about a person's appearance can be sensitive. Some people may not feel comfortable discussing physical traits, and it's important to respect their feelings. Always use this question politely and in the right context, where it is appropriate to do so.", "# --description-- When you want to know about someone's character or personality, you can ask, `What is (he/she) like?`. This question is about the qualities of a person, not about their physical appearance. Example: When you want to know about someone's character or personality, you can ask, `What is (he/she) like?` or `What are they like?`. Imagine you meet a new student in your programming class and you want to know more about her. This question is about the qualities of a person, not about their physical appearance. Example: You can ask a classmate, `What is she like?` Imagine you meet a new student in your programming class and you want to know more about her. You can ask a classmate `What is she like?`. You are not asking if the new student likes computers or games; you are asking about her personality. Maybe she's friendly, smart, or really good at coding."], "neg": []} {"query": "The tests of this step have an issue with spacing, this code fails: This code passes:\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: Regex in 4th test should be changed to optionally allow spaces before , from: to: 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.\n/attempt", "pos": ["You should assign `arr.map()` to the `playerCards.innerHTML` using the `+=` operator. ```js assert.match(code, /playerCards.innerHTMLs++=s*arr.map(s*(s*)s*=>s*{s*}s*)/) assert.match(code, /playerCards.innerHTMLs*+=s*arr.map(s*(s*)s*=>s*{s*}s*)/) ``` # --seed--"], "neg": []} {"query": "The instructions ask to learner to use the Impact font. One learner on the forum posted that the tests fails use of using lower case first letter for the font name. In the screenshots, one picture is the rendering of the unaltered code, the other using impact (lower case) font name. The tests should pass use of either impact or Impact. ! ! NA No response\nThe test right now is: which constrict to a specific casing it could be transformed into Thanks for opening this issue. 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: /challenges/english/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe- Please make sure you read 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.", "pos": ["You should set the `font-family` to `Impact`. ```js const hasFontFamily = new __helpers.CSSHelp(document).getCSSRules().some(x => x.style['font-family'] === 'Impact'); const hasFontFamily = new __helpers.CSSHelp(document).getCSSRules().some(x => x.style['font-family'].toLowerCase() === 'impact'); assert(hasFontFamily); ```"], "neg": []} {"query": "Hello, I believe there is a typo in the join() method example on Learn Basic String and Array Methods by Building a Music Player - Step 18 I expect: should actually be: It's just a typo in the example explaining the join() method. ! N/A No response\nGood catch. I will open it up for first timers contribution\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 The code example in this step needs to be updated to reference the correct array name Happy coding", "pos": ["```js const exampleArr = [\"This\", \"is\", \"a\", \"sentence\"]; const sentence = exampleArray.join(\" \"); // Separator takes a space character const sentence = exampleArr.join(\" \"); // Separator takes a space character console.log(sentence); // Output: \"This is a sentence\" ```"], "neg": []} {"query": "The word 'in' is double I like to workin in the morning. -Proceed to the 4th course 'Learn How to Talk About a Typical Workday and Tasks' -Proceed to Task 2 -Observe the third sentence 'I like to workin in the morning. I like to work in the morning. !\nThanks for opening this issue. 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: /curriculum/challenges/english/21-a2-english-for-developers/learn-how-to-talk-about-a-typical-workday-and- Please make sure you read 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.\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.", "pos": ["Prepositions of time are essential in English to talk about when something happens. The preposition `in` is used for months, years, centuries, and long periods. For example, `We will update the software in July`, `I started learning coding in 2022`. `I like to workin in the morning`. The preposition `in` is used for months, years, centuries, and long periods. For example, `We will update the software in July`, `I started learning coding in 2022`. `I like to work in the morning`. The preposition `on` is used for days and dates. For example: `Our team meets on Mondays`, `The coding class is on April 10th`, `I finished the task on the last day`."], "neg": []} {"query": "After submitting one of the new multifile Python cert projects, when you try to view the project on your settings page - it shows a blank page (links are to .dev) to a a solution to down to the project you just submitted -blank page Either show the python code running, or just remove the button for those projects. !", "pos": ["'showMultifileProjectSolution' ); expect(getSolutionDisplayType(multifilePythonSolution)).toBe( 'showMultifileProjectSolution' 'showUserCode' ); }); it('should handle solutions with a single valid url', () => {", "}: CompletedChallenge): DisplayType => { if (examResults) return 'showExamResults'; if (challengeFiles?.length) return challengeType === challengeTypes.multifileCertProject || challengeType === challengeTypes.multifilePythonCertProject return challengeType === challengeTypes.multifileCertProject ? 'showMultifileProjectSolution' : 'showUserCode'; if (!solution) return 'none';"], "neg": []} {"query": "We are using in the tests of Table component. does not guarantee that the element has the correct role, and this attribute should be the last resort when querying an HTML. We should use the method instead. Remove from the tests Replace with\n/attempt", "pos": ["describe('', () => { it('should apply striped bg color to every odd element', () => { render(
    ); render(
    ); const table = screen.getByTestId('test'); const table = screen.getByRole('table'); const oddTableRowClass = '[&>tbody>tr:nth-of-type(odd)]:bg-background-tertiary'; expect(table).toHaveClass(oddTableRowClass); }); it('should apply the condensed to
    and elements', () => { render(); render(
    ); const table = screen.getByTestId('test'); const table = screen.getByRole('table'); const tableDataClass = '[&_td]:p-1 '; const tableHeaderClass = '[&_th]:p-1';"], "neg": []} {"query": "We need to show the proper syntax for assiging the result of a ternary operator to a variable's text content as mentioned in this . Let's go with this updated description js el.textContent = condition ? \"Use this text if the condition is true\" : \"Use this text if the condition is 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\nI guess I'm fine with being this explicit about it and showing an example. But I would hope by now in the curriculum (this challenge is far in) we have promoted the proper usage of the ternary so that it might be handled just in the assert hints. Also, the hint in the assert for the code posted on the forum isn't super helpful in guiding the camper to the desired syntax.\nI am not sure how the assert messages would be updated here to show the syntax. Unless we just give them the answer here. I am open to ideas for changes", "pos": ["# --description-- Back in your event listener, you need to update the text of the `result` element. Back in your event listener, you need to update the text of the `result` element. You can use a `ternary` operator to achieve this task. Here is an example of assigning the result of a ternary operator to an element's text content: ```js el.textContent = condition ? \"Use this text if the condition is true\" : \"Use this text if the condition is false\"; ``` After the `if` statement, use a ternary operator to check the truthiness of calling `isSpam()` with `messageInput.value` as the argument. If true, set the `textContent` property on the `result` element to `Oh no! This looks like a spam message.`. Otherwise, set it to `This message does not seem to contain any spam.`"], "neg": []} {"query": "I got a mini heart attack as I randomly tested the Storybook page of the component and found that the component failed a11y checks. \"Screenshot; export const Basic: Story = { args: { className: '', label: '' } args: {} }; export default story;", "return ( );"], "neg": []} {"query": "We see far too many campers on the forum who do not understand that the server has to be restarted between changes. I didn't look through all of the curricula but it should be made clear early on. Personally, I would also suggest we teach the options of using or . It doesn't have to be more than a comment in the early backend challenges. Not to have to mention this every time someone has an issue with a backend challenge. 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 have always liked using . It might be nice to have that already in the starter repo and gitpod. That way it will be taken care of for them. Adding a note could be nice though too. thoughts ?\nIt was intentionally removed from all repos. See the last 3 comments in this issue. I don't understand why we are making it more difficult for the camper than it has to be or expect beginners to not trip up on this. We haven't even taught (afaik) that a server has to be restarted before the changes take effect. We should make that clear and teach the solutions to server auto restarting. Even if the camper has to add it manually. I think this is a case of developers forgetting what it was like to be a beginner.\nohh that's interesting that the flag was removed from the repos. I am pretty out of the loop with the changes being made to the backend certs. In this case, I don't see any harm with adding a note about how to auto restart the server using .\nJust to clarify, I don't think we were using in the start scripts but we did use in a few of the repos and that was removed. I'd like to response to this from that issue: This I do not agree with. For beginners, it is difficult. A lot of campers do not even know they need to restart the server between changes. Most do likely not know about arrow-up in the terminal to get to previous commands, meaning they have to write after every change they make to the server file. Which when learning or debugging challenge projects can add up to tons of restarts. Secondly, saying they can just implement their own watcher and it is easy to do completely misses the point. Yes, if you know about it it is easy, if you don't know about it, and we do not even teach it, then it isn't easy. That would be my suggestion as well. Preferable as early as possible.\nLooking at the challenges, we could place a note in the first section for working with the . But the note might work better in the section set of challenges for node and express since they will be writing more code and probably benefit more from the automatic restart of the server. we could add a note at the end of that first set of instructions. something along these lines `\nWhat I have is longer but I think it might be worth going into it a bit more. I can shorten it a bit by removing some of the information.\nWe are hoping to move off of the first few projects soon, and do have a decent lesson outline with a lot of the previous curricula's \"missed bits\": So, for the current curricula, I would go with short, simple, and quick changes. That is, without deliberating on pedagogy.\nHow soon is soon? I don't see an issue with adding some more information to the current challenge. As I said, I can shorten it a bit but it is already written and is easy and quick to add.\nI am terrible at estimations . 2nd quarter.", "pos": ["We recommend to keep the terminal open while working at these challenges. By reading the output in the terminal, you can see any errors that may occur. The server must be restarted after making changes to its files. You can stop the server from the terminal using `Ctrl + C` and start it using Node directly (`node mainEntryFile.js`) or using a run script in the `package.json` file with `npm run`. For example, the `\"start\": \"node server.js\"` script would be run from the terminal using `npm run start`. To implement server auto restarting on file save Node provides the `--watch` flag you can add to your start script `\"start\": \"node --watch server.js\"` or you can install an npm package like `nodemon`. We will leave this to you as an exercise. # --instructions-- Modify the `myApp.js` file to log \"Hello World\" to the console."], "neg": []} {"query": "A in the forum spotted a typo in the instructions for step 62 of Building a Password Generator, Python in the second paragraph should be spelt ! NA No response\nI'm adding the badge to this so new contributors can grab it.\nHello, I would like to work on this issue if it's not assigned to anyone.\nHi , We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labeled 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.\nWhat is the first timers only tag?\nPlease do not ping a maintainer unless it's an urgent matter. You can see the description of a label if you hover on it. The label is to tag issues that are open to first-time contributors. Please also see", "pos": ["`all()` is a built-in Python function that returns `True` if all the elements inside a given iterable evaluate to `True`. Otherwise, it returns `False`. You can combine the `all()` function with the list comphehension syntax to make your code more concise. You can combine the `all()` function with the list comprehension syntax to make your code more concise. Modify your `if` condition by passing the list comprehension you created in the previous step to the `all()` function."], "neg": []} {"query": "This step will fail with code and will pass removing the semicolon at the end of the third line. It doesn't look like this test allows for semicolon", "pos": ["Your `letters.forEach()` callback function should be nested inside the `range(1, 99).forEach(number => {}` callback function. ```js assert.match(code, /ranges*(s*1s*,s*99s*)s*.forEachs*(s*((s*numbers*)|number)s*=>s*{s*[^}]*letters.forEach(s*((s*letters*)|letter)s*=>s*{s*}s*)s*}s*)/) assert.match(code, /ranges*(s*1s*,s*99s*)s*.forEachs*(s*((s*numbers*)|number)s*=>s*{s*[^}]*letters.forEach(s*((s*letters*)|letter)s*=>s*{s*}s*)s*;?s*}s*)/) ``` # --seed--"], "neg": []} {"query": "The wording of the hint text does not match the instructions. The word not is missing from the hint. js (code, /consts+updates=s(?:(sevents))1s)s;?sifs(/); Your condition should check if includes the of the . Your condition should check if does not include the of the . ! NA No response\nFor some more context, the challenge is expecting , but if you input something like this: (no ), the hint is ifvalueidelement It should check that it does not include the id. So we can change the hint to the suggestion - I would change to though: ifvalueid.`` What do you think\nYour condition should check that does not include the of the element. Sounds good.\nSounds like there is a conclusion for what to change the hint to, so I am opening this for contributions", "pos": ["assert.match(code, /consts+updates*=s*(?:(s*events*)|event)s*=>s*{s*consts+elements*=s*event.targets*;?s*consts+values*=s*element.value.replace(s*/s/gs*,s*('|\"|`)1s*)s*;?s*ifs*(/); ``` Your `if` condition should check if `value` includes the `id` of the `element`. Your `if` condition should check that `value` does not include the `id` of the `element`. ```js assert.match(code, /consts+updates*=s*(?:(s*events*)|event)s*=>s*{s*consts+elements*=s*event.targets*;?s*consts+values*=s*element.value.replace(s*/s/gs*,s*('|\"|`)1s*)s*;?s*ifs*(s*!value.includes(s*element.ids*)/);"], "neg": []} {"query": "Setting causes the error Using Or forcing the DNS result order () fixes it. The best I can tell, in newer versions of Node the DNS result order has changed (might have been in v17). We had to fix a different challenge at one point to allow IPv6 IPs. I think this issue is related. Not sure what the best solution is but we might have to update the boilerplate or the challenge text. We can force the result order in the boilerplate if needed. Edit: My best guess why we haven't seen this issue more is because we (at least at one point) forced the engine in and possibly Replit running older versions of Node for a long time. I believe most people will see it locally with new versions of Node and I see it on Gitpod running Node 20. Not to get an error with the code the challenge tells you to use. No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] Forum:\n:sparkles: Thanks to the community, there's an estimated bounty value of $6.81 USD for a successful merge request of this issue via contributions such as 9.750 STORJ tokens. Happy coding :grinning: Details and T&Cs at\nI think updating the challenge text to expect is good.", "pos": ["Within `tests/2_functional-tests.js`, immediately after the `Browser` declaration, add your project URL to the `site` property of the variable: ```js Browser.site = 'http://localhost:3000'; // Your URL here Browser.site = 'http://0.0.0.0:3000'; // Your URL here ``` Then at the root level of the `'Functional Tests with Zombie.js'` suite, instantiate a new instance of the `Browser` object with the following code:", "const browser = new Browser(); ``` And use the `suiteSetup` hook to direct the `browser` to the `/` route with the following code: And use the `suiteSetup` hook to direct the `browser` to the `/` route with the following code. **Note**: `done` is passed as a callback to `browser.visit`, you should not invoke it. ```js suiteSetup(function(done) {"], "neg": []} {"query": "Remove the following classes from the component: - Code:\nsorry for misunderstanding - what is the thing which need to be done?", "pos": ["// remove additional border styles after migration const listClassNames = 'flex mb-0 pl-0 mt-0 border-t-[0px] border-r-[0px] border-l-[0px] border-b-[1px] border-solid border-foreground-quaternary'; 'flex mb-0 pl-0 mt-0 border-b-[1px] border-solid border-foreground-quaternary'; export const TabsTrigger = React.forwardRef< React.ElementRef,"], "neg": []} {"query": "We had this issue on the forum where the camper was unable to pass the test for step 71 with the following code. The test is expecting the use of inside the loop. But is valid too. After a quick scan of the final solution, it looks like the loop is used four times. I have checked the tests, but it is possible that all 4 instances have the same issue where is expected. Update all 4 instances of the tests to accept the use of or multiple pages 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 verified other for loops at step 35, 38 and 57. All these accepts the use of let or const or var.", "pos": ["You should use a `for...of` loop to iterate through the `arr` array. ```js assert.match(code, /consts+detectFullHouses*=s*((s*arrs*)|arr)s*=>s*{.*s*fors*(s*consts+nums+ofs+arrs*)s*{s*.*}/s); assert.match(code, /consts+detectFullHouses*=s*((s*arrs*)|arr)s*=>s*{.*s*fors*(s*(const|let|var)s+nums+ofs+arrs*)s*{s*.*}/s); ``` # --seed--"], "neg": []} {"query": "We still have a high number of campers struggling with the step on how to nest the strong elements inside the existing span elements We should add an example of the syntax so they understand what the markup should look like. html Your answer should follow this basic structure: ```html TEXT TEXT ``` # --hints-- You should add a `strong` element in your first `.stat` element."], "neg": []} {"query": "In the directions for the challenge it states \"Instead, use the back space key on your keyboard to move the p element with the class price next to the p element with the class flavor so that they are on the same line in the editor. Make sure there is no space between them\". But here's the thing, to some campers it might be unclear that the 'them' in the second sentence refers to the elements, and might assume it means the class attribute or something. While this is addressed in the hint, it probably should be clearer in the challenge directions. In this challenge, it should be clear that the last sentence refers to the spacing between the two elements. No response Device: Desktop OS: Windows 10 Browser: Firefox Version: 123.0.1 I've seen at least two threads on the forums covering this challenge.", "pos": ["That worked, but there is still a little space on the right of the price. You could keep trying various percentages for the widths. Instead, use the back space key on your keyboard to move the `p` element with the class `price` next to the `p` element with the class `flavor` so that they are on the same line in the editor. Make sure there is no space between them. You could keep trying various percentages for the widths. Instead, use the back space key on your keyboard to move the `p` element with the class `price` next to the `p` element with the class `flavor` so that they are on the same line in the editor. Make sure there is no space between the two elements. # --hints--"], "neg": []} {"query": "I would suggest removing the second paragraph for step 66 (as a quite novice coder I guess the wording caught me up and I thought the challenge would lean on the side of more difficult rather than easy). I re-read it quite a few times but didn't realize that it was just explaining a later step. It took me a bit of time until I realized that only the first paragraph was needed to solve the solution. I just have an issue with the wording. Nothing else. Sorry if I did something wrong. This is my first time submitting an issue request No response Device: Desktop OS: Windows Browser: Chrome Version: 10 Just had issues with the wording and was recommending it being changed. Sorry if I did something wrong. This is my first github issue request\nIt looks like the original intent was to describe what the function was going to be about. I think removing it all together would leave the step in a place where campers are just asked to create a new function with no clue as to why or what it does. It would be better to provide some explanation on what they will be doing in the next few steps. A rewording would be better. Something like could work I'll open it up for discussion by the other maintainers to hear thoughts on wording. You didn't do anything wrong. It is a good issue\nI am going to go ahead and open this up for contribution", "pos": ["# --description-- Use `const` and arrow syntax to define a function called `setPlayButtonAccessibleText`. To make the application more accessible, it is important that the play button describes the current song or the first song in the playlist. This function will set the `aria-label` attribute to the current song, or to the first song in the playlist. And if the playlist is empty, it sets the `aria-label` to `\"Play\"`. Start by creating an empty arrow function called `setPlayButtonAccessibleText`. # --hints--", "# --description-- Use the `setAttribute` method on the `playButton` element to set an attribute named `\"aria-label\"`. For the value, use a `ternary` to set `song?.title` to `Play ${song.title}` or `\"Play\"` if there's no `song.title` available. The `setPlayButtonAccessibleText` function will set the `aria-label` attribute to the current song, or to the first song in the playlist. And if the playlist is empty, it sets the `aria-label` to `\"Play\"`. Use the `setAttribute` method on the `playButton` element to set an attribute named `\"aria-label\"`. For the value, use a ternary to `set song?.title` to `Play ${song.title}` or `\"Play\"` if there's no `song.title` available. Don't forget you need template interpolation here, so you need to use backticks."], "neg": []} {"query": "The word \"ethical\" is never spoken, only \"ethics\". \"Ethical standards\" is an umbrella term. It would be difficult for a language learner to reach that conclusion without the word ever spoken in context. Edit: I'm not convinced that \"ethical\" is actually the correct word here. If you listen to the audio, at one point, James says \"security standards\". It would make a lot more sense if the required word was \"security\". It would also be an easy fix to change the required word to \"security\". As opposed to fixing the spoken words, which I doubt will happen. code: The exact required word to be spoken and used in context. No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] Forum:\nI updated the issue. I think we might be requiring the wrong word here.\nYes, you are correct. It might make sense to advanced English speakers but no so much for beginners. Lets change: Linda learns that compliance helps maintain safety and _ standards To Meaning Safety becomes the blank word so security is not appearing twice as a blank.\nIt makes more sense to me with the word , as that is how it is used in the spoken sentence. The only time \"standards\" is spoken is with \"security\" before it, so when you reach that part of the fill in the blanks I think it is only logical to assume that the word would be \"security\"", "pos": ["--- `ethical` `security` ### --feedback-- Related to good behavior and honesty. Related to safety and unauthorized access. ---"], "neg": []} {"query": "I can't remember if we have talked about this before. With the current editor layout explaining a concept and giving example code can get awkward. Because the instructions are inside the code it can push the code too far away from the instructions. It would be nice to have the option to disclose more details and example code in the challenge text. Less shallow explanations because of limitations in the layout and allowing the camper to disclose more details as needed. 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 think this should just require a CSS fix so the summary does not appear like this: \"node\": true /* * ENVIRONMENTS * ================= */ // Define globals exposed by Node.js. \"node\": true, /* * ENFORCING OPTIONS * ================= */ // Force all variable names to use either camelCase style or UPPER_CASE // with underscores. \"camelcase\": true, // Prohibit use of == and != in favor of === and !==. \"eqeqeq\": true, // Suppress warnings about == null comparisons. \"eqnull\": true, // Enforce tab width of 2 spaces. \"indent\": 2, // Prohibit use of a variable before it is defined. \"latedef\": true, // Require capitalized names for constructor functions. \"newcap\": true, // Enforce use of single quotation marks for strings. \"quotmark\": \"single\", // Prohibit trailing whitespace. \"trailing\": true, // Prohibit use of explicitly undeclared variables. \"undef\": true, // Warn when variables are defined but never used. \"unused\": true, // Enforce line length to 80 characters \"maxlen\": 80 }", " { /* * ENVIRONMENTS * ================= */ // Define globals exposed by modern browsers. \"browser\": true, // Define globals exposed by jQuery. \"jquery\": true, /* * ENFORCING OPTIONS * ================= */ // Force all variable names to use either camelCase style or UPPER_CASE // with underscores. \"camelcase\": true, // Prohibit use of == and != in favor of === and !==. \"eqeqeq\": true, // Suppress warnings about == null comparisons. \"eqnull\": true, // Enforce tab width of 2 spaces. \"indent\": 2, // Prohibit use of a variable before it is defined. \"latedef\": true, // Require capitalized names for constructor functions. \"newcap\": true, // Enforce use of single quotation marks for strings. \"quotmark\": \"single\", // Prohibit trailing whitespace. \"trailing\": true, // Prohibit use of explicitly undeclared variables. \"undef\": true, // Warn when variables are defined but never used. \"unused\": true, // Enforce line length to 80 characters \"maxlen\": 80, // Enforce placing 'use strict' at the top function scope \"strict\": true' } "], "neg": []} {"query": "There is a typo in this file on this line: This is the ONLY file that needs to be changed. PLEASE READ THE CONTRIBUTOR DOCS BEFORE OPENING A PULL REQUEST An issue with the 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", "pos": ["\"learn-how-to-ask-and-share-about-educational-and-professional-background\": { \"title\": \"Learn How to Ask and Share About Educational and Professional Background\", \"intro\": [ \"In this course, you'll learn how to ask about another person's educational and professional backgrouns and you'll learn how to share information about your background as well.\" \"In this course, you'll learn how to ask about another person's educational and professional backgrounds and you'll learn how to share information about your background as well.\" ] }, \"learn-how-to-talk-about-hobbies-and-interests\": {"], "neg": []} {"query": "The word \"finally\" should be capitalized. \"Screenshot - finally, add the following `h1` to the `body`: `

    Homepage

    ` - Finally, add the following `h1` to the `body`: `

    Homepage

    `
    ## Anchor Elements To create a link in HTML, you use the anchor element. An anchor element is defined by wrapping the text or another HTML element you want to be a link with an `` tag."], "neg": []} {"query": "The second paragraph of the instructions (shown below) uses parentheses twice. \"Screenshot Functions are reusable code blocks that you can call (run) when you need them. To call (or invoke) a function, you just need to write a pair of parentheses next to its name. You will learn more about functions very soon. Functions are reusable code blocks that you can call, or invoke, to run their code when you need them. To call a function, you just need to write a pair of parentheses next to its name. You will learn more about functions very soon. For now, go to a new line and add an empty call to the `print()` function. You should not see any output yet."], "neg": []} {"query": "The description of Working With Text Question D should read \"in an tag\" instead of \"in a tag\". \"Screenshot The `em` element makes text italic. It also semantically places emphasis on the text, which again may affect things like screen readers. To define an emphasized element you wrap text content in a `` tag. The `em` element makes text italic. It also semantically places emphasis on the text, which again may affect things like screen readers. To define an emphasized element you wrap text content in an `` tag. To use `em` on its own: "], "neg": []} {"query": "Typo on Step 61 of Sudoku Solver project in Scientific Computing with Python (Beta) cert: \"withing\" in the hint text when I'm sure you meant \"within\". \"Screen You should have `if (next_empty := self.find_empty_cell()) is None:` withing `solver`. You should have `if (next_empty := self.find_empty_cell()) is None:` within `solver`. ```js const tCode = code.replace(/r/g, '');"], "neg": []} {"query": "When working with the , it mentions the following instructions to complete the challenge: And that's alright, but when running the following correct solution, it doesn't pass and throws the following error: The current test error that it throws is misleading and it's happening because there's a missing test for the above code, which is expecting an implicit return. A test should be to let the user know that an implicit return is expected and can reach to the expected solution: Updating the challenge instruction would be appreciated too. On the other hand, there's a similar case where a correct test is running. When executing the following solution, this happens: This is tested using the following test: ! Device: Laptop OS: macOS 13.6.6 Browser: Chrome Version: 123 No response\nHi that makes sense: regarding the challenge text I would modify it as it follows: What do you think about it? Talking about code that\u2019s right, we should add a test for the listed case in order to fix this. If updated text is ok I\u2019ll proceed adding missing test.\nHey how about being more specific like other the other challenges? Something like the following: And the test error text should be the same when the condition is not met: That's my opinion, ofc. Appreciate that you ask. When able, please submit the PR and let's see what the maintainers think\nHi and I've submitted a PR using juan suggestion about instructions; then I a test assertion just to give explicit error on implicit return. Supravisor PR just fixed text instructions but not a test, so I did it.", "pos": ["Your `idToText` function should return the result of calling `.find()` on the `cells` array with a callback function that takes an `cell` parameter and returns `cell.id === id`. Both of your functions should use implicit returns. # --hints-- You should declare an `idToText` variable in your `evalFormula` function."], "neg": []} {"query": "Change \"You are Sarah\" to \"You're Sarah\" in step 150, 154, and 155 of Learn Greetings in your First Day at the Office. The change is to match the caption text. (The text isn't visible on the Task 155 page, but in the code.) Change \"You are Sarah\" to \"You're Sarah\" in the following files:\nWe introduce contraction form in task 1 () so I assume we would want to use contractions in later tasks. But I'll wait for the curriculum team to confirm before opening this issue up for contribution. (If we don't want to use contraction in these tasks, the caption text should be updated to match the fill the blank text.)", "pos": [" # --description--", "## --sentence-- `Hey. You are Sarah, right? I'm Jake, _ _.` `Hey. You're Sarah, right? I'm Jake, _ _.` ## --blanks--", " # --description--", "## --sentence-- `Hey. You are Sarah, right? I'm Jake, from Security. I'm here to give you _ _ _.` `Hey. You're Sarah, right? I'm Jake, from Security. I'm here to give you _ _ _.` ## --blanks--", ""], "neg": []} {"query": "Looking forward for reporting a security issue: Please report security issues by following our security policy: Describe the bug When using the challenge editor, upon saving changes, the confirmation alert that pops up reads: . It should instead read simply: . Affected Pages Error will appear after saving on on any challenge editor challenge. For example: (http://localhost:3300/07-scientific-computing-with-python/learn-string-manipulation-by-building-a-cipher). To Reproduce the challenge editor with to (http://localhost:3300) to any specific challenege. the save changes button will then produce the alert with the unformatted message. Expected behavior The alert should display: . Screenshots Currently, the alert displays like this: \"broken\" Promise) => () => { makeRequest() .then(res => res.json() as Promise<{ stdout: string; stderr: string }>) .then(data => alert(JSON.stringify(data))) .then( res => res.json() as Promise<{ stdout?: string; stderr?: string; message?: string; }> ) .then(data => { if (data.message) { alert(data.message); } else { alert(JSON.stringify(data)); } }) .catch(err => console.error(err)); };"], "neg": []} {"query": "The \"reset\" button went missing on the projects editor Any page with older style editor The reset button should be present. All\nThere is no need for a reset button here, you can just remove all code?\nThe cash register starts with code\nI think we should have a reset button for the odin remix projects If a camper is a working through one of those challenges, and messes up their HTML, then they should have the ability to reset it. But also, for the JS certs, sometimes it is easier to just click reset and start with a clean slate. Plus the other editors have the reset button, so we should have it for consistency sake IMO.\nThis seems like a great place to start investigating in my opinion. These seem to be multifile cert projects after all.\nReopening, python final projects still miss the button", "pos": [" )} {challengeType !== challengeTypes.multifilePythonCertProject && ( <> )} <> assert.match(code, /(`|\"|')/) assert.match(code, /(`|\"|')/) ``` Your `p` element should have the text `There was an error loading the authors`. ```js assert.match(code, /(`|\"|')Theres+wass+ans+errors+loadings+thes+authors

    1s*;?/)
    assert.match(code, /(`|\"|')Theres+wass+ans+errors+loadings+thes+authors

    1s*;?/)
    ```"], "neg": []} {"query": "A camper on the forum ran into an issue here They wanted to know why they couldn't pass with a regular function for the callback. the directions don't specify it should be an arrow function instead. but both answers should pass. So the tests should be updated. 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\nHi, Can I work on fixing this issue ? I would need some help in locally setting up so that I can test my code changes.", "pos": ["Your `.map()` method should take an empty callback function. ```js assert.match(code, /arr.map(s*(s*)s*=>s*{s*}s*)/); assert.match(code, /arr.map(s*((s*)s*=>|functions*(s*))s*{s*}s*)/); ``` You should use the `+=` operator on `playerCards.innerHTML`.", "You should assign `arr.map()` to the `playerCards.innerHTML` using the `+=` operator. ```js assert.match(code, /playerCards.innerHTMLs*+=s*arr.map(s*(s*)s*=>s*{s*}s*)/) assert.match(code, /playerCards.innerHTMLs*+=s*arr.map(s*((s*)s*=>|functions*(s*))s*{s*}s*)/); ``` # --seed--"], "neg": []} {"query": "In the second paragraph of Step 47: Per my understanding of the text, the \"or\" (italic and bold) should be removed. There is nothing wrong with the testing for this step; it is just a typo. The \"or\" as pointed out above should be deleted. 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\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.", "pos": ["In computer science, a stack is a data structure where items are stored in a LIFO (last-in-first-out) manner. If you imagine a stack of books, the last book you add to the stack is the first book you can take off the stack. Or an array where you can only `.push()` and `.pop()` elements. The call stack is a collection of function calls stored in a stack structure. When you call a function, it is added to the top or of the stack, and when it returns, it is removed from the top / end of the stack. The call stack is a collection of function calls stored in a stack structure. When you call a function, it is added to the top of the stack, and when it returns, it is removed from the top / end of the stack. You'll see this in action by creating mock call stack."], "neg": []} {"query": "In step 28 of the date formatter project, the hint shows the solution, which is not hard to explain. This might not be ideal for learning, as a camper (especially a JS) beginner can go ahead and copy the solution from the hint without bothering to understand what the code does. ! N/A The solution should not be in the hint text because it can be described. We could go with something like this: If the text is too long, it is better to break the hint text and test into two. No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response\nThe same text is in the description, it would make sense to change description to not give out answer at the start.\nBased on the activity I have seen on the forum, I think campers will struggle with connecting \"interpolate the , , , , and \" with the desired format we are asking from them. I think it would be best to show them the desired format in the description. something like this for the description\nSo we should leave the hint as is and modify the description text?\nfor the hint text we could go with this\nOk. Let's open it up for contribution then.\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 please use this for the updated description please use this for the updated hint text Happy coding", "pos": ["# --description-- Inside the `case` for `mm-dd-yyyy-h-mm`, set the `textContent` property of `currentDateParagraph` to `${month}-${day}-${year} ${hours} Hours ${minutes} Minutes`. When the user selects the `Month, Day, Year, Hours, Minutes` option from the dropdown, you need to display the date in the format `mm-dd-yyyy h Hours m Minutes`. Inside the `case` for `mm-dd-yyyy-h-mm`, use string interpolation to assign the formatted date from above to the `textContent` property of `currentDateParagraph`. Make sure to use the `month`, `day`, `year`, `hours`, and `minutes` variables in your answer. # --hints-- You should assign `${month}-${day}-${year} ${hours} Hours ${minutes} Minutes` to the `textContent` property of `currentDateParagraph`. Your answer should follow this format: `mm-dd-yyyy h Hours m Minutes`. Replace `mm`, `dd`, `yyyy`, `h`, and `m` with the `month`, `day`, `year`, `hours`, and `minutes` variables you created earlier. ```js const pattern = /cases*('|\")mm-dd-yyyy-h-mm1s*:s*currentDateParagraph.textContents*=s*`(${month}-${day}-${year} ${hours} Hours ${minutes} Minutes)`/;"], "neg": []} {"query": "A camper on the forum was unable to pass the lesson this was their code the issue was here the tests only accept it if the label is on the next line like this see suggested fix down below about updating the editable regions 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 remembered this issue here where there were issues with the newlines So, I feel like an easier fix would be to just fix the editable regions Here should be the new fix:\nI'm going to flag this one for first-timers only.", "pos": ["return str.match(regex); } --fcc-editable-region-- function addEntry() { const targetInputContainer = document.querySelector(`#${entryDropdown.value} .input-container`); const entryNumber = targetInputContainer.querySelectorAll('input[type=\"text\"]').length; const HTMLString = ` --fcc-editable-region-- `; --fcc-editable-region-- } --fcc-editable-region-- ```"], "neg": []} {"query": "We should make the instructions a little clearer. Let's go with this suggestion from this forum post. ` 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\nI made a PR, but I can close it and let some else do it. It is a nice first time issue.\nno worries. I am currently auditing some of the projects so there will be more first timers only issues coming up soon", "pos": ["You need to update the current song being played as well as the appearance of the `playButton` element. Start by accessing the `userData` object and its `currentSong` property. Set its value equal to the `song` variable. Assign `song` to the `currentSong` property on the `userData` object. *Note*: You should not use the optional chaining operator `?.` in this step because `userData.currentSong` will not be `null` or `undefined` at this point."], "neg": []} {"query": "The description nor the tests mention the answer needs to use as demonstrated by this forum post here It is clear that the camper understood the assignment. So I don't think they should be penalized for using instead of so the tests should be updated to accept both 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", "pos": ["Your `sortSongs` function should use arrow function syntax. ```js assert.match(code, /consts+sortSongss*=s*(s*)s*=>s*{s*}s*;?/) assert.match(code, /const|lets+sortSongss*=s*(s*)s*=>s*{s*}s*;?/) ``` # --seed--"], "neg": []} {"query": "I struggled with the error message, see screenshot below. The error message asks challengers to use the variable, which I clearly did. So, it was not only unclear why the code didn't pass the test, but also misleading because the error message does not point to the real problem here: a second argument for (arg1, arg2) is missing. Since the instruction also doesn't provide a clear description of the syntax of (), I suggest that the syntax information of () be to the instruction. Albeit a minor issue, because anyone can look it up, I believe it would still make the instruction clearer. The error message should alert the challenger about a necessary second argument to pass in () if the variable is already passed in as the first argument. ! Device: Laptop OS: Windows 11 Browser: FireFox Version: 125.0.1 (64-bit) No response\nFor the new updated description, we could use this js (base, exponent) js const base = 4; const exponent = 0.5; // returns 2 (base, exponent); as for the hint text, it looks like the tests are broken up into two for In this case, I think it would be better to just have one test like this js (getStandardDeviation.toString(), /standardDeviations=sMath.pow(svariances,s1s/s2s)/);\nWhy step-51 in codebase is different also there is 58 steps showing when im running freecodecamp locally.But here there is only 55 steps.\nThe project is in beta which means the steps will be changing. So a recent update was made to the stats calculator project which means the step numbers were updated.", "pos": ["# --description-- To calculate a root exponent, such as $sqrt[n]{x}$, you can use an inverted exponent $x^{1/n}$. To calculate a root exponent, such as $sqrt[n]{x}$, you can use an inverted exponent $x^{1/n}$. JavaScript has a built-in `Math.pow()` function that can be used to calculate exponents. Here is the basic syntax for the `Math.pow()` function: ```js Math.pow(base, exponent); ``` Here is an example of how to calculate the square root of `4`: ```js const base = 4; const exponent = 0.5; // returns 2 Math.pow(base, exponent); ``` Declare a `standardDeviation` variable, and use the `Math.pow()` function to assign it the value of $variance^{1/2}$.", "assert.match(getStandardDeviation.toString(), /standardDeviations*=s*Math.pow(/); ``` Your `standardDeviation` variable should use the `variance` variable. ```js assert.match(getStandardDeviation.toString(), /standardDeviations*=s*Math.pow(s*variances*,/); ``` Your `standardDeviation` variable should use the `1/2` exponent. Your `Math.pow()` function should have a base of `variance` and an exponent of `1/2`. ```js assert.match(getStandardDeviation.toString(), /standardDeviations*=s*Math.pow(s*variances*,s*1s*/s*2s*)/);"], "neg": []} {"query": "We had camper that was able to pass the test for step 44 of the pyramid project. However, they created an infinite loop with recursion because of this code here the initial starting code does make it seem like you are supposed to write your code inside the function Here are the current editiable regions but it should be changed to this to make it clearer for beginners where to write their code 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\nCan you please tell me where the file is in the repo?", "pos": ["const count = 8; const rows = []; --fcc-editable-region-- function padRow() { } --fcc-editable-region-- padRow(); --fcc-editable-region--"], "neg": []} {"query": "We should add scripts for running Playwright tests. In the root level , add these two scripts:\nplaywright and to the root level and passed all the tests need review to be merged @ you can check the pr", "pos": ["\"test-tools\": \"jest tools\", \"test-utils\": \"jest utils\", \"postinstall\": \"cypress cache prune\", \"prepare\": \"husky\" \"prepare\": \"husky\", \"playwright:run\": \"playwright test\", \"playwright:watch\": \"playwright test --ui\" }, \"dependencies\": { \"dotenv\": \"16.4.5\""], "neg": []} {"query": "Wording in the description suggests a random number will appear in the console. The number generated is not random. It is a result of the calculation of the number of millisecond elapsed since January 1, 1970 00:00:00 UTC Remove the following text: On a new line, the following text to appear: ! 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\nHi, Can you mention the files where this change should be made.\nThis could be simplified to say \"Open up the console to see the result\"\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 js (()); // ` Happy coding", "pos": ["console.log(Date.now()); // 1628586800000 ``` To see the new result, click on the `\"Add New Task\"` button. Then add a title of `WALK DOG` and click on the `\"Add Task\"` button. Open up the console to see the result with a random number added. To see the new result, click on the `\"Add New Task\"` button. Then add a title of `WALK DOG` and click on the `\"Add Task\"` button. Open up the console to see the result. # --hints--"], "neg": []} {"query": "Faulty method of the class can expose itself only during function tests. Case when number of balls to draw is higher than number of balls in hat is not tested explicitly, but it can fail function test, as it includes such experiment. - - Depending on the number of balls to draw and number of balls in Hat: Remove the required number of balls randomly selected, from the Hat. If number of balls to draw is higher than the number of balls, return all the balls. Test for the method checks only the first case: The second behavior is not checked explicitly, but it's a part of the second sub-case in the function test. This creates situation where passing method test and failing function test, can suggest to camper that issue lies in the function. Example with faulty method: Error: Adding test to check second behavior of the method would make debugging easier for campers, as it would show more clearly where is the issue. No response n/a No response", "pos": ["reload(probability_calculator) probability_calculator.random.seed(95) def test_hat_draw(self): class UnitTests(unittest.TestCase): maxDiff = None def test_hat_draw(self): hat = probability_calculator.Hat(red=5,blue=2) actual = hat.draw(2) expected = ['blue', 'red']", "}); ``` The `draw` method should behave correctly when the number of balls to extract is bigger than the number of balls in the hat. ```js ({ test: () => { pyodide.FS.writeFile(\"/home/pyodide/probability_calculator.py\", code); pyodide.FS.writeFile( \"/home/pyodide/test_module.py\", ` import unittest import probability_calculator from importlib import reload reload(probability_calculator) probability_calculator.random.seed(95) class UnitTests(unittest.TestCase): maxDiff = None def test_hat_draw_2(self): hat = probability_calculator.Hat(yellow=5,red=1,green=3,blue=9,test=1) actual = hat.draw(20) expected = ['yellow', 'yellow', 'yellow', 'yellow', 'yellow', 'red', 'green', 'green', 'green', 'blue', 'blue', 'blue', 'blue', 'blue', 'blue', 'blue', 'blue', 'blue', 'test'] self.assertEqual(actual, expected, 'Expected hat draw to return all items from hat contents.') actual = len(hat.contents) expected = 0 self.assertEqual(actual, expected, 'Expected hat draw to leave no items in contents.') ` ); const testCode = ` from unittest import main import test_module from importlib import reload reload(test_module) t = main(module='test_module', exit=False) t.result.wasSuccessful() `; const out = __pyodide.runPython(testCode); assert(out); }, }); ``` The `experiment` method should return a different probability.", "def draw(self, number): drawn = [] if number >= len(self.contents): return self.contents drawn.extend(self.contents) self.contents = [] else: for i in range(number): drawn.append(", ") return drawn def experiment(hat, expected_balls, num_balls_drawn, num_experiments): def experiment(hat, expected_balls, num_balls_drawn, num_experiments): expected_balls_list = [] drawn_list = [] success = 0", "except: continue if len(exp_ball_list_copy) == 0: success += 1 probability = success/num_experiments success += 1 probability = success/num_experiments return probability ```"], "neg": []} {"query": "We have had a few campers create the wrong variable name for step 22 of pyramid project. Here is an example A few campers are wanting to call it instead of . I think a change in directions will fix this. Here is the updated description here are the updates to the first two hints js (code, /popped/); js (code, /lets+popped/); 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", "pos": ["When a method returns a value, you can think of it as giving the value back to you, making it available for use in other parts of your code. Declare a `popped` variable, and assign it the result of `rows.pop()`. Then, log your `popped` variable. Create a new variable called `popped` and assign it the result of `rows.pop()`. Then, log `popped` to the console. # --hints-- You should declare a `popped` variable. You should declare a variable called `popped`. ```js assert.match(code, /popped/); ``` You should use `let` to declare your `popped` variable. You should use `let` to declare your variable called `popped`. ```js assert.match(code, /lets+popped/);"], "neg": []} {"query": "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.", "pos": ["You should have a `forEach` loop that iterates through the `platforms` array. ```js assert.match(code, /ifs*(.*)s*{s+platforms.forEach(s*((.*)|[^s()]+)s*=>s*{s*(.*?)s*}s*)s*;?/); assert.match(code, /ifs*(.*)s*{s+platforms.forEach(s*((.*)|[^s()]+)s*=>s*{?s*(.*?)s*}?s*)s*;?/); ``` You should use the subtraction assignment operator to subtract 5 from the platform's `x` position. ```js assert.match(code, /platforms.forEach(s*((s*platforms*)|platform)s*=>s*{s*platform.position.xs*-=s*5s*;?s*}s*)s*;?/); assert.match(code, /platforms.forEach(s*((s*platforms*)|platform)s*=>s*{?s*platform.position.xs*-=s*5s*;?s*}?s*)s*;?/); ``` # --seed--", "You should add a `forEach` loop that iterates through the `platforms` array. ```js assert.match(code, /elses+ifs*(.*)s*{s*platforms.forEach(s*((s*platforms*)|platform)s*=>s*{s*(.*?)s*}s*)s*;?/); assert.match(code, /elses+ifs*(.*)s*{s*platforms.forEach(s*((s*platforms*)|platform)s*=>s*{?s*(.*?)s*}?s*)s*;?/); ``` You should use the addition assignment operator to add 5 to the platform's `x` position. ```js assert.match(code, /platforms.forEach(s*((s*platforms*)|platform)s*=>s*{s*platform.position.xs*+=s*5s*;?s*}s*)s*;?/); assert.match(code, /platforms.forEach(s*((s*platforms*)|platform)s*=>s*{?s*platform.position.xs*+=s*5s*;?s*}?s*)s*;?/); ``` # --seed--"], "neg": []} {"query": "There is a typo in the Hint Message of Step 15 of Building a Dice Game, as shown in the Screenshots area. I will raise a PR for it since it is just a typo. The hint message should display: \"You should reassign an empty array to your diceValuesArr variable.\" ! Device: Laptop OS: Windows 11 Browser: FireFox Version: 125.0.2 (64-bit) No response", "pos": ["# --hints-- You should reassign and empty array to your `diceValuesArr` variable. You should reassign an empty array to your `diceValuesArr` variable. ```js assert.match(code, /consts+rollDices*=s*(s*)s*=>s*{s*diceValuesArrs*=s*[s*]s*;?/);"], "neg": []} {"query": "When working through the , mentions the following: And when passing the following solution: This hint shows up: This doesn't pass because is expecting the following: I think adding the hint \"Remember to use the keyword.\" is a valid hint, just like in when the keyword is not in the solution. It may be repetitive, but I think the user should be informed for this possible mistake. It's already in other steps anyway. When passing the incorrect code from the above, add the \"Remember to use the keyword.\" hint and validation. No response Device: Laptop OS: macOS 13.6.6 Browser: Chrome Version: 124 No response\nWe can open this up to since this is a small change This has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the Change the last hint to be the following Happy coding\nI can do it!", "pos": ["assert.match(afterCalculateTotal, /consts+taxs*=/); ``` Assign the value of calling your new `.calculateTaxes()` method, passing `subTotal` as the argument, to the `tax` variable. Assign the value of calling your new `.calculateTaxes()` method, passing `subTotal` as the argument, to the `tax` variable. Remember to use the `this` keyword. ```js const afterCalculateTotal = code.split('calculateTotal')[1];"], "neg": []} {"query": "Describe the bug The first sentence of description contains rogue letter 'y', which needs to be removed: This is 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: Additional context 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.", "pos": ["# --description-- In the Present Perfect Tense, y`for` and `since` are used to discuss time duration and starting points. In the Present Perfect Tense, `for` and `since` are used to discuss time duration and starting points. `For` tells how long something has been happening. `Since` tells when something started. # --fillInTheBlank--"], "neg": []} {"query": "Problem: Simple content description error. It says in the challenge description that when the user has a calorie deficit, the remainingCalories will be a negative (less than 0). It is actually the opposite. For example, if I were to input this in the form: The description of the step must say that it will be a negative value if the input is a surplus (above budget). ! 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", "pos": ["# --description-- When the user has a calorie deficit, the `remainingCalories` value will be negative. You don't want to display a negative number in the result string. When the user has a calorie surplus, the `remainingCalories` value will be negative. You don't want to display a negative number in the result string. `Math.abs()` is a built-in JavaScript method that will return the absolute value of a number."], "neg": []} {"query": "It looks like a lot of people on the forums and discords are confused on the syntax for this step. we could add an updated description with code example to guide campers. js \" \" + \"string\" ` 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\nStep 63 You should now see the same bunch of characters in your console. Your padRow function is doing the exact same thing you were doing earlier, but now it's in a reusable section of its own. Use the addition operator to concatenate a blank space \" \" to the beginning and end of your repeated character string. Remember that you can use the + operator to concatenate strings like this: \" \" + \"string\" This is what i got and it was accepted function padRow(rowNumber, rowCount) { return \" \" + (rowNumber) + \" \" }", "pos": ["Use the addition operator to concatenate a blank space `\" \"` to the beginning and end of your repeated `character` string. Remember that you can use the `+` operator to concatenate strings like this: ```js \" \" + \"string\" ``` # --hints-- You should concatenate an empty space to the beginning of your returned value."], "neg": []} {"query": "Hey any more context on this issue? Seems pretty empty to be already opened with the label.\nthe challenge needs more tests, it's not a high priority thing, that comment has been there for a few years already", "pos": ["assert.deepEqual(tokenize(testStr2, '&', '@'), res2); ``` `tokenize('hello^|world|how^are^you^|', '|', '^')` should return `['hello|world', 'howareyou|']` ```js assert.deepEqual(tokenize(testStr3, '|', '^'), res3); ``` # --seed-- ## --after-user-code--", "const testStr1 = 'one^|uno||three^^^^|four^^^|^cuatro|'; const res1 = ['one|uno', '', 'three^^', 'four^|cuatro', '']; // TODO add more tests const testStr2 = 'a@&bcd&ef&&@@hi'; const res2 = ['a&bcd', 'ef', '', '@hi']; const testStr3 = 'hello^|world|how^are^you^|'; const res3 = ['hello|world', 'howareyou|']; ``` ## --seed-contents--"], "neg": []} {"query": "We need to replace all images and audio samples for the legacy content with the ones that were just to our freeCodeCamp cdn. Here are all of the files that will need to be updated Here are all of the new asset links", "pos": ["}
    \"Quincy \"Quincy

    Quincy Larson

    @ossia

    ", "} \"freeCodeCamp \"freeCodeCamp \"freeCodeCamp \"freeCodeCamp ``` # --solutions--", "} \"freeCodeCamp \"freeCodeCamp \"freeCodeCamp \"freeCodeCamp ```", " \"freeCodeCamp \"freeCodeCamp ``` # --solutions--", "} \"freeCodeCamp \"freeCodeCamp ```", "Here are some audio samples you can use for your drum machine: - [Heater 1](https://s3.amazonaws.com/freecodecamp/drums/Heater-1.mp3) - [Heater 2](https://s3.amazonaws.com/freecodecamp/drums/Heater-2.mp3) - [Heater 3](https://s3.amazonaws.com/freecodecamp/drums/Heater-3.mp3) - [Heater 4](https://s3.amazonaws.com/freecodecamp/drums/Heater-4_1.mp3) - [Clap](https://s3.amazonaws.com/freecodecamp/drums/Heater-6.mp3) - [Open-HH](https://s3.amazonaws.com/freecodecamp/drums/Dsc_Oh.mp3) - [Kick-n'-Hat](https://s3.amazonaws.com/freecodecamp/drums/Kick_n_Hat.mp3) - [Kick](https://s3.amazonaws.com/freecodecamp/drums/RP4_KICK_1.mp3) - [Closed-HH](https://s3.amazonaws.com/freecodecamp/drums/Cev_H2.mp3) - [Heater 1](https://cdn.freecodecamp.org/testable-projects-fcc/audio/Heater-1.mp3) - [Heater 2](https://cdn.freecodecamp.org/testable-projects-fcc/audio/Heater-2.mp3) - [Heater 3](https://cdn.freecodecamp.org/testable-projects-fcc/audio/Heater-3.mp3) - [Heater 4](https://cdn.freecodecamp.org/testable-projects-fcc/audio/Heater-4_1.mp3) - [Clap](https://cdn.freecodecamp.org/testable-projects-fcc/audio/Heater-6.mp3) - [Open-HH](https://cdn.freecodecamp.org/testable-projects-fcc/audio/Dsc_Oh.mp3) - [Kick-n'-Hat](https://cdn.freecodecamp.org/testable-projects-fcc/audio/Kick_n_Hat.mp3) - [Kick](https://cdn.freecodecamp.org/testable-projects-fcc/audio/RP4_KICK_1.mp3) - [Closed-HH](https://cdn.freecodecamp.org/testable-projects-fcc/audio/Cev_H2.mp3) You can build your project by
    using this CodePen template and clicking `Save` to create your own pen. Or you can use this CDN link to run the tests in any environment you like: `https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js`", "[ { \"id\":0, \"imageLink\":\"https://s3.amazonaws.com/freecodecamp/funny-cat.jpg\", \"imageLink\":\"https://cdn.freecodecamp.org/curriculum/legacy-json-apis-ajax/funny-cat.jpg\", \"altText\":\"A white cat wearing a green helmet shaped melon on its head. \", \"codeNames\":[ \"Juggernaut\", \"Mrs. Wallace\", \"Buttercup\" ]", "**User Story:** I can win the game by getting a series of 20 steps correct. I am notified of my victory, then the game starts over. **Hint:** Here are mp3s you can use for each button: `https://s3.amazonaws.com/freecodecamp/simonSound1.mp3`, `https://s3.amazonaws.com/freecodecamp/simonSound2.mp3`, `https://s3.amazonaws.com/freecodecamp/simonSound3.mp3`, `https://s3.amazonaws.com/freecodecamp/simonSound4.mp3`. **Hint:** Here are mp3s you can use for each button: `https://cdn.freecodecamp.org/curriculum/take-home-projects/simonSound1.mp3`, `https://cdn.freecodecamp.org/curriculum/take-home-projects/simonSound2.mp3`, `https://cdn.freecodecamp.org/curriculum/take-home-projects/simonSound3.mp3`, `https://cdn.freecodecamp.org/curriculum/take-home-projects/simonSound4.mp3`. When you are finished, include a link to your project on CodePen and click the \"I've completed this challenge\" button."], "neg": []} {"query": "! Frequently asked question segment is not aligned with the previous elements on the homepage to down to frequently asked questions the misalignment of frequently asked questions segment with the previous elements The frequently asked question segment should be aligned with the previous elements of the homepage for a better UI ! Device: Laptop OS: Windows 11 Browser: Brave Version: 1.64.122 No response\nThis issue is because the Certifications section has extra side padding: We can add a class to the FAQ section, and give it , too. I'm not sure if this change would collide with the changes you're making to the landing page. I'm also wondering if the Certification section being so wide (comparing to the one on /learn) is still desired. If it's not, I think we can take this opportunity to update the section.\nYes, we can standardize all of them. My changes are effecting the landing top section.\nThanks, Ahmad. I'm temporarily blocking this issue until the CSS situation is a little less messy. I'll get back to this and come up with a suggestion after is merged.\nWe will be making changes to the certification section in the near future, so I think we can keep the scope of this issue to just adding some extra padding to the FAQ section, as suggested here: This issue is open for contribution. 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.", "pos": ["const faqItems = t('landing.faqs'); return (

    {t('landing.faq')}

    {faqItems.map((faq, i) => (", "padding: 4vw 15px; } .certification-section { .certification-section, .faq-section { padding-inline: 4vw; }"], "neg": []} {"query": "first discussed on the forum here: I had a concern about the starting sentence of step 26 of the js pyramid project here: It starts out with: \"The let keyword allows a variable to be reassigned.\" which I think can be misinterpreted to mean that we can use the keyword to reassign a variable. I believe a reword to \"Declaring a variable with the let keyword allows it to be reassigned.\" will be not as easy to misinterpret. N/A slight reword to instructions needed as per above No response N/A No response\nSeems like a good change. 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: From: To: Please make sure you read 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.", "pos": ["# --description-- The `let` keyword allows a variable to be reassigned. This means you could change `character` later to be a completely different value. Declaring a variable with the `let` keyword allows it to be reassigned. This means you could change `character` later to be a completely different value. For this project, you will not want to change these variable values. So instead, you should use `const` to declare them. `const` variables are special."], "neg": []} {"query": "Valid code will fail and give the wrong assert message about using which is confusing. Expected If you search for articles on you will find many of the examples has the min value inside the method, this includes MDN, fCC news articles, etc. The min value should be allowed inside the floor method. Update the regex that checks for to not depend on the rest of the code structure to avoid false positives. Tests: Valid code should pass and not throw unrelated assert messages. No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] Forum:", "pos": ["You should use `Math.floor()` to round the result down to the nearest whole number. ```js assert.match(code, /consts+randomDices*=s*Math.floors*(s*Math.randoms*(s*)s**s*6s*)s*/); assert.match(code, /consts+randomDices*=s*Math.floors*((?s*Math.randoms*(s*)s**s*6s*)s*/); ``` You should add `1` to the end result of your `randomDice` variable. ```js assert.match(code, /consts+randomDices*=s*Math.floors*(s*Math.randoms*(s*)s**s*6s*)s*+s*1s*/); assert.match(code, /consts+randomDices*=s*Math.floors*((?s*Math.randoms*(s*)s**s*6s*)s*+s*1)?s*/); ``` # --seed--"], "neg": []} {"query": "We are using the class to conditionally hide some text on mobile screens: This class comes from Bootstrap, which is something we are going to remove (). So instead of using the class, we can use an check, like this (which is also a little more consistent with how we've handled this kind of conditional rendering): Update the file to replace the class with an check. I noticed that we are using multiple methods for mobile device detection, so I think the check should be standardized, and there should be a shared util for this check. But I'm leaving this out of the scope of this issue, and will create a separate issue for it.\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.\nI already have a pull request that technically resolves this. While it is done the same way we did the lower-jaw i.e checks for a desktop instead of being mobile , it does solve the problem and pass the tests.", "pos": ["\"update-email\": \"Update my Email\", \"verify-email\": \"Verify Email\", \"submit-and-go\": \"Submit and go to next challenge\", \"submit-and-go-2\": \"Submit and go to next challenge (Ctrl + Enter)\", \"submit-and-go-3\": \"Submit and go to next challenge (Command + Enter)\", \"go-to-next\": \"Go to next challenge\", \"go-to-next-2\": \"Go to next challenge (Ctrl + Enter)\", \"go-to-next-3\": \"Go to next challenge (Command + Enter)\", \"ask-later\": \"Ask me later\", \"start-coding\": \"Start coding!\", \"go-to-settings\": \"Go to settings to claim your certification\",", "import Progress from '../../../components/Progress'; import GreenPass from '../../../assets/icons/green-pass'; import { Spacer } from '../../../components/helpers'; import { MAX_MOBILE_WIDTH } from '../../../../config/misc'; import './completion-modal.css'; import callGA from '../../../analytics/call-ga';", "const isMacOS = navigator.userAgent.includes('Mac OS'); const isDesktop = window.innerWidth > MAX_MOBILE_WIDTH; let buttonText; if (isDesktop) { if (isMacOS) { buttonText = isSignedIn ? t('buttons.submit-and-go-3') : t('buttons.go-to-next-3'); } else { buttonText = isSignedIn ? t('buttons.submit-and-go-2') : t('buttons.go-to-next-2'); } } else { buttonText = isSignedIn ? t('buttons.submit-and-go') : t('buttons.go-to-next'); } return ( submitChallenge()} > {isSignedIn ? t('buttons.submit-and-go') : t('buttons.go-to-next')} {isMacOS ? ' (Command + Enter)' : ' (Ctrl + Enter)'} {buttonText} {this.state.downloadURL ? ("], "neg": []} {"query": "All links in the english curriculum need to be replaced. This is the last of the S3 links Here are the new CDN links that should be used instead multiple 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", "pos": ["# --instructions-- Time to take a break from Camper Cat and meet fellow camper Zersiax (@zersiax), a champion of accessibility and a screen reader user. To hear a clip of his screen reader in action, add an `audio` element after the `p` element. Include the `controls` attribute. Then place a `source` element inside the `audio` tags with the `src` attribute set to `https://s3.amazonaws.com/freecodecamp/screen-reader.mp3` and `type` attribute set to `\"audio/mpeg\"`. Time to take a break from Camper Cat and meet fellow camper Zersiax (@zersiax), a champion of accessibility and a screen reader user. To hear a clip of his screen reader in action, add an `audio` element after the `p` element. Include the `controls` attribute. Then place a `source` element inside the `audio` tags with the `src` attribute set to `https://cdn.freecodecamp.org/curriculum/applied-accessibility/screen-reader.mp3` and `type` attribute set to `\"audio/mpeg\"`. **Note:** The audio clip may sound fast and be difficult to understand, but that is a normal speed for screen reader users.", "```js assert( $('source').attr('src') === 'https://s3.amazonaws.com/freecodecamp/screen-reader.mp3' 'https://cdn.freecodecamp.org/curriculum/applied-accessibility/screen-reader.mp3' ); ```", "

    A sound clip of Zersiax's screen reader in action.

    ", "}
    \"Quincy \"Quincy

    Quincy Larson

    @ossia

    "], "neg": []} {"query": "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", "pos": ["--fcc-editable-region-- --fcc-editable-region-- if (done === count) { if (done === count) { continueLoop = false; } }", "while (continueLoop) { done++; rows.push(padRow(done, count)); if (done === count) { if (done === count) { continueLoop = false; } }", "while (done !== count) { done++; rows.push(padRow(done, count)); if (done === count) { if (done === count) { continueLoop = false; } }"], "neg": []} {"query": "When invalid code is submitted to step 4 of the gradebook app review project, a message is shown which has a typo. \"Your studentMsg function should return a the correct ...\" Please remove the just click submit without typing anything to trigger the error message display pls correct the typo No response N/A No response\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.\nHi I am intrested to work on this, Can I start?\niam interested to work on this issue\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.\nHi, can I take up this issue? I am new to open source so looking to start with some small contributions.\nWe do not assign issues except to long time contributors and members. please read through this note here on contributing thanks\nI have created a PR for the issue. Waiting for your feedback. Thank you!", "pos": ["assert.strictEqual(studentMsg([56, 23, 89, 42, 75, 11, 68, 34, 91, 19], 100), \"Class average: 50.8. Your grade: A++. You passed the course.\"); ``` Your `studentMsg` function should return a the correct message based on the student's score and the class average. Your `studentMsg` function should return the correct message based on the student's score and the class average. ```js assert.strictEqual(studentMsg([33, 44, 55, 66, 77, 88, 99, 100], 92), \"Class average: 70.25. Your grade: A. You passed the course.\");"], "neg": []} {"query": "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 \u2013 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: \u201cThe function declaration tells JavaScript that the name identifier is going to be a function.\u201d (Replacing \u2018variable\u2019 with \u2018identifier\u2019 and \u2018keyword\u2019 with \u2018declaration\u2019) 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 \u201cdeclare an object called myFunction\u201d instead of saying \u201cdeclare a function called myFunction\u201d. Edited\u2026\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); `", "pos": ["# --hints-- You should declare a `cleanInputString` variable. ```js assert.isDefined(cleanInputString); ``` Your `cleanInputString` variable should be a function. You should declare a `cleanInputString` function. ```js assert.isFunction(cleanInputString);", "# --hints-- You should declare an `isInvalidInput` variable. ```js assert.isDefined(isInvalidInput) ``` `isInvalidInput` should be a function. ```js", "# --hints-- You should declare an `addEntry` variable. ```js assert.isDefined(addEntry); ``` Your `addEntry` variable should be a function. You should declare an `addEntry` function. ```js assert.isFunction(addEntry);"], "neg": []} {"query": "In the Building a Cipher project, comment is first mentioned in step 51: But in step 59, we actually introduce comment and its syntax: In step 51, we introduce function parameters, so I think mentioning comment here would be a little overwhelming. I think the comment introduction should either be moved to an earlier challenge or kept in step 59. If we move the comment introduction to an earlier challenge, step 51 can be kept as-is. But if we keep comment introduction in step 59, we should update step 51. Instead of asking the users to comment out the code, I wonder if we could ask them to remove the line entirely (though the code is in step 50, so it's probably a little odd to immediately remove it in the next step).\nThis does seems to be out of sequence. I would suggest to not comment out in step 51 and let the exception be(the resolution is there in the coming steps). This part of the instruction can be updated from: to:\nIf we don't ask to comment out the function call in step 51 and tell the campers they will work on fixing the error in the next steps, it would be logic to address the error in the console () and require to pass the two positional arguments to the function call in step 52. But then the function will seem to work fine, although it's still using the and variable inside its body instead of the function parameters. The alternative is to ignore the in the console for step 52, and address it directly in step 53. For that we should simply keep the function call instead of commenting it out and there is no need to swap the step order. Honestly, I don't like particularly any of these options.", "pos": ["Modify your function declaration so that it takes two parameters called `message` and `offset`. After that, you'll see an error appear in the terminal. As a temporary fix, comment out the `caesar()` call. After that, you'll see an error appear in the terminal. You'll see how to solve it in the next steps. # --hints-- You should comment out the `caesar()` function call. ```js ({test: () => assert(runPython( `not _Node(_code).find_calls('caesar')` ))}) ``` Your `caesar` function should take `message` and `offset` as the parameters. Remember to separate the parameters with a comma. ```js", "shift = 3 --fcc-editable-region-- def caesar(): --fcc-editable-region-- alphabet = 'abcdefghijklmnopqrstuvwxyz' encrypted_text = ''", "print('encrypted text:', encrypted_text) caesar() --fcc-editable-region-- ```", "print('plain text:', text) print('encrypted text:', encrypted_text) #caesar() caesar() --fcc-editable-region-- ```", "# --description-- Now, uncomment your `caesar()` call. You'll see that your code raises a `TypeError`, because the `caesar` function is defined with two parameters (`message` and `offset`), therefore it expects to be called with two *arguments*. Currently, your code raises a `TypeError`, because the `caesar` function is defined with two parameters (`message` and `offset`), therefore it expects to be called with two *arguments*. Calling `caesar()` without the required arguments stops the execution of the code.", "print('plain text:', message) print('encrypted text:', encrypted_text) --fcc-editable-region-- # caesar() caesar() --fcc-editable-region-- ```"], "neg": []} {"query": "The step asks for a list comprehension, but the following code is accepted as a solution (with parenthesis): I believe the step must only accept the list comprehension with square brackets []: No response Device: Laptop OS: Windows 11 Browser: Brave Version: 1.64.116 No response\nThank you for reporting this issue. I don't think this is a huge problem, since the code works well with a generator expression too. However, since the instructions are asking for a list comprehension, it makes sense to fix the test. The helpers do not discriminate between the various comprehension types, so I'd import the module and check if the value of the variable is an instance of . This additional check should take place within .", "pos": ["You should assign a list comprehension that iterates over `row` to the `row_str` variable. ```js ({ test: () => assert(runPython(`_Node(_code).find_class(\"Board\").find_function(\"__str__\").find_for_loops()[0].find_bodies()[0].find_variable(\"row_str\").find_comp_iters()[0].is_equivalent(\"row\")`)) }) ({ test: () => (runPython(` import ast var = _Node(_code).find_class(\"Board\").find_function(\"__str__\").find_for_loops()[0].find_bodies()[0].find_variable(\"row_str\") assert var.find_comp_iters()[0].is_equivalent(\"row\"), \"You should iterate over row\" assert isinstance(var.tree.value, ast.ListComp), \"It's not a list comprehension\" `)) }) ``` The list comprehension assigned to the `row_str` variable should use `i` as iteration variable."], "neg": []} {"query": "I noticed that we are using both \"a attribute\" and \"an attribute\" in challenge descriptions. And we even use both in the same challenge (): \"Screenshot ``` Inside the existing `img` element, add an `src` attribute with this URL: Inside the existing `img` element, add a `src` attribute with this URL: `https://cdn.freecodecamp.org/curriculum/cat-photo-app/relaxing-cat.jpg`", "assert(document.querySelector('img')); ``` Your `img` element should have an `src` attribute. You have either omitted the attribute or have a typo. Make sure there is a space between the element name and the attribute name. Your `img` element should have a `src` attribute. You have either omitted the attribute or have a typo. Make sure there is a space between the element name and the attribute name. ```js assert(document.querySelector('img').src);", "# --hints-- You should have an `img` element with an `src` value of `https://cdn.freecodecamp.org/curriculum/cat-photo-app/relaxing-cat.jpg`. You may have accidentally deleted it. You should have an `img` element with a `src` value of `https://cdn.freecodecamp.org/curriculum/cat-photo-app/relaxing-cat.jpg`. You may have accidentally deleted it. ```js assert(", "# --description-- After the unordered list, add a new image with an `src` attribute value set to: After the unordered list, add a new image with a `src` attribute value set to: `https://cdn.freecodecamp.org/curriculum/cat-photo-app/lasagna.jpg`", "); ``` The new image does not have an `src` attribute. Check that there is a space after the opening tag's name and/or there are spaces before all attribute names. The new image does not have a `src` attribute. Check that there is a space after the opening tag's name and/or there are spaces before all attribute names. ```js assert($('section')[1].lastElementChild.hasAttribute('src')); ``` The new image should have an `src` value of `https://cdn.freecodecamp.org/curriculum/cat-photo-app/lasagna.jpg`. Make sure the `src` attribute's value is surrounded with quotation marks. The new image should have a `src` value of `https://cdn.freecodecamp.org/curriculum/cat-photo-app/lasagna.jpg`. Make sure the `src` attribute's value is surrounded with quotation marks. ```js assert(", "); ``` The third image should have an `src` attribute set to `https://cdn.freecodecamp.org/curriculum/cat-photo-app/cats.jpg`. The third image should have a `src` attribute set to `https://cdn.freecodecamp.org/curriculum/cat-photo-app/cats.jpg`. ```js const catsImg = document.querySelectorAll('figure > img')[1];", "assert.equal(allSongs[0].duration, \"4:25\"); ``` Your `allSongs` array should have an object with an `src` property set to the string `\"https://cdn.freecodecamp.org/curriculum/js-music-player/scratching-the-surface.mp3\"`. Your `allSongs` array should have an object with a `src` property set to the string `\"https://cdn.freecodecamp.org/curriculum/js-music-player/scratching-the-surface.mp3\"`. ```js assert.equal(allSongs[0].src, \"https://cdn.freecodecamp.org/curriculum/js-music-player/scratching-the-surface.mp3\");", "assert.equal(allSongs[1].duration, \"4:15\"); ``` 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\"`. 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\"`. ```js assert.equal(allSongs[1].src, \"https://cdn.freecodecamp.org/curriculum/js-music-player/can't-stay-down.mp3\");", "assert.equal(allSongs[2].duration, \"3:51\"); ``` The third 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\"`. The third 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\"`. ```js assert.equal(allSongs[2].src, \"https://cdn.freecodecamp.org/curriculum/js-music-player/still-learning.mp3\");"], "neg": []} {"query": "This sentence seems to be confusing campers on the forum Let's go with this updated description here 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\nHi, I have created this PR as a first time contributor (no PRs merged yet) to this codebase. Hope the changes are up to expected requirements. Thanks!", "pos": ["Variable naming follows specific rules: names can include letters, numbers, dollar signs, and underscores, but cannot contain spaces and must not begin with a number. Declare a `character` variable in your code. Use the `let` keyword to declare a variable called `character`. _Note_: It is common practice to end statements in JavaScript with a semicolon. `;`"], "neg": []} {"query": "The contains a lot of unused CSS rules, which should be cleaned up. The unused rules/classes are: .challenge-success-modal .btn-lg .btn-cta-big .completion-modal-body .completion-message .completion-challenge-nameRemove the above classes from Test and confirm that the modal displays properly after the changes\nHi, I can help with this If you would like to assign it to me.", "pos": ["} @media screen and (max-width: 991px) { .challenge-success-modal .btn-lg { font-size: 1rem; } .challenge-success-modal .btn-cta-big { max-width: 100%; font-size: 1rem; } .completion-modal-body { min-height: 340px; } .progress-bar-wrap, .progress-bar-background { height: 10px;", "font-size: 1.2rem; } .completion-challenge-name, .completion-block-name { font-size: 1rem; }"], "neg": []} {"query": "There should be a space between \"CSS\" and \"(Cascading Style Sheets)\". \"Screenshot In this project, you will learn the basics of CSS(Cascading Style Sheets) by building a cafe menu. CSS is the language used to style an HTML document. It describes how HTML elements should be displayed on the screen. In this project, you will learn the basics of CSS (Cascading Style Sheets) by building a cafe menu. CSS is the language used to style an HTML document. It describes how HTML elements should be displayed on the screen. As you learned in the last few steps of the Cat Photo App, there is a basic structure needed to start building your web page. Every HTML document should have a `DOCTYPE` declaration and `html` element. The `DOCTYPE` tells the browser which version of HTML the document is in. And the `html` element represents the root element which contains all other elements."], "neg": []} {"query": "The class is used in : The class doesn't have any effect because there isn't any in : That means it's safe to remove the class now. Remove the selector from Remove the class from\nThis issue is open for contribution. 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.", "pos": ["} } .button-group .btn:not(:last-child) { margin-bottom: 10px; } strong { color: var(--secondary-color); }", "const { t } = useTranslation(); return (
    className={`tool-panel-group button-group ${ className={`tool-panel-group ${ isMobile ? 'tool-panel-group-mobile' : '' }`} >"], "neg": []} {"query": "On , there should be a note displayed between the description and the buttons, but we are seeing an empty div instead: \"Screenshot

    Note: Some browser extensions may interfere with elements on the page. If the tests fail, try disabling your extensions for the most reliable experience.

    "], "neg": []} {"query": "In the last phrase, it is mentioned a element with , but only an element has : . Rectify to the following: No response . No response\nThanks for opening this issue. 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: Change to in the markdown file. Please make sure you read , we prioritize contributors following the instructions in our guides. 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.\nI think the backticks on the / can be dropped while changing this. Other elements mentioned in the paragraph are not backticked.\nBut the question is, shouldn't they be? I think they should, to be consistent with the rest of the curriculum. We use backticks with element types.\nTo be honest I'm not sure what's the current convention, when element type (button/input/output) itself is not actually used in code. This might be also the only project in JS curriculum explicitly naming them in description, instead of referring to them only via id.\nThen I feel like the elements shouldn't be mentioned at all. If we mention the element type, I think the types should have backticks. But I guess I can see your point, and I'm not sure what the convention is here.", "pos": ["All of the HTML and CSS for this project has been provided for you. When you're ready to get started, use the `.getElementById()` method to get the input element with the id `number-input`, and store it in a variable called `numberInput`. Use the same method to get the button element with the id `convert-btn` and store it in a variable called `convertBtn`, and the `h2` element with the id `result` and store it in a variable called `result`. When you're ready to get started, use the `.getElementById()` method to get the `input` element with the id `number-input`, and store it in a variable called `numberInput`. Use the same method to get the `button` element with the id `convert-btn` and store it in a variable called `convertBtn`, and the `output` element with the id `result` and store it in a variable called `result`. **NOTE**: This project will only convert positive numbers into binary."], "neg": []} {"query": "Pyodide can crash when adding or method to the class, while NOT trying to write invalid code. I'm mentioning intent, because it can be encountered when attempting to write correct code. ing instance of the class. or method to the class. On each key pressed, code will execute, including the newly written method. So when we are writing the method: Then starting writing inside of the brackets: . Code will be execute also when it's . That's when it will crash hard: Further changes to code will bring up in browser's console: With example challenge to the at the bottom of code. to class definition, add boilerplate: writing between brackets: on the right crashes at the point when it's . Ideally omitting the crashing part. After the crash window needs to be reloaded to make pyodide on the right work again. Tests still appear to work correctly. Recursive function going into maximum call stack size exceeded does not crash pyodide. I've tested example class from above on , it does not crash pyodide.", "pos": ["const ctx: Worker & typeof globalThis = self as unknown as Worker & typeof globalThis; let pyodide: PyodideInterface; let pyodide: PyodideInterface | null = null; interface PythonRunEvent extends MessageEvent { data: {", "postMessage({ type: 'stopped' }); } function resetPyodide() { if (pyodide) pyodide = null; void setupPyodide(); } void setupPyodide(); function initRunPython() { if (!pyodide) throw new Error('pyodide not loaded'); // eslint-disable-next-line @typescript-eslint/no-unsafe-call const str = pyodide.globals.get('str') as (x: unknown) => string;", "// The runPython helper is a shortcut for running python code with our // custom globals. const runPython = (pyCode: string) => pyodide.runPython(pyCode, { globals }) as unknown; pyodide!.runPython(pyCode, { globals }) as unknown; runPython(` import jscustom from jscustom import print", "} function handleRunRequest(data: PythonRunEvent['data']) { if (ignoreRunMessages) return; const code = (data.code.contents || '').slice(); // TODO: use reset-terminal for clarity? postMessage({ type: 'reset' }); const { runPython, getResetId, globals, printException } = initRunPython(); // use pyodide.runPythonAsync if we want top-level await try { runPython(code); } catch (e) { const err = e as PythonError; // the formatted exception is printed to the terminal printException(); // but the full error is logged to the console for debugging console.error(err); const resetId = getResetId(); // TODO: if a user raises a KeyboardInterrupt with a custom message this // will be treated as a reset, the client will resend their code and this // will loop. Can we fix that? Perhaps by using a custom exception? if (err.type === 'KeyboardInterrupt' && resetId) { // If the client sends a lot of run messages, it's easy for them to build // up while the worker is busy. As such, we both ignore any queued run // messages... ignoreRunMessages = true; // ...and tell the client that we're ignoring them. postMessage({ type: 'stopped', text: getResetId() }); if (ignoreRunMessages) return; const code = (data.code.contents || '').slice(); // TODO: use reset-terminal for clarity? postMessage({ type: 'reset' }); const { runPython, getResetId, globals, printException } = initRunPython(); // use pyodide.runPythonAsync if we want top-level await try { runPython(code); } catch (e) { const err = e as PythonError; // the formatted exception is printed to the terminal printException(); // but the full error is logged to the console for debugging console.error(err); const resetId = getResetId(); // TODO: if a user raises a KeyboardInterrupt with a custom message this // will be treated as a reset, the client will resend their code and this // will loop. Can we fix that? Perhaps by using a custom exception? if (err.type === 'KeyboardInterrupt' && resetId) { // If the client sends a lot of run messages, it's easy for them to build // up while the worker is busy. As such, we both ignore any queued run // messages... ignoreRunMessages = true; // ...and tell the client that we're ignoring them. postMessage({ type: 'stopped', text: getResetId() }); } } finally { getResetId.destroy(); printException.destroy(); globals.destroy(); } } finally { getResetId.destroy(); printException.destroy(); globals.destroy(); } catch (e) { // This should only be reach if pyodide crashes, but it's helpful to log // the error in case it's something else. console.error(e); void resetPyodide(); } }"], "neg": []} {"query": "this makes look like you need to use , but the function call is enough to cause an output to the terminal. Possible solutions: NA NA NA No response\nI'd update the instructions removing the part.\nHi, I'm looking to contribute to open source, could I take this ticket on as a way to onboard to this codebase? And also what is the process usually for grabbing a ticket and pushing a PR?\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.", "pos": ["# --description-- Call the `square_root_bisection` function with the `N` variable as the argument and print the result. Call the `square_root_bisection` function with the `N` variable as the argument. This will print the result to the console. Experiment with larger values.", "# --hints-- You should call the `square_root_bisection` function with the `N` variable as the argument and print the result. You should call the `square_root_bisection` function with the variable `N` as the argument. ```js ({"], "neg": []} {"query": "A2 English blocks have challenges whose title is displayed next to a completion indicator. The indicator is having a right margin, which creates a gap between the indicator and the text. \"Screenshot .badge { .camper-badge { margin-right: 1em; } @media (max-width: 768px) {", "
    {isDonating && (
    ", ")} {isTopContributor && (
    ", "challenge: ChallengeWithCompletedNode; }) => ( {challenge.title}", "const Project = ({ challenge }: { challenge: ChallengeWithCompletedNode }) => ( {challenge.title} "], "neg": []} {"query": "Describe the bug Instructions ask to modify the list comprehension to give a string only when the item is not zero, and an asterisk character otherwise. The accepted answer is: But other answers like or are equally valid. To Reproduce Steps to reproduce the behavior: to Expected behavior Although the instructions ask for a specific solution, it might not be clear enough. Therefore it would be better to modify the test to accept multiple solutions.\nWhile I do agree, I'm not quite sure how to modify the test to make sure that the two others are seen as possibilities are the moment. I don't think our helper method is equipped enough to handle this.\nI would say something like this: Providing all the possible solutions in the list.", "pos": ["The list comprehension assigned to the `row_str` variable should call `str()` on each item `i` in `row` if `i` is truthy, and it should evaluate to `'*'` otherwise. ```js ({ test: () => assert(runPython(`_Node(_code).find_class(\"Board\").find_function(\"__str__\").find_for_loops()[0].find_bodies()[0].find_variable(\"row_str\").find_comp_expr().is_equivalent(\"str(i) if i else '*'\")`)) }) ({ test: () => assert(runPython(` expressions = [\"str(i) if i else '*'\",\"'*' if i == 0 else str(i)\",\"str(i) if i != 0 else '*'\"] node =_Node(_code).find_class(\"Board\").find_function(\"__str__\").find_for_loops()[0].find_bodies()[0].find_variable(\"row_str\").find_comp_expr() any(node.is_equivalent(expr) for expr in expressions)`)) }) ``` # --seed--"], "neg": []} {"query": "Describe the bug Clicking on the certification project name results in both in settings and from the view certification page. ! To Reproduce Steps to reproduce the behavior: to either or (note that you must replace in the link) on a certification project name 404 Page Not Found", "pos": ["'/learn/back-end-development-and-apis/back-end-development-and-apis-projects'; const qaBase = '/learn/quality-assurance/quality-assurance-projects'; const infoSecBase = '/learn/information-security/information-security-projects'; const sciCompPyBase = '/learn/scientific-computing-with-python/' + 'scientific-computing-with-python-projects'; const sciCompPyBase = '/learn/scientific-computing-with-python'; const dataAnalysisPyBase = '/learn/data-analysis-with-python/data-analysis-with-python-projects'; const machineLearningPyBase =", "{ id: '5e44412c903586ffb414c94c', title: 'Arithmetic Formatter', link: `${sciCompPyBase}/arithmetic-formatter`, link: `${sciCompPyBase}/build-an-arithmetic-formatter-project/build-an-arithmetic-formatter-project`, certSlug: Certification.SciCompPy }, { id: '5e444136903586ffb414c94d', title: 'Time Calculator', link: `${sciCompPyBase}/time-calculator`, link: `${sciCompPyBase}/build-a-time-calculator-project/build-a-time-calculator-project`, certSlug: Certification.SciCompPy }, { id: '5e44413e903586ffb414c94e', title: 'Budget App', link: `${sciCompPyBase}/budget-app`, link: `${sciCompPyBase}/build-a-budget-app-project/build-a-budget-app-project`, certSlug: Certification.SciCompPy }, { id: '5e444147903586ffb414c94f', title: 'Polygon Area Calculator', link: `${sciCompPyBase}/polygon-area-calculator`, link: `${sciCompPyBase}/build-a-polygon-area-calculator-project/build-a-polygon-area-calculator-project`, certSlug: Certification.SciCompPy }, { id: '5e44414f903586ffb414c950', title: 'Probability Calculator', link: `${sciCompPyBase}/probability-calculator`, link: `${sciCompPyBase}/build-a-probability-calculator-project/build-a-probability-calculator-project`, certSlug: Certification.SciCompPy } ]"], "neg": []} {"query": "on it says For a beginner, this could be misleading, as they might think, they cannot change the variable. A description like:\nWe should avoid parenthetical information like that whenever we can, in my opinion. It makes the sentence much harder to parse.\nIs it even worth mentioning here? The lesson doesn't show any consequences of immutability, so it might simply be better to remove the sentence.\nI feel like it should be mentioned somewhere, but probably the first lesson where its needed\nI think it is part of teaching strings. Here is how MDN words it: But it would certainly be worth circling back to it when it becomes relevant to make sure the practical implication of it is shown.\nThe description accurately mentions that strings in JavaScript are immutable, meaning their contents cannot be changed once created. However, it's important to clarify that while strings themselves are immutable, the variables holding them can be reassigned to new values. Therefore, no changes are necessary in this instance.\nI agree, the description is correct, though for someone encountering variables, strings and immutability for the first time, they might get confused, thinking they cannot change the variable as it is a string, which is immutable. you learn how to reassign variables. Maybe not mentioning immutability at this early stage is the better choice.\nGood point! Reassigning variables is key. Perhaps mentioning immutability later reinforces the distinction between variable and data type\nI would be fine moving it to somewhere closer to where something like array mutation is taught.\nI think we should at least update the text to say the variable can be reassigned another value. This early on in the learning process, the difference between a \"value\" and a \"variable containing a value\", is likely not that well understood. In some other challenge step, we then show what it actually means that a primitive value is immutable. After they know how to index into a value, then we can show an attempt to update an immutable value directly and explain why it doesn't work.\nLet's start there, then. A PR which resolves this issue will update the text: To the text:", "pos": ["JavaScript has seven primitive data types, with `String` being one of them. In JavaScript, a string represents a sequence of characters and can be enclosed in either single (`'`) or double (`\"`) quotes. Note that strings are immutable, which means once they are created, they cannot be changed. Note that strings are immutable, which means once they are created, they cannot be changed. The variable can still be reassigned another value. Change your `\"Hello\"` string to use single quotes."], "neg": []} {"query": "contains a single CSS rule: This rule is not needed as the underline of the is already turned off by the component library. Remove Remove the class from\nThis issue is open for contribution. 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.", "pos": ["import { CompletedChallenge } from '../../redux/prop-types'; import { getSolutionDisplayType } from '../../utils/solution-display-type'; import './solution-display-widget.css'; import '@freecodecamp/ui/dist/base.css'; interface Props { completedChallenge: CompletedChallenge;", " ); const ShowMultifileProjectSolution = (
    {viewText}{' '}", "); const ShowProjectAndGithubLinks = (
    {viewText}{' '}", " .solutions-dropdown a[role='menuitem'] { text-decoration: none; } "], "neg": []} {"query": "Error message: The string is either empty or holds a space. \"empty space\" and \"blank space\" in this context is confusing. Clear wording: No response All No response\nOpening this up. A PR which resolves this issue will update the messaging to the \"single space\" text Jeremy proposed above.\n\"Screenshot Use the addition operator to concatenate a blank space `\" \"` to the beginning and end of your repeated `character` string. Use the addition operator to concatenate a single space `\" \"` to the beginning and end of your repeated `character` string. Remember that you can use the `+` operator to concatenate strings like this:", "# --hints-- You should concatenate an empty space to the beginning of your returned value. You should concatenate a single space to the beginning of your returned value. ```js assert.match(padRow(1, 1), /^s/); ``` You should concatenate an empty space to the end of your returned value. You should concatenate a single space to the end of your returned value. ```js assert.match(padRow(1, 1), /s$/);"], "neg": []} {"query": "There is a bug in the challenge learn-basic-debugging-by-building-a-random-background-color-changer/step-8 | when entering it passes the test; ! Device: [MacBook Pro 10.15.7] OS: [ iOS Catalina] Browser: [Brave, Chrome] Version: [...] passes test, when it shouldn't`\nVery interesting and confusing finding! This is the passing test: Here's part of the explanation why it passes: Setting to also would pass.", "pos": ["You should not call the `changeBackgroundColor` function. Instead, assign the function reference to the `onclick` property. ```js assert.strictEqual(typeof btn.onclick, 'function'); assert.strictEqual(typeof changeBackgroundColor, 'function'); assert.strictEqual(btn.onclick, changeBackgroundColor); ```"], "neg": []} {"query": "There is a typo in step 87 of Building a Cipher: Fix the typo in the following file:\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. 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.\nIs someone working on this issue? If not, I want to work on it.\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.", "pos": ["# --description-- Two or more strings can be concatenated by using the `+` operator. For example: `'Hello' + ' there!'` results in `'Hello there!`. Two or more strings can be concatenated by using the `+` operator. For example: `'Hello' + ' there!'` results in `'Hello there!'`. Call the `print()` function and use the `+` operator to concatenate the `text` variable to the string `'Encrypted text: '`. Pay attention to the spacing."], "neg": []} {"query": "There is an image in the challenge, and the text of the image has a typo: Fix the typo in the following file:\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.\nFixes Typo in step 1 of Building a Binary Search Tree", "pos": ["This is what a Binary Search Tree looks like: \"a \"a Begin by defining an empty `TreeNode` class. The `TreeNode` class represents a node in a binary search tree. Use the `pass` keyword to fill the class body and avoid an error."], "neg": []} {"query": "In the fill in the blank challenges, the size of the blanks are based on the number of characters in that blank. It's 11px per letter, plus an additional 11px buffer - This works pretty good, but sometimes you get a word with really wide letters and it doesn't fit: \"Screenshot font-family: monospace; padding: 0; text-align: center; background-color: var(--primary-background);", ")}`} onChange={this.handleInputChange} data-index={node.value} style={{ width: `${ blankAnswers[node.value].length * 11 + 11 }px` }} size={blankAnswers[node.value].length} aria-label={t('learn.blank')} /> );"], "neg": []} {"query": "There's typo in two hints. Instead of element it mentions . - - This is 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.\nI was making a PR for a different issue and saw this, so I the fix to the PR.", "pos": ["}; ``` When the `#search-input` element contains the value `Pikachu` and the `#search-button` element is clicked, the `#types` element should contain a single inner element with the value `ELECTRIC`. Make sure the `#type` element content is cleared between searches. When the `#search-input` element contains the value `Pikachu` and the `#search-button` element is clicked, the `#types` element should contain a single inner element with the value `ELECTRIC`. Make sure the `#types` element content is cleared between searches. ```js async () => {", "}; ``` When the `#search-input` element contains the value `94` and the `#search-button` element is clicked, the `#types` element should contain two inner elements with the text values `GHOST` and `POISON`, respectively. Make sure the `#type` element content is cleared between searches. When the `#search-input` element contains the value `94` and the `#search-button` element is clicked, the `#types` element should contain two inner elements with the text values `GHOST` and `POISON`, respectively. Make sure the `#types` element content is cleared between searches. ```js async () => {"], "neg": []} {"query": "There's typo in two hints. Instead of element it mentions . - - This is 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.\nI was making a PR for a different issue and saw this, so I the fix to the PR.", "pos": ["const searchButton = document.getElementById('search-button'); let alertMessage; window.alert = (message) => alertMessage = message; // Override alert and store message const letters = 'ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz' const numbers = '0123456789'; const charactersLength = letters.length; const numbersLength = numbers.length; const firstLetter = letters.charAt(Math.floor(Math.random() * charactersLength)); const secondLetter = letters.charAt(Math.floor(Math.random() * charactersLength)); const thirdLetter = letters.charAt(Math.floor(Math.random() * charactersLength)); const fourthLetter = letters.charAt(Math.floor(Math.random() * charactersLength)); const randomNumber1 = numbers.charAt(Math.floor(Math.random() * numbersLength)); const randomNumber2 = numbers.charAt(Math.floor(Math.random() * numbersLength)); const badName = firstLetter + secondLetter + thirdLetter + fourthLetter + randomNumber1 + randomNumber2; const randomInvalidPokeId = badName; const randomInvalidPokeId = crypto.randomUUID().substring(0, 6); searchInput.value = randomInvalidPokeId; searchInput.dispatchEvent(new Event('change')); searchButton.click(); const res = await fetch('https://pokeapi-proxy.freecodecamp.rocks/api/pokemon/' + randomInvalidPokeId.toString()); // Fetch from proxy to simulate network delay const res = await fetch('https://pokeapi-proxy.freecodecamp.rocks/api/pokemon/' + randomInvalidPokeId); // Fetch from proxy to simulate network delay if (!res.ok) { await new Promise(resolve => setTimeout(resolve, 1000)); // Additional delay to allow the alert to trigger await new Promise(resolve => setTimeout(resolve, 2000)); // Additional delay to allow the alert to trigger assert.include(['pok\u00e9mon not found', 'pokemon not found'], alertMessage.trim().replace(/[.,?!]+$/g, '').toLowerCase()); }", "let alertMessage; window.alert = (message) => alertMessage = message; // Override alert and store message const randomValidPokeId = Math.floor(Math.random() * 1025) + 1; const randomValidPokeId = String(Math.floor(Math.random() * 1025) + 1); searchInput.value = randomValidPokeId; searchInput.dispatchEvent(new Event('change')); searchButton.click(); const res = await fetch('https://pokeapi-proxy.freecodecamp.rocks/api/pokemon/' + randomValidPokeId.toString()); // Fetch from proxy to simulate network delay const res = await fetch('https://pokeapi-proxy.freecodecamp.rocks/api/pokemon/' + randomValidPokeId); // Fetch from proxy to simulate network delay if (res.ok) { await new Promise(resolve => setTimeout(resolve, 1000)); // Additional delay to allow UI to update await new Promise(resolve => setTimeout(resolve, 2000)); // Additional delay to allow UI to update const data = await res.json(); const typesEl = document.getElementById('types'); const actualTypes = data.types.map(typeSlot => typeSlot.type.name); const data = await res.json(); const typesEl = document.getElementById('types'); const actualTypes = data.types.map(typeSlot => typeSlot.type.name); assert.lengthOf(typesEl.children, actualTypes.length); assert.sameMembers(actualTypes, [...typesEl.children].map(el => el.innerText.trim().toLowerCase())); } } catch (err) {"], "neg": []} {"query": "This endpoint needs to use jwtaccesstoken in the same way that web login does.", "pos": ["/* eslint-disable @typescript-eslint/no-unsafe-member-access */ import { setupServer, superRequest } from '../../jest.utils'; import { setupServer, superRequest, createSuperRequest } from '../../jest.utils'; import { AUTH0_DOMAIN } from '../utils/env'; const mockedFetch = jest.fn(); jest.spyOn(globalThis, 'fetch').mockImplementation(mockedFetch); const newUserEmail = 'a.n.random@user.com'; const mockAuth0NotOk = () => ({ ok: false }); const mockAuth0InvalidEmail = () => ({ ok: true, json: () => ({ email: 'invalid-email' }) }); const mockAuth0ValidEmail = () => ({ ok: true, json: () => ({ email: newUserEmail }) }); jest.mock('../utils/env', () => { // eslint-disable-next-line @typescript-eslint/no-unsafe-return return {", "expect(redirectUrl.pathname).toBe('/authorize'); }); }); describe('GET /mobile-login', () => { let superGet: ReturnType; beforeAll(() => { superGet = createSuperRequest({ method: 'GET' }); }); beforeEach(async () => { await fastifyTestInstance.prisma.userRateLimit.deleteMany({}); await fastifyTestInstance.prisma.user.deleteMany({ where: { email: newUserEmail } }); }); it('should be rate-limited', async () => { await Promise.all( [...Array(10).keys()].map(() => superGet('/mobile-login')) ); const res = await superGet('/mobile-login'); expect(res.status).toBe(429); }); it('should return 401 if the authorization header is invalid', async () => { mockedFetch.mockResolvedValueOnce(mockAuth0NotOk()); const res = await superGet('/mobile-login').set( 'Authorization', 'Bearer invalid-token' ); expect(res.body).toStrictEqual({ type: 'danger', message: 'We could not log you in, please try again in a moment.' }); expect(res.status).toBe(401); }); it('should return 400 if the email is not valid', async () => { mockedFetch.mockResolvedValueOnce(mockAuth0InvalidEmail()); const res = await superGet('/mobile-login').set( 'Authorization', 'Bearer valid-token' ); expect(res.body).toStrictEqual({ type: 'danger', message: 'The email is incorrectly formatted' }); expect(res.status).toBe(400); }); it('should set the jwt_access_token cookie if the authorization header is valid', async () => { mockedFetch.mockResolvedValueOnce(mockAuth0ValidEmail()); const res = await superGet('/mobile-login').set( 'Authorization', 'Bearer valid-token' ); expect(res.status).toBe(200); expect(res.get('Set-Cookie')).toEqual( expect.arrayContaining([expect.stringMatching(/jwt_access_token=/)]) ); }); it('should create a user if they do not exist', async () => { mockedFetch.mockResolvedValueOnce(mockAuth0ValidEmail()); const existingUserCount = await fastifyTestInstance.prisma.user.count(); const res = await superGet('/mobile-login').set( 'Authorization', 'Bearer valid-token' ); const newUserCount = await fastifyTestInstance.prisma.user.count(); expect(existingUserCount).toBe(0); expect(newUserCount).toBe(1); expect(res.status).toBe(200); }); it('should redirect to returnTo if already logged in', async () => { mockedFetch.mockResolvedValueOnce(mockAuth0ValidEmail()); const firstRes = await superGet('/mobile-login').set( 'Authorization', 'Bearer valid-token' ); expect(firstRes.status).toBe(200); const res = await superRequest('/mobile-login', { method: 'GET', // eslint-disable-next-line @typescript-eslint/no-unsafe-assignment setCookies: firstRes.get('Set-Cookie') }) .set('Authorization', 'Bearer does-not-matter') .set('Referer', 'https://www.freecodecamp.org/back-home'); expect(res.status).toBe(302); expect(res.headers.location).toBe( 'https://www.freecodecamp.org/back-home' ); }); }); });", "import rateLimit from 'express-rate-limit'; // @ts-expect-error - no types import MongoStoreRL from 'rate-limit-mongo'; import isEmail from 'validator/lib/isEmail'; import { AUTH0_DOMAIN, MONGOHQ_URL } from '../utils/env'; import { auth0Client } from '../plugins/auth0'; import { createAccessToken } from '../utils/tokens'; import { findOrCreateUser } from './helpers/auth-helpers'; const getEmailFromAuth0 = async (req: FastifyRequest) => { const getEmailFromAuth0 = async ( req: FastifyRequest ): Promise => { const auth0Res = await fetch(`https://${AUTH0_DOMAIN}/userinfo`, { headers: { Authorization: req.headers.authorization ?? '' } }); if (!auth0Res.ok) { req.log.error(auth0Res); throw new Error('Invalid Auth0 Access Token'); } if (!auth0Res.ok) return null; const { email } = (await auth0Res.json()) as { email: string }; return email; // For now, we assume the response is a JSON object. If not, we can't proceed // and the only safe thing to do is to throw. const { email } = (await auth0Res.json()) as { email?: string }; return typeof email === 'string' ? email : null; }; /**", "// all auth routes. fastify.addHook('onRequest', fastify.redirectIfSignedIn); fastify.get('/mobile-login', async req => { fastify.get('/mobile-login', async (req, reply) => { const email = await getEmailFromAuth0(req); await findOrCreateUser(fastify, email); if (!email) { return reply.status(401).send({ message: 'We could not log you in, please try again in a moment.', type: 'danger' }); } if (!isEmail(email)) { return reply.status(400).send({ message: 'The email is incorrectly formatted', type: 'danger' }); } const { id } = await findOrCreateUser(fastify, email); reply.setAccessTokenCookie(createAccessToken(id)); }); done();"], "neg": []} {"query": "Under the section, add the following line as the first item:\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.", "pos": ["#### 2. [JavaScript Algorithms and Data Structures Certification](https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures-v8/) - [Learn Introductory JavaScript by Building a Pyramid Generator](https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures-v8/#learn-introductory-javascript-by-building-a-pyramid-generator) - [Learn Basic JavaScript by Building a Role Playing Game](https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures-v8/#learn-basic-javascript-by-building-a-role-playing-game) - [Learn Form Validation by Building a Calorie Counter](https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures-v8/#learn-form-validation-by-building-a-calorie-counter) - [Learn Basic String and Array Methods by Building a Music Player](https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures-v8/#learn-basic-string-and-array-methods-by-building-a-music-player)"], "neg": []} {"query": "In step 41 of the RPG project in the JS beta curriculum, the instruction states: Change the property of the to be \"You enter the store.\". I believe this sentence is not 100% clear without either removing the word \u201cthe\u201d in front of or adding the word \u201cvariable\u201d to the right of . As it is, the sentence misleads a bit because it says \u201cthe \u201d which makes it sound like it is referring to some text somewhere, instead of the text variable. so either: Change the property of to be \"You enter the store.\". or Change the property of the variable to be \"You enter the store.\". will be clearer. Please look at questions posted on the forum for examples of people missing the point of the request with the current wording. I personally prefer the second one. N/A N/A N/A Example of confused learner:", "pos": ["# --description-- Now you need to modify your display text. Change the `innerText` property of the `text` to be `\"You enter the store.\"`. Now you need to modify your display text. Change the `innerText` property of the `text` variable to be `\"You enter the store.\"`. # --hints--", "button1.onclick = buyHealth; button2.onclick = buyWeapon; button3.onclick = goTown; } --fcc-editable-region--"], "neg": []} {"query": "Code in the doesn't seem to be evaluated in production for Cash Register project. (Edit)This appear to be related to the code saving / resetting. In development there isn't such issue. Including building production client and serving it. This is actually the only challenge from the new challenges that is using . Old challenges are working fine when using . Both when names start with ` might be somehow deciding factor, but there isn't any other new challenge to check that. After adding function to user code, error moves normally to the next used in test non-defined variable - and then . Steps to reproduce the behavior: (Be logged in, and have previously saved code for project). to solution. Example: tests. errors. Code present in the should be evaluated after the user code, and before running tests. (Edit) When logged out there's different error, or no errors at all(?!). This might be somehow related to saving / resetting code.\nThanks again for the detailed report, You were dead right about the issue: it's due to the fact that saved challenges don't include head or tail (aka and ) and we were just using them in place of challengeFiles (which does have that stuff).\nI have marked this as a showstopper seeing as it is affecting camper's ability to complete a certificate project. It would be nice to get the fix in as soon as possible, so the forum isn't filled with support threads for this.", "pos": ["challengeFiles: SavedChallengeFiles; }; // TODO: remove unused properties and stop returning them from api? (e.g. // history, ext, name) export type SavedChallengeFile = { fileKey: string; ext: Ext;", " import type { ChallengeFile, SavedChallengeFile } from '../../../redux/prop-types'; import { mergeChallengeFiles } from './saved-challenges'; const jsChallenge = { id: '1', contents: 'js contents', fileKey: 'jsFileKey', name: 'name', ext: 'js' as const, head: 'head', tail: 'tail', history: [], seed: 'original js contents' }; const cssChallenge = { id: '2', contents: 'css contents', fileKey: 'cssFileKey', name: 'name', ext: 'css' as const, head: 'head', tail: 'tail', history: [], seed: 'original css contents' }; const htmlChallenge = { id: '3', contents: 'html contents', fileKey: 'htmlFileKey', name: 'name', ext: 'html' as const, head: 'head', tail: 'tail', history: [], seed: 'original html contents' }; const savedJsChallenge: SavedChallengeFile = { contents: 'saved js contents', fileKey: 'jsFileKey', name: 'name', ext: 'js' as const }; const savedCssChallenge: SavedChallengeFile = { contents: 'saved css contents', fileKey: 'cssFileKey', name: 'name', ext: 'css' as const }; const savedHtmlChallenge: SavedChallengeFile = { contents: 'saved html contents', fileKey: 'htmlFileKey', name: 'name', ext: 'html' as const }; describe('mergeChallengeFiles', () => { it('should return files if savedChallengeFiles is undefined', () => { const files: ChallengeFile[] = [htmlChallenge]; const savedChallengeFiles = undefined; const result = mergeChallengeFiles(files, savedChallengeFiles); expect(result).toEqual(files); }); it('should return an empty array if files is undefined', () => { const files = undefined; const savedChallengeFiles = [savedJsChallenge]; const result = mergeChallengeFiles(files, savedChallengeFiles); expect(result).toEqual([]); }); it('should return files if savedChallengeFiles has a different length', () => { const files: ChallengeFile[] = [cssChallenge]; const savedChallengeFiles: SavedChallengeFile[] = [ savedCssChallenge, savedJsChallenge ]; const result = mergeChallengeFiles(files, savedChallengeFiles); expect(result).toEqual(files); }); it('should return files if the fileKey properties do not match', () => { const files: ChallengeFile[] = [jsChallenge, cssChallenge]; const savedChallengeFiles: SavedChallengeFile[] = [ savedHtmlChallenge, savedCssChallenge ]; const result = mergeChallengeFiles(files, savedChallengeFiles); expect(result).toEqual(files); }); it('should use the contents from the saved file', () => { const files: ChallengeFile[] = [cssChallenge, htmlChallenge, jsChallenge]; const savedChallengeFiles = [ savedJsChallenge, savedCssChallenge, savedHtmlChallenge ]; const result = mergeChallengeFiles(files, savedChallengeFiles); expect(result).toEqual([ { ...cssChallenge, contents: savedCssChallenge.contents }, { ...htmlChallenge, contents: savedHtmlChallenge.contents }, { ...jsChallenge, contents: savedJsChallenge.contents } ]); }); }); ", " import { ChallengeFile, SavedChallengeFile } from '../../../redux/prop-types'; export function mergeChallengeFiles( files?: ChallengeFile[] | null, savedFiles?: SavedChallengeFile[] | null ): ChallengeFile[] { if (!files) return []; if (!savedFiles) return files; if (files.length !== savedFiles.length) return files; const sortedChallengeFiles = files.sort((a, b) => a.fileKey.localeCompare(b.fileKey) ); const sortedSavedChallengeFiles = savedFiles.sort((a, b) => a.fileKey.localeCompare(b.fileKey) ); const fileKeysMatch = sortedChallengeFiles.every( (file, index) => file.fileKey === sortedSavedChallengeFiles[index].fileKey ); if (!fileKeysMatch) return files; return sortedChallengeFiles.map((file, index) => ({ ...file, contents: sortedSavedChallengeFiles[index].contents })); } ", "import MultifileEditor from './multifile-editor'; import DesktopLayout from './desktop-layout'; import MobileLayout from './mobile-layout'; import { mergeChallengeFiles } from './saved-challenges'; import './classic.css'; import '../components/test-frame.css';", "return challenge.id === challengeMeta.id; }); createFiles(savedChallenge?.challengeFiles || challengeFiles || []); createFiles( mergeChallengeFiles(challengeFiles, savedChallenge?.challengeFiles) ); initTests(tests); if (showProjectPreview) openModal('projectPreview');"], "neg": []} {"query": "Thanks for opening this issue. This looks something that can be fixed by \"first time\" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: 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.", "pos": ["**User Stories:** 1. You should have an `input` element with an `id` of `\"search-input\"` 1. You should have a `button` element with an `id` of `\"search-button` 1. You should have a `button` element with an `id` of `\"search-button\"` 1. You should have an element with an `id` of `\"pokemon-name\"` 1. You should have an element with an `id` of `\"pokemon-id\"` 1. You should have an element with an `id` of `\"weight\"`"], "neg": []} {"query": "In the last part of step 5 in the rock, paper, scissors review project, the instructions given say: If there is a winner, you will want to show the resetGameBtn button and hide the optionsContainer so the player can play again. Tips You can use the property to show the resetGameBtn button and hide the optionsContainer. I have 2 concerns here. 1- at no point is there any mention of what type of display the resetGameBtn requires (is it block, inline-block, flex...?) I guessed 'block' which worked but the lack of this detail made me hesitate. 2- the mention of '' is confusing. In the previous project, using style.display was discussed before in the rpg project () but it was never referred to or mentioned as '' before. I wasn't sure if 'el' meant the element in question or if there was an actual 'el' variable somewhere. I ended up going with what made sense (replacing the 'el' with the element reference) but I'm not sure how easy this would be for someone with only the last few js projects under their belt. A clarification would be great here. N/A N/A No response N/A No response\nI fixed the wording of the challenge to make it more clear to the user.\nThis issue has not been triaged yet, in the future please do not create a PR until then. Anyway, I will open it up to contribution.\nmy bad sir, won't happen again.", "pos": ["**Tips** - You can use the `el.style.display` property to show the `resetGameBtn` button and hide the `optionsContainer`. Use the `style.display` property on an element, with the value `\"block\"` or `\"none\"`, to show or hide the element. # --hints--", "} else { assert.equal(winnerMsgElement.innerText, \"Computer has won the game!\"); } ``` You should hide the `optionsContainer` and if the player or computer has reached three points."], "neg": []} {"query": "Example Code Below the expenses list, create a while loop. Use True for the condition, and print the string 'nExpense Tracker' inside the loop body to show the title of the program. Highlighted portion should instead be changed to False, since while loops terminate when their condition is false.\nAs an alternative \"A while loop is another kind of loop that runs a portion of code until a specified condition is A `while` loop is another kind of loop that runs a portion of code until a specified condition is `True`: A `while` loop is another kind of loop that runs a portion of code as long as a specified condition is `True`. The loop terminates when the condition becomes `False`: ```py while condition:"], "neg": []} {"query": "The form element is missing a closing tag, but the challenge still accept it and let me move onto the next step It should respond with \"You are missing the closing tag\", instead of accepting it and letting you move onto the next step ! 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] According to It should result in a valid form element, because the browser will close it. However, the element technically does not have any \"Tag omission\" so it should have an end tag in the HTML (even if it gets to the DOM by the browser).\nThis is no more the first project, it would become regex galore, and when possible instead we prefer to not use regex, so fixing all these tests is probably not worth it\nWe don't need to keep testing for closing tags everywhere. But this challenge is about building a form, so having one test to check the initial form element is created correctly doesn't seem unreasonable.\nAgreed, this seems like a good reason to regex test a closing tag. Opening for contribution.", "pos": ["assert.equal(document.querySelector('form')?.action, 'https://register-demo.freecodecamp.org/'); ``` Your `form` element should have a closing tag ``. ```js assert.match(code, //); ``` # --seed-- ## --seed-contents--"], "neg": []} {"query": "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. 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.", "pos": ["# --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`."], "neg": []} {"query": "I was going through the new JS Beta curriculum and when I got to the date formatter project I realized that it probably doesn't really help add any specific knowledge that would be useful in completing the palindrome project. I think the date formatter project being in its current position may even be a hindrance because I think it is better to get people to work on the skills they have learned sooner rather than later. My suggestion is to move the palindrome project ahead of the date formatter project for this reason. N/A N/A No response N/A No response\nplease assign this to me\nissues are not generally assigned, and this issue has not been marked as ready for contributions.\nokiee thank you\nI agree. That seems like the way to go. A PR which resolves this issue, then, will swap the properties in the meta files for these two projects.", "pos": ["\"dashedName\": \"build-a-palindrome-checker-project\", \"usesMultifileEditor\": true, \"helpCategory\": \"JavaScript\", \"order\": 8, \"order\": 7, \"superBlock\": \"javascript-algorithms-and-data-structures-v8\", \"challengeOrder\": [ {", "\"usesMultifileEditor\": true, \"hasEditableBoundaries\": true, \"dashedName\": \"learn-the-date-object-by-building-a-date-formatter\", \"order\": 7, \"order\": 8, \"superBlock\": \"javascript-algorithms-and-data-structures-v8\", \"challengeOrder\": [ {"], "neg": []} {"query": "The is being hard-coded with an English string, we should change this to use a translation string instead. Additionally, the attribute is redundant as already has role implicitly. Replace the string with a translation string, something like (the string also needs to be to ) Remove", "pos": ["\"last-page\": \"Go to last page\", \"primary-nav\": \"primary\", \"breadcrumb-nav\": \"breadcrumb\", \"timeline-pagination-nav\": \"Timeline Pagination\", \"submit\": \"Use Ctrl + Enter to submit.\", \"running-tests\": \"Running tests\", \"hide-preview\": \"Hide the preview\",", "