Custom command name

[xiao-e-yun]

I want to separate the code, but this results in ambiguous command names
How to customize the name

main.rs

mod other;

fn main() {
  tauri::Builder::default()
    .invoke_handler(tauri::generate_handler![
      other::hello,
    ])
    .run(tauri::generate_context!())
    .expect("error while running tauri application");
}

other.rs

#[tauri::command]
pub fn hello() -> i32 {
  1
}

main.js

__TAURI_INVOKE__("hello") // 1

[JonasKruckenberg]

In it's current implementation the command name is tied to the function name. So to rename the command, change fn hello to fn hello_world or something

[xiao-e-yun]

belike mod1::mod2::mod1_mod2_function?
or

pub fn hello{
  println!("hello");
}

#[tauri::command]
pub fn mod1_hello(){
  hello();
}

I know, but I'm hoping for a better solution

[JonasKruckenberg]

Well, chances are you can name your functions something more specific that avoids clashes with other modules. At least that's my experience working with large Tauri codebases.

But we will be reworking the IPC system in the future, addressing this issue in the process.

[SuiltaPico]

Well, chances are you can name your functions something more specific that avoids clashes with other modules. At least that's my experience working with large Tauri codebases.

But we will be reworking the IPC system in the future, addressing this issue in the process.

Will this problem be solved in v2?

[ThunbergOlle]

Any updates on this?