diff options
| author | Chris McDonough <chrism@agendaless.com> | 2010-01-03 03:47:06 +0000 |
|---|---|---|
| committer | Chris McDonough <chrism@agendaless.com> | 2010-01-03 03:47:06 +0000 |
| commit | a8791b93f0211fe0d2c5a37226ecc45d4e30cb19 (patch) | |
| tree | 73901de89cff67c3a3352adcffe90abc5c93388a | |
| parent | eecdbc34962b00e35d41039af014462cf558acee (diff) | |
| download | pyramid-a8791b93f0211fe0d2c5a37226ecc45d4e30cb19.tar.gz pyramid-a8791b93f0211fe0d2c5a37226ecc45d4e30cb19.tar.bz2 pyramid-a8791b93f0211fe0d2c5a37226ecc45d4e30cb19.zip | |
Missed one.
| -rw-r--r-- | docs/narr/hybrid.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/narr/hybrid.rst b/docs/narr/hybrid.rst index 5c3775e59..4faccae45 100644 --- a/docs/narr/hybrid.rst +++ b/docs/narr/hybrid.rst @@ -355,10 +355,10 @@ hood" for views that match a route use the (very weakly binding) is found has a specific interface, and a global view statement is registered against this interface as its context interface, it's likely that the *global* view will match *before* the view that is -attached to the route unless the ``view_for`` attribute is used on the -``route`` registration to match the "correct" interface first (because -then both the request type and the context type are "more specific" -for the view registration). +attached to the route unless the ``view_context`` attribute is used on +the ``route`` registration to match the "correct" interface first +(because then both the request type and the context type are "more +specific" for the view registration). What it all boils down to is: if a request that matches a route resolves to a view you don't expect it to, use the ``view_context`` |