-
Notifications
You must be signed in to change notification settings - Fork 36.5k
chatSessions supportHotReload #263701
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chatSessions supportHotReload #263701
Conversation
| /** | ||
| * Options for the session | ||
| */ | ||
| readonly options?: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe capabilities? And should this be on the provider instead if it's going to be the same for all sessions from it? Something like:
registerChatSessionContentProvider(type, provider, capabilities?: { supportsHotReload? boolean })There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, I like capabilities.
| * Useful when the chat session can handle interruptions gracefully, e.g. when the chat session pulls | ||
| * from a remote provider and can be reattached to. | ||
| */ | ||
| readonly supportsHotReload?: boolean; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hot reload as a name doesn't feel quite right to me. Maybe something like supportsInterruptions?
|
@copilot make the PR suggestions |
mjbvz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for making the changes. API look is looking good
closes #259967