Decorator order: explicit order should be described or somehow supported about flask-login HOT 4 CLOSED

The Flask route decorator should always be the last decorator over your view function, i.e. your second example is the correct, canonical way to handle route registry. (This is, as far as I know, related to the internals of how Flask handles view registry though you might want to take a closer look at the Flask and Werkzeug source to verify.)

from flask-login.

You are correct, yet it is not entirely obvious to developers. Guidance would help to remove any issues with the use of login_required which has a potentially negative impact. That is the major issue I wished to get across, thus it would be good if guidance was added, if you are open to such a change, I will prepare a small patch to the example and the docs that specifies this explicitly.

from flask-login.

Sure. That would be great!

from flask-login.

This is now duplicated and having had time to think about it, I don't think it falls on the shoulders of the extensions to document Flask behavior (barring a few necessary exceptions, but certainly not common behavior); basically you should already know this and if you don't it should be up to Flask to document and inform users of this.

from flask-login.