Slint LSP vs additional include paths

[bartekjaszczak]

In my project I added "ui" folder as an include path for Slint files. I modified the build.rs file in a following way:

fn main() {
    let mut ui_dir = env::current_dir().unwrap();
    ui_dir.push("ui");

    let config = CompilerConfiguration::new().with_include_paths(vec![ui_dir]);

    slint_build::compile_with_config("ui/main_window.slint", config).expect("Slint build failed");
}

and it works. So when a component file is located directly in the ui folder, Instead of using relative paths in another, deeply nested component, such as:

import { MyComponent } from "../../../remote_component.slint";

I can just do

import { MyComponent } from "remote_component.slint";

and it compiles just fine. The LSP, however, is not fine and says that it cannot find this file. I'm pretty sure that's because I'm adding the include path at build time. Do you know if there's any way of notifying the LSP about the include paths?

[ogoffart]

You can configure that by passing -I... to the command line arguments of slint-lsp
In VSCode, this can also be done in the settings with the slint.includePaths setting.