Separate files for view!

[Grafcube]

Is there any way I can write the html in external files and then import them into view? I'm using neovim and I would like to use the existing html and tailwind language servers for formatting, documentation, autocomplete etc.

[gbj]

Well, it's not HTML, is the thing -- it's a Rust proc macro. In other words, view doesn't take a string, it takes a stream of Rust tokens as its argument. I guess if you wanted the Angular-style* "HTML in one file, CSS in another, Rust in another" you could write another macro that includes a string from a file, parses that into a token stream with syn, and then feeds that into view. you'd lose the ability to have any kind of rust-analyzer support for expressions inside the view macro though (for example, LSP hover support on the component name should give you component docs, etc.)

[mondeja]

I suspect that the easiest way to solve this problem would be to create extractors/matchers for intellisense extensions as plugins. Currently with VSCode + TailwindCSS Intellisense extension if you configure tailwindCSS.includeLanguages.rust: "javascript" you'll get Tailwind autocompletion for class attributes in literal strings, but not if strings are inside closures.

[Grafcube]

I use neovim so it's a little different. I managed to get Tailwind working by following this thread. Essentially, all I had to do was add "rust" to the filetypes table and set lsp.tailwindcss.init_options.userLanguages.rust = "html". The colorizer plugin worked fine with tailwind set to "lsp".

At this point the only issues left are minor annoyances that I can easily ignore but would like to see addressed at some point. A formatter would be convenient, as would automatically closing tags. I have no idea how this could be done but I vaguely remember reading that it's possible to change rust analyzer's behaviour in macros. As for syntax highlighting, on neovim at least, it's possible to use injections with treesitter.

[mondeja]

For formatting in VSCode I'm currently using leptosfmt with the RunOnSave extension, the following setting does the trick:

"emeraldwalk.runonsave": {
  "commands": [
    {
      "match": "\\.rs",
      "isAsync": true,
      "cmd": "leptosfmt ${file}"
    }
  ]
}

[Grafcube]

I didn't know that existed. I've installed it and made an autocommand for format on save.

vim.api.nvim_create_autocmd(
  { "BufWritePost" },
  {
    pattern = { "*.rs" },
    desc = "Leptos Formatter",
    callback = function(_)
      local buf = vim.fn.expand("%:p")
      local sw = vim.api.nvim_buf_get_option(0, "shiftwidth")
      os.execute("leptosfmt -t " .. sw .. " " .. buf)
      vim.cmd("checktime")
    end
  }
)

The syntax highlighting is a little weird though.

Also, rust analyzer seems to be a lot slower to start up after I set up my Cargo.toml for leptos but I'm not sure if that's related.

[gbj]

To me, this seems like a kind of weird treesitter issue, honestly. (I think nvim uses treesitter for highlighting right?) rust-analyzer emits syntactic highlighting info that works correctly, but it seems like nvim doesn't use it, maybe?