Laravel Blade Editor

[trollfalgar]

Hello again.

About the new version 1.44.14927 (pre-release)... (great additions by the way)...

Sugestions

• Space inside double curly braces (and auto close): {{ $nice }} not {{$meh}}.
• Blade Snippets. Autocomplete for directives, global functions, etc.
• Surround with blade snippet (e.g. @for, ....) (comment)
• Autocomplete for route names.
• Autocomplete views in view(), View::make(), @include() (comment)
• Blade Formatter. This would be awesome too, full blade format support.
• Go To Controller or Livewire componente or Blade component class, while inside the view.
• @livewire() directive, <livewire: tag and completion of livewire views

[jakubmisek]

@trollfalgar: thank you for your feedback and your suggestions.

It is all planned;

One question -

Space inside double curly braces ...

What does it mean? is it related to the Blade Formatter?

[trollfalgar]

@trollfalgar: thank you for your feedback and your suggestions.

It is all planned;

One question -

Space inside double curly braces ...

What does it mean? is it related to the Blade Formatter?

Would be perfect auto space in two situations:

• When type {{ or {!!, etc, automatically close with }} or !!} and add two spaces inside with the cursor at the middle to add the content.
• When formating, basically add spaces around the content inside the braces.

There is a extension we are using just to do this: Laravel Blade Spacer.

Other feature interesting, is wrapper selected text inside a blade directive.
Something like that:

Hello,
I received a false positive on blade.php file with this code:
@lang('pagination.message', ['actionText' => $actionText])
The error reported: Syntax error: unexpected token ','PHP(PHP2014)
Thanks

[trollfalgar]

Hello,
I received a false positive on blade.php file with this code:
@lang('pagination.message', ['actionText' => $actionText])
The error reported: Syntax error: unexpected token ','PHP(PHP2014)
Thanks

I received this error too with @component directive.

[AComasSamcla]

Hello,
I received a false positive on blade.php file with this code:
@lang('pagination.message', ['actionText' => $actionText])
The error reported: Syntax error: unexpected token ','PHP(PHP2014)
Thanks

I received this error too with @component directive.

Same error with @can directive

[jakubmisek]

just released 1.44.14950 - fixes @can, @component, @lang (and some other tags with commas)

[jakubmisek]

@trollfalgar I have a question to "Autocomplete for route names":

Isn't it supposed to be view names?

[trollfalgar]

@jakubmisek it's route names.

But view names would be awesome too.

[jakubmisek]

@trollfalgar something like this?

[trollfalgar]

@jakubmisek exactly like this.
Normally the quotes are not showed in the preview, but makes no difference in the result.
Great work.

The view name completion works for all pertinent blade directives?

[jakubmisek]

@trollfalgar thanks for the feedback!

Also, we're adding the completion of the components:

Next, there will be attributes from the component class.

[trollfalgar]

@jakubmisek very nice.
Now the Go To Controller or Livewire componente or Blade component class, inside the view. item, would be the cherry on top.

[jakubmisek]

Please try pre-release version 1.54.16610 - I'd like to hear some feedback

• if the blade views, components, and livewire components are located and suggested wherever you'd expect it
• go to definition works (navigates to the view file)
• completing named routes

[trollfalgar]

Please try pre-release version 1.54.16610 - I'd like to hear some feedback

• if the blade views, components, and livewire components are located and suggested wherever you'd expect it
• go to definition works (navigates to the view file)
• completing named routes

Great work. Some observations:

The @each, @includeFirst @includeWhen, @includeUnless directives has no completitions.

Blade Subviews
Rendering Blade for Collections

--

The @livewire directive works nicelly (completition and navigation). But the navigation just go to blade view. Is important the option to go to the class component as well.
Some extensions offers the option to choose which file to go (class or blade view), others set the default to blade view, and on hover the option to go to class.
And the third option (I like to use in parallel with the previous two options), is a keyboard command to switch between files (class and blade view). This is super handy, 'cause I don't need to search for the file when working in a component. This can be great for Livewire Components and Blade components as well (if the blade component has class file, and if livewire component has blade view file).

Unfornetlly, no support for <livewire:component/> syntax is available, completition or navigation. (I only use this syntax).

Obs: I realize the item Go To Controller or Livewire component or Blade component class, while inside the view is marked as done, but how can we do that? Is exactly what I suggest above.
I believe we mistake it with go to from outside the component.

--

The route names completition and sugestion is working as expected.
But I have one sugestion: navigation to the specific route in the routes file on click. This can be very helpfull.
Nice touch showing the URI on hover.

--

The blade component completition/sugestion is working. But the navigation isn't. It doesn't go to the blade file, and there is no reaction on the CTRL + hover.