summaryrefslogtreecommitdiff
path: root/docs/whatsnew-1.1.rst
AgeCommit message (Collapse)Author
2009-11-18Another topic.Chris McDonough
2009-11-14Speling.Chris McDonough
2009-11-14Spellcheck.Chris McDonough
2009-11-06- ``repoze.bfg.testing.registerRoutesMapper`` testing facility added.Chris McDonough
This testing function registers a routes "mapper" object in the registry, for tests which require its presence. This function is documented in the ``repoze.bfg.testing`` API documentation.
2009-11-04Tweak.Chris McDonough
2009-11-04(no commit message)Chris McDonough
2009-11-04Gah.Chris McDonough
2009-11-04Note bw incompat.Chris McDonough
2009-11-02Typos.Chris McDonough
2009-11-02- Add a new event type: ``repoze.bfg.events.AfterTraversal``. EventsChris McDonough
of this type will be sent after traversal is completed, but before any view code is invoked. Like ``repoze.bfg.events.NewRequest``, This event will have a single attribute: ``request`` representing the current request. Unlike the request attribute of ``repoze.bfg.events.NewRequest`` however, during an AfterTraversal event, the request object will possess attributes set by the traverser, most notably ``context``, which will be the context used when a view is found and invoked. The interface ``repoze.bfg.events.IAfterTraversal`` can be used to subscribe to the event. For example:: <subscriber for="repoze.bfg.interfaces.IAfterTraversal" handler="my.app.handle_after_traverse"/> Like any framework event, a subscriber function should expect one parameter: ``event``.
2009-11-02(no commit message)Chris McDonough
2009-11-02(no commit message)Chris McDonough
2009-11-02- "What's New in ``repoze.bfg`` 1.1" document added to narrativeChris McDonough
documentation. - Minor typo fixes.