Would you watch it?
Would you watch it?
Let's talk about them, as you should definitely check them out to get a better grasp of how everything works!
Let's talk about them, as you should definitely check them out to get a better grasp of how everything works!
You do not need to manually `reload` a signal when the user clicks "next page". Instead, you should think of your resource as dependent on the `page` state and increment the page number when the user clicks. Super easy, fully declarative:
You do not need to manually `reload` a signal when the user clicks "next page". Instead, you should think of your resource as dependent on the `page` state and increment the page number when the user clicks. Super easy, fully declarative:
Here's an example of a resettable timer with `linkedSignal` and an RxJS `interval` Observable:
Here's an example of a resettable timer with `linkedSignal` and an RxJS `interval` Observable:
Tonight, at 4 PM UTC
Tonight, at 4 PM UTC
This week, let's talk about RxJS and answer some burning questions I keep seeing Angular devs ask
- Is RxJS no longer needed?
- Should we replace Observables with Signals?
- If we use both, how do we understand when to reach out for what? (1/2)
This week, let's talk about RxJS and answer some burning questions I keep seeing Angular devs ask
- Is RxJS no longer needed?
- Should we replace Observables with Signals?
- If we use both, how do we understand when to reach out for what? (1/2)
Promise to be back next week!
Promise to be back next week!
No more `ControlValueAccessor` and boilerplate, simply drop some inputs/model signal for value/disabled state/etc, and you're done!
Here's a reusable Rating component example:
No more `ControlValueAccessor` and boilerplate, simply drop some inputs/model signal for value/disabled state/etc, and you're done!
Here's a reusable Rating component example:
Here's an example of multiple string inputs (array), none of which can be empty:
Here's an example of multiple string inputs (array), none of which can be empty:
I feel zoneless is going to continue being a big topic, especially with how it makes Angular simpler again (like the new control flow and standalone)
Watch it here if you missed it: www.youtube.com/watch?v=hfyu...
I feel zoneless is going to continue being a big topic, especially with how it makes Angular simpler again (like the new control flow and standalone)
Watch it here if you missed it: www.youtube.com/watch?v=hfyu...
Change detection now runs once each time (as opposed to twice). I'm unsure what that means or why this happens. Anyone care to weigh in?
Change detection now runs once each time (as opposed to twice). I'm unsure what that means or why this happens. Anyone care to weigh in?
Defining forms is easy even without reactive if you know the details. You can use `ngModelGroup` to achieve the same result:
Defining forms is easy even without reactive if you know the details. You can use `ngModelGroup` to achieve the same result:
So, the #RxJS `tap` operator is specifically designed to perform side-effects
However, its implementation is just taking an Observable and returning a new one with the side-effect slapped on it
So, is `tap` itself a pure function or not? 😁
So, the #RxJS `tap` operator is specifically designed to perform side-effects
However, its implementation is just taking an Observable and returning a new one with the side-effect slapped on it
So, is `tap` itself a pure function or not? 😁
Instead, it encourages the use of new, derived selectors and a direct selection of the state
I believe we should not create computed properties from store signals
What do you think?
Instead, it encourages the use of new, derived selectors and a direct selection of the state
I believe we should not create computed properties from store signals
What do you think?
If you want to bind a resource to `ngModel` in your #Angular component template, use its `value` signal, not the resource itself:
If you want to bind a resource to `ngModel` in your #Angular component template, use its `value` signal, not the resource itself:
Isn't NgRx itself already a facade? A big, complex system with which you interact only via two simple methods (dispatch, select)
Isn't NgRx itself already a facade? A big, complex system with which you interact only via two simple methods (dispatch, select)
Do you think this is a bad practice? If so, how can we avoid it? What would be some cases where this is justified?
Do you think this is a bad practice? If so, how can we avoid it? What would be some cases where this is justified?