diff --git "a/freeCodeCamp/freeCodeCamp.i2c.dev.jsonl" "b/freeCodeCamp/freeCodeCamp.i2c.dev.jsonl" new file mode 100644--- /dev/null +++ "b/freeCodeCamp/freeCodeCamp.i2c.dev.jsonl" @@ -0,0 +1,248 @@ +{"query_id": "q-en-freeCodeCamp-766774c8c8cf90507ee7b46c9a381a9bf3ac86d981e1d459cd1a1b07b87db18f", "query": "Password form button does not respond to click. Additionally the jumbotron div that is meant to have a white background for the form is too short (only approx 96px and form is 317px).\nLui8906 can you confirm the issue is resolved so we can close it?\nStill when I am at the reset form after recieving the email and following the link, I put in a matching password and the button does not do anything or provide any feedback, are there password requirements? etc..\nOk, thanks. To confirm, this is on password reset, after requesting to reset password? I'll look into it, thanks.\nYep On Tue Jan 13 2015 at 8:57:53 AM Nathan wrote:\nWe've fixed this with our recent pull request.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-a64f1d87dd0b110303cc38a4cc0afcaebaa69c55c2547808ba1ec1b7af68ed08", "text": "{ \"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 }", "commid": "freeCodeCamp_pr_2"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-766774c8c8cf90507ee7b46c9a381a9bf3ac86d981e1d459cd1a1b07b87db18f", "query": "Password form button does not respond to click. Additionally the jumbotron div that is meant to have a white background for the form is too short (only approx 96px and form is 317px).\nLui8906 can you confirm the issue is resolved so we can close it?\nStill when I am at the reset form after recieving the email and following the link, I put in a matching password and the button does not do anything or provide any feedback, are there password requirements? etc..\nOk, thanks. To confirm, this is on password reset, after requesting to reset password? I'll look into it, thanks.\nYep On Tue Jan 13 2015 at 8:57:53 AM Nathan wrote:\nWe've fixed this with our recent pull request.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-78ba46e386c37d6b99f989267de7006cdf68144f63df2a048b70fb9c4444950a", "text": " { /* * 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' } ", "commid": "freeCodeCamp_pr_2"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-766774c8c8cf90507ee7b46c9a381a9bf3ac86d981e1d459cd1a1b07b87db18f", "query": "Password form button does not respond to click. Additionally the jumbotron div that is meant to have a white background for the form is too short (only approx 96px and form is 317px).\nLui8906 can you confirm the issue is resolved so we can close it?\nStill when I am at the reset form after recieving the email and following the link, I put in a matching password and the button does not do anything or provide any feedback, are there password requirements? etc..\nOk, thanks. To confirm, this is on password reset, after requesting to reset password? I'll look into it, thanks.\nYep On Tue Jan 13 2015 at 8:57:53 AM Nathan wrote:\nWe've fixed this with our recent pull request.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-788e85ed25dac66e99641c74afc08c8c83d16f4d17e978eaa550fb8280dde013", "text": "\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.", "commid": "freeCodeCamp_pr_24863"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-766774c8c8cf90507ee7b46c9a381a9bf3ac86d981e1d459cd1a1b07b87db18f", "query": "Password form button does not respond to click. Additionally the jumbotron div that is meant to have a white background for the form is too short (only approx 96px and form is 317px).\nLui8906 can you confirm the issue is resolved so we can close it?\nStill when I am at the reset form after recieving the email and following the link, I put in a matching password and the button does not do anything or provide any feedback, are there password requirements? etc..\nOk, thanks. To confirm, this is on password reset, after requesting to reset password? I'll look into it, thanks.\nYep On Tue Jan 13 2015 at 8:57:53 AM Nathan wrote:\nWe've fixed this with our recent pull request.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-805ad3e384fb06295767ac5bcad30236c3a5d681994725daf735c0f358c9898d", "text": "``` 10198442 ``` No newline at end of file ``` ", "commid": "freeCodeCamp_pr_24863"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-4aacb64252f50e2350cec6f5c0cb2dbde666647300a0c9d0759af62ac31f5963", "query": "On the bonfire page the title should have Learn to code with bonfire | Free Code Camp. Learn to code is our SEO keyword, so we want to implement that when we can.\nI just a title and did a pr instead of an issue :)", "positive_passages": [{"docid": "doc-en-freeCodeCamp-1e5402fbb2e3b148702a2b48e1c016f4826c80acc89e0f53270e482b34026876", "text": "## 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.", "commid": "freeCodeCamp_pr_32801"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-ea3fb5de855a4818d86dd0f503987538e32757a1819d39a0489343f394e4b8d0", "query": "Code expects, in one case, for you to only be pulling the key-value pair and treating it as a new individual object, and in the second case, for you to pull the full object that possesses the key-value pair. And output / tests: Fails assert.deepEqual(where([{ 'a': 1 }, { 'a': 1 }, { 'a': 1, 'b': 2 }], { 'a': 1 }), [{ 'a': 1 }, { 'a': 1 }, { 'a': 1 }], 'should return with multiples');AssertionError:should return with multiples: expected [ { a: 1 }, { a: 1 }, { a: 1, b: 2 } ] to deeply equal [ { a: 1 }, { a: 1 }, { a: 1 } ] But Succeeds assert.deepEqual(where([{ first: 'Romeo', last: 'Montague' }, { first: 'Mercutio', last: null }, { first: 'Tybalt', last: 'Capulet' }], { last: 'Capulet' }), [{ first: 'Tybalt', last: 'Capulet' }], 'should return an array of objects');\nSame problem. Going to fix it now.\nCan you please explain for(var key in source)\nthat may be a better question to ask in gitter. See: and", "positive_passages": [{"docid": "doc-en-freeCodeCamp-814f7ba15377430a6a714618ff600b9c391c1d447d33ae817b3b15800ae3ab16", "text": "\"description\": [ \"Write a function that splits an array (first argument) into groups the length of size (second argument) and returns them as a multidimensional array.\" ], \"challengeSeed\": \"function chunk(arr, size) {n // Break it up.rn return arr;rn}nnchunk((['a', 'b', 'c', 'd'], 2));\", \"challengeSeed\": \"function chunk(arr, size) {n // Break it up.rn return arr;rn}nnchunk(['a', 'b', 'c', 'd'], 2);\", \"tests\": [ \"assert.deepEqual(chunk(['a', 'b', 'c', 'd'], 2), [['a', 'b'], ['c', 'd']], 'should return chunked arrays');\", \"assert.deepEqual(chunk([0, 1, 2, 3, 4, 5], 3), [[0, 1, 2], [3, 4, 5]], 'should return chunked arrays');\",", "commid": "freeCodeCamp_pr_99"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-ea3fb5de855a4818d86dd0f503987538e32757a1819d39a0489343f394e4b8d0", "query": "Code expects, in one case, for you to only be pulling the key-value pair and treating it as a new individual object, and in the second case, for you to pull the full object that possesses the key-value pair. And output / tests: Fails assert.deepEqual(where([{ 'a': 1 }, { 'a': 1 }, { 'a': 1, 'b': 2 }], { 'a': 1 }), [{ 'a': 1 }, { 'a': 1 }, { 'a': 1 }], 'should return with multiples');AssertionError:should return with multiples: expected [ { a: 1 }, { a: 1 }, { a: 1, b: 2 } ] to deeply equal [ { a: 1 }, { a: 1 }, { a: 1 } ] But Succeeds assert.deepEqual(where([{ first: 'Romeo', last: 'Montague' }, { first: 'Mercutio', last: null }, { first: 'Tybalt', last: 'Capulet' }], { last: 'Capulet' }), [{ first: 'Tybalt', last: 'Capulet' }], 'should return an array of objects');\nSame problem. Going to fix it now.\nCan you please explain for(var key in source)\nthat may be a better question to ask in gitter. See: and", "positive_passages": [{"docid": "doc-en-freeCodeCamp-fcdd8dd357796a561a09cba2911fb9842b959bfd796be45756c34f710f9102b7", "text": "\"description\": [ \"Return the remaining elements of an array after chopping off n elements from the head.\" ], \"challengeSeed\": \"function slasher(arr) {n // it doesn't allways pay to be firstrn return arr;rn}nnslasher([1, 2, 3], 2);\", \"challengeSeed\": \"function slasher(arr, howMany) {n // it doesn't allways pay to be firstrn return arr;rn}nnslasher([1, 2, 3], 2);\", \"tests\": [ \"assert.deepEqual(slasher([1, 2, 3], 2), [3], 'should drop the first two elements');\", \"assert.deepEqual(slasher([1, 2, 3], 0), [1, 2, 3], 'should return all elements when n < 1');\",", "commid": "freeCodeCamp_pr_99"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-ea3fb5de855a4818d86dd0f503987538e32757a1819d39a0489343f394e4b8d0", "query": "Code expects, in one case, for you to only be pulling the key-value pair and treating it as a new individual object, and in the second case, for you to pull the full object that possesses the key-value pair. And output / tests: Fails assert.deepEqual(where([{ 'a': 1 }, { 'a': 1 }, { 'a': 1, 'b': 2 }], { 'a': 1 }), [{ 'a': 1 }, { 'a': 1 }, { 'a': 1 }], 'should return with multiples');AssertionError:should return with multiples: expected [ { a: 1 }, { a: 1 }, { a: 1, b: 2 } ] to deeply equal [ { a: 1 }, { a: 1 }, { a: 1 } ] But Succeeds assert.deepEqual(where([{ first: 'Romeo', last: 'Montague' }, { first: 'Mercutio', last: null }, { first: 'Tybalt', last: 'Capulet' }], { last: 'Capulet' }), [{ first: 'Tybalt', last: 'Capulet' }], 'should return an array of objects');\nSame problem. Going to fix it now.\nCan you please explain for(var key in source)\nthat may be a better question to ask in gitter. See: and", "positive_passages": [{"docid": "doc-en-freeCodeCamp-4d0883869b833d48b0ea3655822d5459d2864a6679cf6ffe57479e75d51ab8c4", "text": "] }, { \"_id\":\"a8e512fbe388ac2f9198f0fa\", \"name\":\"Where art thou\", \"difficulty\":\"1.55\", \"description\":[ \"Make a function that looks through a list (first argument) and returns an array of all objects that have equivalent property values (second argument).\" ], \"challengeEntryPoint\":\"where([{ first: 'Romeo', last: 'Montague' }, { first: 'Mercutio', last: null }, { first: 'Tybalt', last: 'Capulet' }], { last: 'Capulet' });\", \"challengeSeed\":\"function where(collection, source) {n var arr = [];rn // What's in a name?rn return arr;rn}\", \"tests\":[ \"assert.deepEqual(where([{ first: 'Romeo', last: 'Montague' }, { first: 'Mercutio', last: null }, { first: 'Tybalt', last: 'Capulet' }], { last: 'Capulet' }), [{ first: 'Tybalt', last: 'Capulet' }], 'should return an array of objects');\", \"assert.deepEqual(where([{ 'a': 1 }, { 'a': 1 }, { 'a': 1, 'b': 2 }], { 'a': 1 }), [{ 'a': 1 }, { 'a': 1 }, { 'a': 1, 'b': 2 }], 'should return with multiples');\" ] }, { \"_id\":\"a39963a4c10bc8b4d4f06d7e\", \"name\":\"Seek and Destroy\", \"difficulty\":\"1.60\",", "commid": "freeCodeCamp_pr_99"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-0d7727238988c46886340e4d839ddcd89fc049a2d5714f5a6db551bb7254a87b", "query": "source: Currently Reads: \"Remove all values (last argument(s)) from an array (first argument) and return as a new array.\" Issue: From my understanding, the user is all the values from an array. However, the information in the parentheses (e.g \"last argument(s) and \"first argument\") seem confusing. Can you please ellaborate further?\nHere's another way of saying it: You will be provided with an array (the first argument in the function) and one or more values (the remaining arguments in the function) that must be removed from that array. If you look at the current tests, the arguments are similar: 1 array and 2 values. The instructions are asking you to remove as many values as are provided, but you will pass the tests if you only account for two (this will most likely be updated in the future). Does that help?\nIn the more information section we should mention about the object of JavaScript, and also perhaps link to the MDN page of it.\nSee updated copy: and pull request", "positive_passages": [{"docid": "doc-en-freeCodeCamp-9f803ed6cd571814a3db9e507b895d2286a78fd747e9605eff1d726019439a61", "text": "\"name\":\"Seek and Destroy\", \"difficulty\":\"1.60\", \"description\":[ \"Remove all values (last argument(s)) from an array (first argument) and return as a new array.\" \"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.\" ], \"challengeSeed\": \"function destroyer(arr) {n // Remove all the valuesrn return arr;rn}nndestroyer([1, 2, 3, 1, 2, 3], 2, 3);\", \"tests\": [ \"assert.deepEqual(destroyer([1, 2, 3, 1, 2, 3], 2, 3), [1, 1], 'should remove correct values from an array');\", \"assert.deepEqual(destroyer([1, 2, 3, 5, 1, 2, 3], 2, 3), [1, 5, 1], 'should remove correct values from an array');\" ], \"MDNlinks\" : [\"Array.filter()\"] \"MDNlinks\" : [\"Arguments object\",\"Array.filter()\"] }, { \"_id\": \"a24c1a4622e3c05097f71d67\",", "commid": "freeCodeCamp_pr_311"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-26a3127407cc9ceefd27002d57ad8b83484ba1ff8665d078434031c6cd1c3729", "query": "Seeing this in production here: solution: Use and/or check for user existence and end early. cc:", "positive_passages": [{"docid": "doc-en-freeCodeCamp-575e98e3a5a7392d6ad4ab666b520d4019cffec4bf24e6d15bc2016906120e8e", "text": "_ = require('lodash'), fs = require('fs'), constantStrings = require('constantStrings.json'), constantStrings = require('./constantStrings.json'), User = require('../models/User'), Challenge = require('./../models/Challenge'), Story = require('./../models/Story'),", "commid": "freeCodeCamp_pr_473"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-26a3127407cc9ceefd27002d57ad8b83484ba1ff8665d078434031c6cd1c3729", "query": "Seeing this in production here: solution: Use and/or check for user existence and end early. cc:", "positive_passages": [{"docid": "doc-en-freeCodeCamp-b6c5145a840ae6d7e4f3fbab113db4eaa91949b0b7e17b688e5bd52631caeec2", "text": " var moment = require('moment'), /* eslint-disable no-catch-shadow, no-unused-vars */ var R = require('ramda'), debug = require('debug')('freecc:cntr:story'), Story = require('./../models/Story'), Comment = require('./../models/Comment'), User = require('./../models/User'), moment = require('moment'), resources = require('./resources'), mongodb = require('mongodb'), nodemailer = require('nodemailer'), sanitizeHtml = require('sanitize-html'), MongoClient = mongodb.MongoClient, resources = require('./resources'), secrets = require('../config/secrets'), Story = require('./../models/Story'), Comment = require('./../models/Comment'), User = require('./../models/User'); nodemailer = require('nodemailer'), sanitizeHtml = require('sanitize-html'); function hotRank(timeValue, rank) { /*", "commid": "freeCodeCamp_pr_473"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-26a3127407cc9ceefd27002d57ad8b83484ba1ff8665d078434031c6cd1c3729", "query": "Seeing this in production here: solution: Use and/or check for user existence and end early. cc:", "positive_passages": [{"docid": "doc-en-freeCodeCamp-90e7307950a3cb00fa167e73b79b03341de7c01606b532178c921ae99288011d", "text": "); story.markModified('rank'); story.save(); User.find({ '_id': story.author.userId }, function(err, user) { User.findOne({'_id': story.author.userId}, function(err, user) { if (err) { return next(err); } user = user.pop(); user.progressTimestamps.push(Date.now() || 0); user.save(function (err) { req.user.save(function (err) { user.save(function (err, user) { req.user.save(function (err, user) { if (err) { return next(err); }", "commid": "freeCodeCamp_pr_473"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-26a3127407cc9ceefd27002d57ad8b83484ba1ff8665d078434031c6cd1c3729", "query": "Seeing this in production here: solution: Use and/or check for user existence and end early. cc:", "positive_passages": [{"docid": "doc-en-freeCodeCamp-a4e06f41b5add118917f29d3e842c6747e1fa34a002422b1bdf06227a5b1dc24", "text": "if (link.search(/^https?:///g) === -1) { link = 'http://' + link; } Story.count( { storyLink: new RegExp('^' + storyLink + '(?: [0-9]+)?$', 'i') }, function (err, storyCount) { if (err) { return res.status(500); } Story.count({ storyLink: new RegExp('^' + storyLink + '(?: [0-9]+)?$', 'i')}, function (err, storyCount) { if (err) { return res.status(500); } // if duplicate storyLink add unique number storyLink = (storyCount === 0) ? storyLink : storyLink + ' ' + storyCount; // if duplicate storyLink add unique number storyLink = (storyCount === 0) ? storyLink : storyLink + ' ' + storyCount; var link = data.link; if (link.search(/^https?:///g) === -1) { link = 'http://' + link; var link = data.link; if (link.search(/^https?:///g) === -1) { link = 'http://' + link; } var story = new Story({ headline: sanitizeHtml(data.headline, { allowedTags: [], allowedAttributes: [] }).replace(/"/g, '\"'), timePosted: Date.now(), link: link, description: sanitizeHtml(data.description, { allowedTags: [], allowedAttributes: [] }).replace(/"/g, '\"'), rank: 1, upVotes: [({ upVotedBy: req.user._id, upVotedByUsername: req.user.profile.username })], author: { picture: req.user.profile.picture, userId: req.user._id, username: req.user.profile.username, email: req.user.email }, comments: [], image: data.image, storyLink: storyLink, metaDescription: data.storyMetaDescription, originalStoryAuthorEmail: req.user.email }); story.save(function (err) { if (err) { return res.status(500); } var story = new Story({ headline: sanitizeHtml(data.headline, { allowedTags: [], allowedAttributes: [] }).replace(/"/g, '\"'), timePosted: Date.now(), link: link, description: sanitizeHtml(data.description, { allowedTags: [], allowedAttributes: [] }).replace(/"/g, '\"'), rank: 1, upVotes: [({ upVotedBy: req.user._id, upVotedByUsername: req.user.profile.username })], author: { picture: req.user.profile.picture, userId: req.user._id, username: req.user.profile.username, email: req.user.email }, comments: [], image: data.image, storyLink: storyLink, metaDescription: data.storyMetaDescription, originalStoryAuthorEmail: req.user.email }); story.save(function (err) { req.user.progressTimestamps.push(Date.now() || 0); req.user.save(function (err, user) { if (err) { return res.status(500); return next(err); } req.user.progressTimestamps.push(Date.now() || 0); req.user.save(function (err) { if (err) { return next(err); } }); res.send(JSON.stringify({ storyLink: story.storyLink.replace(/s/g, '-').toLowerCase() })); }); } ); res.send(JSON.stringify({ storyLink: story.storyLink.replace(/s/g, '-').toLowerCase() })); }); }); }; exports.commentSubmit = function(req, res, next) {", "commid": "freeCodeCamp_pr_473"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-26a3127407cc9ceefd27002d57ad8b83484ba1ff8665d078434031c6cd1c3729", "query": "Seeing this in production here: solution: Use and/or check for user existence and end early. cc:", "positive_passages": [{"docid": "doc-en-freeCodeCamp-88b8c23e74a6912b5fdf114e186fe72079adbc930cd1282a9f1e9ba3a958bfd5", "text": "try { // Based on the context retrieve the parent // object of the comment (Story/Comment) Context.find( { '_id': data.associatedPost }, function (err, associatedContext) { Context.find({'_id': data.associatedPost}, function (err, associatedContext) { if (err) { return next(err); } associatedContext = associatedContext.pop(); if (associatedContext) { associatedContext.comments.push(data._id); associatedContext.save(function (err) { if (err) { return next(err); } res.send(true); }); } // Find the author of the parent object User.findOne({'profile.username': associatedContext.author.username}, function(err, recipient) { if (err) { return next(err); } associatedContext = associatedContext.pop(); if (associatedContext) { associatedContext.comments.push(data._id); associatedContext.save(function (err) { if (err) { return next(err); // If the emails of both authors differ, // only then proceed with email notification if ( typeof data.author !== 'undefined' && data.author.email && typeof recipient !== 'undefined' && recipient.email && (data.author.email !== recipient.email) ) { var transporter = nodemailer.createTransport({ service: 'Mandrill', auth: { user: secrets.mandrill.user, pass: secrets.mandrill.password } res.send(true); }); } // Find the author of the parent object User.findOne( { 'profile.username': associatedContext.author.username }, function(err, recipient) { var mailOptions = { to: recipient.email, from: 'Team@freecodecamp.com', subject: data.author.username + ' replied to your post on Camper News', text: [ 'Just a quick heads-up: ', data.author.username, ' replied to you on Camper News.', 'You can keep this conversation going.', 'Just head back to the discussion here: ', 'http://freecodecamp.com/news/', data.originalStoryLink, '- the Free Code Camp Volunteer Team' ].join('n') }; transporter.sendMail(mailOptions, function (err) { if (err) { return next(err); return err; } // If the emails of both authors differ, // only then proceed with email notification if ( typeof data.author !== 'undefined' && data.author.email && typeof recipient !== 'undefined' && recipient.email && (data.author.email !== recipient.email) ) { var transporter = nodemailer.createTransport({ service: 'Mandrill', auth: { user: secrets.mandrill.user, pass: secrets.mandrill.password } }); var mailOptions = { to: recipient.email, from: 'Team@freecodecamp.com', subject: data.author.username + ' replied to your post on Camper News', text: [ 'Just a quick heads-up: ', data.author.username, ' replied to you on Camper News.', 'You can keep this conversation going.', 'Just head back to the discussion here: ', 'http://freecodecamp.com/news/', data.originalStoryLink, '- the Free Code Camp Volunteer Team' ].join('n') }; transporter.sendMail(mailOptions, function (err) { if (err) { return err; } }); } } ); } ); }); } }); }); } catch (e) { // delete comment return next(err); } });", "commid": "freeCodeCamp_pr_473"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-26a3127407cc9ceefd27002d57ad8b83484ba1ff8665d078434031c6cd1c3729", "query": "Seeing this in production here: solution: Use and/or check for user existence and end early. cc:", "positive_passages": [{"docid": "doc-en-freeCodeCamp-a311801fa9959cbbbfaeefe7afe38d9404cfb5e0d5154a52eefa68bf06f8085a", "text": "return next(err); } req.flash('success', { msg: 'Success! You are logged in.' }); if (/hotStories/.test(req.session.returnTo)) { return res.redirect('../news'); } return res.redirect(req.session.returnTo || '/'); }); })(req, res, next);", "commid": "freeCodeCamp_pr_473"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-9c22f1ffb98d4c73f911e606ab0df8e07c0e1f12ecaa7c57f5c679ca0643020b", "query": "Typo on the first test \"your text field have the property of being required\". Also, the second test passes even if the placeholder text field is empty.\nThanks for the report, the copy has been updated.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-72ea9a3034962ed50bcfd2755c53236fa887bc4add12e036ab6f05b36c139871", "text": "\"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!\",", "commid": "freeCodeCamp_pr_647"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-9c22f1ffb98d4c73f911e606ab0df8e07c0e1f12ecaa7c57f5c679ca0643020b", "query": "Typo on the first test \"your text field have the property of being required\". Also, the second test passes even if the placeholder text field is empty.\nThanks for the report, the copy has been updated.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-64c5f560d071975b5f61d34b43c4d8f01193d3bcec7358c79b73426b42918238", "text": "\"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\": [ \"\",", "commid": "freeCodeCamp_pr_647"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-9c22f1ffb98d4c73f911e606ab0df8e07c0e1f12ecaa7c57f5c679ca0643020b", "query": "Typo on the first test \"your text field have the property of being required\". Also, the second test passes even if the placeholder text field is empty.\nThanks for the report, the copy has been updated.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-11603ee4c0318a5ac05d88d9dec011663abb3067d59221619d0adf34e9b6c8ed", "text": "\"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\": [ \"\",", "commid": "freeCodeCamp_pr_647"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-9c22f1ffb98d4c73f911e606ab0df8e07c0e1f12ecaa7c57f5c679ca0643020b", "query": "Typo on the first test \"your text field have the property of being required\". Also, the second test passes even if the placeholder text field is empty.\nThanks for the report, the copy has been updated.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-15753a1264c6a35e1d4e757d2344583b1ce8349ab49e83bb17dd97f02812fc26", "text": "\"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.\"", "commid": "freeCodeCamp_pr_647"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-9c22f1ffb98d4c73f911e606ab0df8e07c0e1f12ecaa7c57f5c679ca0643020b", "query": "Typo on the first test \"your text field have the property of being required\". Also, the second test passes even if the placeholder text field is empty.\nThanks for the report, the copy has been updated.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-4aa2a01a6b29ba591967452055dd2bce22967259ecaf09e557ea3f198cd01986", "text": "\"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\".')\" ],", "commid": "freeCodeCamp_pr_647"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-1018c09c75f47a29b8a61111d9ec35e0ed0194be7c3da8ad1050b2ae0ac7a50a", "query": "Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. What I see: You can apply a class to an HTML element like this:

h2 element's style tag and write the CSS to make all h2 elements blue.\", \"With CSS, there are hundreds of CSS attributes that you can use to change the way an element looks on a web page.\", \"When you entered <h2 style=\"color: red\">CatPhotoApp<h2>, you were giving that individual h2 element an inline style\", \"When you entered <h2 style=\"color: red\">CatPhotoApp</h2>, you were giving that individual h2 element an inline style\", \"That's one way to add style to an element, but a better way is by using Cascading Style Sheets (CSS).\", \"At the top of your code, create a style tag like this: <style></style>\", \"Inside that style element, you can create a css selector for all h2 elements. For example, if you wanted all h2 elements to be red, your style element would look like this: <style>h2 {color: red;}</style>\",", "commid": "freeCodeCamp_pr_764"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-1018c09c75f47a29b8a61111d9ec35e0ed0194be7c3da8ad1050b2ae0ac7a50a", "query": "Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. What I see: You can apply a class to an HTML element like this:

\", \"You can see that we've created a CSS class called \"blue-text\" within the <style> tag.\", \"You can apply a class to an HTML element like this: <h2 class=\"blue-text\">CatPhotoApp<h2>\", \"You can apply a class to an HTML element like this: <h2 class=\"blue-text\">CatPhotoApp</h2>\", \"Note that in your CSS style element, classes should start with a period. In your HTML elements' class declarations, classes shouldn't start with a period.\", \"Instead of creating a new Style tag, try removing the h2 style declaration from the existing style element, and replace it with the class declaration for \".red-text\".\" ],", "commid": "freeCodeCamp_pr_764"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-1018c09c75f47a29b8a61111d9ec35e0ed0194be7c3da8ad1050b2ae0ac7a50a", "query": "Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. What I see: You can apply a class to an HTML element like this:

img element inside an anchor element with a dead link.\", \"You can make elements into links by wrapping them in an anchor tag.\", \"Wrap your image in an anchor tag. Here's an example: <a href='#'><img src='http://bit.ly/fcc-kittens2'></a>\", \"Wrap your image in an anchor tag. Here's an example: <a href='#'><img src='http://bit.ly/fcc-kittens2'/></a>\", \"Remember to use the hash symbol as your anchor tag's href property in order to turn it into a dead link.\", \"Once you've done this, hover over your image with your cursor. Your cursor's normal pointer should become the link clicking pointer. The photo is now a link.\" ],", "commid": "freeCodeCamp_pr_764"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-1018c09c75f47a29b8a61111d9ec35e0ed0194be7c3da8ad1050b2ae0ac7a50a", "query": "Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. What I see: You can apply a class to an HTML element like this:

<ul> element. Then they contain some number of <li> elements.\", \"For example: <ul><li>milk</li><li>cheese</li><ul> would create a bulleted list of \"milk\" and \"cheese\".\" \"For example: <ul><li>milk</li><li>cheese</li></ul> would create a bulleted list of \"milk\" and \"cheese\".\" ], \"tests\": [ \"assert($('ul').length > 0, 'Create a ul element.')\",", "commid": "freeCodeCamp_pr_764"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-1018c09c75f47a29b8a61111d9ec35e0ed0194be7c3da8ad1050b2ae0ac7a50a", "query": "Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. What I see: You can apply a class to an HTML element like this:

ordered list of the the top 3 things cats hate the most.\", \"HTML has a special element for creating ordered lists, or numbered-style lists.\", \"Ordered lists start with a <ol> element. Then they contain some number of <li> elements.\", \"For example: <ol><li>hydrogen</li><li>helium</li><ol> would create a numbered list of \"hydrogen\" and \"helium\".\" \"For example: <ol><li>hydrogen</li><li>helium</li></ol> would create a numbered list of \"hydrogen\" and \"helium\".\" ], \"tests\": [ \"assert($('ul').length > 0, 'You should have an ul element on your webpage.')\",", "commid": "freeCodeCamp_pr_764"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-234245602436879a1774b3132a430122f0c415f762d64dff829b3ead1b3dde17", "query": "Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. Step : \"Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON() to consume APIs.\" incorrectly to this url: It should link to: Unless that misdirection is meant to be tricky for the student ;)\nThis is a duplicate of\nKind of. This one is referring to a different page (challenge/zipline), but I did notice that all of the Ziplines have the same bug.\nThis was fixed ages ago, right? Please close.\nThis isn't actually fixed. The erroneous link still exists in these ziplines: Maybe it's not an issue because we'll be switching over to the content at soon? But I thought you should know that the issue hasn't actually been fixed yet. Actually, the only reason that it isn't an issue on the beta site is that none of the ziplines seem to link directly to the jquery json page.\nThis was fixed in prior to the branch being available through Now they seem to have changed how the ziplines look, so it wouldn't be an issue regardless. Since all changes seem to happen on the branch before ending up in production, issues that are fixed in should probably be considered fixed, even though it might be better to merge small fixes like this into production at a quicker rate than what is the current reality.\nThanks for the explanation! That makes sense. I'm not privy to staging, so I didn't realize it had been fixed there.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-90eba81c49837951ab5edf319b39c16f23ab61b317f6c3690c1e868ba7a2edf8", "text": "\"Hint: Here's an example call to Twitch.tv's JSON API: https://api.twitch.tv/kraken/streams/freecodecamp.\", \"Hint: The relevant documentation about this API call is here: https://github.com/justintv/Twitch-API/blob/master/v3_resources/streams.md#get-streamschannel.\", \"Hint: Here's an array of the Twitch.tv usernames of people who regularly stream coding: [\"freecodecamp\", \"storbeck\", \"terakilobyte\", \"habathcx\",\"RobotCaleb\",\"comster404\",\"brunofin\",\"thomasballinger\",\"noobs2ninjas\",\"beohoff\"]\", \"Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON()\u2009to consume APIs.\", \"Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON()\u2009to consume APIs.\", \"When you are finished, click the \"I've completed this challenge\" button and include a link to your CodePen. If you pair programmed, you should also include the Free Code Camp username of your pair.\", \"If you'd like immediate feedback on your project, click this button and paste in a link to your CodePen project. Otherwise, we'll review it before you start your nonprofit projects.

Click here then add your link to your tweet's text\" ],", "commid": "freeCodeCamp_pr_937"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-234245602436879a1774b3132a430122f0c415f762d64dff829b3ead1b3dde17", "query": "Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. Step : \"Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON() to consume APIs.\" incorrectly to this url: It should link to: Unless that misdirection is meant to be tricky for the student ;)\nThis is a duplicate of\nKind of. This one is referring to a different page (challenge/zipline), but I did notice that all of the Ziplines have the same bug.\nThis was fixed ages ago, right? Please close.\nThis isn't actually fixed. The erroneous link still exists in these ziplines: Maybe it's not an issue because we'll be switching over to the content at soon? But I thought you should know that the issue hasn't actually been fixed yet. Actually, the only reason that it isn't an issue on the beta site is that none of the ziplines seem to link directly to the jquery json page.\nThis was fixed in prior to the branch being available through Now they seem to have changed how the ziplines look, so it wouldn't be an issue regardless. Since all changes seem to happen on the branch before ending up in production, issues that are fixed in should probably be considered fixed, even though it might be better to merge small fixes like this into production at a quicker rate than what is the current reality.\nThanks for the explanation! That makes sense. I'm not privy to staging, so I didn't realize it had been fixed there.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-46d85b6621f358cd9c2996b9c52935a29e5afc2ac4a2e39aa25c0a71a4f4bb73", "text": "\"Here are the user stories you must enable, and optional bonus user stories:\", \"User Story: As a user, I can click a button to show me a new random quote.\", \"Bonus User Story: As a user, I can press a button to tweet out a quote.\", \"Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON()\u2009to consume APIs.\", \"Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON()\u2009to consume APIs.\", \"When you are finished, click the \"I've completed this challenge\" button and include a link to your CodePen. If you pair programmed, you should also include the Free Code Camp username of your pair.\", \"If you'd like immediate feedback on your project, click this button and paste in a link to your CodePen project. Otherwise, we'll review it before you start your nonprofit projects.

Click here then add your link to your tweet's text\" ],", "commid": "freeCodeCamp_pr_937"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-234245602436879a1774b3132a430122f0c415f762d64dff829b3ead1b3dde17", "query": "Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. Step : \"Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON() to consume APIs.\" incorrectly to this url: It should link to: Unless that misdirection is meant to be tricky for the student ;)\nThis is a duplicate of\nKind of. This one is referring to a different page (challenge/zipline), but I did notice that all of the Ziplines have the same bug.\nThis was fixed ages ago, right? Please close.\nThis isn't actually fixed. The erroneous link still exists in these ziplines: Maybe it's not an issue because we'll be switching over to the content at soon? But I thought you should know that the issue hasn't actually been fixed yet. Actually, the only reason that it isn't an issue on the beta site is that none of the ziplines seem to link directly to the jquery json page.\nThis was fixed in prior to the branch being available through Now they seem to have changed how the ziplines look, so it wouldn't be an issue regardless. Since all changes seem to happen on the branch before ending up in production, issues that are fixed in should probably be considered fixed, even though it might be better to merge small fixes like this into production at a quicker rate than what is the current reality.\nThanks for the explanation! That makes sense. I'm not privy to staging, so I didn't realize it had been fixed there.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-4b4337f17232203cb441522fe80c670ebbe9f523710908f9bc8a0b457a36ff1b", "text": "\"Bonus User Story: As a user, I can see an icon depending on the temperature..\", \"Bonus User Story: As a user, I see a different background image depending on the temperature (e.g. snowy mountain, hot desert).\", \"Bonus User Story: As a user, I can push a button to toggle between Fahrenheit and Celsius.\", \"Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON()\u2009to consume APIs.\", \"Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON()\u2009to consume APIs.\", \"When you are finished, click the \"I've completed this challenge\" button and include a link to your CodePen. If you pair programmed, you should also include the Free Code Camp username of your pair.\", \"If you'd like immediate feedback on your project, click this button and paste in a link to your CodePen project. Otherwise, we'll review it before you start your nonprofit projects.

Click here then add your link to your tweet's text\" ],", "commid": "freeCodeCamp_pr_937"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-234245602436879a1774b3132a430122f0c415f762d64dff829b3ead1b3dde17", "query": "Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. Step : \"Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON() to consume APIs.\" incorrectly to this url: It should link to: Unless that misdirection is meant to be tricky for the student ;)\nThis is a duplicate of\nKind of. This one is referring to a different page (challenge/zipline), but I did notice that all of the Ziplines have the same bug.\nThis was fixed ages ago, right? Please close.\nThis isn't actually fixed. The erroneous link still exists in these ziplines: Maybe it's not an issue because we'll be switching over to the content at soon? But I thought you should know that the issue hasn't actually been fixed yet. Actually, the only reason that it isn't an issue on the beta site is that none of the ziplines seem to link directly to the jquery json page.\nThis was fixed in prior to the branch being available through Now they seem to have changed how the ziplines look, so it wouldn't be an issue regardless. Since all changes seem to happen on the branch before ending up in production, issues that are fixed in should probably be considered fixed, even though it might be better to merge small fixes like this into production at a quicker rate than what is the current reality.\nThanks for the explanation! That makes sense. I'm not privy to staging, so I didn't realize it had been fixed there.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-d2e1516120ac28aee978dfdee95d49a0175502f823f1b4e4e067d958aec66d9b", "text": "\"User Story: As a user, I can click a link to go directly to the post's discussion page.\", \"Bonus User Story: As a user, I can see how many upvotes each story has.\", \"Hint: Here's the Camper News Hot Stories API endpoint: http://www.freecodecamp.com/stories/hotStories.\", \"Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON()\u2009to consume APIs.\", \"Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON()\u2009to consume APIs.\", \"When you are finished, click the \"I've completed this challenge\" button and include a link to your CodePen. If you pair programmed, you should also include the Free Code Camp username of your pair.\", \"If you'd like immediate feedback on your project, click this button and paste in a link to your CodePen project. Otherwise, we'll review it before you start your nonprofit projects.

Click here then add your link to your tweet's text\" ],", "commid": "freeCodeCamp_pr_937"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-234245602436879a1774b3132a430122f0c415f762d64dff829b3ead1b3dde17", "query": "Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. Step : \"Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON() to consume APIs.\" incorrectly to this url: It should link to: Unless that misdirection is meant to be tricky for the student ;)\nThis is a duplicate of\nKind of. This one is referring to a different page (challenge/zipline), but I did notice that all of the Ziplines have the same bug.\nThis was fixed ages ago, right? Please close.\nThis isn't actually fixed. The erroneous link still exists in these ziplines: Maybe it's not an issue because we'll be switching over to the content at soon? But I thought you should know that the issue hasn't actually been fixed yet. Actually, the only reason that it isn't an issue on the beta site is that none of the ziplines seem to link directly to the jquery json page.\nThis was fixed in prior to the branch being available through Now they seem to have changed how the ziplines look, so it wouldn't be an issue regardless. Since all changes seem to happen on the branch before ending up in production, issues that are fixed in should probably be considered fixed, even though it might be better to merge small fixes like this into production at a quicker rate than what is the current reality.\nThanks for the explanation! That makes sense. I'm not privy to staging, so I didn't realize it had been fixed there.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-0211ca8fd62b22bfdc2e31434e01671c4e4d52e5e762e6038f27e4f021ab8cb7", "text": "\"Bonus User Story:As a user, I can click a button to see a random Wikipedia entry.\", \"Bonus User Story:As a user, when I type in the search box, I can see a dropdown menu with autocomplete options for matching Wikipedia entries.\", \"Hint: Here's an entry on using Wikipedia's API: http://www.mediawiki.org/wiki/API:Main_page.\", \"Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON()\u2009to consume APIs.\", \"Remember to use RSAP if you get stuck. Try using jQuery's $.getJSON()\u2009to consume APIs.\", \"When you are finished, click the \"I've completed this challenge\" button and include a link to your CodePen. If you pair programmed, you should also include the Free Code Camp username of your pair.\", \"If you'd like immediate feedback on your project, click this button and paste in a link to your CodePen project. Otherwise, we'll review it before you start your nonprofit projects.

Click here then add your link to your tweet's text\" ],", "commid": "freeCodeCamp_pr_937"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-0b2cd09e6d67a6c9e98135863e0917a65e74bd5f3858de9f43513ced82ba4614", "query": "In this lesson: In the second requirement the is included in the code tag markup which indicates it should be part of the href. It's minor but wrong and confusing for people new to html.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-c054adb2998deb7567614c9999d43445a746dc2b15437b8ac1a897b2791744ed", "text": "], \"tests\": [ \"assert((/cat photos/gi).test($(\"a\").text()), 'Your a element should have the anchor text of \"cat photos\"')\", \"assert(/http://catphotoapp.com/gi.test($(\"a\").attr(\"href\")), 'You need an a element that links to http://catphotoapp.com.')\", \"assert(/http://catphotoapp.com/gi.test($(\"a\").attr(\"href\")), 'You need an a element that links to http://catphotoapp.com.')\", \"assert(editor.match(//g) && editor.match(//g).length === editor.match(/a element has a closing tag.')\" ], \"challengeSeed\": [", "commid": "freeCodeCamp_pr_2419"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-26e9843ce77656b9418b6db7e7ef5d449dcefc989f1ec507c7ff3f89d815b7da", "query": "One of the instructions has the following: start this tutorial by running npm install how-to-npm it says to run the npm tutorial by typing 'npm install how-to-npm but you are actually supposed to just type 'how-to-npm'", "positive_passages": [{"docid": "doc-en-freeCodeCamp-2bccdec5a21f4c9b2d30c18de106a3ebff69b12011c0a4084ae70b2bb52b41ab", "text": "\"Wait for the workspace to finish processing and select it on the left sidebar, below the Create New Workspace button.\", \"Click the \"Start Editing\" button.\", \"In the lower right hand corner you should see a terminal window. In this window use the following commands. You don't need to know what these mean at this point.\", \"Run this command: npm install how-to-npm -g\", \"Now start this tutorial by running npm install how-to-npm@2.0.0.\", \"Install how-to-npm with this command: npm install how-to-npm -g\", \"Now start the tutorial by running how-to-npm.\", \"Note that you can resize the c9.io's windows by dragging their borders.\", \"Make sure that you are always in your project's \"workspace\" directory. You can always navigate back to this directory by running this command: cd ~/workspace.\", \"Note that you can only add dist tags to the specific version numbers published in steps 8 and 10. If you receive a 403 or 404 error, run how-to-npm and try again.\",", "commid": "freeCodeCamp_pr_1172"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-6254ed199e52baac6e46ec24eb6e23b68c95b5bdf886cd14059ed0b9e445e1ee", "query": "Challenge has an issue. In JavaScript whole numbers (called integers) can be easily used to preform mathematical functions <-- Let's try a few of the most commonly used ones now <-- We use - for subtraction <---\nmerged to", "positive_passages": [{"docid": "doc-en-freeCodeCamp-1ea516fca574d774df08fd3cd7024d9c027506ad092d391f85eb90371c20ee43", "text": "\"dashedName\": \"waypoint-add-two-numbers-with-javascript\", \"difficulty\": \"9.98141\", \"description\": [ \"In JavaScript whole numbers (called integers) can be easily used to preform mathematical functions\", \"Let's try a few of the most commonly used ones now\", \"We use +for addition\", \"In JavaScript whole numbers (called integers) can be easily used to perform mathematical functions.\", \"Let's try a few of the most commonly used ones now.\", \"We use +for addition.\", \"Replace the 0with correct number to achieve the result in the comment.\" ], \"tests\": [", "commid": "freeCodeCamp_pr_1692"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-6254ed199e52baac6e46ec24eb6e23b68c95b5bdf886cd14059ed0b9e445e1ee", "query": "Challenge has an issue. In JavaScript whole numbers (called integers) can be easily used to preform mathematical functions <-- Let's try a few of the most commonly used ones now <-- We use - for subtraction <---\nmerged to", "positive_passages": [{"docid": "doc-en-freeCodeCamp-ef4b8e9a1d15441c22eadd99cea17b0f35e773238e351c541d9fb713c850b58e", "text": "\"dashedName\": \"waypoint-subtract-one-number-from-another-with-javascript\", \"difficulty\": \"9.98142\", \"description\": [ \"In JavaScript whole numbers (called integers) can be easily used to preform mathematical functions\", \"Let's try a few of the most commonly used ones now\", \"We use -for subtraction\", \"In JavaScript whole numbers (called integers) can be easily used to perform mathematical functions.\", \"Let's try a few of the most commonly used ones now.\", \"We use -for subtraction.\", \"Replace the 0with correct number to achieve the result in the comment.\" ], \"tests\": [", "commid": "freeCodeCamp_pr_1692"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-6254ed199e52baac6e46ec24eb6e23b68c95b5bdf886cd14059ed0b9e445e1ee", "query": "Challenge has an issue. In JavaScript whole numbers (called integers) can be easily used to preform mathematical functions <-- Let's try a few of the most commonly used ones now <-- We use - for subtraction <---\nmerged to", "positive_passages": [{"docid": "doc-en-freeCodeCamp-fd75e49209914046fcbd6a674bd770d934e627992d9a590dbd60aec4cac132e4", "text": "\"dashedName\": \"waypoint-multiply-two-numbers-with-javascript\", \"difficulty\": \"9.98143\", \"description\": [ \"In JavaScript whole numbers (called integers) can be easily used to preform mathematical functions\", \"Let's try a few of the most commonly used ones now\", \"We use *for multiplication\", \"In JavaScript whole numbers (called integers) can be easily used to perform mathematical functions.\", \"Let's try a few of the most commonly used ones now.\", \"We use *for multiplication.\", \"Replace the 0with correct number to achieve the result in the comment.\" ], \"tests\": [", "commid": "freeCodeCamp_pr_1692"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-6254ed199e52baac6e46ec24eb6e23b68c95b5bdf886cd14059ed0b9e445e1ee", "query": "Challenge has an issue. In JavaScript whole numbers (called integers) can be easily used to preform mathematical functions <-- Let's try a few of the most commonly used ones now <-- We use - for subtraction <---\nmerged to", "positive_passages": [{"docid": "doc-en-freeCodeCamp-b702c408e953e929e4a5b77c89907495383bac6ed0e0e31b32309c2f847558cc", "text": "\"dashedName\": \"waypoint-divide-one-number-by-another-with-javascript\", \"difficulty\": \"9.9814\", \"description\": [ \"In JavaScript whole numbers (called integers) can be easily used to preform mathematical functions\", \"Let's try a few of the most commonly used ones now\", \"We use /for division\", \"In JavaScript whole numbers (called integers) can be easily used to perform mathematical functions.\", \"Let's try a few of the most commonly used ones now.\", \"We use /for division.\", \"Replace the 0with correct number to achieve the result in the comment.\" ], \"tests\": [", "commid": "freeCodeCamp_pr_1692"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-6254ed199e52baac6e46ec24eb6e23b68c95b5bdf886cd14059ed0b9e445e1ee", "query": "Challenge has an issue. In JavaScript whole numbers (called integers) can be easily used to preform mathematical functions <-- Let's try a few of the most commonly used ones now <-- We use - for subtraction <---\nmerged to", "positive_passages": [{"docid": "doc-en-freeCodeCamp-e008cab8cabad8a9d7e355aae27b95fae55ce5ff3b30470c8570570f2c9225e8", "text": "\"dashedName\": \"waypoint-create-decimal-numbers-with-javascript\", \"difficulty\": \"9.9815\", \"description\": [ \"in JavaScript we can can work with decimal numbers\", \"In JavaScript we can can work with decimal numbers.\", \"Let's create a variable myDecimal and give it a decimal value.\" ], \"tests\": [", "commid": "freeCodeCamp_pr_1692"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-6addc42d72e8d06e0fa803c64940a9e980139486935b74f92616ee2668763172", "query": "! Same with the other waypoints that ask for a hex code that includes alpha chars.\nGreen worked fine.. blue has case issue.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-d1931b310166eeac7b3ab052e0740756c868a26bb59a2974d365cb0d2335dd92", "text": "], \"tests\": [ \"assert($(\"body\").css(\"background-color\") === \"rgb(255, 0, 0)\", 'Give your body element the background-color of red.')\", \"assert(editor.match(/#FF0000/g) && editor.match(/#FF0000/g).length > 0, 'Use the hex code for the color red instead of the word red. For example body { color: #FF0000; }.')\" \"assert(editor.match(/#FF0000/ig) && editor.match(/#FF0000/ig).length > 0, 'Use the hex code for the color red instead of the word red. For example body { color: #FF0000; }.')\" ], \"challengeSeed\": [ \"\", \"\", \"

CatPhotoApp

\", \"\", \"\", \"
cat photos\", \"\", \"\", \"\", \"\", \"

Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.

\",", "commid": "freeCodeCamp_pr_3813"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-74694663abf147e7e82b45c8dd0e3c2b7c94debd5506871068314a30fb6f73ae", "query": "Challenge has an issue. User Agent is: \"tails\"
property from myDog.\" ], \"tests\": [ \"assert(myDog.bark === undefined, 'message: Delete the property \"bark\" from myDog.');\" \"assert(myDog.tails === undefined, 'message: Delete the property \"tails\" from myDog.');\" ], \"challengeSeed\": [ \"var ourDog = {\",", "commid": "freeCodeCamp_pr_3967"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-38335cf883a58588fb3aaaf627ee19e76729df427798aa4f4126329fbf655285", "query": "Should be \"become\" I would fix it but I'm not sure where this file is located. !\nclosed. Fixed with", "positive_passages": [{"docid": "doc-en-freeCodeCamp-2f7a4af3748b369d0ac6f643988a5afdd52b41411d2cc97530efc6e3dc078821", "text": "[ \"http://i.imgur.com/EoTfOyC.jpg\", \"An image of some of our campers coding together in Montreal.\", \"Keep practicing coding every day and hanging out with other people who code, and you will becoming a job-ready coder.\", \"Keep practicing coding every day and hanging out with other people who code, and you will become a job-ready coder.\", \"\" ], [", "commid": "freeCodeCamp_pr_4154"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-5683e78bf7bba8e0ae6cb448138bb13344ba877a5de561aebb03c97d2436f205", "query": "[x] Trigger Click Events with jQuery [x] Change Text with Click Events [x] Get JSON with the jQuery getJSON Method [x] Convert JSON Data to HTML [x] Render Images from Data Sources [x] Prefilter JSON [x] Get Geo-location Data\nTrabajando en esta", "positive_passages": [{"docid": "doc-en-freeCodeCamp-0fccf35a056b615a835a6cda83e32e2cdae01e077fc6fee4bc4a725bb6e06414", "text": "\"challenges\": [ { \"id\": \"bb000000000000000000001\", \"title\": \"Trigger Click Events with jQuery\", \"title\": \"Trigger Click Events with jQuery\", \"description\": [ \"In this section, we'll learn how to get data from APIs. APIs - or Application Programming Interfaces - are tools that computers use to communicate with one another.\", \"We'll also learn how to update HTML with the data we get from these APIs using a technology called Ajax.\",", "commid": "freeCodeCamp_pr_4772"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-5683e78bf7bba8e0ae6cb448138bb13344ba877a5de561aebb03c97d2436f205", "query": "[x] Trigger Click Events with jQuery [x] Change Text with Click Events [x] Get JSON with the jQuery getJSON Method [x] Convert JSON Data to HTML [x] Render Images from Data Sources [x] Prefilter JSON [x] Get Geo-location Data\nTrabajando en esta", "positive_passages": [{"docid": "doc-en-freeCodeCamp-bb4554ac95afd64d8c6152637990369f08046a310d8efbcc80b280f7144586bf", "text": "\"\" ], \"challengeType\": 0, \"type\": \"waypoint\" \"type\": \"waypoint\", \"nameEs\": \"Activa eventos de pulsaci\u00f3n con jQuery\", \"descriptionEs\": [ \"En esta secci\u00f3n, vamos a aprender c\u00f3mo obtener datos de las APIs. Las APIs - o interfaces de programaci\u00f3n de aplicaciones - son herramientas que utilizan los computadores para comunicarse entre s\u00ed.\", \"Tambi\u00e9n aprenderemos c\u00f3mo actualizar HTML con los datos que obtenemos de estas API usando una tecnolog\u00eda llamada Ajax.\", \"En primer lugar, vamos a revisar lo que hace la funci\u00f3n $(document).ready(). Esta funci\u00f3n hace que todo el c\u00f3digo dentro de ella se ejecute s\u00f3lo hasta que nuestra p\u00e1gina ha sido cargada.\", \"Hagamos que nuestro bot\u00f3n \"Get message\" cambie el texto del elemento con clase message.\", \"Antes de poder hacer esto, tenemos que implementar un evento de pulsaci\u00f3n dentro de nuestra funci\u00f3n $(document).ready(), a\u00f1adiendo este c\u00f3digo:\", \"$(\"#getMessage\").on(\"click\", function(){\", \"\", \"});\" ] }, { \"id\": \"bc000000000000000000001\", \"title\": \"Change Text with Click Events\", \"title\": \"Change Text with Click Events\", \"description\": [ \"When our click event happens, we can use Ajax to update an HTML element.\", \"Let's make it so that when a user clicks the \"Get Message\" button, we change the text of the element with the class message to say \"Here is the message\".\",", "commid": "freeCodeCamp_pr_4772"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-5683e78bf7bba8e0ae6cb448138bb13344ba877a5de561aebb03c97d2436f205", "query": "[x] Trigger Click Events with jQuery [x] Change Text with Click Events [x] Get JSON with the jQuery getJSON Method [x] Convert JSON Data to HTML [x] Render Images from Data Sources [x] Prefilter JSON [x] Get Geo-location Data\nTrabajando en esta", "positive_passages": [{"docid": "doc-en-freeCodeCamp-327c031172ca46cb36aaeba77fc726adb3b98d5968b433639569b6e055b13270", "text": "\"\" ], \"challengeType\": 0, \"type\": \"waypoint\" \"type\": \"waypoint\", \"nameEs\": \"Cambia texto con eventos de pulsaci\u00f3n\", \"descriptionEs\": [ \"Cuando nuestro evento de pulsaci\u00f3n ocurre, podemos utilizar Ajax para actualizar un elemento HTML.\", \"Hagamos que cuando un usuario pulse el bot\u00f3n \"Get Message\", el texto del elemento con la clase message cambie para decir \"Here is the message\".\", \"Podemos hacerlo a\u00f1adiendo el siguiente c\u00f3digo dentro de nuestro evento de pulsaci\u00f3n:\", \"  $(\".message\").html(\"Here is the message\");\" ] }, { \"id\": \"bb000000000000000000002\",", "commid": "freeCodeCamp_pr_4772"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-5683e78bf7bba8e0ae6cb448138bb13344ba877a5de561aebb03c97d2436f205", "query": "[x] Trigger Click Events with jQuery [x] Change Text with Click Events [x] Get JSON with the jQuery getJSON Method [x] Convert JSON Data to HTML [x] Render Images from Data Sources [x] Prefilter JSON [x] Get Geo-location Data\nTrabajando en esta", "positive_passages": [{"docid": "doc-en-freeCodeCamp-f2a6e82719c76947998deb3d20a40ae249bed70c4e4f512da8fa80f364e20405", "text": "\"\" ], \"challengeType\": 0, \"type\": \"waypoint\" \"type\": \"waypoint\", \"nameEs\": \"Obt\u00e9n JSON con el m\u00e9todo getJSON de jQuery\", \"descriptionEs\": [ \"Tambi\u00e9n puedes solicitar los datos de una fuente externa. Aqu\u00ed es donde entran en juego las API. \", \"Recuerda que las API - o interfaces de programaci\u00f3n de aplicaciones - son herramientas que utilizan los ordenadores para comunicarse entre s\u00ed.\", \"La mayor\u00eda de las API para el web transfieren datos en un formato llamado JSON. JSON significa notaci\u00f3n de objeto JavaScript (JavaScript Object Notation).\", \"T\u00fa ya has usado JSON al crear objetos en JavaScript. JSON no es m\u00e1s que las propiedades del objeto y sus valores actuales, intercalados entre un { y un }. \", \"Estas propiedades y sus valores a menudo se denominan \" pares llave-valor\".\", \"Vamos a obtener el JSON de la API de fotos de gato de Free Code Camp.\", \"Aqu\u00ed est\u00e1 el c\u00f3digo que puedes poner en tu evento de pulsaci\u00f3n para lograrlo:\", \"  $.getJSON(\"/json/cats.json\", function(json) {\", \"    $(\".message\").html(JSON.stringify(json));\", \"  });\", \"Una vez lo a\u00f1adas, pulsa el bot\u00f3n \"Get Message\". Su funci\u00f3n Ajax sustituir\u00e1 el texto \"The message will go here\" con la salida JSON en bruto de la API de fotos de gato de Free Code Camp.\" ] }, { \"id\": \"bb000000000000000000003\", \"title\": \"Convert JSON Data to HTML\", \"title\": \"Convert JSON Data to HTML\", \"description\": [ \"Now that we're getting data from a JSON API, let's display it in our HTML.\", \"We can use the .forEach() method to loop through our data and modify our HTML elements.\",", "commid": "freeCodeCamp_pr_4772"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-5683e78bf7bba8e0ae6cb448138bb13344ba877a5de561aebb03c97d2436f205", "query": "[x] Trigger Click Events with jQuery [x] Change Text with Click Events [x] Get JSON with the jQuery getJSON Method [x] Convert JSON Data to HTML [x] Render Images from Data Sources [x] Prefilter JSON [x] Get Geo-location Data\nTrabajando en esta", "positive_passages": [{"docid": "doc-en-freeCodeCamp-18c652f55536cf76e3e554bf29965da877fa8663d855317da81dce7c32af11b0", "text": "\" \", \"
\", \"
\", \" The message will go here\",\"
\", \" The message will go here\", \"
\", \" \", \"
\", \"
\",", "commid": "freeCodeCamp_pr_4772"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-5683e78bf7bba8e0ae6cb448138bb13344ba877a5de561aebb03c97d2436f205", "query": "[x] Trigger Click Events with jQuery [x] Change Text with Click Events [x] Get JSON with the jQuery getJSON Method [x] Convert JSON Data to HTML [x] Render Images from Data Sources [x] Prefilter JSON [x] Get Geo-location Data\nTrabajando en esta", "positive_passages": [{"docid": "doc-en-freeCodeCamp-e256bd630af8f50565de730331d345e06cdf7611b8390d3a91cfcc28c682832f", "text": "\"
\" ], \"challengeType\": 0, \"type\": \"waypoint\" \"type\": \"waypoint\", \"nameEs\": \"Convierte datos JSON a datos HTML\", \"descriptionEs\": [ \"Ahora que estamos obteniendo datos de una API JSON, mostrem\u00f3slos en nuestro HTML.\", \"Podemos usar el m\u00e9todo .forEach() para recorrer nuestros datos y modificar nuestros elementos HTML.\", \"En primer lugar, vamos a declarar una variable llamada html con var html = \"\";.\", \"Despu\u00e9s, iteremos a trave\u015b de nuestro JSON, a\u00f1adiendo m\u00e1s HTML a esa variable. Cuando se termina el ciclo, vamos a presentarla. \", \"Aqu\u00ed est\u00e1 el c\u00f3digo que hace esto:\", \"json.forEach(function(val) {\", \"  var keys = Object.keys(val);\", \"  html += \"<div class = 'cat'>\";\", \"  keys.forEach(function(key) {\", \"    html += \"<b>\" + key + \"</b>: \" + val[key] + \"<br>\";\", \"  });\", \"  html += \"</div><br>\";\", \"});\" ] }, { \"id\": \"bb000000000000000000004\", \"title\": \"Render Images from Data Sources\", \"title\": \"Render Images from Data Sources\", \"description\": [ \"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.\",", "commid": "freeCodeCamp_pr_4772"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-5683e78bf7bba8e0ae6cb448138bb13344ba877a5de561aebb03c97d2436f205", "query": "[x] Trigger Click Events with jQuery [x] Change Text with Click Events [x] Get JSON with the jQuery getJSON Method [x] Convert JSON Data to HTML [x] Render Images from Data Sources [x] Prefilter JSON [x] Get Geo-location Data\nTrabajando en esta", "positive_passages": [{"docid": "doc-en-freeCodeCamp-1fda8203a0661b0d1f81e9b1e998957b2006500c104cf2cfaecb7db9b454529a", "text": "\"
\" ], \"challengeType\": 0, \"type\": \"waypoint\" \"type\": \"waypoint\", \"nameEs\": \"Presentar im\u00e1genes de fuentes de datos\", \"descriptionEs\": [ \"Tanto en el JSON que recibimos de la API de fotos de gato de Free Code Camp, como en \", \"lo que hemos visto en las dos \u00faltimas lecciones, cada objeto en nuestro vector JSON contiene una llave imageLink con un valor que corresponde a la url de la imagen de un gato.\", \"Cuando estamos recorriendo estos objetos, usemos esta propiedad imageLink para visualizar la imagen en un elemento img.\", \"Aqu\u00ed est\u00e1 el c\u00f3digo que hace esto:\", \"  html += \"<img src = '\" + val.imageLink + \"'>\";\" ] }, { \"id\": \"bb000000000000000000005\", \"title\": \"Prefilter JSON\", \"title\": \"Prefilter JSON\", \"description\": [ \"If we don't want to render every cat photo we get from our Free Code Camp's Cat Photo JSON API, we can pre-filter the json before we loop through it.\", \"Let's filter out the cat who's \"id\" key has a value of 1.\",", "commid": "freeCodeCamp_pr_4772"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-5683e78bf7bba8e0ae6cb448138bb13344ba877a5de561aebb03c97d2436f205", "query": "[x] Trigger Click Events with jQuery [x] Change Text with Click Events [x] Get JSON with the jQuery getJSON Method [x] Convert JSON Data to HTML [x] Render Images from Data Sources [x] Prefilter JSON [x] Get Geo-location Data\nTrabajando en esta", "positive_passages": [{"docid": "doc-en-freeCodeCamp-9ec5efc970042ac9fdaf9e353a849e6ed0f5159bd893d9b42f678d1a6690b7cd", "text": "\"\" ], \"challengeType\": 0, \"type\": \"waypoint\" \"type\": \"waypoint\", \"nameEs\": \"Pre-filtra JSON\", \"descriptionEs\": [ \"Si no queremos presentar cada foto de gato que obtengamos de la API JSON de fotos de gato de Free Code Camp, podemos pre-filtrar el json antes de iterar a trav\u00e9s de este.\", \"Vamos a filtrar el gato cuya llave \"id\" tiene un valor de 1.\", \"Aqu\u00ed est\u00e1 el c\u00f3digo para hacer esto:\", \"json = json.filter(function(val) {\", \"  return(val.id !== 1);\", \"});\" ] }, { \"id\": \"bb000000000000000000006\", \"title\": \"Get Geo-location Data\", \"title\": \"Get Geo-location Data\", \"description\": [ \"Another cool thing we can do is access our user's current location. Every browser has a built in navigator that can give us this information.\", \"The navigator will get our user's current longitude and latitude.\",", "commid": "freeCodeCamp_pr_4772"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-5683e78bf7bba8e0ae6cb448138bb13344ba877a5de561aebb03c97d2436f205", "query": "[x] Trigger Click Events with jQuery [x] Change Text with Click Events [x] Get JSON with the jQuery getJSON Method [x] Convert JSON Data to HTML [x] Render Images from Data Sources [x] Prefilter JSON [x] Get Geo-location Data\nTrabajando en esta", "positive_passages": [{"docid": "doc-en-freeCodeCamp-64ba6aa95277cdebfe8c4feac5456c23af351015023ceb14151ea20c8a2e6fe6", "text": "\"\" ], \"challengeType\": 0, \"type\": \"waypoint\" \"type\": \"waypoint\", \"nameEs\": \"Recibir datos de Geo-localizaci\u00f3n\", \"descriptionEs\": [ \"Otra cosa interesante que podemos hacer es acceder a la ubicaci\u00f3n actual de nuestros usuarios. Todos los navegadores han incorporado un geo-localizador que nos puede dar esta informaci\u00f3n. \", \"El navegador puede obtener la longitud y latitud actual de nuestros usuarios.\", \"Como usuario ver\u00e1s un mensaje para permitir o evitar que el sitio conozca tu ubicaci\u00f3n actual. El desaf\u00edo se puede completar de cualquier manera, siempre y cuando el c\u00f3digo sea correcto. \", \"Si lo permites, ver\u00e1s que el texto en el tel\u00e9fono de la derecha cambiar\u00e1 con tu latitud y longitud\", \"Aqu\u00ed hay un c\u00f3digo que hace esto:\", \"if (navigator.geolocation) {\", \"  navigator.geolocation.getCurrentPosition(function(position) {\", \"    $(\"#data\").html(\"latitude: \" + position.coords.latitude + \"<br>longitude: \" + position.coords.longitude);\", \"  });\", \"}\" ] } ] }", "commid": "freeCodeCamp_pr_4772"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-5248a4d319c25277965ac0979b6acd34fdc6ea52ba87c7513f98339191c884fc", "query": "Challenge [Bonfire: Validate US Telephone Numbers] Apparently the test case \"telephoneCheck(\"555-555-5555\") should return true.\" runs twice.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-92d613b71ddf71dbede440a15d3d6f2d869646dd4ed9f3b6c6fe2373f19744c1", "text": "\"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.');\",", "commid": "freeCodeCamp_pr_4678"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-5248a4d319c25277965ac0979b6acd34fdc6ea52ba87c7513f98339191c884fc", "query": "Challenge [Bonfire: Validate US Telephone Numbers] Apparently the test case \"telephoneCheck(\"555-555-5555\") should return true.\" runs twice.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-6603cbdef13febc30282d43428a6d5dcaffd0fd44a61978dd2f180655d88c062", "text": "\"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\": [", "commid": "freeCodeCamp_pr_4678"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-f2bc12afc5447a4f42dfd972b24f1d74d4fdca7e4eb82ab5cee30e7e33d7de2d", "query": "Challenge has an issue. User Agent is: \" \" \"\" ], \"tail\": [ \"(function(a,b){return \"a = \" + a + \", b = \" + b;})(a,b);\"", "commid": "freeCodeCamp_pr_5692"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-26ab1d47556a33594d28174bfb43f745079396f7072c6f64546826f591095400", "query": "and have text in code tags within a blockquote already. The code tagged strings need to be removed. You can see them because they are highlighted again within the code block. Access MultiDimensional Arrays with Indexes: ! Understand String Immutability: !\nAgreed, these just just be in the block quote.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-5b30a79fcbe90301f02cf6daa1dd2f6fbe9206582707f10262b2aa9bc58a9749", "text": "\"description\": [ \"In Javascript, String values are immutable, which means that they cannot be altered once created.\", \"For example, the following code:\", \"
var myStr = \"Bob\";
myStr[0] = \"J\";
\",
\"
var myStr = \"Bob\";
myStr[0] = \"J\";
\",
\"cannot change the value of myStr to \"Job\", because the contents of myStr cannot be altered. Note that this does not mean that myStr cannot be changed, just that the individual characters of a string literal cannot be changed. The only way to change myStr would be to assign it with a new string, like this:\", \"
var myStr = \"Bob\";
myStr = \"Job\";
\",
\"
var myStr = \"Bob\";
myStr = \"Job\";
\",
\"

Instructions

\", \"Correct the assignment to myStr to achieve the desired effect.\" ],", "commid": "freeCodeCamp_pr_6301"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-26ab1d47556a33594d28174bfb43f745079396f7072c6f64546826f591095400", "query": "and have text in code tags within a blockquote already. The code tagged strings need to be removed. You can see them because they are highlighted again within the code block. Access MultiDimensional Arrays with Indexes: ! Understand String Immutability: !\nAgreed, these just just be in the block quote.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-c0ff368b8441be9d71ca9f7ff1a8d0002cdd3a0cf50fddc1e859073fd24fed4e", "text": "\"description\": [ \"One way to think of a multi-dimensional array, is as an array of arrays. When you use brackets to access your array, the first set of bracket refers to the entries in the outer-most array, and each subsequent level of brackets refers to the next level of entries inside.\", \"Example\", \"
var arr = [
[1,2,3],
[4,5,6],
[7,8,9],
[[10,11,12], 13, 14]
];
arr[0]; // equals [1,2,3]
arr[1][2]; // equals 6
arr[3][0][1]; // equals 11
\",
\"
var arr = [
[1,2,3],
[4,5,6],
[7,8,9],
[[10,11,12], 13, 14]
];
arr[0]; // equals [1,2,3]
arr[1][2]; // equals 6
arr[3][0][1]; // equals 11
\",
\"

Instructions

\", \"Read from myArray using bracket notation so that myData is equal to 8\" ],", "commid": "freeCodeCamp_pr_6301"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-40f4b91c41dcba535750f759c0bb8b898b631e3a74013c0972ed46aef11af3f1", "query": "[x] Learn D3 Challenges\nwhat should we do with these ones? I guess they are not finished, so there's no point in translating that one line, or am I wrong?", "positive_passages": [{"docid": "doc-en-freeCodeCamp-832820be50d8cd052de0bee7a5a90d66eb322b0a8ef2d9959b5e24e0a10934cd", "text": "\"tests\": [], \"type\": \"waypoint\", \"challengeType\": 3, \"nameEs\": \"Crea una aplicaci\u00f3n de votaciones\" \"nameEs\": \"Desafios para aprender D3\", \"descriptionEs\": [] } ] }", "commid": "freeCodeCamp_pr_7166"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-40f4b91c41dcba535750f759c0bb8b898b631e3a74013c0972ed46aef11af3f1", "query": "[x] Learn D3 Challenges\nwhat should we do with these ones? I guess they are not finished, so there's no point in translating that one line, or am I wrong?", "positive_passages": [{"docid": "doc-en-freeCodeCamp-41970edebd08a44def58b5e495298a8ce448d2ca0e73d76ee4f4b7db2e5aa57f", "text": "\"tests\": [], \"type\": \"waypoint\", \"challengeType\": 3, \"nameEs\": \"Crea una aplicaci\u00f3n de votaciones\" \"nameEs\": \"Desafios para aprender React\", \"descriptionEs\": [] } ] }", "commid": "freeCodeCamp_pr_7166"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-40f4b91c41dcba535750f759c0bb8b898b631e3a74013c0972ed46aef11af3f1", "query": "[x] Learn D3 Challenges\nwhat should we do with these ones? I guess they are not finished, so there's no point in translating that one line, or am I wrong?", "positive_passages": [{"docid": "doc-en-freeCodeCamp-9272ab315bd773e08ee2547dee88634645aa12fd24e28cd3b557ad9f585da68d", "text": "\"tests\": [], \"type\": \"waypoint\", \"challengeType\": 3, \"nameEs\": \"Crea una aplicaci\u00f3n de votaciones\" \"nameEs\": \"Desafios para aprender Sass\", \"descriptionEs\": [] } ] }", "commid": "freeCodeCamp_pr_7166"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-9934050814375f1bba1a4233e9bcdf79eb7b2bd74f545dd769c3f49306f9d3e2", "query": "[ ] JavaScript Lingo: MDN and Documentation [ ] JavaScript Lingo: Value Types [ ] JavaScript Lingo: Variables & camelCase [ ] JavaScript Lingo: Arrays & Objects [ ] JavaScript Lingo: Finding and Indexing Data in Arays [ ] JavaScript Lingo: Manipulating Data [ ] JavaScript Lingo: Math [ ] JavaScript Lingo: Loops [ ] JavaScript Lingo: Regular Expressions\nWorking on this one", "positive_passages": [{"docid": "doc-en-freeCodeCamp-06283b3dfc6f24122db6499282b4e744f69f6987ad7eb5ca70f419a8806ea565", "text": "] ], \"type\": \"hike\", \"challengeType\": 6 \"challengeType\": 6, \"nameEs\": \"JavaScript Lingo: MDN y Documentaci\u00f3n\", \"descriptionEs\": [ \"Esta es una introducci\u00f3n b\u00e1sica a MDN y el concepto de la documentaci\u00f3n.\", \"MDN, Mozilla Developer Network, es una fant\u00e1stica colaboraci\u00f3n de fuentes abiertas que documenta no s\u00f3lo JavaScript, sino muchos otros lenguajes y temas. Si no has o\u00eddo hablar de ellos, deber\u00edas darles un vistazo ahora. Personalmente obtengo mucha informaci\u00f3n de developer.mozilla.org/en-US/docs/Web/JavaScript \", \"Cuando digo documentaci\u00f3n, estoy hablando acerca de la informaci\u00f3n que se proporciona sobre el producto a sus usuarios. La documentaci\u00f3n de MDN no necesariamente est\u00e1 escrita por la gente detr\u00e1s de JS. Brendan Eich cre\u00f3 JS en 1995, pero hoy en d\u00eda el proyecto contin\u00faa creciendo gracias a un esfuerzo comunitario. \", \"A medida que contin\u00faes aprendiendo JavaScript, jQuery, y pr\u00e1cticamente cualquier otro lenguaje o servicio para desarrollo o programaci\u00f3n, la documentaci\u00f3n ser\u00e1 tu amiga.\", \"Cuanto m\u00e1s r\u00e1pido te sientas c\u00f3modo leyendo y referenciando documentaci\u00f3n, m\u00e1s r\u00e1pido crecer\u00e1s como desarrollador.\", \"Estos v\u00eddeos no van a ense\u00f1arte JavaScript - te presentan t\u00e9rminos y conceptos que ser\u00e1n valiosos a medida que contin\u00faes practicando y aprendiendo.\" ] }, { \"id\": \"56b15f15632298c12f31518d\",", "commid": "freeCodeCamp_pr_7228"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-9934050814375f1bba1a4233e9bcdf79eb7b2bd74f545dd769c3f49306f9d3e2", "query": "[ ] JavaScript Lingo: MDN and Documentation [ ] JavaScript Lingo: Value Types [ ] JavaScript Lingo: Variables & camelCase [ ] JavaScript Lingo: Arrays & Objects [ ] JavaScript Lingo: Finding and Indexing Data in Arays [ ] JavaScript Lingo: Manipulating Data [ ] JavaScript Lingo: Math [ ] JavaScript Lingo: Loops [ ] JavaScript Lingo: Regular Expressions\nWorking on this one", "positive_passages": [{"docid": "doc-en-freeCodeCamp-313398a55431ea07bd4078ac5d8fa7b8617f92ea3806eacf3a4aaa8056616fe3", "text": "] ], \"type\": \"hike\", \"challengeType\": 6 \"challengeType\": 6, \"nameEs\": \"JavaScript Lingo: Tipos de valores\", \"descriptionEs\": [ \"Aprende sobre los tres tipos m\u00e1s b\u00e1sicos de valores: Booleanos, cadenas y n\u00fameros\", \"Un booleano es un valor true (verdadero) o false (falso). Estas palabras son especiales y reservadas. No puedes nombrar a una variable como \"true\", porque esa palabra es ya universal como un valor l\u00f3gico (as\u00ed como lo es \"false\"). \", \"Una cadena es un conjunto de caracteres que se establecen entre ap\u00f3strofes (') o entre comillas (\"). Una cadena puede ser \"true\", siempre y cuando sea con comillas o con ap\u00f3strofes. \", \"Los n\u00fameros se explican por s\u00ed mismos - un n\u00famero es un valor que se compone s\u00f3lo de d\u00edgitos, aunque tambi\u00e9n puede contener un decimal o un signo negativo.\" ] }, { \"id\": \"56b15f15632298c12f31518b\",", "commid": "freeCodeCamp_pr_7228"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-9934050814375f1bba1a4233e9bcdf79eb7b2bd74f545dd769c3f49306f9d3e2", "query": "[ ] JavaScript Lingo: MDN and Documentation [ ] JavaScript Lingo: Value Types [ ] JavaScript Lingo: Variables & camelCase [ ] JavaScript Lingo: Arrays & Objects [ ] JavaScript Lingo: Finding and Indexing Data in Arays [ ] JavaScript Lingo: Manipulating Data [ ] JavaScript Lingo: Math [ ] JavaScript Lingo: Loops [ ] JavaScript Lingo: Regular Expressions\nWorking on this one", "positive_passages": [{"docid": "doc-en-freeCodeCamp-1c3cbc498bf7d4ae3acf527dd2fbd661ba6c360a1bc78ca3673a86a27a9f29c4", "text": "] ], \"type\": \"hike\", \"challengeType\": 6 \"challengeType\": 6, \"nameEs\": \"JavaScript Lingo: Variables y capitalizaci\u00f3nCamello\", \"descriptionEs\": [ \"Vamos a cubrir lo que constituye una variable, y el razonamiento detr\u00e1s de la capitalizaci\u00f3nCamello (camelCase).\", \"Una variable, tambi\u00e9n conocida como una 'var', es el nombre o el espacio para un booleano, una cadena, un n\u00famero, u otra pieza de informaci\u00f3n est\u00e1tica.\", \"Puedes usar las Herramientas de desarrollo de Google para inspeccionar la p\u00e1gina principal de FreeCodeCamp y buscar algunas variables.\", \"Tu 'declaras' variables por primera vez con var en frente de ella, pero despu\u00e9s puedes referenciarla m\u00e1s adelante en tu programa.\", \"capitalizaci\u00f3nCamello es una forma en la que juntas varias palabras y a\u00fan as\u00ed las mantienes legibles. La primera letra de la primera palabra va en min\u00fasculas al igual que el resto de la primera palabra, pero la primera letra de cada palabra que siga se escribe en may\u00fasculas. No hay espacios. Ejemplos: brianaAmaSusMascotas, laMejorComidaEsElQueso, y valeLaPenaAprenderProgramacion.\", \"Al asignar un nombre de variable, usa capitalizaci\u00f3nCamello. Adem\u00e1s, trata de mantener los nombres descriptivos y cortos para que los dem\u00e1s (\u00a1e incluso tu!) puedan entender a lo que se refiere la variable simplemente por el nombre.\" ] }, { \"id\": \"56b15f15632298c12f31518a\",", "commid": "freeCodeCamp_pr_7228"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-9934050814375f1bba1a4233e9bcdf79eb7b2bd74f545dd769c3f49306f9d3e2", "query": "[ ] JavaScript Lingo: MDN and Documentation [ ] JavaScript Lingo: Value Types [ ] JavaScript Lingo: Variables & camelCase [ ] JavaScript Lingo: Arrays & Objects [ ] JavaScript Lingo: Finding and Indexing Data in Arays [ ] JavaScript Lingo: Manipulating Data [ ] JavaScript Lingo: Math [ ] JavaScript Lingo: Loops [ ] JavaScript Lingo: Regular Expressions\nWorking on this one", "positive_passages": [{"docid": "doc-en-freeCodeCamp-893da5d53396e97bb82003655d88035d89d36094a705162d23a9c872c78f24a8", "text": "] ], \"type\": \"hike\", \"challengeType\": 6 \"challengeType\": 6, \"nameEs\": \"JavaScript Lingo: Vectores y objetos\", \"descriptionEs\": [ \"Si desea almacenar m\u00e1s de una pieza de informaci\u00f3n en una variable, puedes hacerlo mediante la creaci\u00f3n de un vector o de un objeto.\", \"** Exenci\u00f3n de responsabilidad: Los objetos de JS no son exactamente lo mismo que los objetos en otros lenguajes. Vamos a discutir aqu\u00ed objetos con respecto a JS. \", \"Los vectores son conjuntos de valores entre [corchetes]. Los valores se separan con comas. Cada valor puede ser booleano, cadena, n\u00famero, o incluso otro vector. A esto \u00faltimo le llamamos vector anidado. A un vector compuesto por vectores de la misma longitud le llamamos matriz. \", \"Los objetos son un tipo de datos que pueden verse o comportarse como un vector, en la medida que se trata de m\u00e1s valores almacenados en una variable de una manera organizada. Oir\u00e1s que un objeto se puede representar en JSON, y con frecuencia cuando haces llamadas a la API de algunos sitios (para obtener informaci\u00f3n que necesitas mostrar en tu propia p\u00e1gina) est\u00e1 ser\u00e1 devuelta en JSON. \", \"Un ejemplo de la notaci\u00f3n de objetos es: var obj = { 'nombre': 'Briana', 'comida': 'queso', 'perro': 'Maurice'};\", \"F\u00edjate que un objeto se encierra entre llaves { ... }, que los diferentes atributos se separan por comas, que cada atributo consta de una palabra llave y de un valor. Por ejemplo son llaves 'nombre', 'comida' y 'perro' y sus respectivos valores son 'Briana', 'queso' y 'Maurice'. En este ejmplo todos los valores fueron cadenas, aunque tambi\u00e9n son v\u00e1lidos booleanos, n\u00fameros y otros tipos de datos.\" ] }, { \"id\": \"56b15f15632298c12f315189\",", "commid": "freeCodeCamp_pr_7228"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-9934050814375f1bba1a4233e9bcdf79eb7b2bd74f545dd769c3f49306f9d3e2", "query": "[ ] JavaScript Lingo: MDN and Documentation [ ] JavaScript Lingo: Value Types [ ] JavaScript Lingo: Variables & camelCase [ ] JavaScript Lingo: Arrays & Objects [ ] JavaScript Lingo: Finding and Indexing Data in Arays [ ] JavaScript Lingo: Manipulating Data [ ] JavaScript Lingo: Math [ ] JavaScript Lingo: Loops [ ] JavaScript Lingo: Regular Expressions\nWorking on this one", "positive_passages": [{"docid": "doc-en-freeCodeCamp-57c5e0638fc0c1e2929b6e279699b086e3cc8e6e05e3aade064f53d3e311aa77", "text": "] ], \"type\": \"hike\", \"challengeType\": 6 \"challengeType\": 6, \"nameEs\": \"JavaScript Lingo: Encontrando e indexando valores en vectores\", \"descriptionEs\": [ \"Hay muchas razones por las que puedes necesitar acceder a una determinada pieza de informaci\u00f3n al interior de un conjunto m\u00e1s amplio, lo cual haces referenciando su \u00edndice.\", \"No vamos a entrar en la sintaxis, pero debes saber que el primer elemento en un vector tiene en realidad el \u00edndice 0.\", \"Esto tambi\u00e9n aplica para cadenas y objetos. Todos estos \u00edndices comienzan en 0, por lo que si en tu programa usas miVector[2], realmente vas a obtener la tercera pieza de informaci\u00f3n del vector miVector.\" ] }, { \"id\": \"56b15f15632298c12f315188\",", "commid": "freeCodeCamp_pr_7228"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-9934050814375f1bba1a4233e9bcdf79eb7b2bd74f545dd769c3f49306f9d3e2", "query": "[ ] JavaScript Lingo: MDN and Documentation [ ] JavaScript Lingo: Value Types [ ] JavaScript Lingo: Variables & camelCase [ ] JavaScript Lingo: Arrays & Objects [ ] JavaScript Lingo: Finding and Indexing Data in Arays [ ] JavaScript Lingo: Manipulating Data [ ] JavaScript Lingo: Math [ ] JavaScript Lingo: Loops [ ] JavaScript Lingo: Regular Expressions\nWorking on this one", "positive_passages": [{"docid": "doc-en-freeCodeCamp-901c9ba944d1ff4d4cdd3f56455445e2842c37fca2c1d8939ebbe93eafe88a46", "text": "] ], \"type\": \"hike\", \"challengeType\": 6 \"challengeType\": 6, \"nameEs\": \"JavaScript Lingo: Manipulaci\u00f3n de los datos\", \"descriptionEs\": [ \"M\u00e9todos y funciones son formas con las que puedes modificar variables u otros conjuntos de informaci\u00f3n.\", \"Los m\u00e9todos est\u00e1n integrados en JavaScript, y te familiarizar\u00e1s con estos cuando realices los desaf\u00edos sobre algoritmos.\", \"Me gustar\u00eda sugerirte dar un vistazo a MDN (Mozilla Developer Network que discutimos en el primer video) para que te familiarices con la cantidad y el potencial general de los m\u00e9todos que existen. developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Methods_Index\", \"Los ejemplos incluyen .split (' '), que convertir\u00e1 una cadena en un vector y puede hacerlo de muchas maneras diferentes. Los m\u00e9todos son de gran alcance - muchas veces cuando quieres que tu programa haga algo, ya habr\u00e1 un m\u00e9todo para eso.\", \"Las funciones, al igual que las variables, son algo que tu defines y creas.\", \"Durante tu pr\u00e1ctica con algoritmos en FreeCodeCamp, vas a crear funciones que reciben una determinada pieza de informaci\u00f3n y la manipulan de la forma que elijas.\", \"Vas a estar m\u00e1s familiarizado con la sintaxis, pero por ahora, s\u00f3lo recuerda que con los m\u00e9todos y funciones puedes hacer casi cualquier cosa con tu c\u00f3digo.\" ] }, { \"id\": \"56b15f15632298c12f315187\",", "commid": "freeCodeCamp_pr_7228"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-9934050814375f1bba1a4233e9bcdf79eb7b2bd74f545dd769c3f49306f9d3e2", "query": "[ ] JavaScript Lingo: MDN and Documentation [ ] JavaScript Lingo: Value Types [ ] JavaScript Lingo: Variables & camelCase [ ] JavaScript Lingo: Arrays & Objects [ ] JavaScript Lingo: Finding and Indexing Data in Arays [ ] JavaScript Lingo: Manipulating Data [ ] JavaScript Lingo: Math [ ] JavaScript Lingo: Loops [ ] JavaScript Lingo: Regular Expressions\nWorking on this one", "positive_passages": [{"docid": "doc-en-freeCodeCamp-3ca895bc72a6121b323ce1394fd66059b886c57e0a58b1f1d877e16fd642d628", "text": "] ], \"type\": \"hike\", \"challengeType\": 6 \"challengeType\": 6, \"nameEs\": \"JavaScript Lingo: Matem\u00e1ticas\", \"descriptionEs\": [ \"Hay un objeto est\u00e1tico de nombre 'Math' en JS con muchos propiedades y m\u00e9todos incluidos.\", \"Vas a querer investigar m\u00e1s de este cuando manipules n\u00fameros. Consulta la documentaci\u00f3n de MDN antes de escribir tus propias funciones, pues ya podr\u00edan estar definidas all\u00ed. \", \"Los ejemplos incluyen Math.random() que devolver\u00e1 un n\u00famero aleatorio en un rango y Math.round() que redondear\u00e1 el n\u00famero decimal que reciba al entero m\u00e1s cercano.\", \"Yo utilic\u00e9 Math.random() cuando constru\u00ed el generador de citas aleatorias como proyecto de desarrollo de interfaces en FreeCodeCamp.\", \"Cuando trabajes con n\u00fameros, tambi\u00e9n debes estar consciente de que JS tiene un atributo interesante llamado 'formato de coma flotante'.\", \"Dependiendo de la cantidad de n\u00fameros, su tama\u00f1o y la cantidad de c\u00e1lculos, JS puede devolver un n\u00famero que es inexacto en 0,00004.\", \"Hay maneras de evitar esto, y en general no plantean problemas, pero es algo que debes tener en cuenta si te encuentras con algunos problemas que parecen no tienen sentido.\" ] }, { \"id\": \"56b15f15632298c12f315186\",", "commid": "freeCodeCamp_pr_7228"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-9934050814375f1bba1a4233e9bcdf79eb7b2bd74f545dd769c3f49306f9d3e2", "query": "[ ] JavaScript Lingo: MDN and Documentation [ ] JavaScript Lingo: Value Types [ ] JavaScript Lingo: Variables & camelCase [ ] JavaScript Lingo: Arrays & Objects [ ] JavaScript Lingo: Finding and Indexing Data in Arays [ ] JavaScript Lingo: Manipulating Data [ ] JavaScript Lingo: Math [ ] JavaScript Lingo: Loops [ ] JavaScript Lingo: Regular Expressions\nWorking on this one", "positive_passages": [{"docid": "doc-en-freeCodeCamp-9630901adcbfd2eb9b5fc044738b97809554ab4e29bd9d679defa62a0abf0fc2", "text": "] ], \"type\": \"hike\", \"challengeType\": 6 \"challengeType\": 6, \"nameEs\": \"JavaScript Lingo: Ciclos\", \"descriptionEs\": [ \"Si hay un conjunto de valores (vamos a utilizar un vector en este ejemplo, pero no tiene que ser as\u00ed) y deseas realizar la misma operaci\u00f3n a cada valor del conjunto, puedes usar algo llamado ciclo. \", \"Los ciclos tienen una sintaxis compleja a la que inicialmente es dif\u00edcil acostumbrarse, pero una vez que la entiendas, son de gran utilidad. Yo us\u00e9 ciclos en muchas de mis soluciones. \", \"No es necesario que entiendas todo aqu\u00ed - s\u00f3lo que sepas que existen ciclos cuando necesitas recorrer un conjunto de datos y que pueden reducir la cantidad de c\u00f3digo que debes escribir.\" ] }, { \"id\": \"56b15f15632298c12f315185\",", "commid": "freeCodeCamp_pr_7228"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-9934050814375f1bba1a4233e9bcdf79eb7b2bd74f545dd769c3f49306f9d3e2", "query": "[ ] JavaScript Lingo: MDN and Documentation [ ] JavaScript Lingo: Value Types [ ] JavaScript Lingo: Variables & camelCase [ ] JavaScript Lingo: Arrays & Objects [ ] JavaScript Lingo: Finding and Indexing Data in Arays [ ] JavaScript Lingo: Manipulating Data [ ] JavaScript Lingo: Math [ ] JavaScript Lingo: Loops [ ] JavaScript Lingo: Regular Expressions\nWorking on this one", "positive_passages": [{"docid": "doc-en-freeCodeCamp-aca49f4599327da818c3bc59dd4dc20b60b9614483a79f8daf01784c06715906", "text": "] ], \"type\": \"hike\", \"challengeType\": 6 \"challengeType\": 6, \"id\": \"56b15f15632298c12f315185\", \"nameEs\": \"JavaScript Lingo: expresiones regulares (RegExp)\", \"descriptionEs\": [ \"Las RegExp no siguen el formato del resto de JS, y pueden requerir una curva de aprendizaje.\", \"Las epresiones regulares (abreviado RegExp) tambi\u00e9n pueden ser una herramienta muy \u00fatil y eficiente.\", \"Usando RegExp, puedes hacer coincidir, reemplazar, buscar y dividir una cadena, uno de los tipos m\u00e1s dif\u00edciles de manipular.\", \"Al igual que con todos los otros videos, no vamos a entrar en detalles, pero quiero mostrar algunos ejemplos donde las RegExp son \u00fatiles.\", \"Si quisieras crear una p\u00e1gina de registro que verifique las contrase\u00f1as para que contengan al menos un n\u00famero y una letra may\u00fascula, puedes usar expresiones regulares.\", \"Si quieres asegurarte de que las fechas introducidas en una p\u00e1gina sean todas fechas v\u00e1lidas en el futuro, puedes usar RegExp.\", \"Si bien hay infinitas maneras de utilizar RegExp, muchas de estas incluyen validaciones o ediciones autom\u00e1ticas de informaci\u00f3n.\" ] } ] }", "commid": "freeCodeCamp_pr_7228"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-0db7f9640729f6ed059bec883a70a1a1556e2e838907b749830feb8afce303e4", "query": "Challenge has an issue. User Agent is: \"Write a function that takes two or more arrays and returns a new array of unique values sorted in order.\" \"Write a function that takes two or more arrays and returns a new array of unique values in the order of the original provided arrays.\", \"The unique numbers should be sorted by their original order, but the final array should not be sorted in numerical order.\", \"Check the assertion tests for examples.\" ], \"challengeSeed\": \"function unite(arr) {n return arr;rn}nnunite([1, 2, 3], [5, 2, 1, 4], [2, 1]);\", \"tests\": [", "commid": "freeCodeCamp_pr_100"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-0db7f9640729f6ed059bec883a70a1a1556e2e838907b749830feb8afce303e4", "query": "Challenge has an issue. User Agent is: ] No newline at end of file ] ", "commid": "freeCodeCamp_pr_100"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-f535349981fb401a764fc6ee4708a6d272eed75f4ab42f7fff2ffc5bea95bacf", "query": "My challenge is makes sure all p elements have closing tag\nThanks for reporting this. But your code is incorrect. GitHub Issues are for reporting bugs on the website only. Please use the for getting challenge related help. Happy Coding.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-089373e27da324936089b8a63a9d6d8b73ad51a2eeec19c909d89ef8d2439e3f", "text": "var isCompletedDate = Math.round(+new Date() / 1000); var bonfireHash = req.body.bonfireInfo.bonfireHash; var isSolution = req.body.bonfireInfo.solution; // TODO debug(isCompletedWith, 'Is completed with'); if (isCompletedWith) { var paired = User.find({\"profile.username\": isCompletedWith}).limit(1);", "commid": "freeCodeCamp_pr_55"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-f535349981fb401a764fc6ee4708a6d272eed75f4ab42f7fff2ffc5bea95bacf", "query": "My challenge is makes sure all p elements have closing tag\nThanks for reporting this. But your code is incorrect. GitHub Issues are for reporting bugs on the website only. Please use the for getting challenge related help. Happy Coding.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-f7074bae61dcd81de65837566cf89d83674231ca217d856ad305b1a7d1cc69c7", "text": "throw err; } if (user && paired) { res.redirect('/bonfires'); res.send(true); } }) }); } }) } else { req.user.completedBonfires.push({ _id: bonfireHash, completedWith: null,", "commid": "freeCodeCamp_pr_55"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-f535349981fb401a764fc6ee4708a6d272eed75f4ab42f7fff2ffc5bea95bacf", "query": "My challenge is makes sure all p elements have closing tag\nThanks for reporting this. But your code is incorrect. GitHub Issues are for reporting bugs on the website only. Please use the for getting challenge related help. Happy Coding.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-1aa605eb80df2e320f6bdcef16b66b99449cfa6f473136fc8c6ad4df6a5c13d1", "text": "}) var index = req.user.uncompletedBonfires.indexOf(bonfireHash); if (index > -1) { req.user.uncompletedBonfires.splice(index,1) } req.user.save(function(err, user) { if (err) { throw err; } if (user) { res.redirect('/bonfires'); debug('Saving user'); res.send(true) } }); } }); // Unique Check API route", "commid": "freeCodeCamp_pr_55"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-f535349981fb401a764fc6ee4708a6d272eed75f4ab42f7fff2ffc5bea95bacf", "query": "My challenge is makes sure all p elements have closing tag\nThanks for reporting this. But your code is incorrect. GitHub Issues are for reporting bugs on the website only. Please use the for getting challenge related help. Happy Coding.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-f13680d0435cbf36b53065c1665d2b3993eb4fc29c4c9b491948f6b895a9b5b6", "text": "return res.redirect('bonfires/meet-bonfire'); } var currentTime = parseInt(+new Date() / 1000); if (currentTime - req.user.lastContentSync > 86400) { if (currentTime - req.user.lastContentSync > 10) { req.user.lastContentSync = currentTime; var completed = req.user.completedBonfires.map(function (elem) { return elem._id;", "commid": "freeCodeCamp_pr_55"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-f535349981fb401a764fc6ee4708a6d272eed75f4ab42f7fff2ffc5bea95bacf", "query": "My challenge is makes sure all p elements have closing tag\nThanks for reporting this. But your code is incorrect. GitHub Issues are for reporting bugs on the website only. Please use the for getting challenge related help. Happy Coding.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-d326d6e516d4f955644f304ed99477c67416e8e0bcf19d62678c0f75e9848582", "text": "} } }); } if (allTestsPassed) { allTestsPassed = false; showCompletion(); if (allTestsPassed) { allTestsPassed = false; showCompletion(); } } };", "commid": "freeCodeCamp_pr_55"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-f535349981fb401a764fc6ee4708a6d272eed75f4ab42f7fff2ffc5bea95bacf", "query": "My challenge is makes sure all p elements have closing tag\nThanks for reporting this. But your code is incorrect. GitHub Issues are for reporting bugs on the website only. Please use the for getting challenge related help. Happy Coding.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-34ba44f798213a4465db989b4db08a15c66d640af01449fe72559acadc768bd2", "text": "$('#complete-bonfire-dialog').modal('show'); // Only post to server if there is an authenticated user if ($('.signup-btn-nav').length < 1) { $.ajax({ type: 'POST', data: { $.post( '/completed-bonfire', { bonfireInfo: { completedWith : didCompleteWith, solution: bonfireSolution, bonfireHash: thisBonfireHash } }, url: '/completed-bonfire/' }); function(res) { if (res) { window.location.href = 'http://localhost:3001/bonfires' } }) } } $('.next-bonfire-button').on('click', function() { var bonfireSolution = myCodeMirror.getValue(); var thisBonfireHash = passedBonfireHash || null; var didCompleteWith = $('#completed-with').val() || null; completedBonfire(didCompleteWith, bonfireSolution, thisBonfireHash); }); $('.all-challenges').on('click', function() { $('#all-challenges-dialog').modal('show'); });", "commid": "freeCodeCamp_pr_55"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-f535349981fb401a764fc6ee4708a6d272eed75f4ab42f7fff2ffc5bea95bacf", "query": "My challenge is makes sure all p elements have closing tag\nThanks for reporting this. But your code is incorrect. GitHub Issues are for reporting bugs on the website only. Please use the for getting challenge related help. Happy Coding.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-b99abe611b9ae009172884f0e6499581d69957110f62eda1ff6d4511423202da", "text": "}); $('.next-bonfire-button').on('click', function() { var bonfireSolution = myCodeMirror.getValue(); var thisBonfireHash = passedBonfireHash || null; var didCompleteWith = $('#completed-with').val() || null; completedBonfire(didCompleteWith, bonfireSolution, thisBonfireHash); window.setTimeout(function() { // TODO window.location = '/bonfires'; }, 100); }); // Bonfire instructions functions $('#more-info').on('click', function() {", "commid": "freeCodeCamp_pr_55"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-1b8336b11f6a1c9e8d15f9e8fb2ec9f30499c6c7101d2aa2039600fa29b329b7", "query": "Challenge has an issue. User Agent is: position property is absolute, which locks the element in place relative to its parent container. Unlike the relative position, this removes the element from the normal flow of the document, so surrounding items ignore it. The CSS offset properties (top or bottom and left or right) are used to adjust the position.\", \"One nuance with absolute positioning is that it will be locked relative to its closest positioned ancestor. If you forget to add a position rule to the parent item, (this is typically done using position: relative;), the browser will keep looking up the chain and ultimately default to the body tag.\", \"
\", \"Lock the #searchbar element to the top-right of its section parent by declaring its position as absolute. Give it top and right offsets of 0.5 pixels each.\" \"Lock the #searchbar element to the top-right of its section parent by declaring its position as absolute. Give it top and right offsets of 50 pixels each.\" ], \"challengeSeed\": [ \" ``` ", "commid": "freeCodeCamp_pr_37756"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-3aa0738c73a98966c6ec81758d81218e55f1f56bfe17649aced191faba61b805", "query": "from its english version at from its english version at from its english version at from its english version at from its english version at from its english version at When you make a PR for this particular issue, do not tag it with instead just reference it with\nHey ! How could I claim so we don't double work? Thanks\nHi ! Actually we just merge in the first PR for open issues. And your comment on this thread is enough. So, its yours. Happy translating.\nI just open a PR for\nthanks a lot that was fast! Would you be interested in translating these in future as well? If yes, please keep a watch on this thread. We will be updating on the progress often Happy contributing.\nDone translating ! My PR is available at ! Thanks for all you do, freeCodeCamp\nI have sent a translation proposal for /docs/how-to-work-on-guide- PR Hope it will help!\nThere is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with\nHello, I'm starting to help on the translation of the document /how-to-set-up-freecodecamp-\nWorking on /docs/spanish/how-to-work-on-guide-\nHello, I've improved the file\nHello, Improving docs/spanish/how-to-catch-outgoing-emails-\nHi, I'm improving docs/spanish/how-to-work-on-coding-\nHi, can I help with /docs/spanish/how-to-setup-freecodecamp-\nSorry, I opened a bad PR regarding but already closed it. I found there was still an English part to be translated\nHi! Is there any remaining documentation where I can help translate?\nyou can improve or fix redaction and spelling errors.\nHi there, It would be good if at the top are checked so we can see what is left to be translated. Thanks\nWhere I can start helping?\nsorry to put it in this issue, but is there any way somebody could help with the pull requests? I mean, there are 5K+ opened already, people are sending them in troves, and I suspect a lot of them are a total crap (Like ) . I guess you opened a Pandora Box with your articule about HacktoberFest.\nHey all, not a translation, but fixes for the language bar of HTML links on the README file for Spanish, and markdown links to the How To guides that everyone has been translating. . or anyone else looking to do translations in Spanish, you could make a copy of the 2 style guides to translate into Spanish from the English version in the doc folder. It looks like those weren't in to the Spanish folder originally or included on this issue. Just leave the title the same, but put it in the Spanish folder\nHola! to all. I believe we should have guidelines for Spanish translations, which include what treatment (formal or informal) to use when referring to actions or the user. For example, Agregue (formal) or Agrega (informal). - I don't know if this kind of things are found in other languages. In the last articles I've read I've seen a mix between formal and informal, and I think we should standardize (I have done it with some articles). I propose to always use informal. Another thing that could be specified in the guidelines is: Challenges translations. Should they be translated? Referrals to types and attributes (which need to be in English for proper coding). For example, type \"date\" not type \"fecha\". If there is a guideline already, please let me know, if not, I would be happy to start one (just let me know where to put it). Hey I would like to know your thoughts about this. Thanks to you all and happy coding!\nI agree that we should standardize around informal. I agree with you that we should look out for words like \"fecha\" that have been accidentally translated during our automated translation process.\nHi all I'm not sure if this is the right issue to discuss this, or if I should open a new one. I'm happy to open a new one if that makes things easier to track. I'll keep it here for the moment. What do people think about translating \"array\" as \"arreglo\"? I think this is a big mistake that has been repeated since somebody made that bad translation many years ago. As any Spanish speaker know, \"arreglo\" means \"repair\" (), and it makes any programming related text even harder to understand. This is especially true for programming texts because it's full of abstract nouns and things that are not easy to represent in a tangible way. I learned to code in English (mainly FCC and Coursera), and after a while, I stumbled upon a programming text written in Spanish. I couldn't understand what it was talking about until I found out that \"arreglo\" was the (really bad) translation of \"array\". Then I could read the text as if I was reading an encoded message that had to be deciphered. I propose that the Spanish version of FreeCodeCamp doesn't carry on with that translation, which is just based on the similarity of the spelling but has nothing to do with the meaning of the words. I think the right term in Spanish is \"ristra\". According to the : Which basically means: \"A group of things placed one after another\" They also share all the phonems in \"array\", with the adittion of /r/ (rolling r) and /t/ in \"ristra\". I'm open to other candidates, but please, let's take \"arreglo\" out of the Spanish version. The word \"array\" has been used in Spanish texts before and even though it's not a Spanish word, I think it's still better than a word that exists with a different meaning. And to be honest, anyone learning how to code will have to become familiar with certain English terms like \"list\", \"function\", \"import\", \"scope\", etc. [1]: [2]:\nHello guy, I vote for yes, let\u2019s do the change and I think will create a huge impact around of the world! Please let me know if you have more question questions or concerns. Andres Haro Cell: (619) 534-3190\nThanks - I agree that these machine translations need improvement. I encourage you to dig in and start fixing them. Be sure to join if you need help getting set up\nThere is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with\nThanks for working on the translations for the \"Contributing to freeCodeCamp\". Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-450ae51feac6069cad87f9b0e7a9563b6735d9515c8a4c62821c444b204930c7", "text": " # Contribution Guidelines # Como trabajar con correos salientes localmente (para el flujo de trabajo de correo electr\u00f3nico) Hello \ud83d\udc4b ! > **Nota:** Hay un **Opcional** Paso - Solo es requerido cuando trabajamos con el cuando se trabaja con flujos de trabajo de correo electr\u00f3nico These instructions have not been translated yet. Please check this issue for details: [`#18312`](https://github.com/freeCodeCamp/freeCodeCamp/issues/18312) No newline at end of file ##\u00a0Introducci\u00f3n Algunos flujos de trabajo del correo electr\u00f3nico, como la actualizar el correo electr\u00f3nico de un usuario, requieren de una API, en el backend para mandar correos electr\u00f3nicos. mientras desarrollamos podemos usar una herramienta para obtenerlos localmente, en lugar de tener que usar un proveedor de correo electr\u00f3nico y enviar un correo electr\u00f3nico real. MailHog es una de las muchas herramientas de email para probar en el entorno de desarrollo para desarrolladores, que capturar\u00e1 los correos electr\u00f3nicos de su instancia local que freeCodeCamp est\u00e1 enviando. ## Instalando MailHog Como podemons instalar y usar MailHog depende del sistema operativo - [Instalando MailHog en macOS](#installing-mailhog-on-macos) - [Instalando MailHog en Windows](#installing-mailhog-on-windows) - [Instalando MailHog en Linux](#installing-mailhog-on-linux) ### Instalando MailHog en MacOS Aqu\u00ed podemos ver como instalar MailHog en macOS [Homebrew](https://brew.sh/): ``` bash brew install mailhog brew services start mailhog ``` Esto emepezara un servicio de mailHog en segundo plano. Siguiente, puedes ir a [using MailHog](#using-mailhog). ### Instalar MailHog en Windows Descarga la versi\u00f3n mas reciente de MailHog de [MailHog's official repository](https://github.com/mailhog/MailHog/releases). Click en el link dependiendo de tu versi\u00f3n de Windows (32 \u00f3 64 bit) y el archivo .exe ser\u00e1 descargado en tu computadora. Una vez que termine la descarga, haga clic en el archivo. Probablemente recibir\u00e1 una notificaci\u00f3n de firewall de Windows donde tendr\u00e1 que permitir el acceso a MailHog. Una vez que lo haga, se abrir\u00e1 una l\u00ednea de comando est\u00e1ndar de Windows con MailHog ya en ejecuci\u00f3n. Para cerrar MailHog, cierre el s\u00edmbolo del sistema. Para volver a ejecutarlo, haga clic en el mismo archivo .exe. No necesitas descargar uno nuevo. Siguiente, Puedes ir a [using MailHog](#using-mailhog). ###\u00a0Instalando MailHog en Linux Primero instalar [Go](https://golang.org). Para sistemas basados en Debian como Ubuntu y Linux Mint, en la terminal: ``` bash sudo apt-get install golang ``` Para CentOS, Fedora, Red Hat Linux, y otros sistemas basados en RPM-based, en la terminal: ``` bash sudo dnf install golang ``` O: ``` bash sudo yum install golang ``` Establecer path para Go: ``` bash echo \"export GOPATH=$HOME/go\" >> ~/.profile echo 'export PATH=$PATH:/usr/local/go/bin:$GOPATH/bin' >> ~/.profile source ~/.profile ``` Despues instalar y correr MailHog: ``` bash go get github.com/mailhog/MailHog sudo cp /home/$(whoami)/go/bin/MailHog /usr/local/bin/mailhog mailhog ``` Siguiente, Puedes ir a [using MailHog](#using-mailhog). ## Using MailHog ## Usando MailHog Una vez que hayas instalado MailHog y lo hayas iniciado, debes abrir tu bandeja de entrada de MailHog en tu navegador, y abre una nueva pesta\u00f1a o ventana y navegar a [http://localhost:8025] (http://localhost:8025). Ahora deber\u00eda ver una pantalla como la siguiente: ![MailHog Screenshot 1](images/mailhog/1.jpg) Cuando la instalaci\u00f3n de freeCodeCamp env\u00ede un correo electr\u00f3nico, ver\u00e1s que aparece aqu\u00ed. Como aqu\u00ed abajo: ![MailHog Screenshot 2](images/mailhog/2.jpg) Abre el correo y ver\u00e1s dos pesta\u00f1as donde puedes ver el contenido: texto sin formato y fuente. Aseg\u00farate de que est\u00e1s en la pesta\u00f1a de texto sin formato. ![MailHog Screenshot 3](images/mailhog/3.jpg) Cualquier enlace en el correo electr\u00f3nico debe ser seleccionable. ## Enlaces \u00fatiles - Para cualquier otra pregunta relacionada con MailHog o para obtener instrucciones sobre configuraciones personalizadas, consulte el repositorio [MailHog] (https://github.com/mailhog/MailHog). No newline at end of file", "commid": "freeCodeCamp_pr_18323"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-3aa0738c73a98966c6ec81758d81218e55f1f56bfe17649aced191faba61b805", "query": "from its english version at from its english version at from its english version at from its english version at from its english version at from its english version at When you make a PR for this particular issue, do not tag it with instead just reference it with\nHey ! How could I claim so we don't double work? Thanks\nHi ! Actually we just merge in the first PR for open issues. And your comment on this thread is enough. So, its yours. Happy translating.\nI just open a PR for\nthanks a lot that was fast! Would you be interested in translating these in future as well? If yes, please keep a watch on this thread. We will be updating on the progress often Happy contributing.\nDone translating ! My PR is available at ! Thanks for all you do, freeCodeCamp\nI have sent a translation proposal for /docs/how-to-work-on-guide- PR Hope it will help!\nThere is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with\nHello, I'm starting to help on the translation of the document /how-to-set-up-freecodecamp-\nWorking on /docs/spanish/how-to-work-on-guide-\nHello, I've improved the file\nHello, Improving docs/spanish/how-to-catch-outgoing-emails-\nHi, I'm improving docs/spanish/how-to-work-on-coding-\nHi, can I help with /docs/spanish/how-to-setup-freecodecamp-\nSorry, I opened a bad PR regarding but already closed it. I found there was still an English part to be translated\nHi! Is there any remaining documentation where I can help translate?\nyou can improve or fix redaction and spelling errors.\nHi there, It would be good if at the top are checked so we can see what is left to be translated. Thanks\nWhere I can start helping?\nsorry to put it in this issue, but is there any way somebody could help with the pull requests? I mean, there are 5K+ opened already, people are sending them in troves, and I suspect a lot of them are a total crap (Like ) . I guess you opened a Pandora Box with your articule about HacktoberFest.\nHey all, not a translation, but fixes for the language bar of HTML links on the README file for Spanish, and markdown links to the How To guides that everyone has been translating. . or anyone else looking to do translations in Spanish, you could make a copy of the 2 style guides to translate into Spanish from the English version in the doc folder. It looks like those weren't in to the Spanish folder originally or included on this issue. Just leave the title the same, but put it in the Spanish folder\nHola! to all. I believe we should have guidelines for Spanish translations, which include what treatment (formal or informal) to use when referring to actions or the user. For example, Agregue (formal) or Agrega (informal). - I don't know if this kind of things are found in other languages. In the last articles I've read I've seen a mix between formal and informal, and I think we should standardize (I have done it with some articles). I propose to always use informal. Another thing that could be specified in the guidelines is: Challenges translations. Should they be translated? Referrals to types and attributes (which need to be in English for proper coding). For example, type \"date\" not type \"fecha\". If there is a guideline already, please let me know, if not, I would be happy to start one (just let me know where to put it). Hey I would like to know your thoughts about this. Thanks to you all and happy coding!\nI agree that we should standardize around informal. I agree with you that we should look out for words like \"fecha\" that have been accidentally translated during our automated translation process.\nHi all I'm not sure if this is the right issue to discuss this, or if I should open a new one. I'm happy to open a new one if that makes things easier to track. I'll keep it here for the moment. What do people think about translating \"array\" as \"arreglo\"? I think this is a big mistake that has been repeated since somebody made that bad translation many years ago. As any Spanish speaker know, \"arreglo\" means \"repair\" (), and it makes any programming related text even harder to understand. This is especially true for programming texts because it's full of abstract nouns and things that are not easy to represent in a tangible way. I learned to code in English (mainly FCC and Coursera), and after a while, I stumbled upon a programming text written in Spanish. I couldn't understand what it was talking about until I found out that \"arreglo\" was the (really bad) translation of \"array\". Then I could read the text as if I was reading an encoded message that had to be deciphered. I propose that the Spanish version of FreeCodeCamp doesn't carry on with that translation, which is just based on the similarity of the spelling but has nothing to do with the meaning of the words. I think the right term in Spanish is \"ristra\". According to the : Which basically means: \"A group of things placed one after another\" They also share all the phonems in \"array\", with the adittion of /r/ (rolling r) and /t/ in \"ristra\". I'm open to other candidates, but please, let's take \"arreglo\" out of the Spanish version. The word \"array\" has been used in Spanish texts before and even though it's not a Spanish word, I think it's still better than a word that exists with a different meaning. And to be honest, anyone learning how to code will have to become familiar with certain English terms like \"list\", \"function\", \"import\", \"scope\", etc. [1]: [2]:\nHello guy, I vote for yes, let\u2019s do the change and I think will create a huge impact around of the world! Please let me know if you have more question questions or concerns. Andres Haro Cell: (619) 534-3190\nThanks - I agree that these machine translations need improvement. I encourage you to dig in and start fixing them. Be sure to join if you need help getting set up\nThere is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with\nThanks for working on the translations for the \"Contributing to freeCodeCamp\". Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-809944fb91618bf8234adb158f2b9c1088f452afcf56fd43f428fab86e9f6326", "text": "Puedes realizar los cambios sin tener que ejecutar nada desde tu sistema local. Despu\u00e9s de que encuentres el archivo que quieras modificar desde la interfaz de GitHub, haz clic en el icono de l\u00e1piz para comenzar a editar el archivo. Esto autom\u00e1ticamente creara una bifurcaci\u00f3n del proyecto, si es que no tienes una todav\u00eda. Despu\u00e9s de que encuentres el archivo que quieras modificar desde la interfaz de GitHub, hace clic en el icono de l\u00e1piz para comenzar a editar el archivo. Esto autom\u00e1ticamente creara una bifurcaci\u00f3n del proyecto, si es que no tienes una todav\u00eda. Tambi\u00e9n puedes clonar el proyecto y editarlo de manera local en tu ordenador. Si necesitas ayuda al respecto, dale un vistazo a la [gu\u00eda principal de contribuci\u00f3n](/CONTRIBUTING.md). ### Patr\u00f3n de los Desaf\u00edos. He aqu\u00ed un patr\u00f3n de c\u00f3mo se ver\u00e1n los archivos markdown correspondientes a los desaf\u00edos. He aqu\u00ed un patr\u00f3n de c\u00f3mo se ver\u00e1n los archivos reduccion correspondientes a los desaf\u00edos. ````md ---", "commid": "freeCodeCamp_pr_19686"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-3aa0738c73a98966c6ec81758d81218e55f1f56bfe17649aced191faba61b805", "query": "from its english version at from its english version at from its english version at from its english version at from its english version at from its english version at When you make a PR for this particular issue, do not tag it with instead just reference it with\nHey ! How could I claim so we don't double work? Thanks\nHi ! Actually we just merge in the first PR for open issues. And your comment on this thread is enough. So, its yours. Happy translating.\nI just open a PR for\nthanks a lot that was fast! Would you be interested in translating these in future as well? If yes, please keep a watch on this thread. We will be updating on the progress often Happy contributing.\nDone translating ! My PR is available at ! Thanks for all you do, freeCodeCamp\nI have sent a translation proposal for /docs/how-to-work-on-guide- PR Hope it will help!\nThere is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with\nHello, I'm starting to help on the translation of the document /how-to-set-up-freecodecamp-\nWorking on /docs/spanish/how-to-work-on-guide-\nHello, I've improved the file\nHello, Improving docs/spanish/how-to-catch-outgoing-emails-\nHi, I'm improving docs/spanish/how-to-work-on-coding-\nHi, can I help with /docs/spanish/how-to-setup-freecodecamp-\nSorry, I opened a bad PR regarding but already closed it. I found there was still an English part to be translated\nHi! Is there any remaining documentation where I can help translate?\nyou can improve or fix redaction and spelling errors.\nHi there, It would be good if at the top are checked so we can see what is left to be translated. Thanks\nWhere I can start helping?\nsorry to put it in this issue, but is there any way somebody could help with the pull requests? I mean, there are 5K+ opened already, people are sending them in troves, and I suspect a lot of them are a total crap (Like ) . I guess you opened a Pandora Box with your articule about HacktoberFest.\nHey all, not a translation, but fixes for the language bar of HTML links on the README file for Spanish, and markdown links to the How To guides that everyone has been translating. . or anyone else looking to do translations in Spanish, you could make a copy of the 2 style guides to translate into Spanish from the English version in the doc folder. It looks like those weren't in to the Spanish folder originally or included on this issue. Just leave the title the same, but put it in the Spanish folder\nHola! to all. I believe we should have guidelines for Spanish translations, which include what treatment (formal or informal) to use when referring to actions or the user. For example, Agregue (formal) or Agrega (informal). - I don't know if this kind of things are found in other languages. In the last articles I've read I've seen a mix between formal and informal, and I think we should standardize (I have done it with some articles). I propose to always use informal. Another thing that could be specified in the guidelines is: Challenges translations. Should they be translated? Referrals to types and attributes (which need to be in English for proper coding). For example, type \"date\" not type \"fecha\". If there is a guideline already, please let me know, if not, I would be happy to start one (just let me know where to put it). Hey I would like to know your thoughts about this. Thanks to you all and happy coding!\nI agree that we should standardize around informal. I agree with you that we should look out for words like \"fecha\" that have been accidentally translated during our automated translation process.\nHi all I'm not sure if this is the right issue to discuss this, or if I should open a new one. I'm happy to open a new one if that makes things easier to track. I'll keep it here for the moment. What do people think about translating \"array\" as \"arreglo\"? I think this is a big mistake that has been repeated since somebody made that bad translation many years ago. As any Spanish speaker know, \"arreglo\" means \"repair\" (), and it makes any programming related text even harder to understand. This is especially true for programming texts because it's full of abstract nouns and things that are not easy to represent in a tangible way. I learned to code in English (mainly FCC and Coursera), and after a while, I stumbled upon a programming text written in Spanish. I couldn't understand what it was talking about until I found out that \"arreglo\" was the (really bad) translation of \"array\". Then I could read the text as if I was reading an encoded message that had to be deciphered. I propose that the Spanish version of FreeCodeCamp doesn't carry on with that translation, which is just based on the similarity of the spelling but has nothing to do with the meaning of the words. I think the right term in Spanish is \"ristra\". According to the : Which basically means: \"A group of things placed one after another\" They also share all the phonems in \"array\", with the adittion of /r/ (rolling r) and /t/ in \"ristra\". I'm open to other candidates, but please, let's take \"arreglo\" out of the Spanish version. The word \"array\" has been used in Spanish texts before and even though it's not a Spanish word, I think it's still better than a word that exists with a different meaning. And to be honest, anyone learning how to code will have to become familiar with certain English terms like \"list\", \"function\", \"import\", \"scope\", etc. [1]: [2]:\nHello guy, I vote for yes, let\u2019s do the change and I think will create a huge impact around of the world! Please let me know if you have more question questions or concerns. Andres Haro Cell: (619) 534-3190\nThanks - I agree that these machine translations need improvement. I encourage you to dig in and start fixing them. Be sure to join if you need help getting set up\nThere is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with\nThanks for working on the translations for the \"Contributing to freeCodeCamp\". Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-54a05d60b9d5f67ecec8de42009949d6f70bd10b1a8209cf575af8be56ad808b", "text": "## Descripci\u00f3n
Una descripci\u00f3n del desaf\u00edo y de los requerimientos aprobatorios Una descripci\u00f3n del desaf\u00edo y de los requisitos aprobacion
## Instrucciones", "commid": "freeCodeCamp_pr_19686"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-3aa0738c73a98966c6ec81758d81218e55f1f56bfe17649aced191faba61b805", "query": "from its english version at from its english version at from its english version at from its english version at from its english version at from its english version at When you make a PR for this particular issue, do not tag it with instead just reference it with\nHey ! How could I claim so we don't double work? Thanks\nHi ! Actually we just merge in the first PR for open issues. And your comment on this thread is enough. So, its yours. Happy translating.\nI just open a PR for\nthanks a lot that was fast! Would you be interested in translating these in future as well? If yes, please keep a watch on this thread. We will be updating on the progress often Happy contributing.\nDone translating ! My PR is available at ! Thanks for all you do, freeCodeCamp\nI have sent a translation proposal for /docs/how-to-work-on-guide- PR Hope it will help!\nThere is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with\nHello, I'm starting to help on the translation of the document /how-to-set-up-freecodecamp-\nWorking on /docs/spanish/how-to-work-on-guide-\nHello, I've improved the file\nHello, Improving docs/spanish/how-to-catch-outgoing-emails-\nHi, I'm improving docs/spanish/how-to-work-on-coding-\nHi, can I help with /docs/spanish/how-to-setup-freecodecamp-\nSorry, I opened a bad PR regarding but already closed it. I found there was still an English part to be translated\nHi! Is there any remaining documentation where I can help translate?\nyou can improve or fix redaction and spelling errors.\nHi there, It would be good if at the top are checked so we can see what is left to be translated. Thanks\nWhere I can start helping?\nsorry to put it in this issue, but is there any way somebody could help with the pull requests? I mean, there are 5K+ opened already, people are sending them in troves, and I suspect a lot of them are a total crap (Like ) . I guess you opened a Pandora Box with your articule about HacktoberFest.\nHey all, not a translation, but fixes for the language bar of HTML links on the README file for Spanish, and markdown links to the How To guides that everyone has been translating. . or anyone else looking to do translations in Spanish, you could make a copy of the 2 style guides to translate into Spanish from the English version in the doc folder. It looks like those weren't in to the Spanish folder originally or included on this issue. Just leave the title the same, but put it in the Spanish folder\nHola! to all. I believe we should have guidelines for Spanish translations, which include what treatment (formal or informal) to use when referring to actions or the user. For example, Agregue (formal) or Agrega (informal). - I don't know if this kind of things are found in other languages. In the last articles I've read I've seen a mix between formal and informal, and I think we should standardize (I have done it with some articles). I propose to always use informal. Another thing that could be specified in the guidelines is: Challenges translations. Should they be translated? Referrals to types and attributes (which need to be in English for proper coding). For example, type \"date\" not type \"fecha\". If there is a guideline already, please let me know, if not, I would be happy to start one (just let me know where to put it). Hey I would like to know your thoughts about this. Thanks to you all and happy coding!\nI agree that we should standardize around informal. I agree with you that we should look out for words like \"fecha\" that have been accidentally translated during our automated translation process.\nHi all I'm not sure if this is the right issue to discuss this, or if I should open a new one. I'm happy to open a new one if that makes things easier to track. I'll keep it here for the moment. What do people think about translating \"array\" as \"arreglo\"? I think this is a big mistake that has been repeated since somebody made that bad translation many years ago. As any Spanish speaker know, \"arreglo\" means \"repair\" (), and it makes any programming related text even harder to understand. This is especially true for programming texts because it's full of abstract nouns and things that are not easy to represent in a tangible way. I learned to code in English (mainly FCC and Coursera), and after a while, I stumbled upon a programming text written in Spanish. I couldn't understand what it was talking about until I found out that \"arreglo\" was the (really bad) translation of \"array\". Then I could read the text as if I was reading an encoded message that had to be deciphered. I propose that the Spanish version of FreeCodeCamp doesn't carry on with that translation, which is just based on the similarity of the spelling but has nothing to do with the meaning of the words. I think the right term in Spanish is \"ristra\". According to the : Which basically means: \"A group of things placed one after another\" They also share all the phonems in \"array\", with the adittion of /r/ (rolling r) and /t/ in \"ristra\". I'm open to other candidates, but please, let's take \"arreglo\" out of the Spanish version. The word \"array\" has been used in Spanish texts before and even though it's not a Spanish word, I think it's still better than a word that exists with a different meaning. And to be honest, anyone learning how to code will have to become familiar with certain English terms like \"list\", \"function\", \"import\", \"scope\", etc. [1]: [2]:\nHello guy, I vote for yes, let\u2019s do the change and I think will create a huge impact around of the world! Please let me know if you have more question questions or concerns. Andres Haro Cell: (619) 534-3190\nThanks - I agree that these machine translations need improvement. I encourage you to dig in and start fixing them. Be sure to join if you need help getting set up\nThere is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with\nThanks for working on the translations for the \"Contributing to freeCodeCamp\". Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-8b5eb6af383951610ce193bcdd9189a36765972fc0f78ecd82d6f001b7519bbd", "text": "Puedes: - [Ayudarnos creando y editando art\u00faclos de la Gu\u00eda](#steps-for-creating-and-editing-guide-articles). - [Ayudarnos creando y editando articulos de la Gu\u00eda](#steps-for-creating-and-editing-guide-articles). - [Ayudarnos a revisar Pull Requests para art\u00edculos de la gu\u00eda]() ## Pasos para crear y editar art\u00edculos de la Gu\u00eda 1. \ud83c\udf74 [Fork este repositorio](https://github.com/freeCodeCamp/freeCodeCamp#fork-destination-box) 2. \ud83d\udc40\ufe0f Sgiue las normas de controbuci\u00f3n expuestas a continuaci\u00f3n. 3. \ud83d\udd27 Prop\u00f3n cambios asombrosos! 2. \ud83d\udc40\ufe0f Sigue las normas de contribuci\u00f3n expuestas a continuaci\u00f3n. 3. \ud83d\udd27 Prop\u00f3ne cambios asombrosos! 4. \ud83d\udcd6 Lee la [gu\u00eda de buenas pr\u00e1cticas de estilo](/docs/style-guide-for-guide-articles). 5. \ud83d\udc49 [Haz una Pull Request](https://github.com/freeCodeCamp/freeCodeCamp/compare) 5. \ud83d\udc49 [Hace un Pull Request](https://github.com/freeCodeCamp/freeCodeCamp/compare) 6. \ud83c\udf89 Consigue que aprueben tu Pull request - \u00c9xito! O siemplement [crea un tema](https://github.com/freeCodeCamp/freeCodeCamp/issues) - toda peque\u00f1a ayuda cuenta! \ud83d\ude0a O simplemente [crea un tema](https://github.com/freeCodeCamp/freeCodeCamp/issues) - toda peque\u00f1a ayuda cuenta! \ud83d\ude0a ### [Sigue estas recomendaciones de nuestra gu\u00eda de estilo para crear un art\u00edculo atractivo](/docs/style-guide-for-guide-articles.md) ### Crear Pull Request para propoenr cambios ### Crear Pull Request para proponer cambios Hay dos formas de proponer cambios en el repositorio tras editar o a\u00f1adir un articulo: Hay dos formas de proponer cambios en el repositorio despues de editar o a\u00f1adir un articulo: - [Utilizando la interfaz de GitHub en tu navegador](#using-the-github-web-interface-on-your-browser). - [Trabajando en tu ordenador personal](#working-on-your-local-machine) (_recomendado_ para previsualiar cambios). - [Utilizando el sistema de comunicacion de GitHub en tu navegador](#using-the-github-web-interface-on-your-browser). - [Trabajando en tu maquina local](#working-on-your-local-machine) (_recomendado_ para pre-visualiar cambios). #### Utilizar la interaz web de GitHub #### Utilizar el sistema de comunicacion web de GitHub Mira este v\u00eddeo de demostraci\u00f3n o sigue los siguientes pasos: **[TODO]** Update the GIF recording. **[TODO]** Actualizar la grabacion GIF. ![GIF showing the GitHub interface steps](#) ![GIF mostrando los pasos de la interfaz de GitHub](#) 1. Ve a la carpets **\"p\u00e1ginas\"** (situado en [`guide`](/guide)) donde encontrar\u00e1s el art\u00edculo raiz que quieras editar. 1. Ve a las carpetas **\"p\u00e1ginas\"** (situado en [`guide`](/guide)) donde encontrar\u00e1s el art\u00edculo raiz que quieras editar. > Todas las ra\u00edces estar\u00e1n en un archivo index.md 2. Pincha en Editar este archivo y haz tus cambios al archivo en la consola de edici\u00f3n de GitHub. 2. Pincha en Editar este archivo y hace tus cambios al archivo en la consola de edici\u00f3n de GitHub. > Si el icono aparece gris y te muestra la alerta \"Debes estar en una rama para hacer o proponer cambios a este archivo\", significa que probablemente est\u00e9s en la rama de otra persona. En la parte superior izquierda de la p\u00e1gina hay una casilla desplegable que dice: \"\u00c1rbol: #######\". Pincha en el desplegable y cambia la rama a maestra. El icono de edici\u00f3n deber\u00eda estar disponible ahora.", "commid": "freeCodeCamp_pr_19689"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-3aa0738c73a98966c6ec81758d81218e55f1f56bfe17649aced191faba61b805", "query": "from its english version at from its english version at from its english version at from its english version at from its english version at from its english version at When you make a PR for this particular issue, do not tag it with instead just reference it with\nHey ! How could I claim so we don't double work? Thanks\nHi ! Actually we just merge in the first PR for open issues. And your comment on this thread is enough. So, its yours. Happy translating.\nI just open a PR for\nthanks a lot that was fast! Would you be interested in translating these in future as well? If yes, please keep a watch on this thread. We will be updating on the progress often Happy contributing.\nDone translating ! My PR is available at ! Thanks for all you do, freeCodeCamp\nI have sent a translation proposal for /docs/how-to-work-on-guide- PR Hope it will help!\nThere is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with\nHello, I'm starting to help on the translation of the document /how-to-set-up-freecodecamp-\nWorking on /docs/spanish/how-to-work-on-guide-\nHello, I've improved the file\nHello, Improving docs/spanish/how-to-catch-outgoing-emails-\nHi, I'm improving docs/spanish/how-to-work-on-coding-\nHi, can I help with /docs/spanish/how-to-setup-freecodecamp-\nSorry, I opened a bad PR regarding but already closed it. I found there was still an English part to be translated\nHi! Is there any remaining documentation where I can help translate?\nyou can improve or fix redaction and spelling errors.\nHi there, It would be good if at the top are checked so we can see what is left to be translated. Thanks\nWhere I can start helping?\nsorry to put it in this issue, but is there any way somebody could help with the pull requests? I mean, there are 5K+ opened already, people are sending them in troves, and I suspect a lot of them are a total crap (Like ) . I guess you opened a Pandora Box with your articule about HacktoberFest.\nHey all, not a translation, but fixes for the language bar of HTML links on the README file for Spanish, and markdown links to the How To guides that everyone has been translating. . or anyone else looking to do translations in Spanish, you could make a copy of the 2 style guides to translate into Spanish from the English version in the doc folder. It looks like those weren't in to the Spanish folder originally or included on this issue. Just leave the title the same, but put it in the Spanish folder\nHola! to all. I believe we should have guidelines for Spanish translations, which include what treatment (formal or informal) to use when referring to actions or the user. For example, Agregue (formal) or Agrega (informal). - I don't know if this kind of things are found in other languages. In the last articles I've read I've seen a mix between formal and informal, and I think we should standardize (I have done it with some articles). I propose to always use informal. Another thing that could be specified in the guidelines is: Challenges translations. Should they be translated? Referrals to types and attributes (which need to be in English for proper coding). For example, type \"date\" not type \"fecha\". If there is a guideline already, please let me know, if not, I would be happy to start one (just let me know where to put it). Hey I would like to know your thoughts about this. Thanks to you all and happy coding!\nI agree that we should standardize around informal. I agree with you that we should look out for words like \"fecha\" that have been accidentally translated during our automated translation process.\nHi all I'm not sure if this is the right issue to discuss this, or if I should open a new one. I'm happy to open a new one if that makes things easier to track. I'll keep it here for the moment. What do people think about translating \"array\" as \"arreglo\"? I think this is a big mistake that has been repeated since somebody made that bad translation many years ago. As any Spanish speaker know, \"arreglo\" means \"repair\" (), and it makes any programming related text even harder to understand. This is especially true for programming texts because it's full of abstract nouns and things that are not easy to represent in a tangible way. I learned to code in English (mainly FCC and Coursera), and after a while, I stumbled upon a programming text written in Spanish. I couldn't understand what it was talking about until I found out that \"arreglo\" was the (really bad) translation of \"array\". Then I could read the text as if I was reading an encoded message that had to be deciphered. I propose that the Spanish version of FreeCodeCamp doesn't carry on with that translation, which is just based on the similarity of the spelling but has nothing to do with the meaning of the words. I think the right term in Spanish is \"ristra\". According to the : Which basically means: \"A group of things placed one after another\" They also share all the phonems in \"array\", with the adittion of /r/ (rolling r) and /t/ in \"ristra\". I'm open to other candidates, but please, let's take \"arreglo\" out of the Spanish version. The word \"array\" has been used in Spanish texts before and even though it's not a Spanish word, I think it's still better than a word that exists with a different meaning. And to be honest, anyone learning how to code will have to become familiar with certain English terms like \"list\", \"function\", \"import\", \"scope\", etc. [1]: [2]:\nHello guy, I vote for yes, let\u2019s do the change and I think will create a huge impact around of the world! Please let me know if you have more question questions or concerns. Andres Haro Cell: (619) 534-3190\nThanks - I agree that these machine translations need improvement. I encourage you to dig in and start fixing them. Be sure to join if you need help getting set up\nThere is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with\nThanks for working on the translations for the \"Contributing to freeCodeCamp\". Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-cc2baa30bab3df9ffdeb5013068b5806343a535d633cba374b1a7d9197ad8b60", "text": "Documentos: Actualizadas recomendaciones de contribuci\u00f3n ``` Se breve, no m\u00e1s de 50 caracteres. Puedes a\u00f1adir informaci\u00f3n extra en la descripci\u00f3n del mensaje. Sea breve, no m\u00e1s de 50 caracteres. Puedes a\u00f1adir informaci\u00f3n extra en la descripci\u00f3n del mensaje. esto no supone ning\u00fan esfuerzo adicional respecto a mensajes como 'update file' o 'add index.md'", "commid": "freeCodeCamp_pr_19689"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-3aa0738c73a98966c6ec81758d81218e55f1f56bfe17649aced191faba61b805", "query": "from its english version at from its english version at from its english version at from its english version at from its english version at from its english version at When you make a PR for this particular issue, do not tag it with instead just reference it with\nHey ! How could I claim so we don't double work? Thanks\nHi ! Actually we just merge in the first PR for open issues. And your comment on this thread is enough. So, its yours. Happy translating.\nI just open a PR for\nthanks a lot that was fast! Would you be interested in translating these in future as well? If yes, please keep a watch on this thread. We will be updating on the progress often Happy contributing.\nDone translating ! My PR is available at ! Thanks for all you do, freeCodeCamp\nI have sent a translation proposal for /docs/how-to-work-on-guide- PR Hope it will help!\nThere is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with\nHello, I'm starting to help on the translation of the document /how-to-set-up-freecodecamp-\nWorking on /docs/spanish/how-to-work-on-guide-\nHello, I've improved the file\nHello, Improving docs/spanish/how-to-catch-outgoing-emails-\nHi, I'm improving docs/spanish/how-to-work-on-coding-\nHi, can I help with /docs/spanish/how-to-setup-freecodecamp-\nSorry, I opened a bad PR regarding but already closed it. I found there was still an English part to be translated\nHi! Is there any remaining documentation where I can help translate?\nyou can improve or fix redaction and spelling errors.\nHi there, It would be good if at the top are checked so we can see what is left to be translated. Thanks\nWhere I can start helping?\nsorry to put it in this issue, but is there any way somebody could help with the pull requests? I mean, there are 5K+ opened already, people are sending them in troves, and I suspect a lot of them are a total crap (Like ) . I guess you opened a Pandora Box with your articule about HacktoberFest.\nHey all, not a translation, but fixes for the language bar of HTML links on the README file for Spanish, and markdown links to the How To guides that everyone has been translating. . or anyone else looking to do translations in Spanish, you could make a copy of the 2 style guides to translate into Spanish from the English version in the doc folder. It looks like those weren't in to the Spanish folder originally or included on this issue. Just leave the title the same, but put it in the Spanish folder\nHola! to all. I believe we should have guidelines for Spanish translations, which include what treatment (formal or informal) to use when referring to actions or the user. For example, Agregue (formal) or Agrega (informal). - I don't know if this kind of things are found in other languages. In the last articles I've read I've seen a mix between formal and informal, and I think we should standardize (I have done it with some articles). I propose to always use informal. Another thing that could be specified in the guidelines is: Challenges translations. Should they be translated? Referrals to types and attributes (which need to be in English for proper coding). For example, type \"date\" not type \"fecha\". If there is a guideline already, please let me know, if not, I would be happy to start one (just let me know where to put it). Hey I would like to know your thoughts about this. Thanks to you all and happy coding!\nI agree that we should standardize around informal. I agree with you that we should look out for words like \"fecha\" that have been accidentally translated during our automated translation process.\nHi all I'm not sure if this is the right issue to discuss this, or if I should open a new one. I'm happy to open a new one if that makes things easier to track. I'll keep it here for the moment. What do people think about translating \"array\" as \"arreglo\"? I think this is a big mistake that has been repeated since somebody made that bad translation many years ago. As any Spanish speaker know, \"arreglo\" means \"repair\" (), and it makes any programming related text even harder to understand. This is especially true for programming texts because it's full of abstract nouns and things that are not easy to represent in a tangible way. I learned to code in English (mainly FCC and Coursera), and after a while, I stumbled upon a programming text written in Spanish. I couldn't understand what it was talking about until I found out that \"arreglo\" was the (really bad) translation of \"array\". Then I could read the text as if I was reading an encoded message that had to be deciphered. I propose that the Spanish version of FreeCodeCamp doesn't carry on with that translation, which is just based on the similarity of the spelling but has nothing to do with the meaning of the words. I think the right term in Spanish is \"ristra\". According to the : Which basically means: \"A group of things placed one after another\" They also share all the phonems in \"array\", with the adittion of /r/ (rolling r) and /t/ in \"ristra\". I'm open to other candidates, but please, let's take \"arreglo\" out of the Spanish version. The word \"array\" has been used in Spanish texts before and even though it's not a Spanish word, I think it's still better than a word that exists with a different meaning. And to be honest, anyone learning how to code will have to become familiar with certain English terms like \"list\", \"function\", \"import\", \"scope\", etc. [1]: [2]:\nHello guy, I vote for yes, let\u2019s do the change and I think will create a huge impact around of the world! Please let me know if you have more question questions or concerns. Andres Haro Cell: (619) 534-3190\nThanks - I agree that these machine translations need improvement. I encourage you to dig in and start fixing them. Be sure to join if you need help getting set up\nThere is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with\nThanks for working on the translations for the \"Contributing to freeCodeCamp\". Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-79ed061ff482f71ca575c39f6b501ad75ad90a153f7f58049ea77ca4970283ea", "text": "5. En la siguiente pantalla, puedes a\u00f1adir m\u00e1s detalles sobre tu PR, luego pincha en Crear pull request. Enhorabuena \ud83c\udf89! Acabas de crear una pull request. Felicidades \ud83c\udf89! Acabas de crear un pull request. #### Trabajar desde tu sistema local (_recomendado_ para revisar cambios) No es obligatorio que trabajes en tu sistema personal, salvo que desees previsualizar tus cambios, o trabajar con mejoras y arreglos de UI. Tambi\u00e9n es recomendable si tienes problemas con git como errores de integraci\u00f3n, rebase, etc. No es obligatorio que trabajes en tu sistema personal, salvo que desees pre-visualizar tus cambios, o trabajar con version actualizada y arreglos de UI. Tambi\u00e9n es recomendable si tienes problemas con git como errores de integraci\u00f3n, rebase, etc. ##### Lee sobre esta recomendaciones en [C\u00f3mo configurar freeCodeCamp localmente](/docs/how-to-setup-freecodecamp-locally.md) ##### Lee sobre estas recomendaciones en [C\u00f3mo configurar freeCodeCamp localmente](/docs/how-to-setup-freecodecamp-locally.md) ### Aceptaci\u00f3n de la PR Estas son algunos criterios utilizados por los revisores cuando eval\u00faan PRs: Estos son algunos criterios utilizados por los criticos cuando eval\u00faan PRs: - Descripci\u00f3n y t\u00edtulo relevantes - La PR respeta la [gu\u00eda de estilo](/docs/style-guide-for-guide-articles) - Consejos generales de QA de las [recomendaciones para Moderadores](https://forum.freecodecamp.org/t/freecodecamp-moderator-guidelines/18295) - Siempre y cuando la PR suponga una mejora o ampliaci\u00f3n de la gu\u00eda, ser\u00e1 aceptada aunque tenga errores gramaticales o contenido parcial - Siempre y cuando el PR suponga una mejora o ampliaci\u00f3n de la gu\u00eda, ser\u00e1 aceptado aunque tenga errores gramaticos o contenido parcial - Las PR m\u00e1s antiguas se revisan primero #### Etiquetas - **contenido** es para Pull Requests que modifican el contenido de art\u00edculos en la gu\u00eda (a\u00f1aden un nuevo art\u00edculo o actualizan uno existente) - **duplicada** es para Pull Request que contienen el mismo contenido que otra PR abierta - **cambios solicitados** es para Pull Requests que necesitan alg\u00fan cambio antes de ser integradas - **pasada** es para Pull Requests que con etiqueta _\"changes requested\"_ que no han tenido actividad durante al menos 2 semanas y ser\u00e1n por tanto cerradas - Una pull request _pasada_ debe cerrarse. - **duplicada** es para Pull Request que contienen el mismo contenido que otro PR abierto - **cambios solicitados** es para Pull Requests que necesitan alg\u00fan cambio antes de ser integrados - **pasada** es para Pull Requests que con etiqueta _\"changes requested\"_ que no han tenido actividad durante al menos 2 semanas y ser\u00e1n por tanto cerrados - Un pull request _pasado_ debe cerrarse. - Este es [un ejemplo](https://github.com/freeCodeCamp/freeCodeCamp/pull/235). #### Contenido conflictivo/duplicado Se considera **duplicada** una PR si hace cambios al mismo art\u00edculo que otra PR. Se considera **duplicado** un PR si hace cambios al mismo art\u00edculo que otro PR. En general el revisor: 1. Organizar\u00e1 las PR desde la m\u00e1s antigua 1. Organizar\u00e1 los PR desde lo m\u00e1s antiguo 2. Buscar\u00e1 para PRs con contenido similar 3. Integrar\u00e1 desde la m\u00e1s antigua a las m\u00e1s nueva 3. Integrar\u00e1 desde lo m\u00e1s antiguo a los m\u00e1s nuevos Muy probablemente aparecer\u00e1n conflictos al integrar PRs duplicadas. Muy probablemente aparecer\u00e1n conflictos al integrar PRs duplicados. Los revisores har\u00e1n todos los esfuerzos posibles para resolver estos conflictos e integrar las PRs. Los revisores har\u00e1n todos los esfuerzos posibles para resolver estos conflictos e integrar los PRs. #### Solicitar cambios Si la Pull Request no es perfect el revisor podr\u00eda: Si el Pull Request no es perfecto el revisor podr\u00eda: - solicitar cambios al contribuidor y a\u00f1adir la etiqueta *cambios solicitados* - solucionar errores menores y hacer un env\u00edo encima de la PR - solucionar errores menores y hacer un env\u00edo encima de el PR #### Travis CI Build Todas las PRs deben superar los test de Travis CI antes de poder ser integradas. Todos los PRs deben superar los test de Travis CI antes de poder ser integrados. Si una PR rompe la ejecuci\u00f3n (un test de Travis CI falla y muestra una \"X\" roja) hay tres cauas probables y tendr\u00e1s que resolver el problemas antes de que podamos integrar la PR: Si un PR rompe la ejecuci\u00f3n (un test de Travis CI falla y muestra una \"X\" roja) hay tres causas probables y tendr\u00e1s que resolver el problema antes de que podamos integrar el PR: 1. Tu PR crea un nueva art\u00edculo pero la falta un archivo `index.md` en alg\u00fan lugar. 1. Tu PR crea un nuevo art\u00edculo pero le falta un archivo `index.md` en alg\u00fan lugar. - Cada directorio en `src/pages` necesita un archivo `index.md` en \u00e9l (y debe llamarse `index.md`). - Dos escenarios muy probables son - llamaste al archivo de forma distinta a `index.md`, o", "commid": "freeCodeCamp_pr_19689"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-35d602ee7ccda20fb5414057a65c66f318a288913d14a6e9aa6b26950a449373", "query": "from its english version at from its english version at from its english version at from its english version at from its english version at from its english version at \nPlease, review\n[x] [x] /docs/russian/how-to-work-on-coding- [] ()\nFixes the html links in the top language bar for all language README docs. Not a translation, but just link fixes. Once the Russian README files get merged, we can add the markdown style for links to all the articles in Russian too!\nstarted to review PRs. ping me if more help needed reviewed and requested changed at LGTM from native russian speaker view LGTM Resolve conflict is needed\nHi, guys! Please review my PR\nThanks for working on the translations for the \"Contributing to freeCodeCamp\". Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-143145a27ba2f7762b2c6dc85600400b42bf139d0b1afcaf22d4bb9f36212886", "text": " | [Read these guidelines in other languages](/docs/i18n-languages) | |-| # \u041a\u0430\u043a \u0441\u043e\u0437\u0434\u0430\u0442\u044c Pull Request (\u041f\u0443\u043b\u043b \u0420\u0435\u043a\u0432\u0435\u0441\u0442) ## \u041a\u0430\u043a \u0441\u0434\u0435\u043b\u0430\u0442\u044c \u0445\u043e\u0440\u043e\u0448\u0438\u0439 \u0437\u0430\u0433\u043e\u043b\u043e\u0432\u043e\u043a \u0434\u043b\u044f Pull Request: \u0421\u043e\u0437\u0434\u0430\u0432\u0430\u044f Pull Request (PR), \u0432\u043e\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0439\u0442\u0435\u0441\u044c \u0434\u0430\u043d\u043d\u043e\u0439 \u0442\u0430\u0431\u043b\u0438\u0446\u0435\u0439, \u0447\u0442\u043e\u0431\u044b \u0440\u0435\u0448\u0438\u0442\u044c, \u043a\u0430\u043a \u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u043e \u043e\u0437\u0430\u0433\u043b\u0430\u0432\u0438\u0442\u044c PR \u0432 \u0444\u043e\u0440\u043c\u0430\u0442\u0435: `fix/feat/chore/refactor/docs/perf (scope): PR Title` \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440: `fix(learn): Fixed tests for the do...while loop challenge`. | \u041e\u0431\u043b\u0430\u0441\u0442\u044c | \u041e\u043f\u0438\u0441\u0430\u043d\u0438\u0435 | |---|---| | `learn`,`curriculum` | \u0414\u043b\u044f PR'\u043e\u0432, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0432\u043d\u043e\u0441\u044f\u0442 \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u044f \u0432 \u0443\u0447\u0435\u0431\u043d\u044b\u0439 \u043f\u043b\u0430\u043d. | | `client` | \u0414\u043b\u044f PR'\u043e\u0432, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0432\u043d\u043e\u0441\u044f\u0442 \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u044f \u0432 \u043b\u043e\u0433\u0438\u043a\u0443 \u043a\u043b\u0438\u0435\u043d\u0442\u0441\u043a\u043e\u0439 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u044b \u0438\u043b\u0438 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044c\u0441\u043a\u0438\u0439 \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441. | | `guide` | \u0414\u043b\u044f PR'\u043e\u0432, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0432\u043d\u043e\u0441\u044f\u0442 \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u044f \u0432 \u0438\u043d\u0441\u0442\u0443\u043a\u0446\u0438\u0438. | | `docs` | \u0414\u043b\u044f PR'\u043e\u0432, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0432\u043d\u043e\u0441\u044f\u0442 \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u044f \u0432 \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044e. | ## \u0421\u043e\u0437\u0434\u0430\u043d\u0438\u0435 \u041f\u0443\u043b\u043b \u0420\u0435\u043a\u0432\u0435\u0441\u0442\u0430 (PR) 1. \u041f\u043e\u0441\u043b\u0435 \u0442\u043e\u0433\u043e, \u043a\u0430\u043a \u0432\u044b \u0432\u043d\u0435\u0441\u0451\u0442\u0435 \u043a\u0430\u043a\u0438\u0435-\u043d\u0438\u0431\u0443\u0434\u044c \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u044f \u0432 \u0441\u0432\u043e\u0439 \u0444\u043e\u0440\u043a \u0440\u0435\u043f\u043e\u0437\u0438\u0442\u043e\u0440\u0438\u044f, GitHub \u043f\u0440\u0435\u0434\u043b\u043e\u0436\u0438\u0442 \u0432\u0430\u043c \u0441\u043e\u0437\u0434\u0430\u0442\u044c PR ![\u0418\u0437\u043e\u0431\u0440\u0430\u0436\u0435\u043d\u0438\u0435 - \u041f\u0440\u0435\u0434\u043b\u043e\u0436\u0435\u043d\u0438\u0435 \u043e \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u0438 PR](/docs/images/github/compare-pull-request-prompt.png) 2. \u041f\u043e \u0443\u043c\u043e\u043b\u0447\u0430\u043d\u0438\u044e \u0432\u0441\u0435 PR \u0441\u043e\u0437\u0434\u0430\u044e\u0442\u0441\u044f \u0432 \u0432\u0435\u0442\u043a\u0443 `master` \u043e\u0441\u043d\u043e\u0432\u043d\u043e\u0433\u043e \u0440\u0435\u043f\u043e\u0437\u0438\u0442\u043e\u0440\u0438\u044f freeCodeCamp \u041f\u0440\u0438 \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u0438 PR, \u0443\u0431\u0435\u0434\u0438\u0442\u0435\u0441\u044c, \u0447\u0442\u043e \u0432 \u043f\u043e\u043b\u0435 \"base fork\" \u0443\u043a\u0430\u0437\u0430\u043d \u0440\u0435\u043f\u043e\u0437\u0438\u0442\u043e\u0440\u0438\u0439 freeCodeCamp/freeCodeCamp ![\u0418\u0437\u043e\u0431\u0440\u0430\u0436\u0435\u043d\u0438\u0435 - \u0421\u0440\u0430\u0432\u043d\u0435\u043d\u0438\u0435 \u0444\u043e\u0440\u043a\u043e\u0432 \u043f\u0440\u0438 \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u0438 PR](/docs/images/github/comparing-forks-for-pull-request.png) 3. \u041d\u0430\u0436\u0430\u0442\u044c \u043d\u0430 \u043a\u043d\u043e\u043f\u043a\u0443 \"Create pull request\", \u0434\u043b\u044f \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u044f PR \u0438\u0437 \u0432\u0430\u0448\u0435\u0439 \u0432\u0435\u0440\u043a\u0438 \u0432 \u0432\u0435\u0442\u043a\u0443 `master` freeCodeCamp. 4. \u0412 \u043f\u043e\u043b\u0435 \u043e\u043f\u0438\u0441\u0430\u043d\u0438\u044f PR \u0434\u043e\u0431\u0430\u0432\u044c\u0442\u0435 \u0431\u043e\u043b\u0435\u0435 \u043f\u043e\u0434\u0440\u043e\u0431\u043d\u044b\u0439 \u043e\u0442\u0447\u0451\u0442 \u0441\u0434\u0435\u043b\u0430\u043d\u043d\u044b\u0445 \u0432\u0430\u043c\u0438 \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u0439 \u0438 \u043f\u0440\u0438\u0447\u0438\u043d\u044b \u043f\u043e \u043a\u043e\u0442\u043e\u0440\u044b\u043c \u043f\u043e\u044f\u0432\u0438\u043b\u0430\u0441\u044c \u0442\u0430\u043a\u0430\u044f \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u043e\u0441\u0442\u044c - \u0412\u0430\u043c \u0431\u0443\u0434\u0435\u0442 \u043f\u0440\u0435\u0434\u043e\u0441\u0442\u0430\u0432\u043b\u0435\u043d \u0448\u0430\u0431\u043b\u043e\u043d, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0441\u043e\u0434\u0435\u0440\u0436\u0438\u0442 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c\u043d\u044b\u0435 \u0441\u043f\u0438\u0441\u043e\u043a \u043f\u0443\u043d\u043a\u0442\u043e\u0432, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0432\u0430\u043c \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u043e \u0432\u044b\u043f\u043e\u043b\u043d\u0438\u0442\u044c, \u043f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u0432\u044b \u0441\u043e\u0437\u0434\u0430\u0434\u0438\u0442\u0435 PR. - \u0417\u0430\u043f\u043e\u043b\u043d\u0438\u0442\u0435 \u044d\u0442\u0438 \u043f\u0443\u043d\u043a\u0442\u044b. \u041e\u043f\u0438\u0440\u0430\u044f\u0441\u044c \u043d\u0430 \u043d\u0438\u0445, \u0431\u0443\u0434\u0435\u0442 \u043f\u0440\u0438\u043d\u0438\u043c\u0430\u0442\u044c\u0441\u044f \u0440\u0435\u0448\u0435\u043d\u0438\u0435 \u043e \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0435\u043d\u0438\u0438 \u0438 \u043f\u0440\u0438\u043d\u044f\u0442\u0438\u0438 \u0432\u0430\u0448\u0435\u0433\u043e PR - \u0415\u0441\u043b\u0438 PR \u043f\u0440\u0435\u0434\u043d\u0430\u0437\u043d\u0430\u0447\u0435\u043d \u0434\u043b\u044f \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u044e\u0449\u0435\u0439 \u043e\u0448\u0438\u0431\u043a\u0438/\u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b, \u0442\u043e \u0432 \u043a\u043e\u043d\u0446\u0435 \u043e\u043f\u0438\u0441\u0430\u043d\u0438\u0435 \u0432\u0430\u0448\u0435\u0433\u043e PR \u0434\u043e\u0431\u0430\u0432\u044c\u0442\u0435 \u043a\u043b\u044e\u0447\u0435\u0432\u043e\u0435 \u0441\u043b\u043e\u0432\u043e `closes` \u0438 #xxxx (\u0433\u0434\u0435 xxxx \u044d\u0442\u043e \u043d\u043e\u043c\u0435\u0440 \u0432\u044b\u043f\u0443\u0441\u043a\u0430). \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440: `closes #1337`. \u0422\u0430\u043a GitHub \u043f\u043e\u0439\u043c\u0451\u0442, \u0447\u0442\u043e \u043f\u0440\u0438 \u0443\u0441\u043f\u0435\u0448\u043d\u043e\u043c \u043f\u0440\u0438\u043d\u044f\u0442\u0438\u0438 PR \u043d\u0443\u0436\u043d\u043e \u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u0438 \u0437\u0430\u043a\u0440\u044b\u0442\u044c Issue \u0441 \u0443\u043a\u0430\u0437\u0430\u043d\u043d\u044b\u043c \u043d\u043e\u043c\u0435\u0440\u043e\u043c 5. \u0423\u043a\u0430\u0436\u0438\u0442\u0435, \u0442\u0435\u0441\u0442\u0438\u0440\u043e\u0432\u0430\u043b\u0438 \u043b\u0438 \u0432\u044b \u043b\u043e\u043a\u0430\u043b\u044c\u043d\u0443\u044e \u043a\u043e\u043f\u0438\u044e \u0441\u0430\u0439\u0442\u0430 \u0438\u043b\u0438 \u043d\u0435\u0442. \u0422\u0435\u0441\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u043e, \u043a\u043e\u0433\u0434\u0430 \u0432\u044b \u043d\u0435 \u043f\u0440\u043e\u0441\u0442\u043e \u043c\u0435\u043d\u044f\u0435\u0442\u0435 \u043a\u0430\u043a\u043e\u0439-\u0442\u043e \u0442\u0435\u043a\u0441\u0442 (\u043d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \u0441\u0442\u0430\u0442\u044c\u044e \u0440\u0443\u043a\u043e\u0432\u043e\u0434\u0441\u0442\u0432\u0430), \u0430 \u0438\u0437\u043c\u0435\u043d\u044f\u0435\u0442\u0435 JavaScript, HTML \u0438\u043b\u0438 CSS \u0444\u0430\u0439\u043b\u044b, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043e\u0433\u0443\u0442 \u0438\u0437\u043c\u0435\u043d\u0438\u0442\u044c \u0444\u0443\u043d\u043a\u0446\u0438\u043e\u043d\u0430\u043b\u044c\u043d\u043e\u0441\u0442\u044c \u0438\u043b\u0438 \u043c\u0430\u043a\u0435\u0442 \u0441\u0442\u0440\u0430\u043d\u0438\u0446\u044b. ", "commid": "freeCodeCamp_pr_37199"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-2e3d81e54fa9b6987665cc5241947f205be6b7c98e01850f679bdf10975bb825", "query": " ", "commid": "freeCodeCamp_pr_28589"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-2e3d81e54fa9b6987665cc5241947f205be6b7c98e01850f679bdf10975bb825", "query": " ", "commid": "freeCodeCamp_pr_28589"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-5710c410b2fdda6888e754827143ecaed3ace3caec9a3a99f3ea92c115376c5c", "query": "n'; const jsCatch = 'n;/*fcc*/n';", "commid": "freeCodeCamp_pr_36714"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-d3f260ddb9ee7fb54e7dd7b7b61ee149a32a2cb18d536f3518a9a61378872b83", "query": "I did not see anyone raising this issue, but I don't think the background of the preview in default or night mode should be anything other than white unless the coding exercise specifically changes the background to something else. The preview should be exactly what you would see in a browser. In almost all the challenges, the background would be white. !\nI share your concerns The reason we changed the color of the display is that a white display is discomforting to the eye on night mode when everything else is dark. so we injected some styles to harmonize the view in general. That convention was carried over to light mode.\nIt might be better to default to white in light mode, same as the editor. As for night mode, some of the css challenges might need some changes to look reasonable in both modes. For instance, in night mode, looks like this: ! If we change the seed code to it would become ! It would have to be case-by-case, though.\nThat is a very good point. I will defer this to\nLogically, I have to agree with - displaying anything other than what the code in the editor would produce might confuse campers. But it is a little rough on the eyes to have the white background on night mode. And the current theme looks a lot better - so it's a tough call. I scrolled through a number of challenges, and there's quite a few that don't look right with the blue background. So there might be a decent amount of work to go through and fix all of them.\nI really like the new theme, but a preview should be a true preview. We want to make this like the real world. Developers working in some kind of night mode on their favorite local editors, still expect to check the \"real\" result of the code they have written on a browser or in a preview mode in their local editors. The night mode should only apply to the editor or the non-preview part of the FCC site. Anything else is just not realistic.\nThe preview should be white.\nI agree with everyone here on this thread. The preview should remain white. Note that soon the preview won't always be there on the right side \"brightening up\" the user interface and ruining people's night mode experience. Soon we will have a single column layout where you the preview only shows up when you click a button to show it, or it loads in a separate tab. - could you update the styling on this so that the preview area is unaffected by our styling?\nDefinitely.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-3abb7b043ccbda9530c7ddaeb7c9f9280eee0a38f6e5c818455c95dd40cd1f54", "text": "[stubTrue, identity] ]); export function concatHtml({ required = [], template, files = [], theme = 'night' } = {}) { theme = theme === '' ? 'night' : theme; export function concatHtml({ required = [], template, files = [] } = {}) { const createBody = template ? _template(template) : defaultTemplate; const displayTheme = theme === 'night' ? nightThemeStyle : ` `; const head = required .map(({ link, src }) => { if (link && src) {", "commid": "freeCodeCamp_pr_36714"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-d3f260ddb9ee7fb54e7dd7b7b61ee149a32a2cb18d536f3518a9a61378872b83", "query": "I did not see anyone raising this issue, but I don't think the background of the preview in default or night mode should be anything other than white unless the coding exercise specifically changes the background to something else. The preview should be exactly what you would see in a browser. In almost all the challenges, the background would be white. !\nI share your concerns The reason we changed the color of the display is that a white display is discomforting to the eye on night mode when everything else is dark. so we injected some styles to harmonize the view in general. That convention was carried over to light mode.\nIt might be better to default to white in light mode, same as the editor. As for night mode, some of the css challenges might need some changes to look reasonable in both modes. For instance, in night mode, looks like this: ! If we change the seed code to it would become ! It would have to be case-by-case, though.\nThat is a very good point. I will defer this to\nLogically, I have to agree with - displaying anything other than what the code in the editor would produce might confuse campers. But it is a little rough on the eyes to have the white background on night mode. And the current theme looks a lot better - so it's a tough call. I scrolled through a number of challenges, and there's quite a few that don't look right with the blue background. So there might be a decent amount of work to go through and fix all of them.\nI really like the new theme, but a preview should be a true preview. We want to make this like the real world. Developers working in some kind of night mode on their favorite local editors, still expect to check the \"real\" result of the code they have written on a browser or in a preview mode in their local editors. The night mode should only apply to the editor or the non-preview part of the FCC site. Anything else is just not realistic.\nThe preview should be white.\nI agree with everyone here on this thread. The preview should remain white. Note that soon the preview won't always be there on the right side \"brightening up\" the user interface and ruining people's night mode experience. Soon we will have a single column layout where you the preview only shows up when you click a button to show it, or it loads in a separate tab. - could you update the styling on this so that the preview area is unaffected by our styling?\nDefinitely.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-ba24aebd423ce9687d72c945e81b257cc9e4dc7aa9ed6ce1c361d7145f6eeb85", "text": "} return ''; }) .reduce((head, element) => head.concat(element), displayTheme); .reduce((head, element) => head.concat(element)); const source = files.reduce( (source, file) => source.concat(file.contents, htmlCatch),", "commid": "freeCodeCamp_pr_36714"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-d3f260ddb9ee7fb54e7dd7b7b61ee149a32a2cb18d536f3518a9a61378872b83", "query": "I did not see anyone raising this issue, but I don't think the background of the preview in default or night mode should be anything other than white unless the coding exercise specifically changes the background to something else. The preview should be exactly what you would see in a browser. In almost all the challenges, the background would be white. !\nI share your concerns The reason we changed the color of the display is that a white display is discomforting to the eye on night mode when everything else is dark. so we injected some styles to harmonize the view in general. That convention was carried over to light mode.\nIt might be better to default to white in light mode, same as the editor. As for night mode, some of the css challenges might need some changes to look reasonable in both modes. For instance, in night mode, looks like this: ! If we change the seed code to it would become ! It would have to be case-by-case, though.\nThat is a very good point. I will defer this to\nLogically, I have to agree with - displaying anything other than what the code in the editor would produce might confuse campers. But it is a little rough on the eyes to have the white background on night mode. And the current theme looks a lot better - so it's a tough call. I scrolled through a number of challenges, and there's quite a few that don't look right with the blue background. So there might be a decent amount of work to go through and fix all of them.\nI really like the new theme, but a preview should be a true preview. We want to make this like the real world. Developers working in some kind of night mode on their favorite local editors, still expect to check the \"real\" result of the code they have written on a browser or in a preview mode in their local editors. The night mode should only apply to the editor or the non-preview part of the FCC site. Anything else is just not realistic.\nThe preview should be white.\nI agree with everyone here on this thread. The preview should remain white. Note that soon the preview won't always be there on the right side \"brightening up\" the user interface and ruining people's night mode experience. Soon we will have a single column layout where you the preview only shows up when you click a button to show it, or it loads in a separate tab. - could you update the styling on this so that the preview area is unaffected by our styling?\nDefinitely.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-7c5a09a75181c7e8dd97b6d1e70dfd0d190d36ca28c7716b840a16189ce02dbd", "text": " export const nightThemeStyle = ` `; ", "commid": "freeCodeCamp_pr_36714"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-d3f260ddb9ee7fb54e7dd7b7b61ee149a32a2cb18d536f3518a9a61378872b83", "query": "I did not see anyone raising this issue, but I don't think the background of the preview in default or night mode should be anything other than white unless the coding exercise specifically changes the background to something else. The preview should be exactly what you would see in a browser. In almost all the challenges, the background would be white. !\nI share your concerns The reason we changed the color of the display is that a white display is discomforting to the eye on night mode when everything else is dark. so we injected some styles to harmonize the view in general. That convention was carried over to light mode.\nIt might be better to default to white in light mode, same as the editor. As for night mode, some of the css challenges might need some changes to look reasonable in both modes. For instance, in night mode, looks like this: ! If we change the seed code to it would become ! It would have to be case-by-case, though.\nThat is a very good point. I will defer this to\nLogically, I have to agree with - displaying anything other than what the code in the editor would produce might confuse campers. But it is a little rough on the eyes to have the white background on night mode. And the current theme looks a lot better - so it's a tough call. I scrolled through a number of challenges, and there's quite a few that don't look right with the blue background. So there might be a decent amount of work to go through and fix all of them.\nI really like the new theme, but a preview should be a true preview. We want to make this like the real world. Developers working in some kind of night mode on their favorite local editors, still expect to check the \"real\" result of the code they have written on a browser or in a preview mode in their local editors. The night mode should only apply to the editor or the non-preview part of the FCC site. Anything else is just not realistic.\nThe preview should be white.\nI agree with everyone here on this thread. The preview should remain white. Note that soon the preview won't always be there on the right side \"brightening up\" the user interface and ruining people's night mode experience. Soon we will have a single column layout where you the preview only shows up when you click a button to show it, or it loads in a separate tab. - could you update the styling on this so that the preview area is unaffected by our styling?\nDefinitely.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-1b23c12b7149f68541048a0d82b9d38f6e6f4cddcae8cd3bd64ba8082b4e93e2", "text": "import { createExecuteChallengeSaga } from './execute-challenge-saga'; import { createCurrentChallengeSaga } from './current-challenge-saga'; import { challengeTypes } from '../../../../utils/challengeTypes'; import { userSelector } from '../../../redux'; export const ns = 'challenge'; export const backendNS = 'backendChallenge';", "commid": "freeCodeCamp_pr_36714"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-d3f260ddb9ee7fb54e7dd7b7b61ee149a32a2cb18d536f3518a9a61378872b83", "query": "I did not see anyone raising this issue, but I don't think the background of the preview in default or night mode should be anything other than white unless the coding exercise specifically changes the background to something else. The preview should be exactly what you would see in a browser. In almost all the challenges, the background would be white. !\nI share your concerns The reason we changed the color of the display is that a white display is discomforting to the eye on night mode when everything else is dark. so we injected some styles to harmonize the view in general. That convention was carried over to light mode.\nIt might be better to default to white in light mode, same as the editor. As for night mode, some of the css challenges might need some changes to look reasonable in both modes. For instance, in night mode, looks like this: ! If we change the seed code to it would become ! It would have to be case-by-case, though.\nThat is a very good point. I will defer this to\nLogically, I have to agree with - displaying anything other than what the code in the editor would produce might confuse campers. But it is a little rough on the eyes to have the white background on night mode. And the current theme looks a lot better - so it's a tough call. I scrolled through a number of challenges, and there's quite a few that don't look right with the blue background. So there might be a decent amount of work to go through and fix all of them.\nI really like the new theme, but a preview should be a true preview. We want to make this like the real world. Developers working in some kind of night mode on their favorite local editors, still expect to check the \"real\" result of the code they have written on a browser or in a preview mode in their local editors. The night mode should only apply to the editor or the non-preview part of the FCC site. Anything else is just not realistic.\nThe preview should be white.\nI agree with everyone here on this thread. The preview should remain white. Note that soon the preview won't always be there on the right side \"brightening up\" the user interface and ruining people's night mode experience. Soon we will have a single column layout where you the preview only shows up when you click a button to show it, or it loads in a separate tab. - could you update the styling on this so that the preview area is unaffected by our styling?\nDefinitely.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-04c240b9afba40f7033c9dcc432a1690895c32a5bf2468cf0046fb719ec5d0ce", "text": "state[ns].projectFormValues || {}; export const challengeDataSelector = state => { const { theme } = userSelector(state); const { challengeType } = challengeMetaSelector(state); let challengeData = { challengeType }; if (", "commid": "freeCodeCamp_pr_36714"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-d3f260ddb9ee7fb54e7dd7b7b61ee149a32a2cb18d536f3518a9a61378872b83", "query": "I did not see anyone raising this issue, but I don't think the background of the preview in default or night mode should be anything other than white unless the coding exercise specifically changes the background to something else. The preview should be exactly what you would see in a browser. In almost all the challenges, the background would be white. !\nI share your concerns The reason we changed the color of the display is that a white display is discomforting to the eye on night mode when everything else is dark. so we injected some styles to harmonize the view in general. That convention was carried over to light mode.\nIt might be better to default to white in light mode, same as the editor. As for night mode, some of the css challenges might need some changes to look reasonable in both modes. For instance, in night mode, looks like this: ! If we change the seed code to it would become ! It would have to be case-by-case, though.\nThat is a very good point. I will defer this to\nLogically, I have to agree with - displaying anything other than what the code in the editor would produce might confuse campers. But it is a little rough on the eyes to have the white background on night mode. And the current theme looks a lot better - so it's a tough call. I scrolled through a number of challenges, and there's quite a few that don't look right with the blue background. So there might be a decent amount of work to go through and fix all of them.\nI really like the new theme, but a preview should be a true preview. We want to make this like the real world. Developers working in some kind of night mode on their favorite local editors, still expect to check the \"real\" result of the code they have written on a browser or in a preview mode in their local editors. The night mode should only apply to the editor or the non-preview part of the FCC site. Anything else is just not realistic.\nThe preview should be white.\nI agree with everyone here on this thread. The preview should remain white. Note that soon the preview won't always be there on the right side \"brightening up\" the user interface and ruining people's night mode experience. Soon we will have a single column layout where you the preview only shows up when you click a button to show it, or it loads in a separate tab. - could you update the styling on this so that the preview area is unaffected by our styling?\nDefinitely.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-74eee25e108173bb75e88790317ac0502b6ba88daa71f00b1744172c94fcebca", "text": "template }; } challengeData.theme = theme; return challengeData; };", "commid": "freeCodeCamp_pr_36714"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-d3f260ddb9ee7fb54e7dd7b7b61ee149a32a2cb18d536f3518a9a61378872b83", "query": "I did not see anyone raising this issue, but I don't think the background of the preview in default or night mode should be anything other than white unless the coding exercise specifically changes the background to something else. The preview should be exactly what you would see in a browser. In almost all the challenges, the background would be white. !\nI share your concerns The reason we changed the color of the display is that a white display is discomforting to the eye on night mode when everything else is dark. so we injected some styles to harmonize the view in general. That convention was carried over to light mode.\nIt might be better to default to white in light mode, same as the editor. As for night mode, some of the css challenges might need some changes to look reasonable in both modes. For instance, in night mode, looks like this: ! If we change the seed code to it would become ! It would have to be case-by-case, though.\nThat is a very good point. I will defer this to\nLogically, I have to agree with - displaying anything other than what the code in the editor would produce might confuse campers. But it is a little rough on the eyes to have the white background on night mode. And the current theme looks a lot better - so it's a tough call. I scrolled through a number of challenges, and there's quite a few that don't look right with the blue background. So there might be a decent amount of work to go through and fix all of them.\nI really like the new theme, but a preview should be a true preview. We want to make this like the real world. Developers working in some kind of night mode on their favorite local editors, still expect to check the \"real\" result of the code they have written on a browser or in a preview mode in their local editors. The night mode should only apply to the editor or the non-preview part of the FCC site. Anything else is just not realistic.\nThe preview should be white.\nI agree with everyone here on this thread. The preview should remain white. Note that soon the preview won't always be there on the right side \"brightening up\" the user interface and ruining people's night mode experience. Soon we will have a single column layout where you the preview only shows up when you click a button to show it, or it loads in a separate tab. - could you update the styling on this so that the preview area is unaffected by our styling?\nDefinitely.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-cf81084053f70aa409efca5b5fae125edbe7a3926613ed950e9fdfe0a81ae0de", "text": "runTestInTestFrame(document, testString, testTimeout); } export function buildDOMChallenge({ files, required = [], template = '', theme = `` }) { export function buildDOMChallenge({ files, required = [], template = '' }) { const finalRequires = [...globalRequires, ...required, ...frameRunner]; const loadEnzyme = Object.keys(files).some(key => files[key].ext === 'jsx'); const toHtml = [jsToHtml, cssToHtml];", "commid": "freeCodeCamp_pr_36714"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-d3f260ddb9ee7fb54e7dd7b7b61ee149a32a2cb18d536f3518a9a61378872b83", "query": "I did not see anyone raising this issue, but I don't think the background of the preview in default or night mode should be anything other than white unless the coding exercise specifically changes the background to something else. The preview should be exactly what you would see in a browser. In almost all the challenges, the background would be white. !\nI share your concerns The reason we changed the color of the display is that a white display is discomforting to the eye on night mode when everything else is dark. so we injected some styles to harmonize the view in general. That convention was carried over to light mode.\nIt might be better to default to white in light mode, same as the editor. As for night mode, some of the css challenges might need some changes to look reasonable in both modes. For instance, in night mode, looks like this: ! If we change the seed code to it would become ! It would have to be case-by-case, though.\nThat is a very good point. I will defer this to\nLogically, I have to agree with - displaying anything other than what the code in the editor would produce might confuse campers. But it is a little rough on the eyes to have the white background on night mode. And the current theme looks a lot better - so it's a tough call. I scrolled through a number of challenges, and there's quite a few that don't look right with the blue background. So there might be a decent amount of work to go through and fix all of them.\nI really like the new theme, but a preview should be a true preview. We want to make this like the real world. Developers working in some kind of night mode on their favorite local editors, still expect to check the \"real\" result of the code they have written on a browser or in a preview mode in their local editors. The night mode should only apply to the editor or the non-preview part of the FCC site. Anything else is just not realistic.\nThe preview should be white.\nI agree with everyone here on this thread. The preview should remain white. Note that soon the preview won't always be there on the right side \"brightening up\" the user interface and ruining people's night mode experience. Soon we will have a single column layout where you the preview only shows up when you click a button to show it, or it loads in a separate tab. - could you update the styling on this so that the preview area is unaffected by our styling?\nDefinitely.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-65ec91f62e7310d3b83225065fe14adec18279b15ee2b9b658438a4b7a49b35a", "text": ".then(checkFilesErrors) .then(files => ({ challengeType: challengeTypes.html, build: concatHtml({ required: finalRequires, template, files, theme }), build: concatHtml({ required: finalRequires, template, files }), sources: buildSourceMap(files), loadEnzyme }));", "commid": "freeCodeCamp_pr_36714"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-4e32b4aa53c0c39e8c176aae90836e946bbc9e46c6898b5f9216b8b1522f24fe", "query": "Is there a reason the certifications have an apparent margin above them? ! It's bigger with a taller viewport. Seems like there should be no margin there.", "positive_passages": [{"docid": "doc-en-freeCodeCamp-a73a1e9b2818fefd9ee1a3b11edc04659895bb4f84cf26306503358ecbf69f16", "text": "} .certification-namespace.certificate-wrapper { top: calc(100vh / 20); position: relative; font-family: 'Sax Mono', monospace; }", "commid": "freeCodeCamp_pr_36755"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-5e5ba63eb6171f205e0cd48090b59b21276c34252b08812900ee182be92990ef", "query": "\"Screen Col Col, Row } from '@freecodecamp/react-bootstrap'; import Helmet from 'react-helmet';", "commid": "freeCodeCamp_pr_37096"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-5e5ba63eb6171f205e0cd48090b59b21276c34252b08812900ee182be92990ef", "query": "\"Screen const placeholderText = `Please provide as much detail as possible about the account or behavior you are reporting.`; return ( Report a users profile | freeCodeCamp.org

Do you want to report {username} 's profile for abuse?

We will notify the community moderators' team, and a send copy of this report to your email:{' '} {email}. this report to your email: {email}

We may get back to you for more information, if required.

Additional Information What would you like to report? placeholder='' placeholder={placeholderText} value={textarea} />
); }", "commid": "freeCodeCamp_pr_37096"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-a3634e7457c9bdaf867d6baf35042d84308c7b4bb127642bb64333d94ea57729", "query": "Is there any reason not to put the real and in ? I reflexively put in a dummy key when I set this up, but now that I revisit this, that seems like a mistake.\nYes, actually it broke the .dev build unsurprisingly , I think noticed it and reported in the team chat. My bad for not catching this previously. The real fix is to ignore and move ahead when the keys are not available are default. We do this with google application credentials.\nOh, I assume it broke the build because .dev isn't using I didn't think of that... So, we should implement the fix and add the public keys to , right?\nI was thinking something more along the lines of (example from api-server): I would try to avoid hundreds of contributors hitting the indexes locally. Ideally people should get their own keys. While the key and index is public, it's still not recommended to hit it?\nAs for the production keys, it's actually fine because the build should fail. I have since the keys in the build pipeline.\nOne thing: if we don't want contributors spamming search (fair enough!) I think there should be some docs that let people know what's what. Either that search isn't available in development or the steps they need to take to make it work.\nI agree. We should add some docs on getting keys, or perhaps creating a test index and sharing that instead", "positive_passages": [{"docid": "doc-en-freeCodeCamp-0df06ecd356f761024e8a2263f6865fa5e6359968ce44198c7095f31d93959da", "text": " require('dotenv').config(); const env = require('../config/env'); const { createFilePath } = require('gatsby-source-filesystem');", "commid": "freeCodeCamp_pr_37088"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-a3634e7457c9bdaf867d6baf35042d84308c7b4bb127642bb64333d94ea57729", "query": "Is there any reason not to put the real and in ? I reflexively put in a dummy key when I set this up, but now that I revisit this, that seems like a mistake.\nYes, actually it broke the .dev build unsurprisingly , I think noticed it and reported in the team chat. My bad for not catching this previously. The real fix is to ignore and move ahead when the keys are not available are default. We do this with google application credentials.\nOh, I assume it broke the build because .dev isn't using I didn't think of that... So, we should implement the fix and add the public keys to , right?\nI was thinking something more along the lines of (example from api-server): I would try to avoid hundreds of contributors hitting the indexes locally. Ideally people should get their own keys. While the key and index is public, it's still not recommended to hit it?\nAs for the production keys, it's actually fine because the build should fail. I have since the keys in the build pipeline.\nOne thing: if we don't want contributors spamming search (fair enough!) I think there should be some docs that let people know what's what. Either that search isn't available in development or the steps they need to take to make it work.\nI agree. We should add some docs on getting keys, or perhaps creating a test index and sharing that instead", "positive_passages": [{"docid": "doc-en-freeCodeCamp-1ea56a9fb4e831fd1fa52fc7595d5e8d7a6d4a2f64bf0738b32b8c89924878d0", "text": "} }; exports.createPages = function createPages({ graphql, actions }) { exports.createPages = function createPages({ graphql, actions, reporter }) { if (!env.algoliaAPIKey || !env.algoliaAppId) { if (process.env.FREECODECAMP_NODE_ENV === 'production') { throw new Error( 'Algolia App id and API key are required to start the client!' ); } else { reporter.info( 'Algolia keys missing or invalid. Required for search to yield results.' ); } } const { createPage } = actions; return new Promise((resolve, reject) => {", "commid": "freeCodeCamp_pr_37088"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-a3634e7457c9bdaf867d6baf35042d84308c7b4bb127642bb64333d94ea57729", "query": "Is there any reason not to put the real and in ? I reflexively put in a dummy key when I set this up, but now that I revisit this, that seems like a mistake.\nYes, actually it broke the .dev build unsurprisingly , I think noticed it and reported in the team chat. My bad for not catching this previously. The real fix is to ignore and move ahead when the keys are not available are default. We do this with google application credentials.\nOh, I assume it broke the build because .dev isn't using I didn't think of that... So, we should implement the fix and add the public keys to , right?\nI was thinking something more along the lines of (example from api-server): I would try to avoid hundreds of contributors hitting the indexes locally. Ideally people should get their own keys. While the key and index is public, it's still not recommended to hit it?\nAs for the production keys, it's actually fine because the build should fail. I have since the keys in the build pipeline.\nOne thing: if we don't want contributors spamming search (fair enough!) I think there should be some docs that let people know what's what. Either that search isn't available in development or the steps they need to take to make it work.\nI agree. We should add some docs on getting keys, or perhaps creating a test index and sharing that instead", "positive_passages": [{"docid": "doc-en-freeCodeCamp-5385a4cf50009d67cc7ebe4fb9a32a634a980bad4072d081f79d8192a9eb6af0", "text": "const DEBOUNCE_TIME = 100; const searchClient = algoliasearch(algoliaAppId, algoliaAPIKey); // If a key is missing, searches will fail, but the client will still render. const searchClient = algoliaAppId && algoliaAPIKey ? algoliasearch(algoliaAppId, algoliaAPIKey) : {}; const propTypes = { children: PropTypes.any,", "commid": "freeCodeCamp_pr_37088"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-a3634e7457c9bdaf867d6baf35042d84308c7b4bb127642bb64333d94ea57729", "query": "Is there any reason not to put the real and in ? I reflexively put in a dummy key when I set this up, but now that I revisit this, that seems like a mistake.\nYes, actually it broke the .dev build unsurprisingly , I think noticed it and reported in the team chat. My bad for not catching this previously. The real fix is to ignore and move ahead when the keys are not available are default. We do this with google application credentials.\nOh, I assume it broke the build because .dev isn't using I didn't think of that... So, we should implement the fix and add the public keys to , right?\nI was thinking something more along the lines of (example from api-server): I would try to avoid hundreds of contributors hitting the indexes locally. Ideally people should get their own keys. While the key and index is public, it's still not recommended to hit it?\nAs for the production keys, it's actually fine because the build should fail. I have since the keys in the build pipeline.\nOne thing: if we don't want contributors spamming search (fair enough!) I think there should be some docs that let people know what's what. Either that search isn't available in development or the steps they need to take to make it work.\nI agree. We should add some docs on getting keys, or perhaps creating a test index and sharing that instead", "positive_passages": [{"docid": "doc-en-freeCodeCamp-8e3cad7c916cc8a5feb2994f6a35c013aa7a6c9b13a7cb860dd6ec126ad8b00f", "text": "module.exports = Object.assign(locations, { locale, stripePublicKey, algoliaAppId, algoliaAPIKey algoliaAppId: !algoliaAppId || algoliaAppId === 'Algolia app id from dashboard' ? null : algoliaAppId, algoliaAPIKey: !algoliaAPIKey || algoliaAPIKey === 'Algolia api key from dashboard' ? null : algoliaAPIKey });", "commid": "freeCodeCamp_pr_37088"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-a3634e7457c9bdaf867d6baf35042d84308c7b4bb127642bb64333d94ea57729", "query": "Is there any reason not to put the real and in ? I reflexively put in a dummy key when I set this up, but now that I revisit this, that seems like a mistake.\nYes, actually it broke the .dev build unsurprisingly , I think noticed it and reported in the team chat. My bad for not catching this previously. The real fix is to ignore and move ahead when the keys are not available are default. We do this with google application credentials.\nOh, I assume it broke the build because .dev isn't using I didn't think of that... So, we should implement the fix and add the public keys to , right?\nI was thinking something more along the lines of (example from api-server): I would try to avoid hundreds of contributors hitting the indexes locally. Ideally people should get their own keys. While the key and index is public, it's still not recommended to hit it?\nAs for the production keys, it's actually fine because the build should fail. I have since the keys in the build pipeline.\nOne thing: if we don't want contributors spamming search (fair enough!) I think there should be some docs that let people know what's what. Either that search isn't available in development or the steps they need to take to make it work.\nI agree. We should add some docs on getting keys, or perhaps creating a test index and sharing that instead", "positive_passages": [{"docid": "doc-en-freeCodeCamp-65a5e8c8273ce3def9c99c8d98308b51b2ea66f8a05f4b5a957ab573fab165b8", "text": "ROLLBAR_CLIENT_ID='post_client_id from rollbar dashboard' ALGOLIA_ADMIN_KEY=123abc ALGOLIA_APP_ID=ACDEFG ALGOLIA_API_KEY=123abc ALGOLIA_APP_ID='Algolia app id from dashboard' ALGOLIA_API_KEY='Algolia api key from dashboard' AUTH0_CLIENT_ID=stuff AUTH0_CLIENT_SECRET=stuff", "commid": "freeCodeCamp_pr_37088"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-6ec8e735d85c760ded6043928d47078eb9725564268f3a009878b9599a8f4e71", "query": "The font size for the CTA could use similar breakpoints for the h1, h2. and set to 1.2 - 1.3 rem !\nI'd like to work on this.\ncan i?\nWhere is this button?", "positive_passages": [{"docid": "doc-en-freeCodeCamp-068ef6036b4a5ca5758546e51f00d0d0714d3a06871404f050946bccbf398e98", "text": "h3 { font-size: 1rem; } .btn-cta { font-size: 1.2rem; } } .text-center {", "commid": "freeCodeCamp_pr_37201"}], "negative_passages": []} +{"query_id": "q-en-freeCodeCamp-a47984b70ae1ef6bb7963849482a42e0b10827f8e615a2a12ffad81d716028aa", "query": "