mirror of
https://github.com/Raghu-Ch/angular-challenges.git
synced 2026-02-10 12:53:03 -05:00
fix: more typos
This commit is contained in:
@@ -36,13 +36,13 @@ import MyIcon from './MyIcon.astro';
|
||||
display: flex;
|
||||
flex-direction: column;
|
||||
gap: 0.7rem;
|
||||
margin-bottom: 10px;
|
||||
margin-bottom: 10px;
|
||||
}
|
||||
|
||||
.button-sponsor {
|
||||
background-color: red;
|
||||
border-color: red;
|
||||
color: write;
|
||||
color: white;
|
||||
}
|
||||
|
||||
</style>
|
||||
@@ -20,7 +20,6 @@ In this application, we retrieve three pieces of information inside our `TestCom
|
||||
In Angular versions 15 or earlier, we use `ActivatedRoute` to obtain all this information and receive them through observables to listen for URL changes.
|
||||
|
||||
In version 16, Angular introduced a new `Input` that can listen to route data. You can read more about it [here](https://medium.com/ngconf/accessing-route-params-in-angular-1f8e12770617).
|
||||
.
|
||||
|
||||
## Statement
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@ WIP: The following documentation will be reviewed and improved. However, you can
|
||||
|
||||
Angular offer the static function **ngTemplateContextGuard** to strongly type structural directive.
|
||||
|
||||
However the context of **NgTemplateOutlet** type is **Object**. But which the help of the above guard, we can improve that behavior.
|
||||
However the context of **NgTemplateOutlet** type is **Object**. But with the help of the above guard, we can improve that behavior.
|
||||
|
||||
## Statement
|
||||
|
||||
@@ -41,4 +41,4 @@ Currently we have the following piece of code.
|
||||
|
||||
As we can see, student is of type "any". We want to infer the correct type.
|
||||
|
||||
But in this part, we can pass to ListComponent, a list of **any object**. And we still want the correct type to be infered.
|
||||
But in this part, we can pass to ListComponent, a list of **any object**. And we still want the correct type to be inferred.
|
||||
|
||||
@@ -54,4 +54,4 @@ this.todos = [...this.todos.filter((t) => t.id !== todoUpdated.id), todoUpdated]
|
||||
### Step 4: Awesomeness!!! master your state.
|
||||
|
||||
- Use the **component store of ngrx** as a local state of your component. _(or any other 3rd Party lib)_
|
||||
- Have a **localize** Loading/Error indicator, e.g. only on the Todo being processed and **disable** all buttons of the processed Todo. _(Hint: you will need to create an ItemComponent)_
|
||||
- Have a **localized** Loading/Error indicator, e.g. only on the Todo being processed and **disable** all buttons of the processed Todo. _(Hint: you will need to create an ItemComponent)_
|
||||
|
||||
@@ -20,5 +20,5 @@ The goal is to test the functionality of `child.component.ts`. I have prepared a
|
||||
|
||||
**Note:** You are welcome to use Testing Library if you wish.
|
||||
|
||||
Documentation for CDK Component Harness is [here](https://material.angular.io/cdk/test-harnesses/overview#api-for-test-authors)
|
||||
Documentation for Angular Material component is [here](https://material.angular.io/components/button/overview)
|
||||
Documentation for CDK Component Harness is [here](https://material.angular.io/cdk/test-harnesses/overview#api-for-test-authors).
|
||||
Documentation for Angular Material component is [here](https://material.angular.io/components/button/overview).
|
||||
|
||||
@@ -43,7 +43,7 @@ import MyIcon from '../../components/MyIcon.astro';
|
||||
challenges provides real-world use cases to apply what you've been learning.
|
||||
Anyone can comment or offer assistance.
|
||||
<b>
|
||||
Learning alone is great, but learning alongside others will get you farer.
|
||||
Learning alone is great, but learning alongside others will get you further.
|
||||
</b>
|
||||
</Card>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user