mercredi 15 août 2018

Ember queryParams in Router VS in Controller

I am confused about queryParams from Ember's documentation. It shows that you can put queryParams to Controller or Route. What are the differences having queryParams in Route vs Controller except syntax?

As far as I understand, having queryParams as object in Route allows me to do following things:

  1. Use replace: true and refreshModel options.
  2. Capture queryParams faster than controller.
  3. Model hook can receive params values

In what case would you choose to have queryParams in Controller?




Aucun commentaire:

Enregistrer un commentaire