orbit-oss/flask
4
4
Fork 2
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update docs - add command for listing rules.

Browse source
This commit is contained in:
Kamil Wargula 2018-06-20 14:37:52 +02:00 • committed by Kamil Wargula
parent 7627d9ce13
commit c92c1e93c7
No known key found for this signature in database
GPG key ID: D2BE5902F80D185E
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