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 Componentized: (source)
I am a mixin to allow you to be adapted in various ways persistently.
I define a list of persistent adapters. This is to allow adapter classes to store system-specific state, and initialized on demand. The getComponent method implements this. You must also register adapters for this class for the interfaces that you wish to pass to getComponent.
Many other classes and utilities listed here are present in Zope3; this one is specific to Twisted.
||Utility method that calls addComponent. I take an adapter class and instantiate it with myself as the first argument.|
||Add a component to me, for all appropriate interfaces.|
||Create or retrieve an adapter for the given interface.|
||Remove the given component from me entirely, for all interfaces for which it has been registered.|
||Cache a provider for the given interface, by adapting self using the given adapter class.|
||Cache a provider of the given interface.|
||Remove my component specified by the given interface class.|
Utility method that calls addComponent. I take an adapter class and instantiate it with myself as the first argument.
|The adapter instantiated.|
Add a component to me, for all appropriate interfaces.
In order to determine which interfaces are appropriate, the component's provided interfaces will be scanned.
If the argument 'ignoreClass' is True, then all interfaces are considered appropriate.
Otherwise, an 'appropriate' interface is one for which its class has been registered as an adapter for my class according to the rules of getComponent.
Create or retrieve an adapter for the given interface.
If such an adapter has already been created, retrieve it from the cache that this instance keeps of all its adapters. Adapters created through this mechanism may safely store system-specific state.
If you want to register an adapter that will be created through getComponent, but you don't require (or don't want) your adapter to be cached and kept alive for the lifetime of this Componentized object, set the attribute 'temporaryAdapter' to True on your adapter class.
If you want to automatically register an adapter for all appropriate interfaces (with addComponent), set the attribute 'multiComponent' to True on your adapter class.
Remove the given component from me entirely, for all interfaces for which it has been registered.
|a list of the interfaces that were removed.|
Cache a provider for the given interface, by adapting self using the given adapter class.
Cache a provider of the given interface.
Remove my component specified by the given interface class.