Question about recommended way to access a controller from a route given `no-controller-access-in-routes` rule

Accessing this.controllerFor() property inside setupController/resetController method in a route class raises a lint error ( no-controller-access-in-routes). Is that the expected behavior and if yes, how can one access another controller in a route class.

I am accessing the controller to setup route transition redirect like this (I could opt to use query params or disable the lint on the affected LOC but is there an option to access another controller in a route)

[roomman]

Also hitting up against this: the rule and the Ember guides for Storing and Retrying Transitions are at odds. 🙃

[doska80]

I am upgrading ember from version 3.20 to 3.24.

The no-controller-access-in-routes rule recommends not using a controller within a route, unless the reference to the controller is in the setupController/resetController hooks, as can be seen in the link below:

https://github.com/ember-cli/eslint-plugin-ember/blob/master/docs/rules/no-controller-access-in-routes.md

However we have some willTransition actions that access the controller, and even the ember documentation, there is an example of willTransition accessing the controller, as can be seen in the link below:

https://api.emberjs.com/ember/3.26/classes/Route/events/willTransition?anchor=willTransition

this eslint rule is correct? If the app needs access to the controller from willTransition, how to handler this question?