angular-challenges VS notely

Instead of immediately reading the solution, I created a challenge inside AngularChallenges for those who want to try resolving and understanding the source of the bug first. After that, you can come back to this article to compare your solution with mine and understand what went wrong.

Answer:25 generator extending lib #70

I suggests you to do these Angular Challanges: https://github.com/tomalaforge/angular-challenges/

This article will also help you to resolve challenge #11 of Angular Challenges, which is intended for developers who already have a strong understanding of observables. However anyone can read this article and learn from it. If you want to try this challenge first, I encourage you to do so then come back to compare your solution with the guidance provided here. (You can also submit a PR that I'll review)

{ "name": "@tomalaforge/ngrx-callstate-store", "version": "0.0.1", "description": "Enhance NgRx component-store by providing a loading/error state", "publishConfig": { "access": "public" }, "repository": { "type": "git", "url": "https://github.com/tomalaforge/angular-challenges/tree/main/libs/shared/ngrx-callstate-store" }, "keywords": [ "angular", "state", "ngrx/component-store" ], "author": { "name": "Thomas Laforge" }, "peerDependencies": { "@angular/common": "^15.0.0", "@angular/core": "^15.0.0", "@ngrx/component-store": "^15.0.0" }, "dependencies": { "tslib": "^2.3.0" } }

If you haven’t done the challenge yet, I invite you to try it first by going to Angular Challenges and coming back afterward to compare your solution with mine. (You can also submit a PR that I’ll review)