Search bar offers the following options:
Term presence. The below example searches for documents that
must contain “foo”, might contain “bar” and must not contain “baz”:
+foo bar -baz
Wildcards. The below example searches for documents with words beginning with “foo”:
Search in specific fields. The following search matches all objects
in "twisted.mail" that matches “search”:
Possible fields: 'name', 'qname' (fully qualified name), 'docstring', and 'kind'. Last two fields are only applicable if "search in docstrings" is enabled.
Fuzzy matches. The following search matches all documents
that have a word within 1 edit distance of “foo”:
Results provided by Lunr.js
class Element: (source)
Base for classes which can render part of a page.
An Element is a renderer that can be embedded in a stan document and can hook its template (from the loader) up to render methods.
An Element might be used to encapsulate the rendering of a complex piece of data which is to be displayed in multiple different contexts. The Element allows the rendering logic to be easily re-used in different ways.
Element returns render methods which are registered using
twisted.web._element.renderer. For example:
class Menu(Element): @renderer def items(self, request, tag): ....
Render methods are invoked with two arguments: first, the
twisted.web.http.Request being served and second, the tag object which "invoked" the render method.
||Look up and return the named render method.|
||The factory which will be used to load documents to return from render.|
Callable[: (source) ¶
[ Optional[ IRequest], Tag], Flattenable]
Look up and return the named render method.
(This will simply load the template from the loader; when used in a template, the flattening engine will keep track of this object separately as the object to lookup renderers on and call
Element.renderer to look them up. The resulting object from this method is not directly associated with this