@samatawy/rules
    Preparing search index...

    Interface TypesFileReaderOptions

    Options for configuring the behavior of the TypesFileReader when parsing types from a file.

    interface TypesFileReaderOptions {
        read_by: "block" | "line";
        workspace?: Workspace;
        accept: "all" | "partial";
    }

    Hierarchy (View Summary)

    Index

    Properties

    read_by: "block" | "line"

    Determines whether to read the file content line by line or block by block (separated by empty lines). This allows for flexible formatting of the file, where each entry can either be defined on a single line or as a block of text.

    • 'line': Read the file content line by line, where each line is considered a separate entry to parse. Empty lines will be skipped.
    • 'block': Read the file content block by block, where blocks are separated by one or more empty lines. Each block (which can consist of multiple lines) is considered a separate entry to parse. Empty blocks will be skipped.
    workspace?: Workspace

    Optional reference to the Workspace instance, which can be used by the RuleParser to access existing rules, types, functions, and constants when parsing rules from the file. This allows for more complex rule definitions that can reference other components within the Workspace.

    accept: "all" | "partial"

    Determines whether to accept all types (including invalid ones) or only fully valid types.

    • 'all': Accept all types, but include errors for any invalid types. The resulting types object will include only the successfully parsed types, and the errors array will contain messages for any types that failed to parse.
    • 'partial': Only accept types if all of them are valid. If any type fails to parse, the entire parsing process will be considered a failure, and the resulting types object will be empty while the errors array will contain messages for all failed types.