How can I modularize command handler generation?

[TylerJMcLean]

As the title suggests, I am looking to modularize the creation of command handlers so that I don't bloat the Tauri builder setup with a potentially large amount of commands that need to be accessible from the front-end. I know you can't call invoke_handler more than once per a comment on a similar thread from Fabian but I don't want to call it multiple times anyways. I want to just have a way to split the creation of the handlers or a way to make a combination of the two. Ideally it would look something like the following
module_1.rs

pub fn create_module_handlers() -> CompatibleAndConcatableReturnType {
    //Manipulate this in a way that I can combine it with another
    generate_handler![
        function_1,
        function_2,
        ...
        function_15
    ]
} 

module_2.rs

pub fn create_module_handlers() -> CompatibleAndConcatableReturnType  {
    //Manipulate this in a way that I can combine it with another
    generate_handler![
        function_16,
        function_17,
        ...
        function_30
    ]
} 

lib.rs

pub fn run() {
    tauri::Builder::default()
        .invoke_handler(module_1::create_module_handlers() + module_2::create_module_handlers())
        .run(tauri::generate_context!())
        .expect("error while running tauri application");
} 

Obviously I'm trivializing some details here for the sake of getting my point across but if anyone knows how to do something similar I'd be forever grateful!