[help] How to make autocompletion works in blade?

[feryardiant]

First of all, thanks for the amazing work in this plugin. I've spent whole day today setting up my neovim config to work with blade files.

Screen.Recording.2024-09-17.at.19.08.24.mp4

Everything seems working just fine, until I realize that :

• Only directives that defined in grammar.json is highlighted, other than that (directive from third-party package, e.g: inertia) is not.
• The auto-completion (me using intelephense) is not working.
• There's ERROR in the InspectTree on directive' param.

Can anyone guide me regarding above points? Thank you in advance.

My config: feryardiant/dotfiles#17

Best regards,
Fery

[EmranMR]

Hi @feryardiant, and thanks for the kind words!

Inertia

• I am not an Inertia user, can you direct me where I can find all the directives for inertia, or list them here, and I will add them to the grammar.
• The errors are probably because of the inertia directives in your case, which will be fixed once I know where I can find them all.

Autocompletion.

• This is a tricky one, intelephense LSP does not recognise the blade files.
• I can confirm the emmet LSP does work in blade files, but you need to adjust your config files. I successfully got it working for Helix. But that is just for the HTML stuff
• For Nova, they have API for userland completion and LSP, so I just used the API to create the extension and implement other language functions.

Workaround for NeoVim?

• well, I am not sure if there are extensions that provide autocompletion
• I have the same issue in Helix, but yet to try out the snippet LSP, and just basically make a snippet library. Of course these probably would not be context aware and dynamic like intelephense...

Hopefully the new extension laravel is developing for vscode is an actual LSP which would resolve it practically for all editors!

[feryardiant]

• can you direct me where I can find all the directives for inertia, or list them here, and I will add them to the grammar

• @inertia and @inertiaHead are from inertiajs/inertia-laravel package
• @routes is from tighten/ziggy package

• The errors are probably because of the inertia directives in your case

I'm not sure that was the case, as you can see when I click the "error" line on the InspectTree side, it'll highlight the line on the blade file side which is on @vite() directive.

• This is a tricky one, intelephense LSP

Indeed, based on this config by @calebdw, I made this and hopefully it could work but it's not 😅

Even though I can see that intelephense is listed when I run :LspInfo on that blade file.

Hopefully the new extension laravel is developing for vscode is an actual LSP which would resolve it practically for all editors!

Yes! and I hope they have free tier like what intelephense does.

[calebdw]

Errors are not a concern in and of themselves---you need to determine what language they are occurring in (toggle the languages in the tree). Errors in injections are expected

[calebdw]

Intelephense likely isn't going to work for blade files, even with the php injections because the language server has no context to work with

[feryardiant]

Errors are not a concern in and of themselves---you need to determine what language they are occurring in (toggle the languages in the tree). Errors in injections are expected

Yes, the error isn't bothering me that much, but if there's a way to "fix" it, that would be better. 😁

Intelephense likely isn't going to work for blade files, even with the php injections because the language server has no context to work with

That's unfortunate 🥲

[calebdw]

Here's something you might be interested in:

https://github.com/ricardoramirezr/blade-nav.nvim

[feryardiant]

I think I've already got the answer for the autocompletion and the error message, but not the grammar.

@EmranMR did you have any plan to add supports for directives from third-party packages?

[EmranMR]

Hi @feryardiant I just pushed the new version with Inertia and Ziggy directives support.

did you have any plan to add supports for directives from third-party packages?

The custom if statements are already supported as long as the third party package, follows the Laravel convention. If there are none-standard directives, they need to be defined by the grammar. For example, Livewire 3 has some directives that are not hardcoded and already supported.

For keyword style directives, they all need to be defined manually. There are actually not that many keywords as far as I know, and thankfully it is super easy to extend the grammar. However, dynamic support is fairly impossible, to give you an example, you can not simply use RegEx to say @whatever should be parsed as directive, this will lead to issues with[email protected]. JavaScript grammar definitions for tree-sitter itself does not support lookahead and lookbehinds.