@eagleoutice/flowr - v2.10.2
    Preparing search index...

    Interface FileAnalysisResponseMessageJson

    Answer for a successful FileAnalysisRequestMessage. It contains the results of the analysis in JSON format (guided by FileAnalysisRequestMessage#format).

    The idMap of the normalization step (see NormalizedAst) is not serialized as it would essentially repeat the complete normalized AST, you have to re-create it yourself if you require it.

    The serialization of maps and sets is controlled by the jsonReplacer as part of sendMessage.

    interface FileAnalysisResponseMessageJson {
        cfg?: ControlFlowInformation<CfgVertex>;
        format: "json";
        id: string | undefined;
        results: PipelineOutput<typeof DEFAULT_DATAFLOW_PIPELINE>;
        type: "response-file-analysis";
    }

    Hierarchy (View Summary)

    Hierarchy-Diagram

    UML class diagram of FileAnalysisResponseMessageJson
    Index

    Properties

    cfg? format id results type

    Properties

    cfg?: ControlFlowInformation<CfgVertex>

    Only if the FileAnalysisRequestMessage contained a cfg: true this will contain the ControlFlowInformation of the file.

    format: "json"
    id: string | undefined

    The id that links a request with its responses, it is up to the calling client to make sure it is unique. However, the client does not have to pass the id if it does not need to link the request with its response. The id is always undefined if the message is unprompted (e.g., with hello) or the id unknown.

    results: PipelineOutput<typeof DEFAULT_DATAFLOW_PIPELINE>

    See the PipelineExecutor and DEFAULT_DATAFLOW_PIPELINE for details on the results.

    type: "response-file-analysis"

    The at this time unknown type

    Settings

    Member Visibility

    On This Page

    Properties