I’m trying to implement data resolution and access permissions using resolvers and guards respectively. However, given that for some reason we cannot have a Route Reuse Strategy of our own, I defaulted to using conditions of when the resolvers are to be executed so as to not have the data resolution occur every single time a user navigates back to the home screen. Referring to the ionic conference app as an example, should the conference data, if it were retrieved by a resolver, should not be loaded every time the user navigates back from a session detail. So, in light of this, I am trying to use the runGuardsAndResolvers property to check whether this is a forwards or backwards navigation, and if it is a back then there is no need to execute neither guards or resolvers. However, the runGuardsAndResolvers property is completely ignored. Created a brand new conference app, added the condition below to disable the CanLoad guard completely, just to see whether it works, and unfortunately this does not affect it at all.
However, in the stackblitz link below one can clearly see that this is working as intended. Can someone shed some light on this?
Ionic Framework : @ionic/angular 5.1.1
@angular-devkit/build-angular : 0.803.25
@angular-devkit/schematics : 8.3.25
@angular/cli : 8.3.25
@ionic/angular-toolkit : 2.2.0