How to set default activationStrategy in aurelia

后端 未结 3 1240
心在旅途
心在旅途 2020-12-19 01:37

Aurelia normally ignores any changes in the querystring.

It is possible to set the activationStrategy to invoke-lifecycle in the VM so it w

相关标签:
3条回答
  • 2020-12-19 01:52

    You can use config.options.compareQueryParams = true.

    Changelog entry

    0 讨论(0)
  • 2020-12-19 01:59

    On the ViewModel

    (I misread your question at first too, but I'm leaving this in for completeness)

    Place a method determineActivationStrategy() on the ViewModel and from there you can return the name or type of the activation strategy you wish to use. Example:

    determineActivationStrategy() {
        return "invoke-lifecycle";
    }
    

    The strings "invoke-lifecycle" or "replace" will work. You can also use the typed version by importing the enum activationStrategy and returing activationStrategy.replace / activationStrategy.invokeLifecycle. They work the same.

    In the RouteConfig

    Or, as stated by Marton (who gave this answer before I did), you can put it directly in route config as the property activationStrategy.

    This approach is better suited if the strategy does not depend on any particular state of your ViewModel and you don't wish to litter your view model with this stuff.

    invoke-lifecycle vs. replace

    In your question you say you want to

    re-run the all the life cycles in the VM

    Note that invoke-lifecycle reuses the existing ViewModel and will only invoke the router activation lifecycle, which is as follows:

    1. canDeactivate()
    2. deactivate()
    3. canActivate(params, routeConfig, navigationInstruction)
    4. activate(params, routeConfig, navigationInstruction)

    Whereas replace will throw away the existing ViewModel and invoke the whole ViewModel lifecycle again on top of the router activation lifecycle:

    1. canDeactivate()
    2. deactivate()
    3. detached()
    4. unbind()
    5. (new instance): constructor()
    6. canActivate(params, routeConfig, navigationInstruction)
    7. activate(params, routeConfig, navigationInstruction)
    8. created(owningView, thisView)
    9. bind(bindingContext, overrideContext)
    10. attached()

    So if you really want to run all the ViewModel lifecycle steps, you'll need to use replace.

    0 讨论(0)
  • 2020-12-19 02:05

    activationStrategy is a property of RouterConfig, which represents the route config object used by config.map(). I think that you need to set it on each route definition.

    Example:

    configureRouter(config, router) {
      ...
      config.map([
        { 
          route: ['', 'home'],       
          name: 'home',       
          moduleId: 'home/index', 
          activationStrategy: 'invoke-lifecycle'
        }
      ]);
      ...
    }
    

    (Edit reason: I've made a terrible mistake by misreading your question at first, sorry :))

    0 讨论(0)
提交回复
热议问题