okay so we need to be able to handle the following cases: ExpressionStatement CallExpression Identifier | MemberExpression ExpressionLiterals: [ CallExpression StringLiteral NumericLiteral ArrayLiteralExpression ExpressionLiterals ObjectLiteralExpression PropertyAssignment Identifier ExpressionLiterals ]

Hierarchy

Constructors

Properties

parser: ParseFunction

Methods

  • We should separate loading the parser into its own function because loading the grammar takes some time. If there are multiple concurrent parse calls, it's faster to just wait for building the parser once and then use it for all subsequent calls. See expression.test.ts for an example.

    Returns Promise<void>

  • Calls the parser with a given input and optional configuration options. If the input is a string, it creates a generation with the input as text and calls parseResult. If the input is a BaseMessage, it creates a generation with the input as a message and the content of the input as text, and then calls parseResult.

    Parameters

    • input: string | BaseMessage

      The input to the parser, which can be a string or a BaseMessage.

    • Optional options: BaseCallbackConfig

      Optional configuration options.

    Returns Promise<ParsedType>

    A promise of the parsed output.

  • Stream all output from a runnable, as reported to the callback system. This includes all inner runs of LLMs, Retrievers, Tools, etc. Output is streamed as Log objects, which include a list of jsonpatch ops that describe how the state of the run has changed in each step, and the final state of the run. The jsonpatch ops can be applied in order to construct state.

    Parameters

    • input: string | BaseMessage
    • Optional options: Partial<BaseCallbackConfig>
    • Optional streamOptions: Omit<LogStreamCallbackHandlerInput, "autoClose">

    Returns AsyncGenerator<RunLogPatch, any, unknown>

Generated using TypeDoc