H5P NodeJS Library
    Preparing search index...

    The editor integration object is used to pass information to the page that is created by the renderer. Note that this object is NOT standard H5P behavior but specific to our NodeJS implementation. The editor view created by the renderer has to copy these values into the H5PEditor object! This is the responsibility of the implementation and NOT done by the H5P client automatically!

    interface ILumiEditorIntegration {
        ajaxPath: string;
        apiVersion: { majorVersion: number; minorVersion: number };
        assets: { css: string[]; js: string[] };
        basePath?: string;
        baseUrl?: string;
        contentId?: string;
        contentRelUrl?: string;
        copyrightSemantics?: any;
        editorRelUrl?: string;
        enableContentHub?: boolean;
        fileIcon?: { height: number; path: string; width: number };
        filesPath: string;
        hub?: { contentSearchUrl: string };
        language?: string;
        libraryUrl: string;
        metadataSemantics?: any;
        nodeVersionId: string;
        relativeUrl?: string;
        wysiwygButtons?: string[];
    }

    Hierarchy (View Summary)

    Index

    Properties

    ajaxPath: string
    apiVersion: { majorVersion: number; minorVersion: number }
    assets: { css: string[]; js: string[] }
    basePath?: string
    baseUrl?: string
    contentId?: string
    contentRelUrl?: string
    copyrightSemantics?: any
    editorRelUrl?: string
    enableContentHub?: boolean
    fileIcon?: { height: number; path: string; width: number }

    This is a reference ot a generic binary file icon used in some content types.

    filesPath: string

    The path at which temporary files can be retrieved from.

    hub?: { contentSearchUrl: string }
    language?: string
    libraryUrl: string
    metadataSemantics?: any
    nodeVersionId: string
    relativeUrl?: string
    wysiwygButtons?: string[]