chore(chat-client): update to 0.2.0 - rename widgets to Website Chats - #513
Merged
Merged
Conversation
The Chat API renamed its widgets resource to Website Chats (the embeddable chat product is now called Website Chat): /v1/widgets -> /v1/website-chats, *ChatWidget(s) operations -> *WebsiteChat(s), widget_id -> website_chat_id, website_chat -> settings, website_chat_embed -> embed, bootstrap website_chat_id / frame_origin, sessions website_chat. Also picks up the anonymous email verification operations. Regenerates the @epilot/sdk chat definitions and the CLI chat entry. Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The embeddable chat product is now called Website Chat, because "widgets" already means a different system in epilot 360. The Chat API renamed its
widgetsresource (chat-api!6); this regenerates@epilot/chat-clientfrom the renamed specs and bumps it to 0.2.0 (0.x, so a minor bump for a breaking change).@epilot/sdkand@epilot/cliare regenerated and released by CI after merge./v1/widgets→/v1/website-chats;listChatWidgets/createChatWidget/getChatWidget/updateChatWidget/deleteChatWidget→listWebsiteChats/createWebsiteChat/getWebsiteChat/updateWebsiteChat/deleteWebsiteChatgetPublicChatWidget→getPublicWebsiteChat(/v1/website-chats/{website_chat_id}/configuration); bootstrapwidget_key→website_chat_id,widget_origin→frame_origin; sessionswidget→website_chatChatWidget→WebsiteChat,ListChatWidgetsResponse→ListWebsiteChatsResponse(widgets→website_chats),Create/UpdateChatWidgetRequest→Create/UpdateWebsiteChatRequest,Widget→PublicWebsiteChat,WidgetDesign→WebsiteChatDesignwidget_id→website_chat_id,website_chat→settings,website_chat_embed→embedgetChatVerification,startChatEmailVerification,verifyChatEmailCode,cancelChatVerification, schemaVerificationState,authentication.email_code, 6 error codesupdate-openapi.cjsreads the management spec from its new pathsrc/website-chats/definition.jsonIt's breaking for the old names with no aliases, but the Chat API has no production consumers yet. The only consumer is epilot360-agent-builder, which is updated once the CI release of
@epilot/sdkis out.Test plan
pnpm generate-sdk+ build + test for@epilot/sdk)