diff options
Diffstat (limited to 'src/debputy/manifest_parser/declarative_parser.py')
| -rw-r--r-- | src/debputy/manifest_parser/declarative_parser.py | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/debputy/manifest_parser/declarative_parser.py b/src/debputy/manifest_parser/declarative_parser.py index 32e93fe..84e0230 100644 --- a/src/debputy/manifest_parser/declarative_parser.py +++ b/src/debputy/manifest_parser/declarative_parser.py @@ -720,7 +720,7 @@ class ParserGenerator: ``` While this is sufficient for programmers, it is a bit ridig for the packager writing the manifest. Therefore, - you can also provide a TypedDict descriping the input, enabling more flexibility: + you can also provide a TypedDict describing the input, enabling more flexibility: >>> class InstallDocsRule(DebputyParsedContent): ... sources: List[str] @@ -737,7 +737,7 @@ class ParserGenerator: In this case, the `sources` field can either come from a single `source` in the manifest (which must be a string) or `sources` (which must be a list of strings). The parser also ensures that only one of `source` or `sources` - is used to ensure the input is not ambigious. For the `into` parameter, the parser will accept it being a str + is used to ensure the input is not ambiguous. For the `into` parameter, the parser will accept it being a str or a list of strings. Regardless of how the input was provided, the parser will normalize the input such that both `sources` and `into` in the result is a list of strings. As an example, this parser can accept both the previous input but also the following input: |