Note about limitations of static files in blueprints

[masklinn]

Warn about issue 348's issue, at least until it is resolved.

[masklinn]

#348

(had incorrectly linked the issue)

[ghost]

-1. It already works correctly. There is nothing wrong in this behavior.
My proposal:

Default URLs are: / for the mount point and static/ for the static folder, relative to the mount point.
As a result, /static/ is the default blueprint static folder, and so it collides with the app static folder.

[masklinn]

-1. It already works correctly.

That simply makes no sense: following the blueprint docs for static files will lead to the blueprint's static files not being available with no warnings. If the current behavior is desired, it should be noted and warned. If it's not, it should be fixed.

#348 is about the long term discussion of its fixing, this proposal is about warning about it in the meantime: the number of interventions on #348 shows the behavior is unexpected.

[ghost]

There is nothing wrong in that behavior, but it is not documented. It would be nice to have that fact mentioned at http://flask.pocoo.org/docs/blueprints/#static-files and/or http://flask.pocoo.org/docs/api/#blueprint-objects

Citing from the bug.

[masklinn]

Citing from the bug.

1. that does not contradict what I wrote
2. not everybody on Static files only work for blueprints registered with url_prefix #348 agrees that "there is nothing wrong in that behavior"

[ghost]

Well, I'd just take a neutral position. But do what you want.