summaryrefslogtreecommitdiff
path: root/CHANGES.txt
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2012-08-25 00:10:46 -0400
committerChris McDonough <chrism@plope.com>2012-08-25 00:10:46 -0400
commit95f766bc7c380797c569da464f1f41d12b05bdbe (patch)
treee89b3566d189aebd26d4fdb93bfd720817608f32 /CHANGES.txt
parentbf64f1e841fe39597402dea8346abd2cd900d0dd (diff)
downloadpyramid-95f766bc7c380797c569da464f1f41d12b05bdbe.tar.gz
pyramid-95f766bc7c380797c569da464f1f41d12b05bdbe.tar.bz2
pyramid-95f766bc7c380797c569da464f1f41d12b05bdbe.zip
Subscriber predicates:
- Add ``add_subscriber_predicate`` method to Configurator. - Allow ``add_subscriber`` and ``subscriber`` venusian decorator to accept ``**predicates`` arguments. - Document subscriber predicate feature. - Share more code between view, route, and subscriber related method wrt predicates.
Diffstat (limited to 'CHANGES.txt')
-rw-r--r--CHANGES.txt13
1 files changed, 8 insertions, 5 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index d20257679..369e9d74d 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -40,9 +40,11 @@ Bug Fixes
Features
--------
-- Third-party custom view and route predicates can now be added for use by
- view authors via ``pyramid.config.Configurator.add_view_predicate`` and
- ``pyramid.config.Configurator.add_route_predicate``. So, for example,
+- Third-party custom view, route, and subscriber predicates can now be added
+ for use by view authors via
+ ``pyramid.config.Configurator.add_view_predicate``,
+ ``pyramid.config.Configurator.add_route_predicate`` and
+ ``pyramid.config.Configurator.add_subscriber_predicate``. So, for example,
doing this::
config.add_view_predicate('abc', my.package.ABCPredicate)
@@ -52,8 +54,9 @@ Features
@view_config(abc=1)
- See "Adding A Third Party View or Route Predicate" in the Hooks chapter for
- more information.
+ Similar features exist for ``add_route``, and ``add_subscriber``. See
+ "Adding A Third Party View, Route, or Subscriber Predicate" in the Hooks
+ chapter for more information.
Note that changes made to support the above feature now means that only
actions registered using the same "order" can conflict with one another.