2025-12-23 18:40:58 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-11-30 16:25:51 -03:00
|
|
|
|
2025-10-29 18:54:33 -03:00
|
|
|
use crate::shared::models::UserSession;
|
2025-11-11 09:42:52 -03:00
|
|
|
use crate::shared::state::AppState;
|
|
|
|
|
use log::{error, trace};
|
2025-10-29 18:54:33 -03:00
|
|
|
use rhai::{Dynamic, Engine};
|
|
|
|
|
use serde_json::json;
|
|
|
|
|
use std::sync::Arc;
|
Looking at this diff, I can see it's a comprehensive documentation
update and code refactoring focused on:
1. Adding new documentation pages to the table of contents
2. Restructuring the bot templates documentation
3. Changing keyword syntax from underscore format to space format (e.g.,
`SET_BOT_MEMORY` → `SET BOT MEMORY`)
4. Updating compiler and keyword registration to support the new
space-based syntax
5. Adding new keyword modules (social media, lead scoring, templates,
etc.)
Refactor BASIC keywords to use spaces instead of underscores
Change keyword syntax from underscore format (SET_BOT_MEMORY) to more
natural space-separated format (SET BOT MEMORY) throughout the codebase.
Key changes:
- Update Rhai custom syntax registration to use space tokens
- Simplify compiler preprocessing (fewer replacements needed)
- Update all template .bas files to use new syntax
- Expand documentation with consolidated examples and new sections
- Add new keyword modules: social_media, lead_scoring, send_template,
core_functions, qrcode, sms, procedures, import_export, llm_macros,
on_form_submit
2025-11-30 10:53:59 -03:00
|
|
|
|
2025-12-23 18:40:58 -03:00
|
|
|
|
2025-11-30 16:25:51 -03:00
|
|
|
#[derive(Debug, Clone)]
|
|
|
|
|
pub enum SuggestionType {
|
2025-12-23 18:40:58 -03:00
|
|
|
|
2025-11-30 16:25:51 -03:00
|
|
|
Context(String),
|
2025-12-23 18:40:58 -03:00
|
|
|
|
|
|
|
|
|
2025-11-30 16:25:51 -03:00
|
|
|
Tool {
|
|
|
|
|
name: String,
|
|
|
|
|
params: Option<Vec<String>>,
|
|
|
|
|
},
|
|
|
|
|
}
|
|
|
|
|
|
2025-11-11 09:42:52 -03:00
|
|
|
pub fn clear_suggestions_keyword(
|
|
|
|
|
state: Arc<AppState>,
|
|
|
|
|
user_session: UserSession,
|
|
|
|
|
engine: &mut Engine,
|
|
|
|
|
) {
|
2025-11-02 14:21:38 -03:00
|
|
|
let cache = state.cache.clone();
|
Looking at this diff, I can see it's a comprehensive documentation
update and code refactoring focused on:
1. Adding new documentation pages to the table of contents
2. Restructuring the bot templates documentation
3. Changing keyword syntax from underscore format to space format (e.g.,
`SET_BOT_MEMORY` → `SET BOT MEMORY`)
4. Updating compiler and keyword registration to support the new
space-based syntax
5. Adding new keyword modules (social media, lead scoring, templates,
etc.)
Refactor BASIC keywords to use spaces instead of underscores
Change keyword syntax from underscore format (SET_BOT_MEMORY) to more
natural space-separated format (SET BOT MEMORY) throughout the codebase.
Key changes:
- Update Rhai custom syntax registration to use space tokens
- Simplify compiler preprocessing (fewer replacements needed)
- Update all template .bas files to use new syntax
- Expand documentation with consolidated examples and new sections
- Add new keyword modules: social_media, lead_scoring, send_template,
core_functions, qrcode, sms, procedures, import_export, llm_macros,
on_form_submit
2025-11-30 10:53:59 -03:00
|
|
|
|
2025-12-23 18:40:58 -03:00
|
|
|
|
2025-11-02 14:21:38 -03:00
|
|
|
engine
|
Looking at this diff, I can see it's a comprehensive documentation
update and code refactoring focused on:
1. Adding new documentation pages to the table of contents
2. Restructuring the bot templates documentation
3. Changing keyword syntax from underscore format to space format (e.g.,
`SET_BOT_MEMORY` → `SET BOT MEMORY`)
4. Updating compiler and keyword registration to support the new
space-based syntax
5. Adding new keyword modules (social media, lead scoring, templates,
etc.)
Refactor BASIC keywords to use spaces instead of underscores
Change keyword syntax from underscore format (SET_BOT_MEMORY) to more
natural space-separated format (SET BOT MEMORY) throughout the codebase.
Key changes:
- Update Rhai custom syntax registration to use space tokens
- Simplify compiler preprocessing (fewer replacements needed)
- Update all template .bas files to use new syntax
- Expand documentation with consolidated examples and new sections
- Add new keyword modules: social_media, lead_scoring, send_template,
core_functions, qrcode, sms, procedures, import_export, llm_macros,
on_form_submit
2025-11-30 10:53:59 -03:00
|
|
|
.register_custom_syntax(&["CLEAR", "SUGGESTIONS"], true, move |_context, _inputs| {
|
2025-11-02 14:21:38 -03:00
|
|
|
if let Some(cache_client) = &cache {
|
|
|
|
|
let redis_key = format!("suggestions:{}:{}", user_session.user_id, user_session.id);
|
|
|
|
|
let mut conn = match cache_client.get_connection() {
|
|
|
|
|
Ok(conn) => conn,
|
|
|
|
|
Err(e) => {
|
|
|
|
|
error!("Failed to connect to cache: {}", e);
|
|
|
|
|
return Ok(Dynamic::UNIT);
|
|
|
|
|
}
|
|
|
|
|
};
|
Looking at this diff, I can see it's a comprehensive documentation
update and code refactoring focused on:
1. Adding new documentation pages to the table of contents
2. Restructuring the bot templates documentation
3. Changing keyword syntax from underscore format to space format (e.g.,
`SET_BOT_MEMORY` → `SET BOT MEMORY`)
4. Updating compiler and keyword registration to support the new
space-based syntax
5. Adding new keyword modules (social media, lead scoring, templates,
etc.)
Refactor BASIC keywords to use spaces instead of underscores
Change keyword syntax from underscore format (SET_BOT_MEMORY) to more
natural space-separated format (SET BOT MEMORY) throughout the codebase.
Key changes:
- Update Rhai custom syntax registration to use space tokens
- Simplify compiler preprocessing (fewer replacements needed)
- Update all template .bas files to use new syntax
- Expand documentation with consolidated examples and new sections
- Add new keyword modules: social_media, lead_scoring, send_template,
core_functions, qrcode, sms, procedures, import_export, llm_macros,
on_form_submit
2025-11-30 10:53:59 -03:00
|
|
|
|
2025-11-11 09:42:52 -03:00
|
|
|
let result: Result<i64, redis::RedisError> =
|
|
|
|
|
redis::cmd("DEL").arg(&redis_key).query(&mut conn);
|
Looking at this diff, I can see it's a comprehensive documentation
update and code refactoring focused on:
1. Adding new documentation pages to the table of contents
2. Restructuring the bot templates documentation
3. Changing keyword syntax from underscore format to space format (e.g.,
`SET_BOT_MEMORY` → `SET BOT MEMORY`)
4. Updating compiler and keyword registration to support the new
space-based syntax
5. Adding new keyword modules (social media, lead scoring, templates,
etc.)
Refactor BASIC keywords to use spaces instead of underscores
Change keyword syntax from underscore format (SET_BOT_MEMORY) to more
natural space-separated format (SET BOT MEMORY) throughout the codebase.
Key changes:
- Update Rhai custom syntax registration to use space tokens
- Simplify compiler preprocessing (fewer replacements needed)
- Update all template .bas files to use new syntax
- Expand documentation with consolidated examples and new sections
- Add new keyword modules: social_media, lead_scoring, send_template,
core_functions, qrcode, sms, procedures, import_export, llm_macros,
on_form_submit
2025-11-30 10:53:59 -03:00
|
|
|
|
2025-11-02 14:21:38 -03:00
|
|
|
match result {
|
|
|
|
|
Ok(deleted) => {
|
2025-11-11 09:42:52 -03:00
|
|
|
trace!(
|
|
|
|
|
"Cleared {} suggestions from session {}",
|
|
|
|
|
deleted,
|
|
|
|
|
user_session.id
|
|
|
|
|
);
|
2025-11-02 14:21:38 -03:00
|
|
|
}
|
|
|
|
|
Err(e) => error!("Failed to clear suggestions from Redis: {}", e),
|
|
|
|
|
}
|
|
|
|
|
} else {
|
2025-11-11 09:42:52 -03:00
|
|
|
trace!("No cache configured, suggestions not cleared");
|
2025-11-02 14:21:38 -03:00
|
|
|
}
|
Looking at this diff, I can see it's a comprehensive documentation
update and code refactoring focused on:
1. Adding new documentation pages to the table of contents
2. Restructuring the bot templates documentation
3. Changing keyword syntax from underscore format to space format (e.g.,
`SET_BOT_MEMORY` → `SET BOT MEMORY`)
4. Updating compiler and keyword registration to support the new
space-based syntax
5. Adding new keyword modules (social media, lead scoring, templates,
etc.)
Refactor BASIC keywords to use spaces instead of underscores
Change keyword syntax from underscore format (SET_BOT_MEMORY) to more
natural space-separated format (SET BOT MEMORY) throughout the codebase.
Key changes:
- Update Rhai custom syntax registration to use space tokens
- Simplify compiler preprocessing (fewer replacements needed)
- Update all template .bas files to use new syntax
- Expand documentation with consolidated examples and new sections
- Add new keyword modules: social_media, lead_scoring, send_template,
core_functions, qrcode, sms, procedures, import_export, llm_macros,
on_form_submit
2025-11-30 10:53:59 -03:00
|
|
|
|
2025-11-02 14:21:38 -03:00
|
|
|
Ok(Dynamic::UNIT)
|
|
|
|
|
})
|
|
|
|
|
.unwrap();
|
|
|
|
|
}
|
Looking at this diff, I can see it's a comprehensive documentation
update and code refactoring focused on:
1. Adding new documentation pages to the table of contents
2. Restructuring the bot templates documentation
3. Changing keyword syntax from underscore format to space format (e.g.,
`SET_BOT_MEMORY` → `SET BOT MEMORY`)
4. Updating compiler and keyword registration to support the new
space-based syntax
5. Adding new keyword modules (social media, lead scoring, templates,
etc.)
Refactor BASIC keywords to use spaces instead of underscores
Change keyword syntax from underscore format (SET_BOT_MEMORY) to more
natural space-separated format (SET BOT MEMORY) throughout the codebase.
Key changes:
- Update Rhai custom syntax registration to use space tokens
- Simplify compiler preprocessing (fewer replacements needed)
- Update all template .bas files to use new syntax
- Expand documentation with consolidated examples and new sections
- Add new keyword modules: social_media, lead_scoring, send_template,
core_functions, qrcode, sms, procedures, import_export, llm_macros,
on_form_submit
2025-11-30 10:53:59 -03:00
|
|
|
|
2025-11-11 09:42:52 -03:00
|
|
|
pub fn add_suggestion_keyword(
|
|
|
|
|
state: Arc<AppState>,
|
|
|
|
|
user_session: UserSession,
|
|
|
|
|
engine: &mut Engine,
|
|
|
|
|
) {
|
2025-11-01 20:53:45 -03:00
|
|
|
let cache = state.cache.clone();
|
2025-11-30 16:25:51 -03:00
|
|
|
let cache2 = state.cache.clone();
|
|
|
|
|
let cache3 = state.cache.clone();
|
|
|
|
|
let user_session2 = user_session.clone();
|
|
|
|
|
let user_session3 = user_session.clone();
|
Looking at this diff, I can see it's a comprehensive documentation
update and code refactoring focused on:
1. Adding new documentation pages to the table of contents
2. Restructuring the bot templates documentation
3. Changing keyword syntax from underscore format to space format (e.g.,
`SET_BOT_MEMORY` → `SET BOT MEMORY`)
4. Updating compiler and keyword registration to support the new
space-based syntax
5. Adding new keyword modules (social media, lead scoring, templates,
etc.)
Refactor BASIC keywords to use spaces instead of underscores
Change keyword syntax from underscore format (SET_BOT_MEMORY) to more
natural space-separated format (SET BOT MEMORY) throughout the codebase.
Key changes:
- Update Rhai custom syntax registration to use space tokens
- Simplify compiler preprocessing (fewer replacements needed)
- Update all template .bas files to use new syntax
- Expand documentation with consolidated examples and new sections
- Add new keyword modules: social_media, lead_scoring, send_template,
core_functions, qrcode, sms, procedures, import_export, llm_macros,
on_form_submit
2025-11-30 10:53:59 -03:00
|
|
|
|
2025-12-23 18:40:58 -03:00
|
|
|
|
|
|
|
|
|
2025-10-29 18:54:33 -03:00
|
|
|
engine
|
2025-11-11 09:42:52 -03:00
|
|
|
.register_custom_syntax(
|
Looking at this diff, I can see it's a comprehensive documentation
update and code refactoring focused on:
1. Adding new documentation pages to the table of contents
2. Restructuring the bot templates documentation
3. Changing keyword syntax from underscore format to space format (e.g.,
`SET_BOT_MEMORY` → `SET BOT MEMORY`)
4. Updating compiler and keyword registration to support the new
space-based syntax
5. Adding new keyword modules (social media, lead scoring, templates,
etc.)
Refactor BASIC keywords to use spaces instead of underscores
Change keyword syntax from underscore format (SET_BOT_MEMORY) to more
natural space-separated format (SET BOT MEMORY) throughout the codebase.
Key changes:
- Update Rhai custom syntax registration to use space tokens
- Simplify compiler preprocessing (fewer replacements needed)
- Update all template .bas files to use new syntax
- Expand documentation with consolidated examples and new sections
- Add new keyword modules: social_media, lead_scoring, send_template,
core_functions, qrcode, sms, procedures, import_export, llm_macros,
on_form_submit
2025-11-30 10:53:59 -03:00
|
|
|
&["ADD", "SUGGESTION", "$expr$", "AS", "$expr$"],
|
2025-11-11 09:42:52 -03:00
|
|
|
true,
|
|
|
|
|
move |context, inputs| {
|
|
|
|
|
let context_name = context.eval_expression_tree(&inputs[0])?.to_string();
|
|
|
|
|
let button_text = context.eval_expression_tree(&inputs[1])?.to_string();
|
Looking at this diff, I can see it's a comprehensive documentation
update and code refactoring focused on:
1. Adding new documentation pages to the table of contents
2. Restructuring the bot templates documentation
3. Changing keyword syntax from underscore format to space format (e.g.,
`SET_BOT_MEMORY` → `SET BOT MEMORY`)
4. Updating compiler and keyword registration to support the new
space-based syntax
5. Adding new keyword modules (social media, lead scoring, templates,
etc.)
Refactor BASIC keywords to use spaces instead of underscores
Change keyword syntax from underscore format (SET_BOT_MEMORY) to more
natural space-separated format (SET BOT MEMORY) throughout the codebase.
Key changes:
- Update Rhai custom syntax registration to use space tokens
- Simplify compiler preprocessing (fewer replacements needed)
- Update all template .bas files to use new syntax
- Expand documentation with consolidated examples and new sections
- Add new keyword modules: social_media, lead_scoring, send_template,
core_functions, qrcode, sms, procedures, import_export, llm_macros,
on_form_submit
2025-11-30 10:53:59 -03:00
|
|
|
|
2025-12-02 21:09:43 -03:00
|
|
|
add_context_suggestion(cache.as_ref(), &user_session, &context_name, &button_text)?;
|
2025-11-30 16:25:51 -03:00
|
|
|
|
|
|
|
|
Ok(Dynamic::UNIT)
|
|
|
|
|
},
|
|
|
|
|
)
|
|
|
|
|
.unwrap();
|
|
|
|
|
|
2025-12-23 18:40:58 -03:00
|
|
|
|
|
|
|
|
|
2025-11-30 16:25:51 -03:00
|
|
|
engine
|
|
|
|
|
.register_custom_syntax(
|
|
|
|
|
&["ADD", "SUGGESTION", "TOOL", "$expr$", "AS", "$expr$"],
|
|
|
|
|
true,
|
|
|
|
|
move |context, inputs| {
|
|
|
|
|
let tool_name = context.eval_expression_tree(&inputs[0])?.to_string();
|
|
|
|
|
let button_text = context.eval_expression_tree(&inputs[1])?.to_string();
|
|
|
|
|
|
2025-12-02 21:09:43 -03:00
|
|
|
add_tool_suggestion(
|
|
|
|
|
cache2.as_ref(),
|
|
|
|
|
&user_session2,
|
|
|
|
|
&tool_name,
|
|
|
|
|
None,
|
|
|
|
|
&button_text,
|
|
|
|
|
)?;
|
2025-11-30 16:25:51 -03:00
|
|
|
|
|
|
|
|
Ok(Dynamic::UNIT)
|
|
|
|
|
},
|
|
|
|
|
)
|
|
|
|
|
.unwrap();
|
|
|
|
|
|
2025-12-23 18:40:58 -03:00
|
|
|
|
|
|
|
|
|
2025-11-30 16:25:51 -03:00
|
|
|
engine
|
|
|
|
|
.register_custom_syntax(
|
|
|
|
|
&[
|
|
|
|
|
"ADD",
|
|
|
|
|
"SUGGESTION",
|
|
|
|
|
"TOOL",
|
|
|
|
|
"$expr$",
|
|
|
|
|
"WITH",
|
|
|
|
|
"$expr$",
|
|
|
|
|
"AS",
|
|
|
|
|
"$expr$",
|
|
|
|
|
],
|
|
|
|
|
true,
|
|
|
|
|
move |context, inputs| {
|
|
|
|
|
let tool_name = context.eval_expression_tree(&inputs[0])?.to_string();
|
|
|
|
|
let params_value = context.eval_expression_tree(&inputs[1])?;
|
|
|
|
|
let button_text = context.eval_expression_tree(&inputs[2])?.to_string();
|
|
|
|
|
|
2025-12-23 18:40:58 -03:00
|
|
|
|
2025-11-30 16:25:51 -03:00
|
|
|
let params = if params_value.is_array() {
|
|
|
|
|
params_value
|
|
|
|
|
.cast::<rhai::Array>()
|
|
|
|
|
.iter()
|
|
|
|
|
.map(|v| v.to_string())
|
|
|
|
|
.collect()
|
2025-11-11 09:42:52 -03:00
|
|
|
} else {
|
2025-11-30 16:25:51 -03:00
|
|
|
params_value
|
|
|
|
|
.to_string()
|
|
|
|
|
.split(',')
|
|
|
|
|
.map(|s| s.trim().to_string())
|
|
|
|
|
.collect()
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
add_tool_suggestion(
|
2025-12-02 21:09:43 -03:00
|
|
|
cache3.as_ref(),
|
2025-11-30 16:25:51 -03:00
|
|
|
&user_session3,
|
|
|
|
|
&tool_name,
|
|
|
|
|
Some(params),
|
|
|
|
|
&button_text,
|
|
|
|
|
)?;
|
Looking at this diff, I can see it's a comprehensive documentation
update and code refactoring focused on:
1. Adding new documentation pages to the table of contents
2. Restructuring the bot templates documentation
3. Changing keyword syntax from underscore format to space format (e.g.,
`SET_BOT_MEMORY` → `SET BOT MEMORY`)
4. Updating compiler and keyword registration to support the new
space-based syntax
5. Adding new keyword modules (social media, lead scoring, templates,
etc.)
Refactor BASIC keywords to use spaces instead of underscores
Change keyword syntax from underscore format (SET_BOT_MEMORY) to more
natural space-separated format (SET BOT MEMORY) throughout the codebase.
Key changes:
- Update Rhai custom syntax registration to use space tokens
- Simplify compiler preprocessing (fewer replacements needed)
- Update all template .bas files to use new syntax
- Expand documentation with consolidated examples and new sections
- Add new keyword modules: social_media, lead_scoring, send_template,
core_functions, qrcode, sms, procedures, import_export, llm_macros,
on_form_submit
2025-11-30 10:53:59 -03:00
|
|
|
|
2025-11-11 09:42:52 -03:00
|
|
|
Ok(Dynamic::UNIT)
|
|
|
|
|
},
|
|
|
|
|
)
|
2025-10-29 18:54:33 -03:00
|
|
|
.unwrap();
|
2025-11-02 10:45:57 -03:00
|
|
|
}
|
2025-11-30 16:25:51 -03:00
|
|
|
|
2025-12-23 18:40:58 -03:00
|
|
|
|
2025-11-30 16:25:51 -03:00
|
|
|
fn add_context_suggestion(
|
2025-12-02 21:09:43 -03:00
|
|
|
cache: Option<&Arc<redis::Client>>,
|
2025-11-30 16:25:51 -03:00
|
|
|
user_session: &UserSession,
|
|
|
|
|
context_name: &str,
|
|
|
|
|
button_text: &str,
|
|
|
|
|
) -> Result<(), Box<rhai::EvalAltResult>> {
|
|
|
|
|
if let Some(cache_client) = cache {
|
|
|
|
|
let redis_key = format!("suggestions:{}:{}", user_session.user_id, user_session.id);
|
|
|
|
|
|
2025-12-23 18:40:58 -03:00
|
|
|
|
2025-11-30 16:25:51 -03:00
|
|
|
let suggestion = json!({
|
|
|
|
|
"type": "context",
|
|
|
|
|
"context": context_name,
|
|
|
|
|
"text": button_text,
|
|
|
|
|
"action": {
|
|
|
|
|
"type": "select_context",
|
|
|
|
|
"context": context_name
|
|
|
|
|
}
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
let mut conn = match cache_client.get_connection() {
|
|
|
|
|
Ok(conn) => conn,
|
|
|
|
|
Err(e) => {
|
|
|
|
|
error!("Failed to connect to cache: {}", e);
|
|
|
|
|
return Ok(());
|
|
|
|
|
}
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
let result: Result<i64, redis::RedisError> = redis::cmd("RPUSH")
|
|
|
|
|
.arg(&redis_key)
|
|
|
|
|
.arg(suggestion.to_string())
|
|
|
|
|
.query(&mut conn);
|
|
|
|
|
|
|
|
|
|
match result {
|
|
|
|
|
Ok(length) => {
|
|
|
|
|
trace!(
|
|
|
|
|
"Added context suggestion '{}' to session {}, total: {}",
|
|
|
|
|
context_name,
|
|
|
|
|
user_session.id,
|
|
|
|
|
length
|
|
|
|
|
);
|
|
|
|
|
|
2025-12-23 18:40:58 -03:00
|
|
|
|
2025-11-30 16:25:51 -03:00
|
|
|
let active_key = format!(
|
|
|
|
|
"active_context:{}:{}",
|
|
|
|
|
user_session.user_id, user_session.id
|
|
|
|
|
);
|
|
|
|
|
|
|
|
|
|
let _: Result<i64, redis::RedisError> = redis::cmd("HSET")
|
|
|
|
|
.arg(&active_key)
|
|
|
|
|
.arg(context_name)
|
|
|
|
|
.arg("inactive")
|
|
|
|
|
.query(&mut conn);
|
|
|
|
|
}
|
|
|
|
|
Err(e) => error!("Failed to add suggestion to Redis: {}", e),
|
|
|
|
|
}
|
|
|
|
|
} else {
|
|
|
|
|
trace!("No cache configured, suggestion not added");
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
Ok(())
|
|
|
|
|
}
|
|
|
|
|
|
2025-12-23 18:40:58 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-11-30 16:25:51 -03:00
|
|
|
fn add_tool_suggestion(
|
2025-12-02 21:09:43 -03:00
|
|
|
cache: Option<&Arc<redis::Client>>,
|
2025-11-30 16:25:51 -03:00
|
|
|
user_session: &UserSession,
|
|
|
|
|
tool_name: &str,
|
|
|
|
|
params: Option<Vec<String>>,
|
|
|
|
|
button_text: &str,
|
|
|
|
|
) -> Result<(), Box<rhai::EvalAltResult>> {
|
|
|
|
|
if let Some(cache_client) = cache {
|
|
|
|
|
let redis_key = format!("suggestions:{}:{}", user_session.user_id, user_session.id);
|
|
|
|
|
|
2025-12-23 18:40:58 -03:00
|
|
|
|
2025-11-30 16:25:51 -03:00
|
|
|
let suggestion = json!({
|
|
|
|
|
"type": "tool",
|
|
|
|
|
"tool": tool_name,
|
|
|
|
|
"text": button_text,
|
|
|
|
|
"action": {
|
|
|
|
|
"type": "invoke_tool",
|
|
|
|
|
"tool": tool_name,
|
|
|
|
|
"params": params,
|
2025-12-23 18:40:58 -03:00
|
|
|
|
|
|
|
|
|
2025-11-30 16:25:51 -03:00
|
|
|
"prompt_for_params": params.is_none()
|
|
|
|
|
}
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
let mut conn = match cache_client.get_connection() {
|
|
|
|
|
Ok(conn) => conn,
|
|
|
|
|
Err(e) => {
|
|
|
|
|
error!("Failed to connect to cache: {}", e);
|
|
|
|
|
return Ok(());
|
|
|
|
|
}
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
let result: Result<i64, redis::RedisError> = redis::cmd("RPUSH")
|
|
|
|
|
.arg(&redis_key)
|
|
|
|
|
.arg(suggestion.to_string())
|
|
|
|
|
.query(&mut conn);
|
|
|
|
|
|
|
|
|
|
match result {
|
|
|
|
|
Ok(length) => {
|
|
|
|
|
trace!(
|
|
|
|
|
"Added tool suggestion '{}' to session {}, total: {}, has_params: {}",
|
|
|
|
|
tool_name,
|
|
|
|
|
user_session.id,
|
|
|
|
|
length,
|
|
|
|
|
params.is_some()
|
|
|
|
|
);
|
|
|
|
|
}
|
|
|
|
|
Err(e) => error!("Failed to add tool suggestion to Redis: {}", e),
|
|
|
|
|
}
|
|
|
|
|
} else {
|
|
|
|
|
trace!("No cache configured, tool suggestion not added");
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
Ok(())
|
|
|
|
|
}
|