mirror of
https://github.com/freeCodeCamp/freeCodeCamp.git
synced 2026-02-27 20:02:15 -05:00
fix(curriculum): remove duplicated words (#58163)
This commit is contained in:
@@ -334,7 +334,7 @@ textarea.inputarea {
|
||||
bottom: var(--monaco-scrollbar-arrow-icon-top-bottom) !important;
|
||||
}
|
||||
|
||||
/* we can live with with no color change for hover state if browser doesn't
|
||||
/* we can live with no color change for hover state if browser doesn't
|
||||
support :has (the mouse cursor will still change to pointer) */
|
||||
@supports (selector(html:has(body))) {
|
||||
.vs .monaco-scrollable-element .scrollbar .arrow-background:hover,
|
||||
|
||||
@@ -221,7 +221,7 @@ function Hotkeys({
|
||||
: {})
|
||||
};
|
||||
// GlobalHotKeys is always mounted and tracks all keypresses. Without it,
|
||||
// keyup events can be missed and react-hotkeys assumes that that key is still
|
||||
// keyup events can be missed and react-hotkeys assumes that key is still
|
||||
// being pressed.
|
||||
// allowChanges is necessary if the handlers depend on props (in this case
|
||||
// canFocusEditor)
|
||||
|
||||
@@ -21,7 +21,7 @@ You should chain the `addEventListener()` method to your `audio` variable.
|
||||
assert.match(code, /audio\.addEventListener\(/)
|
||||
```
|
||||
|
||||
The event listener you used on on your `audio` variable should listen for an `"ended"` event.
|
||||
The event listener you used on your `audio` variable should listen for an `"ended"` event.
|
||||
|
||||
```js
|
||||
assert.match(code, /audio\.addEventListener\(\s*('|")ended\1/)
|
||||
|
||||
@@ -10,7 +10,7 @@ dashedName: problem-165-intersections
|
||||
|
||||
A segment is uniquely defined by its two endpoints. By considering two line segments in plane geometry there are three possibilities: the segments have zero points, one point, or infinitely many points in common.
|
||||
|
||||
Moreover when two segments have exactly one point in common it might be the case that that common point is an endpoint of either one of the segments or of both. If a common point of two segments is not an endpoint of either of the segments it is an interior point of both segments.
|
||||
Moreover when two segments have exactly one point in common it might be the case that common point is an endpoint of either one of the segments or of both. If a common point of two segments is not an endpoint of either of the segments it is an interior point of both segments.
|
||||
|
||||
We will call a common point $T$ of two segments $L_1$ and $L_2$ a true intersection point of $L_1$ and $L_2$ if $T$ is the only common point of $L_1$ and $L_2$ and $T$ is an interior point of both segments.
|
||||
|
||||
|
||||
@@ -21,7 +21,7 @@ Child 2: snake
|
||||
|
||||
# --instructions--
|
||||
|
||||
Write a function that takes an input array of words. The function should return an array of words where the first letter of each word is the same as the last letter of the previous word. Only use the words in the input array, and once a word is used it cannot be repeated. The words in the return array should be selected and sequenced so that that its length is maximized.
|
||||
Write a function that takes an input array of words. The function should return an array of words where the first letter of each word is the same as the last letter of the previous word. Only use the words in the input array, and once a word is used it cannot be repeated. The words in the return array should be selected and sequenced so that its length is maximized.
|
||||
|
||||
# --hints--
|
||||
|
||||
|
||||
@@ -37,7 +37,7 @@ This word refers to the ongoing or current moment in which events happen.
|
||||
|
||||
The phrase `in real time` refers to something happening immediately as events occur, without delay. It is often used in the context of monitoring, communication, or data processing. For example:
|
||||
|
||||
`The system updates the dashboard in real time, so you can see changes instantly.` - Meaning the dashboard changes immediately after the updates after the updates are applied.
|
||||
`The system updates the dashboard in real time, so you can see changes instantly.` - Meaning the dashboard changes immediately after the updates are applied.
|
||||
|
||||
In Jake's sentence, he means that while he checked for security vulnerabilities, it wasn't always done immediately as the updates happened.
|
||||
|
||||
|
||||
@@ -49,4 +49,4 @@ This sentence is in the `Present Simple` tense, not the `Present Perfect continu
|
||||
|
||||
# --explanation--
|
||||
|
||||
The negative form of the `Present Perfect continuous` tense tense is created with `hasn't/haven't + been + present participle`. It describes an ongoing action that started in the past and continues or remains relevant but hasn't occurred as expected.
|
||||
The negative form of the `Present Perfect continuous` tense is created with `hasn't/haven't + been + present participle`. It describes an ongoing action that started in the past and continues or remains relevant but hasn't occurred as expected.
|
||||
|
||||
@@ -16,7 +16,7 @@ Fulfill the user stories below and get all the tests to pass to complete the lab
|
||||
1. You should declare a variable `num` and assign it a number of your choice. The assigned number should be between `1` and `20` inclusive.
|
||||
1. Create a function named `factorialCalculator` that takes a number as an argument and returns the factorial of that number.
|
||||
1. Inside the function, declare a `result` variable and assign it the value of `1`. Using a loop, loop through all numbers from `1` to the input number(inclusive) and for each number, multiply the `result` variable by the current number and assign the result to the `result` variable. You can choose to use either a `for` loop, `while` loop or `do...while` loop here.
|
||||
1. You should call the `factorialCalculator` function with with `num` as the argument and assign the result to the variable `factorial`.
|
||||
1. You should call the `factorialCalculator` function with `num` as the argument and assign the result to the variable `factorial`.
|
||||
1. You should store the final output in the format `Factorial of [num] is [factorial]` and assign it to the variable `resultMsg`.
|
||||
1. You should output the value of `resultMsg` to the console.
|
||||
|
||||
|
||||
@@ -90,7 +90,7 @@ Why is it important to keep the footer accessible while using an infinite scroll
|
||||
|
||||
## --answers--
|
||||
|
||||
It helps make the make the colors stand out more on the page.
|
||||
It helps make the colors stand out more on the page.
|
||||
|
||||
### --feedback--
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ This is easier said than done. Most people who start this curriculum will at som
|
||||
|
||||
Tip number 2: routine is your friend. If you make a habit of waking up 30 minutes earlier every day, you can get in a coding session before you go to work. After a few weeks of doing this, it just becomes part of your routine. You don't really have to think too much about it, or expend any additional willpower. It's just something that you do.
|
||||
|
||||
Now, I understand that you're probably busy. I wish I could tell you that there was just some magic book that you could buy, and that that would be enough. The reason buying a book feels so good is that it feels like you're also buying the time to read it. But there's no magic involved in learning to code. You've got to put in the time. You've got to put in the reps at the keyboard.
|
||||
Now, I understand that you're probably busy. I wish I could tell you that there was just some magic book that you could buy, and that would be enough. The reason buying a book feels so good is that it feels like you're also buying the time to read it. But there's no magic involved in learning to code. You've got to put in the time. You've got to put in the reps at the keyboard.
|
||||
|
||||
I'll tell you this: if you can code for even 30 minutes a day, you're going to make serious gains over the course of a year.
|
||||
|
||||
|
||||
@@ -13,7 +13,7 @@ All the core functionalities are now in place. The only issue now is that the ne
|
||||
|
||||
To fix that, you can set up an event listener which will detect when the currently playing song ends. The `"ended"` event listener is appropriate for this. It is fired when the playback of a media reaches the end.
|
||||
|
||||
Add an event listener to the `audio` element which listens for the `"ended"` event and pass in a a reference to the `playNextSong` function. With that the music player project is complete!
|
||||
Add an event listener to the `audio` element which listens for the `"ended"` event and pass in a reference to the `playNextSong` function. With that the music player project is complete!
|
||||
|
||||
# --hints--
|
||||
|
||||
@@ -23,7 +23,7 @@ You should chain the `addEventListener()` method to your `audio` variable.
|
||||
assert.match(__helpers.removeJSComments(code), /audio\.addEventListener\(/)
|
||||
```
|
||||
|
||||
The event listener you used on on your `audio` variable should listen for an `"ended"` event.
|
||||
The event listener you used on your `audio` variable should listen for an `"ended"` event.
|
||||
|
||||
```js
|
||||
assert.match(__helpers.removeJSComments(code), /audio\.addEventListener\(\s*('|")ended\1/)
|
||||
|
||||
@@ -27,7 +27,7 @@ Your `wordCount` variable should be set to the result of `getWordCount("I love f
|
||||
assert.equal(wordCount, getWordCount("I love freeCodeCamp"));
|
||||
```
|
||||
|
||||
You should log the `wordCount` variable to the console with the parameter `"Word Count Count: ${wordCount}"`.
|
||||
You should log the `wordCount` variable to the console with the parameter `"Word Count: ${wordCount}"`.
|
||||
|
||||
```js
|
||||
assert.match(code, /console\.log\((?:('|"|`)Word\s+Count:\s+('|"|`)\s+\+\s+wordCount|`Word\s+Count:\s+\${wordCount}`)\);?/)
|
||||
|
||||
Reference in New Issue
Block a user