When editing a blade file the filetype becomes BLADE but then auto indentation for HTML and PHP (within <?php, ?> tags no longer works as spected).

Should blade indent bring in html and php indent files?

For proper html autoindent inside php files i'm using this plugin:

                  Plug 'captbaritone/better-indent-support-for-php-with-html'

Hey Jason

Thank you for an awesome syntax for vim! I'd like to discuss something with you:

1. Long time ago I've selected your syntax plugin as a part of vim-polyglot language pack. It is regularly updated and developed for more than 2 years now. I'd like to ask you to link to it, so all language packs and vim-polyglot can gain popularity as a community :) I'm sending a pull-request with one possible reference in the README, but maybe you want to write one by yourself? Vim-polyglot already lists and links to your plugin.
2. Vim-polyglot is an open source project, but I'd like to make it a community effort. Maybe you'd like to become a contributor to it? You'd have commit access so you could fix any issues vim-polyglot introduces, release updates, and propose/evaluate/develop other language packs.

Thank you for considering both requests.

Regards, Adam

Hi,

I have a problem with indentation on *.blade.php files. I was using this trick based on the following issue https://github.com/xsbeats/vim-blade/issues/1

autocmd BufNewFile,BufRead *.blade.php set ft=html | set ft=phtml | set ft=blade " Fix blade auto-indent

@foreach ($articles as $article)
   <h1>{{ $article->title }}</h1>
   <p>{{ $article->content }}</p>#
|
@endforeach

When it should be

@foreach ($articles as $article)
   <h1>{{ $article->title }}</h1>
   <p>{{ $article->content }}</p>#
   |
@endforeach

The following command outputs:

:set ft?
filtetype=blade

How to solve it?

Regards,

Highlighting plugins seem like the kind of project which could really use test cases since I imagine they're pretty susceptible to regressions.

I figure it might be pretty easy to build a test case for a current version by using the :TOhtml function in vim and dumping that in a file, then the test case can check the current output against the saved. Once satisfied that a new change doesn't regress anything, the new test blade code is added and the HTML regenerated.

Just an idea.

Trying to use this plugin to develop in Laravel. Syntax looks nice, but the indentation doesn't seem to work properly. Given this sample code below, when I press o at the cursor # the new line | starts at the very beginning not at the proper indentation level.

@foreach ($articles as $article)
   <h1>{{ $article->title }}</h1>
   <p>{{ $article->content }}</p>#
|
@endforeach

When it should be:

@foreach ($articles as $article)
   <h1>{{ $article->title }}</h1>
   <p>{{ $article->content }}</p>#
   |
@endforeach

This happens at any indentation level. Any ideas how to fix it?

Currently indentation is based on the function HtmlIndent which is the default.

But there are plugins that add their own indentation. The eclim is one of those.

It is good to give the user option to continue using HTML and PHP indenting of your favorite plugin and only add the Blade indentation.

I added a check to see which base indentation should follow, if none is defined or is not valid, will use the default HtmlIndent. It also checks if the required function exists.

For now I only know eclim, but if someone inform other cases like this, it will be easy to add.

This change does not alter the operation of anyone, even if you use the eclim.

If someone has the eclim and want to use the standard indentation eclim and only add the indentation blade, just add in your .vimrc the following line:

let g:BladeIndentBase = 'eclim'

The main difference in eclim indentation is that it increases the indentation when there is line break between attributes.

Default:

<input name="example"
value="example" />

Eclim:

<input name="example"
        value="example" />

It was this difference that I realized I had something was out of the pattern of other files.

I have the following piece of code in one of my blade files. For some reason, the first line of code breaks the highlight as seen on the screenshot

<button class="navbar-toggler"  data-toggle="collapse" data-target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="{{ __('Toggle navigation') }}">
    <span class="navbar-toggler-icon"></span>
</button>

If I break the first line in two lines, the higlight works as expected.

Example file (named test.blade.php):

<div>
    |
</div>

Pipe shows where to position the cursor. In insert mode, type: {{ $foo->

Upon hitting the > key, the line will outdent.

I'm using the latest version of NeoVim and vim-blade on Arch Linux. The ft is indeed blade and I don't think there's anything in my config which could be messing with this.

My previous commit (fc9fceb) broke the highlighting of keywords with numbers in it (e.g. h1-h6). I changed it to the default value of iskeyword plus @-@

The old code overwrites the indentation of eclim plugin.

With these changes, if the indentation of eclim is available, this will be used, otherwise it continues using the default indentation.

Overview

This PR resolves #74 by adding the @props directive to the list of default supported directives.

The @props directive was supplied by Laravel as part of their Blade component upgrade (docs here) as a way to pass data into anonymous components. For anyone unfamiliar, anonymous components are Blade components that are not backed by a PHP class and only consist of a Blade file.

Since Laravel has added this directive directly into the framework, I think we ought to have it in this plugin as well!

Additions

• Adds the @props directive to syntax/blade.vim
• Adds a test to test.blade.php

Other Notes

I added the @props directive to the top of the test.blade.php file because, typically, that's where the directive would go in everyday use.

I'm fairly certain that I added the directive to the correct spot in the syntax file, as it was working when I tested using the provided blade testing file, but I'm happy to move it somewhere else in the list if that would be preferable.

Thank you again for maintaining this package! It's an integral part to my Laravel development workflow, so I really appreciate it.

From what I can tell, it seems that the @props directive that is used by Laravel to make Blade Components (here) isn't supported by default at the moment.

Since this is a Laravel-supported directive, I think it would make sense to add into the plugin. Right now, I can get around it fairly easily by using the vim configurations for custom directive (thanks for adding that, by the way–it's super helpful), but it would be nice to not have to worry about adding @props to the list myself.

I'm happy to take a stab at this issue, but I'm going out of town shortly for about a week, so I figured that I'd go ahead and open an Issue in case anyone wanted to work on this while I'm away from my computer.

Also, as always, if this isn't an issue, please let me know!

Thanks for supporting this plugin! It's a huge part of my vim workflow for Laravel development 👍🏻

I'm using

<option @if($prod->key) selected @endif value="yes">Yes</option>

and it gets confused when it encounters > and the highlighting is screwed up until the closing </option> tag.

When testing this, I realized that it has trouble with the data keyword as well...but that just might be from a conflict with html5.vim. Come to think of it, maybe it all has to do with the fact that I'm using othree/html5.vim? Does this affect anyone else?

I just pulled a fresh installation of Laravel and took a look in the default welcome.blade.php file.

Hit gg V G = and ended up with the following results.

Before:

After:

Clearly, the indentation is all wrong and the syntax highlighting doesn't seem to recognize the new custom if-conditionals (@auth and its closing tag @endauth) - the latter seemingly being the root of the problem.