diff options
| author | Chris McDonough <chrism@plope.com> | 2012-10-26 00:32:08 -0400 |
|---|---|---|
| committer | Chris McDonough <chrism@plope.com> | 2012-10-26 00:32:08 -0400 |
| commit | c25a8fd5d2895a117d8eb77162ed8388f0482674 (patch) | |
| tree | 6eeb21a5805c33407818a108e0a6d582d1e67382 /docs/whatsnew-1.4.rst | |
| parent | c773a62030c6a183ce82278433b93d3c9b545746 (diff) | |
| download | pyramid-c25a8fd5d2895a117d8eb77162ed8388f0482674.tar.gz pyramid-c25a8fd5d2895a117d8eb77162ed8388f0482674.tar.bz2 pyramid-c25a8fd5d2895a117d8eb77162ed8388f0482674.zip | |
- New ``physical_path`` view predicate. If specified, this value should be a
string or a tuple representing the physical traversal path of the context
found via traversal for this predicate to match as true. For example:
``physical_path='/'`` or ``physical_path='/a/b/c'`` or ``physical_path=('',
'a', 'b', 'c')``. This is not a path prefix match or a regex, it's a
whole-path match. It's useful when you want to always potentially show a
view when some object is traversed to, but you can't be sure about what kind
of object it will be, so you can't use the ``context`` predicate. The
individual path elements inbetween slash characters or in tuple elements
should be the Unicode representation of the name of the resource and should
not be encoded in any way.
Diffstat (limited to 'docs/whatsnew-1.4.rst')
0 files changed, 0 insertions, 0 deletions
