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

    Interface SliceRequestMessage

    Can only be sent after you have sent the FileAnalysisRequestMessage. Using the same filetoken as in the FileAnalysisRequestMessage you can slice the respective file given the respective criteria.

    interface SliceRequestMessage {
        criterion: SlicingCriteria;
        direction?: SliceDirection;
        filetoken: string;
        id: string | undefined;
        noMagicComments?: boolean;
        type: "request-slice";
    }

    Hierarchy (View Summary)

    Hierarchy-Diagram

    UML class diagram of SliceRequestMessage
    Index

    Properties

    criterion direction? filetoken id noMagicComments? type

    Properties

    criterion: SlicingCriteria

    The slicing criteria to use

    direction?: SliceDirection

    The direction to slice in. Defaults to backward slicing if unset.

    filetoken: string

    The FileAnalysisRequestMessage#filetoken of the file/data to slice

    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.

    noMagicComments?: boolean

    Should the magic comments (force-including lines within the slice) be ignored?

    type: "request-slice"

    The at this time unknown type

    Settings

    Member Visibility

    On This Page

    Properties