Added an API doc entry for the new "@named()" function.

1 files changed, 30 insertions, 0 deletions

diff --git a/docs/api.rst b/docs/api.rst
index 1d6d06d..a853dc7 100644
--- a/docs/api.rst
+++ b/docs/api.rst
@@ -1029,3 +1029,33 @@ For example:
 Get an ObjectSpecification bound to either an instance or a class,
 depending on how we were accessed.
 
+
+:class:`zope.interface.declarations.named`
+---------------------------------------------
+
+API
++++
+
+.. autoclass:: zope.interface.declarations.named
+   :members:
+   :member-order: bysource
+
+Usage
++++++
+
+For example:
+
+.. doctest::
+
+   >>> from zope.interface.declarations import named
+
+   >>> @named('foo')
+   ... class Foo(object):
+   ...     pass
+
+   >>> Foo.__component_name__
+   'foo'
+
+When registering an adapter or utility component, the registry looks for the
+`__component_name__` attribute and uses it, if no name was explicitely
+provided.