This package adds syntax definitions for the Laravel Blade engine.

Here is the error message I get when I try to load any .blade.php file

Error loading syntax file "Packages/Laravel Blade Highlighter/blade.sublime-syntax": Apparent recursion within a with_prototype action: 25000 context sanity limit hit

Any idea what's going on and how I can fix it?

Today, I was going to work and my Blade Highlighting broke after getting version 3092 of Sublime Text 3. My color scheme is called IR_Black.

Why is this is happening?

My ST updated to Build 3103 and now my commenting is not working correctly. Instead of using the blade comments, it is wrapping in HTML comments

{{-- Old comment style --}}

<!-- New comment style -->

unless it is a line with an @include or {{ ... }} directive, in which case it comments like this:

// {{ trans('page.content') }}

which of course isn't even a comment at all.

This definitely changed when I upgraded to ST Build 3103.

thanx for the last update, however now we cant make an html comment as all now is being treated as blade comments only.

also the blade comment end is not colored mainly because the {{-- have a scope of punctuation.definition.comment.html while the other side --}} doesn't have it.

When both are installed, and a php/blade file is opened, this error occurs:

Error loading syntax file "Packages/Laravel Blade Highlighter/blade.sublime-syntax": Apparent recursion within a with_prototype action: 25000 context sanity limit hit

Using build 3126 of Sublime. Removing either package fixes the issue.

Syntax highlighting breaks when using either @stack or @push/@endpush in Sublime Text 3 Build 3114.

Screenshot from Sublime Text 3 Build 3103 for reference

I don't know if is intended to work like this but for a while now, I can no longer use (Ctrl/CMD) + / to toggle the blade comments.

Is there anything I can do to fix it? I just have no idea what to modify in order for it to work, I don't want the html comments in my blade files.

What I want in the end is to be able to comment like this:

<div class="form-group">
    <label for="category">Category</label>
    <select id="category" class="form-control" name="category" placeholder="Select category">
        <option value="awesome">Awesome</option>
        {{-- <option value="">Select</option> --}}
        {{--
            @foreach( $categorys as $category )
                <option value="{{ $category->id }}">{{ ucfirst($category->name) }}</option>
            @endforeach
        --}}
    </select>
</div>

I don't mind manually installing the package.

Thanks in advance.

Sublime text 2 installation using package control causes the package folder to be called "Laravel Blade Highlighter" instead of "laravel-blade"

Which causes sublime text 2 to trigger an error every time its launched.

Uninstalled and try to install again. Got this error in console.

Package Control: Error downloading package. HTTP error 404 downloading https://codeload.github.com/Medalink/laravel-blade/zip/1.6.18.

A couple of days ago the package does not work anymore I get this error message:

Error loading syntax file 'Packages/Laravel Blade Highlighter/blade.sublime-syntax': Apparent recursion within a with_prototype action: 25000 context sanity limit hit

Hi,

My blade files are no longer being highlighted correctly. Any @if statements that appear within quotes are not closing correctly and the highlight that is usually used between quotes runs all the way through the rest of the code.

For example:

<p class="first-class @if(x==true) second-class @endif">Text</p>

The above statement will cause string highlighting to continue all the way down the code.

I think the update 2 days ago (15/08/2017) might have caused this issue.

I'm not sure if this applies to @for and the other blade control structures.

Thank you for the package!

Fixes #196

This commit adds a fallback pattern to generic-attribute-values context in order to correctly scope attribute values, even if no attribute names have been consumed before.

The @click directive is not scoped as attribute name due to a design issue of basic HTML syntax with regards to prototype handling within tags. Hence HTML does not match/consume the value assignment via =.