Extension Points¶
The parser has several available extension points, with more added as the need arises. Take a look at our outline of the process for more information about the plugin system in general. Here we document specific extension points an example uses.
eregs_ns.parser.layers (deprecated)¶
List of strings referencing layer classes (generally implementing the
abstract base class regparser.layer.layer:Layer).
Examples:
This has been deprecated in favor of layers applicable to specific document types (see below).
eregs_ns.parser.layer.cfr¶
Layer classes (implementing the abstract base class
regparser.layer.layer:Layer) which should apply the CFR documents.
eregs_ns.parser.layer.preamble¶
Layer classes (implementing the abstract base class
regparser.layer.layer:Layer) which should apply the “preamble” documents
(i.e. proposed rules).
eregs_ns.parser.preprocessors¶
List of strings referencing preprocessing classes (generally implementing the
abstract base class
regparser.tree.xml_parser.preprocessors:PreProcessorBase).
Examples:
Preprocessors may have a plugin_order attribute, an integer which defines
the order in which the plugins are executed. Defaults to zero. Sorts
ascending.
eregs_ns.parser.term_definitions¶
dict: string->[(string,string)]: List of phrases which should trigger a
definition. Pair is of the form (term, context), where “context” refers to a
substring match for a specific paragraph. e.g. (“bob”, “text noting that it
defines bob”).
Examples:
eregs_ns.parser.term_ignores¶
dict: string->[string]: List of phrases which shouldn’t contain defined
terms. Keyed by CFR part or ALL.
Examples: