feat: add challenge 49

[alcaidio]

Here's another challenge ready for the week after ^^ for rxjs this time.

(Need to merge #759 before this one)

Looking forward to your feedback.

[jdegand]

I don't know if @tomalaforge wants to focus much on RxJS much in the future, as RxJS becoming optional seems to be inevitable, but this is a nice callback to past RxJS challenges I've seen.

This repo is a great resource for RxJS challenges.

The deployment failed because the authors json file is missing?

[alcaidio]

The deployment failed because the authors json file is missing?

Yes @jdegand it will be fixed after #759 has merged

[tomalaforge]

This is a super nice challenge. I love it 😍
@jdegand you are right and not right 😅 Indeed rxjs will be less and less present inside Angular. The goal of the team is to make it optional. (But this is not in a near future), and rxjs is still very powerful and can let you do things in a nice way that other lib cannot.
And moreover, there are always old angular projects that are far from using signals.
And lastly, rxjs is great for async events, which are not signal. So rxjs is still and will still be a great tool to have in your toolkit. So keep producing rxjs challenges 🔥

And when I have more time, I will try to start with some signal challenges.

[jdegand]

Actually, I looked into this and Angular is in a weird place. Most of the community is not adopting signals or even standalone components yet. See Academind state of Angular 2024.

Async/await can be used in Angular (See this YouTube video) and its usage should only grow after zoneless hits.

[tomalaforge]

Actually, I looked into this and Angular is in a weird place. Most of the community is not adopting signals or even standalone components yet. See Academind state of Angular 2024.

Async/await can be used in Angular (See this YouTube video) and its usage should only grow after zoneless hits.

Yes I know, and the weird place is not over yet. I think the time angular gets more stable will take more than a year. We will see what's the future holds. but for now, let's do challenges on rxjs. But I agree with you, if rxjs become optional, it will become less and less used. Because people will not bother learn it. It's too hard to understand.
async/await is simpler because it can be sequential.

[tomalaforge]

The build fail, because the path is wrong.

try npm run doc:dev before pushing to test that the documentation site is launching correctly

[tomalaforge]

@alcaidio Can you rebase it and correct the path of the image so I can merge it tomorrow ?

[alcaidio]

@alcaidio Can you rebase it and correct the path of the image so I can merge it tomorrow ?

Sorry @tomalaforge I wasn't available, but I see you've merged thank you!