vcgit-forge/angular-challenges
1
0
Fork 0
mirror of https://github.com/Raghu-Ch/angular-challenges.git synced 2026-02-10 12:53:03 -05:00
Code Issues Packages Projects Releases Wiki Activity

docs: improve readme file

Browse Source
This commit is contained in:
Devesh
2023-10-17 08:38:06 +05:30
parent da77f4160d
commit b62c151794
2 changed files with 18 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
apps/rxjs-catch-error/src/app/app.component.ts
View File

@@ -38,11 +38,11 @@ export class AppComponent {
ngOnInit() { ngOnInit() {
this.submit$$ this.submit$$
.pipe( .pipe(
takeUntilDestroyed(this.destroyRef),
map(() => this.input), map(() => this.input),
concatMap((value) => concatMap((value) =>
this.http.get(`https://jsonplaceholder.typicode.com/${value}/1`) this.http.get(`https://jsonplaceholder.typicode.com/${value}/1`)
) ),
takeUntilDestroyed(this.destroyRef)
) )
.subscribe({ .subscribe({
next: (value) => { next: (value) => {

39
docs/src/content/docs/challenges/rxjs/38-rxjs-catch-error.md
View File

@@ -1,12 +1,22 @@
--- ---
title: 🟢 catchError title: 🟢 catchError
description: Challenge 38 is about learning obervable completion. description: Challenge 38 is about learning obervable
completion.
Author: Devesh Chaudhari
command: rxjs-catch-error
challengeNumber: 38
sidebar: sidebar:
order: 14 order: 14
badge: New badge: New
--- ---
<div class="chip">Challenge #38</div> :::note
WIP: The following documentation will be reviewed and improved. However, you can still take on the challenge. If you don't understand a certain part, please feel free to reach out or create an issue.
:::
## Information
---
## How to Use the Application ## How to Use the Application
@@ -22,27 +32,10 @@ A bug has been identified in our application. Users are only able to successfull
This application provides an opportunity to understand the correct placement of a `catchError` operator. If placed incorrectly, the overall subscription will be completed, preventing users from sending more requests. The goal is to preserve the overall subscription by handling error notifications from inner observables appropriately. This application provides an opportunity to understand the correct placement of a `catchError` operator. If placed incorrectly, the overall subscription will be completed, preventing users from sending more requests. The goal is to preserve the overall subscription by handling error notifications from inner observables appropriately.
## Statement
The goal is to use the catchError operator to handle error management inside your Rxjs stream.
## Constraints ## Constraints
Users should be able to log the value/error each time they click the "Fetch" button. Users should be able to log the value/error each time they click the "Fetch" button.
:::note
Start the project by running: `npx nx serve rxjs-catch-error`.
:::
:::tip[Reminder]
Your PR title must start with <b>Answer:38</b>.
:::
<div class="article-footer">
<a
href="https://github.com/tomalaforge/angular-challenges/pulls?q=label%3A38+label%3Aanswer"
alt="catchError community solutions">
❖ Community Answers
</a>
<a
href='https://github.com/tomalaforge/angular-challenges/pulls?q=label%3A38+label%3A"answer+author"'
alt="catchError solution author">
▶︎ Author Answer
</a>
</div>