About the authorauthor

Tim Deschryver

NgRx team member

Angularpost
23 April 20202 min read
The difference between the canActivate and canActivateChild guards

canActivate > Interface that a class can implement to be a guard deciding if a route can be activated. If all guards return true, navigation will continue. If any guard returns false, navigation will be cancelled. If any guard returns a UrlTree, current navigation will be cancelled and a new navigation will be kicked off to the UrlTree returned from the guard. The canActivate guard decides if route can be navigated to, which results in the creation of the route's component. To implement the gua

Angularpost
23 April 20202 min read
The difference between the canActivate and canActivateChild guards

canActivate > Interface that a class can implement to be a guard deciding if a route can be activated. If all guards return true, navigation will continue. If any guard returns false, navigation will be cancelled. If any guard returns a UrlTree, current navigation will be cancelled and a new navigation will be kicked off to the UrlTree returned from the guard. The canActivate guard decides if route can be navigated to, which results in the creation of the route's component. To implement the gua

Read more
AngularpostThe difference between the canActivate and canActivateChild guards

23 April 2020

2 min read

canActivate > Interface that a class can implement to be a guard deciding if a route can be activated. If all guards return true, navigation will continue. If any guard returns false, navigation will be cancelled. If any guard returns a UrlTree, current navigation will be cancelled and a new navigation will be kicked off to the UrlTree returned from the guard. The canActivate guard decides if route can be navigated to, which results in the creation of the route's component. To implement the gua

Read more
RxJSpost
23 April 20204 min read
How to not create your RxJS Observables

Last week a friend and college of mine was stuck with a problem. An NgRx effect was subscribed to a stream of WebSocket messages, but the effect didn't receive any messages. Though, we saw that the server was sending them and that they reached the client. The problem wasn't the Effect, but the WebSocket stream that was wrongfully initialized. The use case was to only establish the WebSocket connection for the users that had enough permissions to start a process. The WebSocket was created to re

RxJSpost
23 April 20204 min read
How to not create your RxJS Observables

Last week a friend and college of mine was stuck with a problem. An NgRx effect was subscribed to a stream of WebSocket messages, but the effect didn't receive any messages. Though, we saw that the server was sending them and that they reached the client. The problem wasn't the Effect, but the WebSocket stream that was wrongfully initialized. The use case was to only establish the WebSocket connection for the users that had enough permissions to start a process. The WebSocket was created to re

Read more
RxJSpostHow to not create your RxJS Observables

23 April 2020

4 min read

Last week a friend and college of mine was stuck with a problem. An NgRx effect was subscribed to a stream of WebSocket messages, but the effect didn't receive any messages. Though, we saw that the server was sending them and that they reached the client. The problem wasn't the Effect, but the WebSocket stream that was wrongfully initialized. The use case was to only establish the WebSocket connection for the users that had enough permissions to start a process. The WebSocket was created to re

Read more
sveltepost
19 February 202010 min read
Unlocking reactivity with Svelte and RxJS

I keep being surprised by how reactive Svelte feels. In this article, we take a glance at the Svelte internals to see how Svelte accomplishes this. This is important if we want to use RxJS in Svelte.