feat(chat-client): implement export conversation flow

[viktorsaws]

Problem

We need to:

• Implement Export Conversations feature in Chat Client
• Add support for history option set in Q Language Server at initialization to toggle View History functionality in Chat Client

Solution

• Added Chat Export functionality to go from Chat Client to Language Server. Q Chat server is controlling the UX flow and contains business logic for export functionality. Using new protocol methods to implement Export feature flow feat: protocol extensions for chat tab actions and export features language-server-runtimes#433.
• Update Sample VSCode extension with implementation of Show Save File dialog and added support.
• Updated Runtimes dependencies to latest version.

Integration of Chat History and Export features with Extension

To fully intergate export feature with IDE, Extension must add support for next features:

1. Implement support for showSaveFileDialog

Export feature is conditionally enabled by Q Chat server if client signals support for initializationOptions?.aws?.awsClientCapabilities?.window?.showSaveFileDialog feature.

Extension must implement aws/showSaveFileDialog protocol and set awsClientCapabilities?.window?.showSaveFileDialog flag to true.

2. Implement support of response routing for openTab and getSerializedChat requests

New getSerializedChat request in Chat Client requires Extension to support routing of responses between inbound and outbound messages from Chat Client to Language Server. This is archived by requestId argument in inbound getSerializedChat Chat Client message. getSerializedChat and openTab requests are sent from Language Server, and server expects response with result coming from the Chat Client.
Extension must attach and track requestId field for getSerializedChat and openTab requests, and route responses from Chat Client to corresponding incoming request from LSP Server.

Reference implementation of message routing can be found in Sample VSCode extension

language-servers/client/vscode/src/chatActivation.ts

Lines 192 to 243 in 2ac19b7

	const registerHandlerWithResponseRouter = (command: string) => {
	const handler = async (params: any, _: any) => {
	const mapErrorType = (type: string | undefined): number => {
	switch (type) {
	case 'InvalidRequest':
	return ErrorCodes.InvalidRequest
	case 'InternalError':
	return ErrorCodes.InternalError
	case 'UnknownError':
	default:
	return ErrorCodes.UnknownErrorCode
	}
	}
	const requestId = uuidv4()
	webviewView.webview.postMessage({
	requestId: requestId,
	command: command,
	params: params,
	})
	const responsePromise = new Promise<UiMessageResultParams | undefined>((resolve, reject) => {
	const timeout = setTimeout(() => {
	disposable.dispose()
	reject(new Error('Request timed out'))
	}, 30000)
	const disposable = webviewView.webview.onDidReceiveMessage((message: any) => {
	if (message.requestId === requestId) {
	clearTimeout(timeout)
	disposable.dispose()
	resolve(message.params)
	}
	})
	})
	const result = await responsePromise
	if (result?.success) {
	return result.result
	} else {
	return new ResponseError(
	mapErrorType(result?.error.type),
	result?.error.message ?? 'No response from client'
	)
	}
	}
	languageClient.onRequest(command, handler)
	}
	registerHandlerWithResponseRouter(openTabRequestType.method)
	registerHandlerWithResponseRouter(getSerializedChatRequestType.method)

.

TODO

• Release and upgrade to latest ChatUI and Runtime types package to include feat: protocol extensions for chat tab actions and export features language-server-runtimes#433
• Rework implementation to go through Server, like Delete event. There will be server-side logic after all, that we depend upon, round-trip to server is necessary to export not loaded history conversation.
• Integrate Export Conversation as action in Chat History.
• Unit tests

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[volodkevych]

nit: for completeness, we should also be checking for not called if not set

[volodkevych]

nice catch!

[volodkevych]

nit: introducing constants for this critical ids (as above) makes it a bit easier to track the logic across files