-
Notifications
You must be signed in to change notification settings - Fork 959
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature: Laravel Module #2318
Comments
Maybe try to use this one |
i gotchu dude, first thing is that there is proper support for blade officially, even in vscode you would only get snippets for directives but if you reference something in Blade templates , then lsp doesnt know what you tryna do, that is the same behaviour for both neovim and vscode, phpstorm has intellisense for each and everything, and the tree sitter syntax hightlighting isnt officially supported for laravel blade files but i copied someone's setup and it has these stuff: |
I have a similar problem as described here. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Did you check the docs?
Is your feature request related to a problem? Please describe.
I've found laravel to be the weakest ecosystem in terms of neovim plugins. it's hard to get syntax highlighting and good LSP setup. this is especially true in the blade file format.
Describe the solution you'd like
I module (or extra as you call it) that sets up all the laravel related packages for the user.
Describe alternatives you've considered
Initially I tried doing everything on my own like I usually do with typescript but I found hurdles along the way. (missing autocomplete options, no blade syntax highlighting, LSP errors where there shouldn't be an error, etc..)
Additional context
No response
The text was updated successfully, but these errors were encountered: