Move SlashCommandWorkingSet
to assistant_slash_command
(#23252)
This PR moves the `SlashCommandWorkingSet` out of the `assistant` crate and into `assistant_slash_command`. This will unlock moving some things that depend on it out of the `assistant` crate. Release Notes: - N/A
This commit is contained in:
parent
b7726238ad
commit
c9f24c7d45
7 changed files with 13 additions and 11 deletions
|
@ -1,5 +1,4 @@
|
|||
use super::{AssistantEdit, MessageCacheMetadata};
|
||||
use crate::slash_command_working_set::SlashCommandWorkingSet;
|
||||
use crate::{
|
||||
assistant_panel, prompt_library, slash_command::file_command, AssistantEditKind, CacheStatus,
|
||||
Context, ContextEvent, ContextId, ContextOperation, InvokedSlashCommandId, MessageId,
|
||||
|
@ -8,7 +7,7 @@ use crate::{
|
|||
use anyhow::Result;
|
||||
use assistant_slash_command::{
|
||||
ArgumentCompletion, SlashCommand, SlashCommandContent, SlashCommandEvent, SlashCommandOutput,
|
||||
SlashCommandOutputSection, SlashCommandRegistry, SlashCommandResult,
|
||||
SlashCommandOutputSection, SlashCommandRegistry, SlashCommandResult, SlashCommandWorkingSet,
|
||||
};
|
||||
use assistant_tool::ToolWorkingSet;
|
||||
use collections::{HashMap, HashSet};
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue