/g), 'message: Only use jQuery to add these classes to the element.');\" ], \"type\": \"waypoint\",", "commid": "freeCodeCamp_pr_6976"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-cc128fa3cb2aa38bfd8b83096242de2a49d173c4ada7c01a28e95fc055144192", "query": "[x] Chrome Dev Tools: Elements [x] Chrome Dev Tools: Network [x] Chrome Dev Tools: Sources [x] Chrome Dev Tools: Timeline [x] Chrome Dev Tools: Profiles [x] Chrome Dev Tools: Resources [x] Chrome Dev Tools: Audits [x] Chrome Dev Tools: Console [x] Chrome Dev Tools: Summary\nWorking on it", "positive_passages": [{"docid": "doc-en-freeCodeCamp-697abb99502cf65652db8661648f0de3bee8fbcae612a7692b4e08c0c430f29e", "text": "] ], \"type\": \"hike\",
\"challengeType\": 6 \"challengeType\": 6, \"nameEs\": \"Herramientas de desarrollo de Chrome: Elementos\", \"descriptionEs\": [ \"Esta es informaci\u00f3n b\u00e1sica y una mini-lecci\u00f3n sobre la pesta\u00f1a Elements en las herramientas de desarrollo de Chrome. Echa un vistazo a la documentaci\u00f3n m\u00e1s detallada aqu\u00ed: developers.google.com/web/tools/iterate/inspect-styles/basics \", \"Vamos a utilizar la p\u00e1gina web mckellen.com/ por sugerencia del usuario de FreeCodeCamp kmiasko.\", \"Si pulsas con el bot\u00f3n derecho y seleccionas 'Inspeccionar elemento', tendr\u00e1s acceso a la pesta\u00f1a elements. \u00a1Puedes cambiar el texto, el color de fondo, el color de texto y cualquier otra propiedad CSS o elemento HTML que desees!\", \"Estos cambios no se establecen de forma autom\u00e1tica, por lo que no debes usar el inspector como un IDE o como un lugar para crear o editar cualquier cosa que desees guardar. Puedes configurar algo que se llama 'autor\u00eda persistente' para salvar.\", \"Las reglas de CSS como cascada, herencia y otras se aplican, as\u00ed que tenlo en cuenta a medida que juegas. Adem\u00e1s, los estilos anulados se muestran con un tachado sobre ellos. \", \"Tambi\u00e9n hay que se\u00f1alar que todo el c\u00f3digo que veas en ese '\u00e1rbol' es c\u00f3digo HTML actual, no el original que hab\u00eda cuando se carg\u00f3 la p\u00e1gina. Si utilizas jQuery o JavaScript para cambiar algo, est\u00e9 \u00e1rbol se actualizar\u00e1.\", \"El relleno, los bordes y los m\u00e1rgenes se inspeccionan f\u00e1cilmente y puedes editarlos usando la caja con colores que encontrar\u00e1s al lado derecho o en la parte de abajo.\", \"Por favor, echa un vistazo a la documentaci\u00f3n de las herramientas de desarrollo de Chrome en developers.google.com/web/tools/chrome-devtools/\" ] }, { \"id\": \"56b15f15632298c12f315183\",", "commid": "freeCodeCamp_pr_7200"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-cc128fa3cb2aa38bfd8b83096242de2a49d173c4ada7c01a28e95fc055144192", "query": "[x] Chrome Dev Tools: Elements [x] Chrome Dev Tools: Network [x] Chrome Dev Tools: Sources [x] Chrome Dev Tools: Timeline [x] Chrome Dev Tools: Profiles [x] Chrome Dev Tools: Resources [x] Chrome Dev Tools: Audits [x] Chrome Dev Tools: Console [x] Chrome Dev Tools: Summary\nWorking on it", "positive_passages": [{"docid": "doc-en-freeCodeCamp-cc695a8cddb673c30d75c8493093cb1feae1ab3f3c74d3e2b06bd76203f8957c", "text": "] ], \"type\": \"hike\",
\"challengeType\": 6 \"challengeType\": 6, \"nameEs\": \"Herramientas de desarrollo de Chrome: red\", \"descriptionEs\": [ \"La pesta\u00f1a network (red) ayuda a responder preguntas como '\u00bfQu\u00e9 elemento o parte de la p\u00e1gina fue el m\u00e1s demorado?' o '\u00bfQu\u00e9 inici\u00f3 una petici\u00f3n?'\", \"El panel de red registra informaci\u00f3n detallada sobre cu\u00e1nto tarda en cargar cada elemento de su p\u00e1gina o aplicaci\u00f3n.\", \"Cada solicitud se registra en la bit\u00e1cora, que se puede encontrar en la parte inferior del panel de red.\", \"Si te fijas en la l\u00ednea al lado derecho, te dar\u00e1s cuenta de un patr\u00f3n de colores. Cada color representa un tipo diferente de contenido en la solicitud. \", \"Cuanto m\u00e1s larga sea la l\u00ednea de un color determinado, tanto m\u00e1s tiempo tom\u00f3 ese tipo de contenido en la solicitud. En \u00faltimas quieres l\u00edneas cortas, y si cualquier solicitud tiene largas l\u00edneas, sabes que puede estar ralentizando la p\u00e1gina web.\", \"Si pulsas sobre una solicitud en la bit\u00e1cora, podr\u00e1s obtener informaci\u00f3n m\u00e1s detallada.\", \"Consulta m\u00e1s documentaci\u00f3n detallada aqu\u00ed: developers.google.com/web/tools/profile-performance/network-performance/resource-loading\" ] }, { \"id\": \"56b15f15632298c12f315182\",", "commid": "freeCodeCamp_pr_7200"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-cc128fa3cb2aa38bfd8b83096242de2a49d173c4ada7c01a28e95fc055144192", "query": "[x] Chrome Dev Tools: Elements [x] Chrome Dev Tools: Network [x] Chrome Dev Tools: Sources [x] Chrome Dev Tools: Timeline [x] Chrome Dev Tools: Profiles [x] Chrome Dev Tools: Resources [x] Chrome Dev Tools: Audits [x] Chrome Dev Tools: Console [x] Chrome Dev Tools: Summary\nWorking on it", "positive_passages": [{"docid": "doc-en-freeCodeCamp-125f4612904460b3d9f49788ade2a5a24caeaa5a99d50fdfd2e8a1769f105eb0", "text": "] ], \"type\": \"hike\",
\"challengeType\": 6 \"challengeType\": 6, \"nameEs\": \"Herramientas de desarrollo de Chrome: Fuentes\", \"descriptionEs\": [ \"La pesta\u00f1a 'fuentes' es m\u00e1s \u00fatil para la depuraci\u00f3n de JavaScript. Cuanto m\u00e1s grande sea tu proyecto, tanto m\u00e1s dif\u00edcil resulta encontrar exactamente d\u00f3nde se produce un problema. \", \"Puedes seleccionar diferentes partes del c\u00f3digo para ser 'puntos de interrupci\u00f3n', puestos de control que detendr\u00e1n la ejecuci\u00f3n del c\u00f3digo en ese preciso momento. \", \"Hay diferentes puntos de interrupci\u00f3n que puedes establecer, por ejemplo una l\u00ednea de c\u00f3digo espec\u00edfica, un evento del DOM, una petici\u00f3n del servidor llamada solicitud XMLHTTP, o un evento de JavaScript.\", \"Cuando estableces un punto de interrupci\u00f3n, el navegador detiene todo cuando llega a interpretar esa l\u00ednea de c\u00f3digo o evento.\", \"Al reducir la velocidad de todo y darte la oportunidad de examinar lo que est\u00e1 sucediendo en cada punto que hayas configurado, podr\u00e1s controlar exactamente lo que est\u00e1 sucediendo en la p\u00e1gina o aplicaci\u00f3n.\", \"Una vez has establecido todos los puntos de interrupci\u00f3n, puedes recorrer el c\u00f3digo y examinar el estado de tu p\u00e1gina o aplicaci\u00f3n en cada punto de interrupci\u00f3n.\", \"Al igual que con los elementos, puedes editar en vivo mediante las herramientas de desarrollo, pero recuerda que debes guardar esos cambios para que no pierdas tu progreso.\", \"Revisa documentaci\u00f3n m\u00e1s detallada aqu\u00ed: developers.google.com/web/tools/javascript/breakpoints/\" ] }, { \"id\": \"56b15f15632298c12f315181\",", "commid": "freeCodeCamp_pr_7200"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-cc128fa3cb2aa38bfd8b83096242de2a49d173c4ada7c01a28e95fc055144192", "query": "[x] Chrome Dev Tools: Elements [x] Chrome Dev Tools: Network [x] Chrome Dev Tools: Sources [x] Chrome Dev Tools: Timeline [x] Chrome Dev Tools: Profiles [x] Chrome Dev Tools: Resources [x] Chrome Dev Tools: Audits [x] Chrome Dev Tools: Console [x] Chrome Dev Tools: Summary\nWorking on it", "positive_passages": [{"docid": "doc-en-freeCodeCamp-639fa9c742877d0ed523b5a12d9fc633e1b0706f5e2c05dd06dc590ab8f82d3b", "text": "] ], \"type\": \"hike\",
\"challengeType\": 6 \"challengeType\": 6, \"nameEs\": \"Herramientas de desarrollo de Chrome: L\u00ednea de tiempo\", \"descriptionEs\": [ \"El panel L\u00ednea de tiempo te permite grabar y analizar toda la actividad en tu aplicaci\u00f3n mientras se ejecuta. Es el mejor lugar para comenzar a investigar los problemas de rendimiento que percibas en tu aplicaci\u00f3n. \", \"Al igual que usas el panel de red para averiguar cu\u00e1nto tiempo toman las partes de la p\u00e1gina para comunicarse con el Internet y utilizas fuentes para averiguar d\u00f3nde algo se da\u00f1a, puedes utilizar la l\u00ednea de tiempo para averiguar con m\u00e1s detalle lo que est\u00e1 pasando y el tiempo que tarda.\", \"En el panel l\u00ednea de tiempo grabas acontecimientos con el peque\u00f1o bot\u00f3n circular. Puedes grabar (o capturar) pilas, perfiles js, la memoria y la presentaci\u00f3n (CSS). \", \"Al grabarlos (capturalos), quedan en peque\u00f1os y detallados registros que puedes organizar de muchas maneras para que se adapten a tus necesidades.\", \"Todo esto te ayudar\u00e1 a entender mejor lo que est\u00e1 pasando en el navegador, en particular cu\u00e1les eventos requieren m\u00e1s memoria del navegador.\", \"Cuando uses la l\u00ednea de tiempo, recuerda que debes utilizar el bot\u00f3n 'limpiar' (clear) para iniciar la grabaci\u00f3n y antes de cargar la p\u00e1gina, dependiendo de lo que desees capturar.\", \"Te dar\u00e1s cuenta de que cuando grabas eventos JS, al pulsar en el t\u00edtulo o en una 'llamada a una funci\u00f3n' al lado izquierdo, te llevar\u00e1 al documento y a la l\u00ednea de esa funci\u00f3n en el panel de recursos. \", \"Revisa documentaci\u00f3n m\u00e1s detallada aqu\u00ed: developers.google.com/web/tools/profile-performance/evaluate-performance/timeline-tool\" ] }, { \"id\": \"56b15f15632298c12f315180\",", "commid": "freeCodeCamp_pr_7200"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-cc128fa3cb2aa38bfd8b83096242de2a49d173c4ada7c01a28e95fc055144192", "query": "[x] Chrome Dev Tools: Elements [x] Chrome Dev Tools: Network [x] Chrome Dev Tools: Sources [x] Chrome Dev Tools: Timeline [x] Chrome Dev Tools: Profiles [x] Chrome Dev Tools: Resources [x] Chrome Dev Tools: Audits [x] Chrome Dev Tools: Console [x] Chrome Dev Tools: Summary\nWorking on it", "positive_passages": [{"docid": "doc-en-freeCodeCamp-3540d87ada4d72958b76fe0577921150332a0c5b28d69334e1cb4dd6c6669ffe", "text": "] ], \"type\": \"hike\",
\"challengeType\": 6 \"challengeType\": 6, \"nameEs\": \"Herramientas de desarrollo de Chrome: Perfiles\", \"descriptionEs\": [ \"El panel Perfiles te permite perfilar el tiempo de ejecuci\u00f3n y el uso de memoria de una aplicaci\u00f3n web o de una p\u00e1gina. Esto se aplica principalmente a la ejecuci\u00f3n de JavaScript en su p\u00e1gina o aplicaci\u00f3n. \", \"Hay tres tipos de perfiles que se pueden recolectar: el perfil de la CPU, instant\u00e1neas de la memoria con estructura mont\u00f3n (Heap), y el perfil de la memoria con estructura mont\u00f3n. Los perfiles de memoria en estructura mont\u00f3n tienen m\u00e1s que ver con el uso de memoria, mientras que un perfil de la CPU tiene m\u00e1s que ver con el rendimiento de JavaScript. \", \"Un perfilador llamado V8 se usa mientras se ejecuta el c\u00f3digo para identificar lo que en el JavaScript toma mucho tiempo, facilit\u00e1ndote de esta forma optimizar tu c\u00f3digo.\", \"Cada uno de estos perfiles se puede ver a la izquierda, y se puede tomar m\u00faltiples perfiles de cada uno. En general, la pesta\u00f1a de perfiles es muy \u00fatil cuando deseas optimizar tu c\u00f3digo. \", \"Revisa documentaci\u00f3n m\u00e1s detallada aqu\u00ed: developers.google.com/web/tools/profile-performance/rendering-tools/js-execution\" ] }, { \"id\": \"56b15f15632298c12f31517f\",", "commid": "freeCodeCamp_pr_7200"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-cc128fa3cb2aa38bfd8b83096242de2a49d173c4ada7c01a28e95fc055144192", "query": "[x] Chrome Dev Tools: Elements [x] Chrome Dev Tools: Network [x] Chrome Dev Tools: Sources [x] Chrome Dev Tools: Timeline [x] Chrome Dev Tools: Profiles [x] Chrome Dev Tools: Resources [x] Chrome Dev Tools: Audits [x] Chrome Dev Tools: Console [x] Chrome Dev Tools: Summary\nWorking on it", "positive_passages": [{"docid": "doc-en-freeCodeCamp-18dbebf71a1e569fdd9b589a6ebf7718c1f113ef6211ad1b74bb3247882d4843", "text": "] ], \"type\": \"hike\",
\"challengeType\": 6 \"challengeType\": 6, \"nameEs\": \"Herramientas de desarrollo de Chrome: Recursos\", \"descriptionEs\": [ \"El panel de Recursos te permite inspeccionar los recursos que se cargan en la p\u00e1gina, incluyendo IndexedDB o bases de datos SQL Web, almacenamiento local y de sesi\u00f3n, las galletas (cookies), memoria cach\u00e9 de aplicaciones, im\u00e1genes, fuentes y hojas de estilo.\", \"Puedes ver y editar toda esta informaci\u00f3n dentro del navegador.\", \"A medida que vayas construyendo aplicaciones web m\u00e1s avanzadas, juega con el panel de recursos y ver\u00e1s c\u00f3mo te ayudar\u00e1 a entender los requisitos de tu aplicaci\u00f3n y de tu p\u00e1gina en tiempo real.\", \"Revisa documentaci\u00f3n m\u00e1s detallada aqu\u00ed: developers.google.com/web/tools/iterate/manage-data/index\" ] }, { \"id\": \"56b15f15632298c12f31517e\",", "commid": "freeCodeCamp_pr_7200"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-cc128fa3cb2aa38bfd8b83096242de2a49d173c4ada7c01a28e95fc055144192", "query": "[x] Chrome Dev Tools: Elements [x] Chrome Dev Tools: Network [x] Chrome Dev Tools: Sources [x] Chrome Dev Tools: Timeline [x] Chrome Dev Tools: Profiles [x] Chrome Dev Tools: Resources [x] Chrome Dev Tools: Audits [x] Chrome Dev Tools: Console [x] Chrome Dev Tools: Summary\nWorking on it", "positive_passages": [{"docid": "doc-en-freeCodeCamp-d2537a8a7042b4238f2d79ee22015ae8b21b9fc850dfbc18fc943de2b7be9b47", "text": "] ], \"type\": \"hike\",
\"challengeType\": 6 \"challengeType\": 6, \"nameEs\": \"Herramientas de desarrollo de Chrome: Las auditor\u00edas\", \"descriptionEs\": [ \"La herramienta de auditor\u00eda te gu\u00eda para mejorar tu p\u00e1gina paso a paso.\", \"En este v\u00eddeo, se utiliza esta herramienta con un generador de citas aleatorias desarrollado como uno de los proyectos de desarrollo de interfaces.\", \"Las sugerencias que se ven, se generan autom\u00e1ticamente con la funci\u00f3n de auditor\u00eda.\", \"Es importante tenerlas en cuenta para contextualizarlos con el resto de conocimiento que tienes de tu sitio.\", \"A veces, puede ser que sea lo acertado, pero en ocasiones, por tu situaci\u00f3n las sugerencias que da son equivocadas.\", \"Usa esta herramienta cuando desees mejorar tu sitio o aplicaci\u00f3n, pero no sepas por d\u00f3nde empezar.\" ] }, { \"id\": \"56b15f15632298c12f31517d\",", "commid": "freeCodeCamp_pr_7200"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-cc128fa3cb2aa38bfd8b83096242de2a49d173c4ada7c01a28e95fc055144192", "query": "[x] Chrome Dev Tools: Elements [x] Chrome Dev Tools: Network [x] Chrome Dev Tools: Sources [x] Chrome Dev Tools: Timeline [x] Chrome Dev Tools: Profiles [x] Chrome Dev Tools: Resources [x] Chrome Dev Tools: Audits [x] Chrome Dev Tools: Console [x] Chrome Dev Tools: Summary\nWorking on it", "positive_passages": [{"docid": "doc-en-freeCodeCamp-8fd8e3ccb34f78480c1d57fbb31ce9101fcc36452a8adb6b9f11ac804fd927fc", "text": "] ], \"type\": \"hike\",
\"challengeType\": 6 \"challengeType\": 6, \"nameEs\": \"Herramientas de desarrollo de Chrome: Consola\", \"descriptionEs\": [ \"El panel de la consola ofrece dos funciones principales: registro de datos de diagn\u00f3stico en el proceso de desarrollo y proporcionar un int\u00e9rprete de \u00f3rdenes que puedes utilizar para interactuar con el documento y las Herramientas de desarrollo\", \"Al utilizar la consola, puedes ver los datos en bruto o estructurados mediante instrucciones est\u00e1ndar JS y \u00f3rdenes espec\u00edficas para la consola.\", \"Un ejemplo de datos estructurados ser\u00eda la informaci\u00f3n JSON que devuelva una API. Muy \u00fatil cuando se construyen las primeras aplicaciones de desarrollo de interfaces para FreeCodeCamp.\", \"Debes saber que los mensajes se apilan y que puedes limpiarlos escribiendo clear()
. Tambi\u00e9n puedes guardar la bit\u00e1cora seleccionando 'Preserve Log'. \", \"Hay diferentes \u00f3rdenes que registrar\u00e1n en bit\u00e1coras de manera diferente, como console.log() para registrar informaci\u00f3n b\u00e1sica, console.error() y console.warn() para registrar en bit\u00e1coras 'informaci\u00f3n llamativa'.\", \"La consola puede realizar un seguimiento de excepciones, que b\u00e1sicamente registra cuando algo sale mal. Puede incluso hacer una pausa en el c\u00f3digo durante esas excepciones, funci\u00f3n que posiblemente recuerdes de la pesta\u00f1a 'Fuente'. \", \"Revisa documentaci\u00f3n m\u00e1s detallada aqu\u00ed: developers.google.com/web/tools/javascript/console/\" ] }, { \"id\": \"56b15f15632298c12f31517c\",", "commid": "freeCodeCamp_pr_7200"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-cc128fa3cb2aa38bfd8b83096242de2a49d173c4ada7c01a28e95fc055144192", "query": "[x] Chrome Dev Tools: Elements [x] Chrome Dev Tools: Network [x] Chrome Dev Tools: Sources [x] Chrome Dev Tools: Timeline [x] Chrome Dev Tools: Profiles [x] Chrome Dev Tools: Resources [x] Chrome Dev Tools: Audits [x] Chrome Dev Tools: Console [x] Chrome Dev Tools: Summary\nWorking on it", "positive_passages": [{"docid": "doc-en-freeCodeCamp-6c359b9b16dc5e61b0967e71d1ef20ebd65edced77028059095b62534400907a", "text": "] ], \"type\": \"hike\",
\"challengeType\": 6 \"challengeType\": 6, \"nameEs\": \"Herramientas de desarrollo de Chrome: Resumen\", \"descriptionEs\": [ \", Las herramientas de desarrollo de Chrome son impresionantes, y cuanto m\u00e1s te puedas sumergir y tratar de utilizarlas, m\u00e1s r\u00e1pido aumentar\u00e1 tu nivel. \", \", Utiliza la documentaci\u00f3n, incluso si nunca has le\u00eddo documentaci\u00f3n antes: developers.google.com/web/tools/chrome-devtools/ \", \", Una vez que comiences a sentirte c\u00f3modo en una pesta\u00f1a, r\u00e9tate aprendiendo a usar una diferente. Trabajar eficazmente con todas las pesta\u00f1as te servir\u00e1 exponencialmente m\u00e1s que pegarte en tu zona de confort.\" ] } ] }", "commid": "freeCodeCamp_pr_7200"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-54b85bde8e5a5af5df0206257682ad180f4b5758e3b7ce6ca6e13556fdb9d061", "query": "[x] Build a JavaScript Calculator [x] Build a Pomodoro Clock [x] Build a Tic Tac Toe Game [x] Build a Simon Game\nWorking on this one", "positive_passages": [{"docid": "doc-en-freeCodeCamp-e774f67d80e823ddcc5ae0c890f8041c50647f034c716f7ac16dcb19f862f014", "text": "\"challengeType\": 3, \"nameEs\": \"Crea una calculadora JavaScript\", \"descriptionEs\": [
\"Objetivo: Crea una aplicaci\u00f3n con CodePen.io que reproduzca efectivamente mediante ingenier\u00eda inversa este app: http://codepen.io/FreeCodeCamp/full/zrRzMR.\", \"Objetivo: Crea una aplicaci\u00f3n con CodePen.io cuya funcionalidad sea similar a esta: http://codepen.io/FreeCodeCamp/full/zrRzMR.\", \"
Regla #1: No veas el c\u00f3digo del proyecto de ejemplo en CodePen. Encuentra la forma de hacerlo por tu cuenta.\",
\"Regla #2: Puedes usar cualquier librer\u00eda o APIs que necesites.\", \"Regla #3: Usa ingenier\u00eda inversa para reproducir la funcionalidad del proyecto de ejemplo, pero tambi\u00e9n si\u00e9ntete en la libertad de personalizarlo.\", \"Las siguientes son las historias de usuario que debes satisfacer, incluyendo las historias opcionales:\", \"Historia de usuario: Como usuario, puedo sumar, restar, multiplicar y dividir dos n\u00fameros.\", \"Regla #2: Satisface las siguientes historias de usuario. Usa cualquier librer\u00eda o API que necesites. Dale tu estilo personal.\", \"Historia de usuario: Puedo sumar, restar, multiplicar y dividir dos n\u00fameros.\", \"
Historia de usuario opcional: Puedo limpiar la pantalla con un bot\u00f3n de borrar.\", \"
Historia de usuario opcional: Puedo concatenar continuamente varias operaciones hasta que pulse el bot\u00f3n de igual, y la calculadora me mostrar\u00e1 la respuesta correcta.\",
\"Recuerda utilizar Read-Search-Ask si te sientes atascado.\", \"Cuando hayas terminado, pulsa el bot\u00f3n de \"I've completed this challenge\" e incluye un link a tu CodePen. Si programaste en pareja, debes incluir tambi\u00e9n el nombre de usuario de Free Code Camp de tu compa\u00f1ero.\", \"Si quieres retroalimentaci\u00f3n inmediata de parte de tus compa\u00f1eros campistas, pulsa este bot\u00f3n y pega el link de tu proyecto en CodePen.
Pulsa aqu\u00ed y agrega tu link en el texto del tweet\" \"Recuerda utilizar Leer-Buscar-Preguntar si te sientes atascado.\", \"Cuando hayas terminado, pulsa el bot\u00f3n de \"I've completed this challenge\" e incluye un enlace a tu CodePen. \", \"Puedes obtener retroalimentaci\u00f3n sobre tu proyecto por parte de otros campistas, comparti\u00e9ndolo en nuestra Sala de chat para revisi\u00f3n de c\u00f3digo. Tambi\u00e9n puedes compartirlo en Twitter y en el campamento de tu ciudad (en Facebook).\" ], \"isRequired\": true },", "commid": "freeCodeCamp_pr_7005"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-54b85bde8e5a5af5df0206257682ad180f4b5758e3b7ce6ca6e13556fdb9d061", "query": "[x] Build a JavaScript Calculator [x] Build a Pomodoro Clock [x] Build a Tic Tac Toe Game [x] Build a Simon Game\nWorking on this one", "positive_passages": [{"docid": "doc-en-freeCodeCamp-b8ce72853f5c0c5d57c9ccbe0894a872456b4e1f28e18188f30ab4d70734da75", "text": "], \"nameEs\": \"Crea un reloj pomodoro\", \"descriptionEs\": [
\"Objetivo: Crea una aplicaci\u00f3n con CodePen.io que reproduzca efectivamente mediante ingenier\u00eda inversa este app: http://codepen.io/FreeCodeCamp/full/VemPZX.\", \"Objetivo: Crea una aplicaci\u00f3n con CodePen.io cuya funcionalidad sea similar a la de esta: http://codepen.io/FreeCodeCamp/full/VemPZX.\", \"
Regla #1: No veas el c\u00f3digo del proyecto de ejemplo en CodePen. Encuentra la forma de hacerlo por tu cuenta.\",
\"Regla #2: Puedes usar cualquier librer\u00eda o APIs que necesites.\", \"Regla #3: Usa ingenier\u00eda inversa para reproducir la funcionalidad del proyecto de ejemplo, pero tambi\u00e9n si\u00e9ntete en la libertad de personalizarlo.\", \"Las siguientes son las historias de usuario que debes satisfacer, incluyendo las historias opcionales:\", \"Historia de usuario: Como usuario, puedo iniciar un pomodoro de 25 minutos, y el cron\u00f3metro terminar\u00e1 cuando pasen 25 minutos.\", \"Regla #2: Satisface las siguientes historias de usuario. Usa cualquier librer\u00eda o APIs que necesites. Dale tu estilo personal.\", \"Historia de usuario: Puedo iniciar un pomodoro de 25 minutos, y el cron\u00f3metro terminar\u00e1 cuando pasen 25 minutos.\", \"
Historia de usuario: Como usuario, puedo reiniciar el reloj para comenzar mi siguiente pomodoro.\",
\"Historia de usuario opcional: Como usuario, puedo personalizar la longitud de cada pomodoro.\", \"Recuerda utilizar Read-Search-Ask si te sientes atascado.\", \"Cuando hayas terminado, pulsa el bot\u00f3n de \"I've completed this challenge\" e incluye un link a tu CodePen. Si programaste en pareja, debes incluir tambi\u00e9n el nombre de usuario de Free Code Camp de tu compa\u00f1ero.\", \"Si quieres retroalimentaci\u00f3n inmediata de parte de tus compa\u00f1eros campistas, pulsa este bot\u00f3n y pega el link de tu proyecto en CodePen.
Pulsa aqu\u00ed y agrega tu link en el texto del tweet\" \"Historia de usuario: Como usuario, puedo personalizar la longitud de cada pomodoro.\", \"Recuerda utilizar Leer-Buscar-Preguntar si te sientes atascado.\", \"Cuando hayas terminado, pulsa el bot\u00f3n de \"I've completed this challenge\" e incluye un enlace a tu CodePen.\", \"Puedes obtener retroalimentaci\u00f3n sobre tu proyecto por parte de otros campistas, comparti\u00e9ndolo en nuestra Sala de chat para revisi\u00f3n de c\u00f3digo. Tambi\u00e9n puedes compartirlo en Twitter y en el campamento de tu ciudad (en Facebook).\" ], \"isRequired\": true, \"challengeType\": 3", "commid": "freeCodeCamp_pr_7005"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-54b85bde8e5a5af5df0206257682ad180f4b5758e3b7ce6ca6e13556fdb9d061", "query": "[x] Build a JavaScript Calculator [x] Build a Pomodoro Clock [x] Build a Tic Tac Toe Game [x] Build a Simon Game\nWorking on this one", "positive_passages": [{"docid": "doc-en-freeCodeCamp-b48afaa1fa894ce28e8131b6458b5f6c763cc0302eb40393f68e5e9aba7397f1", "text": "\"challengeType\": 3, \"nameEs\": \"Crea un juego de Tic Tac Toe\", \"descriptionEs\": [
\"Objetivo: Crea una aplicaci\u00f3n con CodePen.io que reproduzca efectivamente mediante ingenier\u00eda inversa este app: http://codepen.io/FreeCodeCamp/full/adBpvw.\", \"Objetivo: Construye una aplicaci\u00f3n en CodePen.io cuya funcionalidad sea similar a la de esta: http://codepen.io/FreeCodeCamp/full/adBpvw.\", \"
Regla #1: No veas el c\u00f3digo del proyecto de ejemplo en CodePen. Encuentra la forma de hacerlo por tu cuenta.\",
\"Regla #2: Puedes usar cualquier librer\u00eda o APIs que necesites.\", \"Regla #3: Usa ingenier\u00eda inversa para reproducir la funcionalidad del proyecto de ejemplo, pero tambi\u00e9n si\u00e9ntete en la libertad de personalizarlo.\", \"Las siguientes son las historias de usuario que debes satisfacer, incluyendo las historias opcionales:\", \"Historia de usuario: Como usuario, puedo iniciar un juego de Tic Tac Toe con la computadora.\", \"Historia de usuario opcional: Como usuario, nunca puedo ganar contra la computadora - en el mejor de los casos puedo empatar.\", \"Historia de usuario opcional: Como usuario, mi juego se reiniciar\u00e1 tan pronto como se termine, de tal forma que pueda jugar de nuevo.\", \"Historia de usuario opcional: Como usuario, puedo elegir si quiero jugar como X o como O.\", \"Recuerda utilizar Read-Search-Ask si te sientes atascado.\", \"Cuando hayas terminado, pulsa el bot\u00f3n de \"I've completed this challenge\" e incluye un link a tu CodePen. Si programaste en pareja, debes incluir tambi\u00e9n el nombre de usuario de Free Code Camp de tu compa\u00f1ero.\", \"Si quieres retroalimentaci\u00f3n inmediata de parte de tus compa\u00f1eros campistas, pulsa este bot\u00f3n y pega el link de tu proyecto en CodePen.
Pulsa aqu\u00ed y agrega tu link en el texto del tweet\" \"Regla #2: Satisface las siguientes historias de usuario. Usa cualquier librer\u00eda o APIs que necesites. Dale tu estilo personal.\", \"Historia de usuario: Puedo jugar un juego de Tic Tac Toe contra el computador.\", \"Historia de usuario: Mi juego se reiniciar\u00e1 tan pronto como termine para poder jugar de nuevo.\", \"Historia de usuario: Puedo elegir si quiero jugar como X o como O.\", \"Recuerda utilizar Leer-Buscar-Preguntar si te sientes atascado.\", \"Cuando hayas terminado, pulsa el bot\u00f3n de \"I've completed this challenge\" e incluye un enlace a tu CodePen.\", \"Puedes obtener retroalimentaci\u00f3n sobre tu proyecto por parte de otros campistas, comparti\u00e9ndolo en nuestra Sala de chat para revisi\u00f3n de c\u00f3digo. Tambi\u00e9n puedes compartirlo en Twitter y en el campamento de tu ciudad (en Facebook).\" ], \"isRequired\": true },", "commid": "freeCodeCamp_pr_7005"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-54b85bde8e5a5af5df0206257682ad180f4b5758e3b7ce6ca6e13556fdb9d061", "query": "[x] Build a JavaScript Calculator [x] Build a Pomodoro Clock [x] Build a Tic Tac Toe Game [x] Build a Simon Game\nWorking on this one", "positive_passages": [{"docid": "doc-en-freeCodeCamp-e9ee1ec774663eabd51cc58a148fe7b113504a4523732e039ea1ddda6fdf72d2", "text": "\"challengeType\": 3, \"nameEs\": \"Construye un juego de Simon\", \"descriptionEs\": [
\"Objetivo: Crea una aplicaci\u00f3n con CodePen.io que reproduzca efectivamente mediante ingenier\u00eda inversa este app: http://codepen.io/FreeCodeCamp/full/obYBjE.\", \"Objetivo: Construye una aplicaci\u00f3n en CodePen.io cuya funcionalidad sea similar a la de esta: http://codepen.io/Em-Ant/full/QbRyqq/.\", \"
Regla #1: No veas el c\u00f3digo del proyecto de ejemplo en CodePen. Encuentra la forma de hacerlo por tu cuenta.\",
\"Regla #2: Puedes usar cualquier librer\u00eda o APIs que necesites.\", \"Regla #3: Usa ingenier\u00eda inversa para reproducir la funcionalidad del proyecto de ejemplo, pero tambi\u00e9n si\u00e9ntete en la libertad de personalizarlo.\", \"Las siguientes son las historias de usuario que debes satisfacer, incluyendo las historias opcionales:\", \"Historia de usuario: Como usuario, se me presenta una serie de colores aleatoria.\", \"Historia de usuario: Como usuario, cada vez que presiono una secuencia de colores correctamente, veo la misma serie de colores con un paso adicional.\", \"Historia de usuario: Como usuario, escucho un sonido que corresponde a cada bot\u00f3n cuando una sequencia se me presenta, as\u00ed como cuando yo presiono un bot\u00f3n.\", \"Historia de usuario: Como usuario, si presiono el bot\u00f3n equivocado, se me notifica sobre mi error, y la serie correcta de colores se muestra de nuevo para recordarme cu\u00e1l es la secuencia correcta, tras lo cual puedo probar de nuevo.\", \"Historia de usuario: Como usuario, puedo ver cu\u00e1ntos pasos hay en la serie de botones actual.\", \"Historia de usuario opcional: Como usuario, si deseo reiniciar, puedo pulsar un bot\u00f3n para hacerlo, y el juego comenzar\u00e1 desde una secuencia con un solo paso.\", \"Historia de usuario opcional: Como usuario, puedo jugar en modo estricto donde si presiono el bot\u00f3n equivocado, se me notifica de mi error, y el juego vuelve a comenzar con una nueva serie aleatoria de colores.\", \"Historia de usuario opcional: Como usuario, la velocidad del juego se incrementa en el quinto, noveno y decimotercer paso.\", \"Historia de usuario opcional: Como usuario, puedo ganar el juego si completo 20 pasos correctos. Se me notifica sobre mi victoria, tras lo cual el juego se reinicia.\", \"Regla #2: Satisface las siguientes historias de usuario. Usa cualquier librer\u00eda o APIs que necesites. Dale tu estilo personal.\", \"Historia de usuario: Se me presenta una serie aleatoria de pulsaciones a botones.\", \"Historia de usuario: Cada vez que presiono una secuencia de pulsaciones correctamente, veo que vuelve a ejecutarse la misma serie de pulsaciones con un paso adicional.\", \"Historia de usuario: Escucho un sonido que corresponde a cada bot\u00f3n cuando se ejecuta una secuencia de pulsaciones, as\u00ed como cuando yo presiono un bot\u00f3n.\", \"Historia de usuario: Si presiono el bot\u00f3n equivocado, se me notifica sobre mi error, y se ejecuta de nuevo la serie correcta de pulsaciones para recordarme cu\u00e1l es la secuencia correcta, tras lo cual puedo intentar de nuevo.\", \"Historia de usuario: Puedo ver cu\u00e1ntos pasos hay en la serie de pulsaciones actual.\", \"Historia de usuario: Si deseo reiniciar, puedo pulsar un bot\u00f3n para hacerlo, y el juego comenzar\u00e1 desde una secuencia con un solo paso.\", \"Historia de usuario: Puedo jugar en modo estricto donde si presiono el bot\u00f3n equivocado, se me notifica de mi error, y el juego vuelve a comenzar con una nueva serie aleatoria de colores.\", \"Historia de usuario: Puedo ganar el juego si completo 20 pasos correctos. Se me notifica sobre mi victoria, tras lo cual el juego se reinicia.\", \"
Pista: Aqu\u00ed hay algunos mp3s que puedes utilizar para tus botones:
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
.\",
\"Recuerda utilizar Read-Search-Ask si te sientes atascado.\", \"Cuando hayas terminado, pulsa el bot\u00f3n de \"I've completed this challenge\" e incluye un link a tu CodePen. Si programaste en pareja, debes incluir tambi\u00e9n el nombre de usuario de Free Code Camp de tu compa\u00f1ero.\", \"Si quieres retroalimentaci\u00f3n inmediata de parte de tus compa\u00f1eros campistas, pulsa este bot\u00f3n y pega el link de tu proyecto en CodePen.
Pulsa aqu\u00ed y agrega tu link en el texto del tweet\" \"Recuerda utilizar Leer-Buscar-Preguntar si te sientes atascado.\", \"Cuando hayas terminado, pulsa el bot\u00f3n de \"I've completed this challenge\" e incluye un enlace a tu CodePen.\", \"Puedes obtener retroalimentaci\u00f3n sobre tu proyecto por parte de otros campistas, comparti\u00e9ndolo en nuestra Sala de chat para revisi\u00f3n de c\u00f3digo. Tambi\u00e9n puedes compartirlo en Twitter y en el campamento de tu ciudad (en Facebook).\" ], \"isRequired\": true } ]
} No newline at end of file
} ", "commid": "freeCodeCamp_pr_7005"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-9f4940d06b254ceaad7e3fdb3d2d88c056e9a7f5f6fe0167302651ba700fdc2f", "query": "Challenge has an issue. User Agent is:
\"challengeSeed\": \"function inventory(arr1, arr2) {n // All inventory must be accounted for or you're fired!rn return arr1;rn}nn// Example inventory listsrnvar curInv = [rn [21, 'Bowling Ball'],rn [2, 'Dirty Sock'],rn [1, 'Hair pin'],rn [5, 'Microphone']rn];rnrnvar newInv = [rn [2, 'Hair Pin'],rn [3, 'Half-Eaten Apple'],rn [67, 'Bowling Ball'],rn [7, 'Toothpaste']rn];rnrninventory(curInv, newInv);\", \"tests\": [ \"expect(inventory([[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair pin'], [5, 'Microphone']], [[2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [67, 'Bowling Ball'], [7, 'Toothpaste']])).to.be.a('array');\", \"assert.equal(inventory([[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair pin'], [5, 'Microphone']], [[2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [67, 'Bowling Ball'], [7, 'Toothpaste']]).length, 6);\", \"assert.deepEqual(inventory([[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair pin'], [5, 'Microphone']], [[2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [67, 'Bowling Ball'], [7, 'Toothpaste']]), [[88, 'Bowling Ball'], [2, 'Dirty Sock'], [3, 'Hair pin'], [3, 'Half-Eaten Apple'], [5, 'Microphone'], [7, 'Toothpaste']]);\", \"assert.deepEqual(inventory([[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair pin'], [5, 'Microphone']], []), [[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair pin'], [5, 'Microphone']]);\", \"assert.deepEqual(inventory([], [[2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [67, 'Bowling Ball'], [7, 'Toothpaste']]), [[2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [67, 'Bowling Ball'], [7, 'Toothpaste']]);\", \"assert.deepEqual(inventory([[0, 'Bowling Ball'], [0, 'Dirty Sock'], [0, 'Hair pin'], [0, 'Microphone']], [[1, 'Hair Pin'], [1, 'Half-Eaten Apple'], [1, 'Bowling Ball'], [1, 'Toothpaste']]), [[1, 'Bowling Ball'], [1, 'Dirty Sock'], [1, 'Hair pin'], [1, 'Half-Eaten Apple'], [1, 'Microphone'], [1, 'Toothpaste']]);\" \"challengeSeed\": \"function inventory(arr1, arr2) {n // All inventory must be accounted for or you're fired!rn return arr1;rn}nn// Example inventory listsrnvar curInv = [rn [21, 'Bowling Ball'],rn [2, 'Dirty Sock'],rn [1, 'Hair Pin'],rn [5, 'Microphone']rn];rnrnvar newInv = [rn [2, 'Hair Pin'],rn [3, 'Half-Eaten Apple'],rn [67, 'Bowling Ball'],rn [7, 'Toothpaste']rn];rnrninventory(curInv, newInv);\", \"tests\": [ \"expect(inventory([[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair Pin'], [5, 'Microphone']], [[2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [67, 'Bowling Ball'], [7, 'Toothpaste']])).to.be.a('array');\", \"assert.equal(inventory([[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair Pin'], [5, 'Microphone']], [[2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [67, 'Bowling Ball'], [7, 'Toothpaste']]).length, 6);\", \"assert.deepEqual(inventory([[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair Pin'], [5, 'Microphone']], [[2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [67, 'Bowling Ball'], [7, 'Toothpaste']]), [[88, 'Bowling Ball'], [2, 'Dirty Sock'], [3, 'Hair Pin'], [3, 'Half-Eaten Apple'], [5, 'Microphone'], [7, 'Toothpaste']]);\", \"assert.deepEqual(inventory([[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair Pin'], [5, 'Microphone']], []), [[21, 'Bowling Ball'], [2, 'Dirty Sock'], [1, 'Hair Pin'], [5, 'Microphone']]);\", \"assert.deepEqual(inventory([], [[2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [67, 'Bowling Ball'], [7, 'Toothpaste']]), [[67, 'Bowling Ball'], [2, 'Hair Pin'], [3, 'Half-Eaten Apple'], [7, 'Toothpaste']]);\", \"assert.deepEqual(inventory([[0, 'Bowling Ball'], [0, 'Dirty Sock'], [0, 'Hair Pin'], [0, 'Microphone']], [[1, 'Hair Pin'], [1, 'Half-Eaten Apple'], [1, 'Bowling Ball'], [1, 'Toothpaste']]), [[1, 'Bowling Ball'], [0, 'Dirty Sock'], [1, 'Hair Pin'], [1, 'Half-Eaten Apple'], [0, 'Microphone'], [1, 'Toothpaste']]);\" ] } ]", "commid": "freeCodeCamp_pr_106"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-1900eb6c754a31f7f4a4737a49530c75b5d45ee9dc1abb6ba52245f2c91bd944", "query": "Challenge has an issue. User Agent is: \"Now that we've built a foundation in jQuery, let's go back to Dash and do it's last challenge.\", \"Now that we've built a foundation in jQuery, let's go back to Dash and do its last challenge.\", \"If you aren't familiar with Mad Libs, they basically involve inserting random nouns, adjectives and verbs in to stories. The stories that result are often hilarious.\", \"Go to https://dash.generalassemb.ly/projects/mad-libs-1 and complete the fifth project.\" ]", "commid": "freeCodeCamp_pr_27"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-1900eb6c754a31f7f4a4737a49530c75b5d45ee9dc1abb6ba52245f2c91bd944", "query": "Challenge has an issue. User Agent is: .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;", "commid": "freeCodeCamp_pr_30"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-1900eb6c754a31f7f4a4737a49530c75b5d45ee9dc1abb6ba52245f2c91bd944", "query": "Challenge has an issue. User Agent is: .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;", "commid": "freeCodeCamp_pr_30"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-1900eb6c754a31f7f4a4737a49530c75b5d45ee9dc1abb6ba52245f2c91bd944", "query": "Challenge has an issue. User Agent is: .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", "commid": "freeCodeCamp_pr_30"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-1900eb6c754a31f7f4a4737a49530c75b5d45ee9dc1abb6ba52245f2c91bd944", "query": "Challenge has an issue. User Agent is: 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", "commid": "freeCodeCamp_pr_30"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-1900eb6c754a31f7f4a4737a49530c75b5d45ee9dc1abb6ba52245f2c91bd944", "query": "Challenge has an issue. User Agent is: \"expect(sumPrimes(10)).to.equal(27);\", \"expect(sumPrimes(10)).to.equal(17);\", \"expect(sumPrimes(977)).to.equal(73156);\" ] },", "commid": "freeCodeCamp_pr_87"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-aaf5753eb39e674e331b05fb15d8afe05fa9175903ea67c896f0988d99acdcdc", "query": " # --description--", "commid": "freeCodeCamp_pr_53038"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-f9bb0b76e1d1baecb3f89f97bb1398c552090346a8726cc608dc62daa37b8e2e", "query": "The fill-in-the-blank sentence doesn't match what the character says. The written sentence is: The character says: Note the \"the\", instead of \"our\". No response Device: all OS: all Browser: all Version: all No response\nThank you for reporting the issue. Note for maintainers: Step 54 () uses \"our\" instead of \"the\" in the quiz. I think it's fine as-is since there isn't associated audio/caption text, but I'd vote updating it, too, for consistency. This issue is open to first-time code contributors to this repository. Requirements: In Change the text in the tag from to In Change the text in the tag from to Change the fill-in-the-blank text from to Change the backtick placement in the description text from ` In Change the text of the answers 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.\nHi I've created a PR addressing these changes.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-50ae99ed20d62cf795810476927eec3e04c3b65164a195b45db67e5ad995a8b7", "text": "## --answers-- `What do she does as our team lead?` `What do she does as the team lead?` ### --feedback--", "commid": "freeCodeCamp_pr_53038"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-f9bb0b76e1d1baecb3f89f97bb1398c552090346a8726cc608dc62daa37b8e2e", "query": "The fill-in-the-blank sentence doesn't match what the character says. The written sentence is: The character says: Note the \"the\", instead of \"our\". No response Device: all OS: all Browser: all Version: all No response\nThank you for reporting the issue. Note for maintainers: Step 54 () uses \"our\" instead of \"the\" in the quiz. I think it's fine as-is since there isn't associated audio/caption text, but I'd vote updating it, too, for consistency. This issue is open to first-time code contributors to this repository. Requirements: In Change the text in the tag from to In Change the text in the tag from to Change the fill-in-the-blank text from to Change the backtick placement in the description text from ` In Change the text of the answers 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.\nHi I've created a PR addressing these changes.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-288d7ce9223278f76d1ad0a638eb4c7131a78dac45ed6e799658a2acf9d3b3f3", "text": "--- `What does he does as our team lead?` `What does he does as the team lead?` ### --feedback--", "commid": "freeCodeCamp_pr_53038"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-f9bb0b76e1d1baecb3f89f97bb1398c552090346a8726cc608dc62daa37b8e2e", "query": "The fill-in-the-blank sentence doesn't match what the character says. The written sentence is: The character says: Note the \"the\", instead of \"our\". No response Device: all OS: all Browser: all Version: all No response\nThank you for reporting the issue. Note for maintainers: Step 54 () uses \"our\" instead of \"the\" in the quiz. I think it's fine as-is since there isn't associated audio/caption text, but I'd vote updating it, too, for consistency. This issue is open to first-time code contributors to this repository. Requirements: In Change the text in the tag from to In Change the text in the tag from to Change the fill-in-the-blank text from to Change the backtick placement in the description text from ` In Change the text of the answers 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.\nHi I've created a PR addressing these changes.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-a6dac553ef5bcf533bd5c3f450cfb08b4fb961697a6b671a06e2de70e3edda10", "text": "--- `What do he does as our team lead?` `What do he does as the team lead?` ### --feedback--", "commid": "freeCodeCamp_pr_53038"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-f9bb0b76e1d1baecb3f89f97bb1398c552090346a8726cc608dc62daa37b8e2e", "query": "The fill-in-the-blank sentence doesn't match what the character says. The written sentence is: The character says: Note the \"the\", instead of \"our\". No response Device: all OS: all Browser: all Version: all No response\nThank you for reporting the issue. Note for maintainers: Step 54 () uses \"our\" instead of \"the\" in the quiz. I think it's fine as-is since there isn't associated audio/caption text, but I'd vote updating it, too, for consistency. This issue is open to first-time code contributors to this repository. Requirements: In Change the text in the tag from to In Change the text in the tag from to Change the fill-in-the-blank text from to Change the backtick placement in the description text from ` In Change the text of the answers 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.\nHi I've created a PR addressing these changes.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-20bdea9f47a6a2d85a10a31b827c31dca3c918732120380e653d93a03e324f0c", "text": "--- `What does she do as our team lead?` `What does she do as the team lead?` ## --video-solution--", "commid": "freeCodeCamp_pr_53038"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-f9bb0b76e1d1baecb3f89f97bb1398c552090346a8726cc608dc62daa37b8e2e", "query": "The fill-in-the-blank sentence doesn't match what the character says. The written sentence is: The character says: Note the \"the\", instead of \"our\". No response Device: all OS: all Browser: all Version: all No response\nThank you for reporting the issue. Note for maintainers: Step 54 () uses \"our\" instead of \"the\" in the quiz. I think it's fine as-is since there isn't associated audio/caption text, but I'd vote updating it, too, for consistency. This issue is open to first-time code contributors to this repository. Requirements: In Change the text in the tag from to In Change the text in the tag from to Change the fill-in-the-blank text from to Change the backtick placement in the description text from ` In Change the text of the answers 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.\nHi I've created a PR addressing these changes.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-752b2e24371b4f06a812009bb711c540111623589eea5596f413c6a4922e125a", "text": "dashedName: task-55 --- # --description-- Now you will practice listening for the correct form of `do.` Listen carefully to how Tom asks about Maria's job as a team lead. Now you will practice listening for the correct form of `do`. Listen carefully to how Tom asks about Maria's job as a team lead. # --instructions--", "commid": "freeCodeCamp_pr_53038"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-f9bb0b76e1d1baecb3f89f97bb1398c552090346a8726cc608dc62daa37b8e2e", "query": "The fill-in-the-blank sentence doesn't match what the character says. The written sentence is: The character says: Note the \"the\", instead of \"our\". No response Device: all OS: all Browser: all Version: all No response\nThank you for reporting the issue. Note for maintainers: Step 54 () uses \"our\" instead of \"the\" in the quiz. I think it's fine as-is since there isn't associated audio/caption text, but I'd vote updating it, too, for consistency. This issue is open to first-time code contributors to this repository. Requirements: In Change the text in the tag from to In Change the text in the tag from to Change the fill-in-the-blank text from to Change the backtick placement in the description text from ` In Change the text of the answers 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.\nHi I've created a PR addressing these changes.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-9c9ff29ae2c51e3cb29bd30b06fcf9adcc5fd130cfa771c979f1ad1586cc107a", "text": "## --sentence-- `Those are great traits for someone in her position, I think. What _ she _ as our team lead?` `Those are great traits for someone in her position, I think. What _ she _ as the team lead?` ## --blanks--", "commid": "freeCodeCamp_pr_53038"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-fa9d3d896a8feac20b08a2cd7a9fd968b1fe213b20a2af22d9ab18db419f1a62", "query": "So the problem is that the \u201chint\u201d where it tells you what you should\u2019ve have coded it tells you that you should have \u201cdata\u201d as key, when you code that and it doesn\u2019t work it tells you you should have \u201cmyTaskArr\u201d as key, but that\u2019s wrong it should tell you \u201cmyTaskArr\u201d as \u201cvalue\u201d. So I was trying to have 2 keys, and obviously it was always wrong. The hint should tell you that \"myTaskArr\" is a value, not a key as it currently says. ! Device: Desktop PC OS: Windows 10 Browser: Edge Version: [e.g. 22] 120.0.2210.121\nNote: Due to PR adding one more step, earlier in this project, the relevant step in codebase is 49 now. Although that change did not yet reach the production at this time.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-4f7a5b40d00ea67c7ef4336cc27bce1629ef21a559d8974da062deb3500c2b43", "text": "assert.match(code, /localStorage.setItem((\"|')data1/) ``` Your `localStorage.setItem()` should have a key of `myTaskArr`. Your `localStorage.setItem()` should have a value of `myTaskArr`. ```js assert.match(code, /localStorage.setItem((\"|')data1,s*myTaskArr);?/)", "commid": "freeCodeCamp_pr_53173"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-a9a20e6fb4828abe2d97db8f2a0dbd64d972923038d3879afd3152d7f904ea02", "query": "The description here is missing backticks for the number zero. Here is the new updated description. 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 Here is the correct file that needs to be updated. Note: Even though the file says step 62 instead of step 63 that is on the site, this is still the correct file that needs updating. We recently made changes to the ordering and those changes haven't shown up yet on the live site. Happy coding 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\nStep 145 has the same issue here Here is the file that needs to be updated here is the correct use of backticks for the number zero in the last sentence here", "positive_passages": [{"docid": "doc-en-freeCodeCamp-e425bbdac185dd58ecf5fec4beae2ed8b5f276c9b15bbd62ae4c67cacb57f88b", "text": "Pass in only the first element of the `locations` array by adding `[0]` at the end of the variable. For example: `myFunction(arg[0]);`. This is called bracket notation. Values in an array are accessed by index. Indices are numerical values and start at 0 - this is called zero-based indexing. `arg[0]` would be the first element in the `arg` array. This is called bracket notation. Values in an array are accessed by index. Indices are numerical values and start at `0` - this is called zero-based indexing. `arg[0]` would be the first element in the `arg` array. # --hints--", "commid": "freeCodeCamp_pr_53243"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-a9a20e6fb4828abe2d97db8f2a0dbd64d972923038d3879afd3152d7f904ea02", "query": "The description here is missing backticks for the number zero. Here is the new updated description. 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 Here is the correct file that needs to be updated. Note: Even though the file says step 62 instead of step 63 that is on the site, this is still the correct file that needs updating. We recently made changes to the ordering and those changes haven't shown up yet on the live site. Happy coding 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\nStep 145 has the same issue here Here is the file that needs to be updated here is the correct use of backticks for the number zero in the last sentence here", "positive_passages": [{"docid": "doc-en-freeCodeCamp-5ef7dedf806b7fdb07c5f693505e991a4526e3340503b2f25c1d37214bc2508f", "text": "The attack of the monster will be based on the monster's `level` and the player's `xp`. In the `getMonsterAttackValue` function, use `const` to create a variable called `hit`. Assign it the equation `(level * 5) - (Math.floor(Math.random() * xp));`. This will set the monster's attack to five times their `level` minus a random number between 0 and the player's `xp`. This will set the monster's attack to five times their `level` minus a random number between `0` and the player's `xp`. # --hints--", "commid": "freeCodeCamp_pr_53243"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-07d4a66ff07b253f027cbf2a27d3a6c0ff3f63bb8e279ef0254900dc17fa5e4a", "query": "Describe the bug Task 37 requires typing in one of the blanks. This can be problematic due to the letter, which might not be present in the used keyboard layout. Expected behavior I don't want to say to use completely different word for the fill the blank, as at some point there might be no other choice. There could be some kind way to ease up procuring of the letter in question, for example including it in the feedback, so it can be copied.\nHi I would love to work on this. If someone could point me in the right direction, that would be amazing!\nHi Thank you for being eager to contribute. This issue has not been triaged yet. Feel free to share your insights and ideas on the matter. However as far as the code contributing, take a look at the issues with label. 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. Thank you and happy coding.\nYes, I think in both of those challenges we can update the \"Don't forget the stress mark.\" in the feedback to: \"Don't forget the stress mark ().\"\nI will open the issue to contribution with this as the solution", "positive_passages": [{"docid": "doc-en-freeCodeCamp-193ada1f903cb72746ea0ceaefdf6085db19a14c4ba4822b395ba0498f59178a", "text": "### --feedback-- Places where you can buy and eat food. Don't forget the stress mark. Places where you can buy and eat food. Don't forget the stress mark (`\u00e9`). # --scene--", "commid": "freeCodeCamp_pr_53945"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-07d4a66ff07b253f027cbf2a27d3a6c0ff3f63bb8e279ef0254900dc17fa5e4a", "query": "Describe the bug Task 37 requires typing in one of the blanks. This can be problematic due to the letter, which might not be present in the used keyboard layout. Expected behavior I don't want to say to use completely different word for the fill the blank, as at some point there might be no other choice. There could be some kind way to ease up procuring of the letter in question, for example including it in the feedback, so it can be copied.\nHi I would love to work on this. If someone could point me in the right direction, that would be amazing!\nHi Thank you for being eager to contribute. This issue has not been triaged yet. Feel free to share your insights and ideas on the matter. However as far as the code contributing, take a look at the issues with label. 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. Thank you and happy coding.\nYes, I think in both of those challenges we can update the \"Don't forget the stress mark.\" in the feedback to: \"Don't forget the stress mark ().\"\nI will open the issue to contribution with this as the solution", "positive_passages": [{"docid": "doc-en-freeCodeCamp-e9b4a6ac98179f12ce325c81c9b6ab14551c26d3b54f3288e080ac2444141ea0", "text": "### --feedback-- Places to eat or drink. Don't forget the stress mark. Places to eat or drink. Don't forget the stress mark (`\u00e9`). ---", "commid": "freeCodeCamp_pr_53945"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-aeb123045e55ed3ca93a0b150d76e7738cb3f868f6a3f9473295b5db406483ea", "query": "A camper on the forum had issues with passing step 37 of the pyramid project This was their code Their code is correct but the tests expect a certain order of The tests should be updated to expect either 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\nconst character = \"#\"; const count = 8; const rows = []; for (let i = 0; i < count; i = i + 1) { (i); } let result = \"\" for (const row of rows) { result = + ; (result); } This worked for me, it took a while but realized I needed to swap the result with the row... This was helpful thank you\nThank you for this,I was really stuck", "positive_passages": [{"docid": "doc-en-freeCodeCamp-1f076b99e3c7c67284df98b6e95436e176ee4824ca5e50800ade88eb50ff25da", "text": "You should use the concatenation operator on your `result` variable. ```js assert.match(code, /results*+/); assert.match(code, /(?:results*+|+s*result)/); ``` You should concatenate `row` to your `result` variable. ```js assert.match(code, /results*+s*row/); assert.match(code, /results*+s*row|rows*+s*result/); ``` You should assign the result of your concatenation back to the `result` variable. ```js assert.match(code, /results*=s*results*+s*row;?/) assert.match(code, /results*=s*(results*+s*row|rows*+s*result);?/); ``` # --seed--", "commid": "freeCodeCamp_pr_54468"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-4be4c06a2e93db01cf60910074389899515ad47983d67a7d1e4df2d184a42091", "query": "When working through the , it's expected from the user to create a method that internally uses a to make a sum, like the following: But when presented the following solution, making the reduce's callback sum the other way around, it doesn't pass: Because of the , the previous presented solution should work. No response Device: Laptop OS: macOS 13.6.6 Browser: Chrome Version: 124 No response\nI agree that both versions should be accepted since they are valid solutions.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-750747c0de366fdc61bd395347ae9d85b96e0c4117fe270d116ebb0235cb8f38", "text": "```js const afterCalculateTotal = code.split('calculateTotal')[1]; assert.match(afterCalculateTotal, /(s*totals*,s*items*)s*=>s*totals*+s*item.price/); assert.match(afterCalculateTotal, /(s*totals*,s*items*)s*=>s*(?:totals*+s*item.price|item.prices*+s*total)/); ``` Your `reduce` call should have an initial value of `0`. ```js const afterCalculateTotal = code.split('calculateTotal')[1]; assert.match(afterCalculateTotal, /thiss*.s*itemss*.s*reduces*(s*(s*totals*,s*items*)s*=>s*totals*+s*item.prices*,s*0s*)/); assert.match(afterCalculateTotal, /thiss*.s*itemss*.s*reduces*(s*(s*totals*,s*items*)s*=>s*(?:totals*+s*item.price|item.prices*+s*total)s*,s*0s*)/); ``` # --seed--", "commid": "freeCodeCamp_pr_54631"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-78f396ad66fdcf58e169a99f61c1bb00ed339fb81f724e2a5abb5503f8116fb9", "query": "Currently on step number 5 there's a note that reads Note that when reassigning a variable that has already been declared, you do not use the let keyword. As it stands this note is incorrect and unnecessary. No code, just instructions re-wording. The note could be changed to: Note: You can only re-assign a variables that has been declared with Or we can simply remove it altogether instead.
Note that when reassigning a variable that has already been declared, you do **not** use the `let` keyword. Note that when reassigning a variable, you do **not** use the `let` keyword again. After your `console.log`, assign the value `\"World\"` to your `character` variable.", "commid": "freeCodeCamp_pr_54750"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-8e65f225c1a5cd51ab405d9298c02ec8e9590c3bfa58ebf801795d278c129122", "query": "There is a typo at the following step: It should present the text: Device: Laptop OS: Windows 11 Browser: Brave Version: 1.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-52c36d0cb49026c6e252e7b9df71672889ec5f8ae22712cf9d761764e3780348", "text": "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;", "commid": "freeCodeCamp_pr_30"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-8e65f225c1a5cd51ab405d9298c02ec8e9590c3bfa58ebf801795d278c129122", "query": "There is a typo at the following step: It should present the text: Device: Laptop OS: Windows 11 Browser: Brave Version: 1.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-dcd93f573fe9b6449e6dead840938b11a7be5ab4fee6d9b25b12eccef7f9f2fa", "text": "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;", "commid": "freeCodeCamp_pr_30"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-8e65f225c1a5cd51ab405d9298c02ec8e9590c3bfa58ebf801795d278c129122", "query": "There is a typo at the following step: It should present the text: Device: Laptop OS: Windows 11 Browser: Brave Version: 1.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-716ed0a99336d96c333a5894aad136a78559c688b8998eec06621cb6e6341f2d", "text": "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", "commid": "freeCodeCamp_pr_30"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-8e65f225c1a5cd51ab405d9298c02ec8e9590c3bfa58ebf801795d278c129122", "query": "There is a typo at the following step: It should present the text: Device: Laptop OS: Windows 11 Browser: Brave Version: 1.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-7b96a1fd6254002bca9bd99a4d8e54ddadb4f6b9df0c4b588fb16916994c1057", "text": "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", "commid": "freeCodeCamp_pr_30"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-3cd71940ee3b93ec6139f35e4cb0de31947a1b5a05de8d0c71446a7df21bafd6", "query": "In the first paragraph, on the 2nd phrase, you can read: . Rectify to the following: No response . 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.\nI would suggest we remove \"those\" and keep \"the\" so we are not repeating \"those\". I would also suggest using \"attribute value\"\nThe next paragraph reads pretty bad as well. It's just confusing to read. Maybe we can come up with something better. Edit: take two Or something like that?\nI know the first line already mentioned \"paragraph elements\", so it is presumed that the second line is referring to that type of element. But as a newbie, when I read \"to select the element with that attribute value\", it seems any kind of element. Could we be more specific, and edit to \"(...) to select the paragraph element (...)\"?\nIt is selecting by so the element type doesn't matter. Saying what the element type is seems redundant to me. But if you or anyone else feel it would make it more clear, then I wouldn't be opposed to it.\nYes, you are right. Mentioning is what matters.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-c3af8062adddbf73c195b7865633133e86c345ce3feca7e3d67502f2e8239771", "text": "# --description-- You used the `inputVal` property as the `id` attribute for your paragraph elements. Now you can target those the paragraph elements with those `id`s. You have set the `id` attribute for your paragraph elements to the `obj.inputVal` property. Use the `.getElementById()` method to select the element with the `id` attribute with the value of the `inputVal` property of the current object. Now, use `getElementById` to select the element with that attribute value, again using the `obj.inputVal` property. # --hints--", "commid": "freeCodeCamp_pr_55048"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-694a072215ae702ece27c4fe6f7af6c6880197ed837023de6e2418b62fec4be3", "query": "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: File: 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.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-7247e86453a7e100b5758504925d65575f9196183c23c89bf68c52425f02f100", "text": "assert.match(calculateCalories.toString(), /document.querySelectorAll(s*('|\")#breakfast input[s*type=numbers*]s*1s*)/); ``` You should assign the result of your `odocument.querySelectorAll()` call to `breakfastNumberInputs`. You should assign the result of your `document.querySelectorAll()` call to `breakfastNumberInputs`. ```js assert.match(calculateCalories.toString(), /breakfastNumberInputss*=s*document.querySelectorAll(s*('|\")#breakfast input[s*type=numbers*]s*1s*)/);", "commid": "freeCodeCamp_pr_55282"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-493a68277a02a81ae39ea87707da3484b4270fecb5d444bcc424847a41a088d1", "query": "In step 10 of Luhn Algorithm, we teach campers how to create a substring using the operator. I think the explanation is a little short and could improved by: Adding comment next to each example, showing the result of each operation (we are currently communicating the value via the variable name, but I don't think it's clear enough) Mention that the starting index is inclusive, and the ending index is exclusive Additionally, I think we could: Change to to have the syntax more self-descriptive Mention that the default value of is 1 Perhaps the description should be changed to: python mystring = 'camperbot' mystring[0:6] == 'camper' # True my_string[0:6:3] == 'cp' # True `\nDifferent project but same kind of example: I remember we decided not to use because of translations, but using them in the code example and then explain what they mean is fine :+1:\nare we able to open this up for contribution?\nPersonally, I'd prefer to change the snippet into the following: I agree with all the rest.\nI've updated the issue description with Dario's code snippet. This issue is open for contributions. 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.\nWhoops, sorry. I just noticed that Farhan is assigned to the issue. Are you working on this or could we mark this one up-for-grabs?\nYeah please mark this as up for grab", "positive_passages": [{"docid": "doc-en-freeCodeCamp-1c0da98c60c51e0c05cbb34f240e41b8868766345e5c6bc3f7177c1b8a5de478", "text": "# --description-- You have accessed elements (characters) of a string before, using the index operator `[]`. You can also use the index operator to access a range of characters in a string with `string[x:y:h]`: You have accessed elements (characters) of a string before, using the index operator `[]`. You can also use the index operator to access a range of characters in a string with `string[start:stop:step]`: ```python my_string = 'camperbot' camper = my_string[0:6] cp = my_string[0:6:3] my_string[0:6] == 'camper' # True my_string[0:6:3] == 'cp' # True ``` Where `x` is the starting index, `y` is the ending index, and `h` is the step (the amount of characters to skip over). Where `start` is the starting index (inclusive), `stop` is the ending index (exclusive), and `step` is the amount of characters to skip over. If not specified, `step` is default to 1. Create a variable named `card_number_reversed` and assign it the value of the first 4 characters of `card_number`.", "commid": "freeCodeCamp_pr_56133"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-867030372fbd448a158e4df3e60290322f4827d743c61b6e1b8c4f4129d6d918", "query": "Step 22 of build a Todo app can use a better a hint or a short reminder on destructuring if one can be into the instructions. If we forget to put the curly braces around the parameter names to destructure them, the hint only says: You should destructure id, title, date, description as the parameters of the callback of your forEach(). A better hint would be I think parameter destructuring was only covered once before this project. (though I may recall that incorrectly) here: Either a better hint or a reminder of parameter destructuring in the instructions would be helpful. No response N/A No response\nHello. I would like to work on this issue. Please assign this to me.\nLet's go with this text.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-c0efafa170a2d1265e52c7e95ef36c33011993b5e3c752485c9c6a946396bd6c", "text": "assert.match(code, /taskData.forEach(s*/) ``` You should destructure `id`, `title`, `date`, `description` as the parameters of the callback of your `forEach()`. You should use `{id, title, date, description}` as the destructured parameters of the `forEach()` callback function. ```js assert.match(code, /taskData.forEach(s*(s*{s*(?:ids*,s*titles*,s*dates*,s*description)|(?:titles*,s*ids*,s*dates*,s*description)|(?:dates*,s*ids*,s*titles*,s*description)|(?:ids*,s*dates*,s*titles*,s*description)|(?:titles*,s*dates*,s*ids*,s*description)|(?:dates*,s*titles*,s*ids*,s*description)|(?:dates*,s*titles*,s*descriptions*,s*id)|(?:titles*,s*dates*,s*descriptions*,s*id)|(?:descriptions*,s*dates*,s*titles*,s*id)|(?:dates*,s*descriptions*,s*titles*,s*id)|(?:titles*,s*descriptions*,s*dates*,s*id)|(?:descriptions*,s*titles*,s*dates*,s*id)|(?:descriptions*,s*ids*,s*dates*,s*title)|(?:ids*,s*descriptions*,s*dates*,s*title)|(?:dates*,s*descriptions*,s*ids*,s*title)|(?:descriptions*,s*dates*,s*ids*,s*title)|(?:ids*,s*dates*,s*descriptions*,s*title)|(?:dates*,s*ids*,s*descriptions*,s*title)|(?:titles*,s*ids*,s*descriptions*,s*date)|(?:ids*,s*titles*,s*descriptions*,s*date)|(?:descriptions*,s*titles*,s*ids*,s*date)|(?:titles*,s*descriptions*,s*ids*,s*date)|(?:ids*,s*descriptions*,s*titles*,s*date)|(?:descriptions*,s*ids*,s*titles*,s*date)s*}/)", "commid": "freeCodeCamp_pr_55643"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-51bcc5efa8857f0d5651211ee245bcb79bd0e8cc5266d4e068df8dd9e725a145", "query": "The instructions for step 103 of the spreadsheet project request that a range be created from an array. The say: My solution (listed below) tries to do that by passing in the first number found in nums and the last number found in nums as arguments to the range function. This solution is not accepted and the hint says: On reading this initially I have no clue what this hint is attempting to say. Does it want the range to span from the first number of the array to the second number only? Does it want the range property to define a function that takes two arguments? I'm really not sure what it wants. After some investigations though it seems that this step wanted the range to be between the first and second numbers of the array. I think this confusion could have been easily avoided if the instructions just said that. Change the instructions to say: numsnums No response N/A No response\nOne of the tests is checking , so it's clearly intended to use first and second number.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-4686fe8300776ca49a55dc4db0f9558dd72077f9f4c93a2fb5612abb9ab34fbf", "text": "# --description-- Add a `range` property which generates a range from `nums`. Remember that you have a `range` function you can reuse here. Add a `range` property which generates a range from the first number in `nums` to the second number in `nums`. Remember that you have a `range` function you can reuse here. # --hints--", "commid": "freeCodeCamp_pr_55747"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-d2ee317ccc60294a809a518b2e6dfb985d113573f551aaf8567199e471e68d35", "query": "The code should not be centered in the preview modal. or to on button for certification project with code ! ! 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_", "positive_passages": [{"docid": "doc-en-freeCodeCamp-d86d0d308f5bf86c1441ce209a469926a29c64d6f1e17954153bfb629e0d09d2", "text": " )} {id && ( {`${username}'s Solution to ${ idToNameMap.get(id)?.challengeTitle ?? '' }`} If a large straight is rolled, your `checkForStraights` function should enable the fifth radio button, set the value to `40`, and update the displayed text to `, score = 0`. If a large straight is rolled, your `checkForStraights` function should enable the fifth radio button, set the value to `40`, and update the displayed text to `, score = 40`. ```js resetRadioOptions();", "commid": "freeCodeCamp_pr_55947"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-55e02a4ddabdb0d3d11c965cc479e6e4748e9a816f8473cf78f8024180ac85db", "query": "The challenge or lesson asks the user to provide answer by looking at or by executing the sample code provided in front of him/her but the sample doesn't provide any output in console. When a user try that piece of code he/she should see an output in console. 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\nCan I work on this and just add the myFunction(); at the end?\nhi 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.\nOk, yes, it makes sense to add a function call in the code snippet. I'm opening this up for contributors to work on. This is the piece of code that needs to be changed: 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.\nHi I'd like to work on this issue and submit a pull request to address it. This will be my first issue. I just wanted to know if the video-solution is correct on that page. Just seems to say '2'. Is that intentional or is it missing a zero. Either way I'll add the function call in the code snippet and send a merge req right away. Thanks!\nHey 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.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-f2098f4d39e68d814e59e66d3686a465111b33bd13afffd63c93d0c9c70082fe", "text": "let x = 20; console.log(x); } myFunction(); ``` ## --answers--", "commid": "freeCodeCamp_pr_56458"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-a0576a87f4cf2a28a4895412e10465c1a7b265fb291212aa477a546c7e500330", "query": "I suggest changing the phrase 'template interpolation' to 'template literals,' because are correctly referred to as template literals, which support string interpolation. ! 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_\nit should be \"string interpolation\". Template literals are already mentioned a few words before, it would be extremely redundant. I'm opening this issue for first timers to make the change \"template interpolation\" -\"string interpolation\". This change needs to be done twice in this file: 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.\nSorry for the misunderstanding. I need to change the text from 'template interpolation' -'string interpolation'\nHi, I guess has raised his PR with the needed change. I haven't contributed before to any open source project. I thought this was an easy one to do to get started. Please tell any easy code or non-code contributions to be made. Happy to help.\nI am able to make the required change and happy to start open source contribution with hacktoberfest . Kindly assign this issue to me.\nWe 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.\nThis pull request resolves the issue of incorrect terminology in the JavaScript curriculum where \"template interpolation\" was used. The correct term is \"string interpolation,\" as template literals support string interpolation. I have made the following changes: Replaced \"template interpolation\" with \"string interpolation\" in the two locations within the file. Fix :\nAfter reading the contributing guidelines, I now understand the mistake I made in my PR.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-be80b4c59c6c55b3b2d12ee697b115fecd0669761ac6b35d327e1a8864cece9b", "text": "# --description-- Inside the template literal, create a `div` element with the `id` set to the `index` from the `.forEach()` array method. Remember to use template interpolation to do this. Inside the template literal, create a `div` element with the `id` set to the `index` from the `.forEach()` array method. Remember to use string interpolation to do this. Also, add a `class` of `\"user-card\"` to the `div`.", "commid": "freeCodeCamp_pr_56440"}], "negative_passages": []}
+{"query_id": "q-en-freeCodeCamp-a0576a87f4cf2a28a4895412e10465c1a7b265fb291212aa477a546c7e500330", "query": "I suggest changing the phrase 'template interpolation' to 'template literals,' because are correctly referred to as template literals, which support string interpolation. ! 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_\nit should be \"string interpolation\". Template literals are already mentioned a few words before, it would be extremely redundant. I'm opening this issue for first timers to make the change \"template interpolation\" -\"string interpolation\". This change needs to be done twice in this file: 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.\nSorry for the misunderstanding. I need to change the text from 'template interpolation' -'string interpolation'\nHi, I guess has raised his PR with the needed change. I haven't contributed before to any open source project. I thought this was an easy one to do to get started. Please tell any easy code or non-code contributions to be made. Happy to help.\nI am able to make the required change and happy to start open source contribution with hacktoberfest . Kindly assign this issue to me.\nWe 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.\nThis pull request resolves the issue of incorrect terminology in the JavaScript curriculum where \"template interpolation\" was used. The correct term is \"string interpolation,\" as template literals support string interpolation. I have made the following changes: Replaced \"template interpolation\" with \"string interpolation\" in the two locations within the file. Fix :\nAfter reading the contributing guidelines, I now understand the mistake I made in my PR.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-254df91b4dd83ed27e6822926cd7e9e3e298a5196828676e59bad120d391f5f7", "text": "assert.include(document.querySelector('#author-container > div')?.className, 'user-card'); ``` Your `div` element should have the `id` of `index`. Remember to use template interpolation to set the `id`. Your `div` element should have the `id` of `index`. Remember to use string interpolation to set the `id`. ```js displayAuthors([{author: \"Naomi\"}]);", "commid": "freeCodeCamp_pr_56440"}], "negative_passages": []}