Make the workspace optional when building a chat launcher

This commit is contained in:
Thorsten Sommer committed 2026-09-14 09:20:55 +02:00
1 parent 3548b1d44d
commit d25bdb35b7
6 files changed
+27 -27

No files matched your search

@@ -32,8 +32,7 @@
@bind-ProfileId="@this.profileId"
@bind-ChatTemplateId="@this.chatTemplateId"
@bind-DataSourceIds="@this.dataSourceIds"
@bind-ToolIds="@this.toolIds"
ValidateWorkspaceName="@this.ValidateWorkspaceName"/>
@bind-ToolIds="@this.toolIds"/>
</MudPaper>
</MudForm>
@@ -152,7 +152,9 @@ public partial class DirectChatLauncherSettingsDialog : MSGComponentBase
//
// An empty selection means "use the chat defaults" and is left out of the plugin, whereas
// the empty GUID explicitly selects no profile or no chat template:
// the empty GUID explicitly selects no profile or no chat template. Clearing the workspace
// name is a change of its own: the tile then opens a disappearing chat, and the writer
// switches the launch behavior accordingly.
//
return new(
this.workspaceName.Trim(),
@@ -248,8 +250,6 @@ public partial class DirectChatLauncherSettingsDialog : MSGComponentBase
private string? ValidateDescription(string value) => string.IsNullOrWhiteSpace(value) ? T("Please provide a description for this tile.") : null;
private string? ValidateWorkspaceName(string value) => string.IsNullOrWhiteSpace(value) ? T("Please select or enter a workspace name for this tile.") : null;
private void Cancel() => this.MudDialog.Cancel();
private static Guid? ParseOptionalGuid(string value) => Guid.TryParse(value, out var parsed) ? parsed : null;