maya-chen/flask
1
0
Fork 0
forked from orbit-oss/flask
Code Pull requests Activity

Merge pull request #2837 from quamilek/update-docs

Browse source 
Update docs - add command for listing rules.
This commit is contained in:
David Lord 2018-06-20 06:50:59 -07:00 • committed by GitHub
commit 827536e20a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/blueprints.rst
View file

@ -95,9 +95,10 @@ So how do you register that blueprint? Like this::
If you check the rules registered on the application, you will find If you check the rules registered on the application, you will find
these:: these::
[<Rule '/static/<filename>' (HEAD, OPTIONS, GET) -> static>, >>> app.url_map
Map([<Rule '/static/<filename>' (HEAD, OPTIONS, GET) -> static>,
<Rule '/<page>' (HEAD, OPTIONS, GET) -> simple_page.show>, <Rule '/<page>' (HEAD, OPTIONS, GET) -> simple_page.show>,
<Rule '/' (HEAD, OPTIONS, GET) -> simple_page.show>] <Rule '/' (HEAD, OPTIONS, GET) -> simple_page.show>])
The first one is obviously from the application itself for the static The first one is obviously from the application itself for the static
files. The other two are for the `show` function of the ``simple_page`` files. The other two are for the `show` function of the ``simple_page``
@ -110,9 +111,10 @@ Blueprints however can also be mounted at different locations::
And sure enough, these are the generated rules:: And sure enough, these are the generated rules::
[<Rule '/static/<filename>' (HEAD, OPTIONS, GET) -> static>, >>> app.url_map
Map([<Rule '/static/<filename>' (HEAD, OPTIONS, GET) -> static>,
<Rule '/pages/<page>' (HEAD, OPTIONS, GET) -> simple_page.show>, <Rule '/pages/<page>' (HEAD, OPTIONS, GET) -> simple_page.show>,
<Rule '/pages/' (HEAD, OPTIONS, GET) -> simple_page.show>] <Rule '/pages/' (HEAD, OPTIONS, GET) -> simple_page.show>])
On top of that you can register blueprints multiple times though not every On top of that you can register blueprints multiple times though not every
blueprint might respond properly to that. In fact it depends on how the blueprint might respond properly to that. In fact it depends on how the