Hierarchy (View Summary)

Implements

Implemented by

Constructors

Properties

Methods

completeImportAutoTestConfiguration copyAutoTestConfiguration createAssistant createAssistantConversation createAssistantMessage createAutoTestSnapshot createEditorSession createSafeProgram createTerminal deleteAutoTestConfiguration destroy executeDraftDocumentJupyterCell executeEditorDocumentJupyterCell getAssistant getAssistantConversation getAssistantMessage getAutoTestConfiguration getAutoTestPublishedSnapshot getAutoTestRubricResults getAutoTestSnapshot getDraftDocument getEditorDocument getEditorFileDownloadLink getEditorSession getPearsonContextTemplate getPearsonContextTemplateQuestion handInEditorSession instantiatePearsonTemplate interruptDraftDocumentJupyterKernel interruptEditorDocumentJupyterKernel listAssignmentAssistants listAssistantMessageDetails listAssistantMessages listAutoTestSnapshots listDraftDocumentJupyterCellOutputs listDraftDocuments listEditorDocumentJupyterCellOutputs listEditorDocuments listEditorSessions listUserAssistantConversations paginateListAssignmentAssistants paginateListAssistantMessageDetails paginateListAssistantMessages paginateListAutoTestSnapshots paginateListDraftDocumentJupyterCellOutputs paginateListDraftDocuments paginateListEditorDocumentJupyterCellOutputs paginateListEditorDocuments paginateListEditorSessions paginateListUserAssistantConversations putAutoTestConfiguration putEditorFile putPearsonBook putPearsonContextTemplate putPearsonQuestion putPearsonTemplate replyDraftDocumentJupyterInput replyEditorDocumentJupyterInput send updateAssistant updateAutoTestConfiguration updatePearsonBook updatePearsonContextTemplate updatePearsonContextTemplateQuestion updatePearsonCourse waitUntilSnapshotPublishable

Constructors

Properties

The resolved configuration of Apiv2Client class. This is resolved and normalized from the constructor configuration interface.

initConfig?: object

Holds an object reference to the initial configuration object. Used to check that the config resolver stack does not create dangling instances of an intermediate form of the configuration object.

middlewareStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>

Methods

  • Destroy underlying resources, like sockets. It's usually not necessary to do this. However in Node.js, it's best to explicitly shut down the client's agent when it is no longer needed. Otherwise, sockets might stay open for quite a long time before the server terminates them.

    Returns void