From c92c1e93c712d71d31aa79675a04703d6e8fe6b6 Mon Sep 17 00:00:00 2001 From: Kamil Wargula Date: Wed, 20 Jun 2018 14:37:52 +0200 Subject: [PATCH] Update docs - add command for listing rules. --- docs/blueprints.rst | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/blueprints.rst b/docs/blueprints.rst index 1b6de08c..3d670b99 100644 --- a/docs/blueprints.rst +++ b/docs/blueprints.rst @@ -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 these:: - [' (HEAD, OPTIONS, GET) -> static>, + >>> app.url_map + Map([' (HEAD, OPTIONS, GET) -> static>, ' (HEAD, OPTIONS, GET) -> simple_page.show>, - simple_page.show>] + simple_page.show>]) 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`` @@ -110,9 +111,10 @@ Blueprints however can also be mounted at different locations:: And sure enough, these are the generated rules:: - [' (HEAD, OPTIONS, GET) -> static>, + >>> app.url_map + Map([' (HEAD, OPTIONS, GET) -> static>, ' (HEAD, OPTIONS, GET) -> simple_page.show>, - simple_page.show>] + simple_page.show>]) 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