Releases: pizcadesaber/vscode-livewire-jump
2.0.1
2.0.0
I’ve completely replaced the previous core, and now all the providers are connected to a single, massive caching system. There’s a new option in the context menu that allows you to read all the Blade files and register them locally in the workspace, enabling faster loading rather than loading them in real time.
For now, this is the only way to update, but I plan to integrate it soon with a filesystem watcher so that small changes can be automatically detected, avoiding the need to manually read all the files.
I believe the current system is a significant improvement, especially with the new view configuration. Now, you can specify prefixes for views and tags. The key should be in the format bladeDir|classDir
, and the value tagPrefix|aliasPrefix
. The aliasPrefix
is designed to be used for subdirectories. For the key, both |
and :
are accepted as separators, but for the value, I’ve preferred to stick with |
, as :
is used in cases like livewire:
.
1.3.0
- Livewire and Blade component tag links.
- View string autocompletion and go to view.
1.2.1
- Added support for Blade component classes:
- Navigate between
/resources/views/components/my-class.blade.php
and/app/Views/Components/MyClass.php
. - Commands dynamically adjust visibility based on the file type currently open (
Blade
orPHP
).
- Navigate between
- Improved command visibility logic:
- Commands like
Go to Blade View
orGo to PHP Class
are now context-aware and will only appear in the context menu when applicable.
- Commands like
- Enhanced
Go to
functionality for Livewire components and Blade views.
1.2.0
- Autocomplete
<livewire:
. - Go to Livewire view.
1.1.0
This release excludes the x-slot
tag because it is reserved in Blade.
1.0.0
Features
- Go to PHP class from Livewire Blade views: Right-click and select
Go to Livewire Class
. - Go to Livewire or Blade component views from Blade views (
Ctrl+click
).