You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an automated pull request included with your Shifty Plan. It contains curated refactors to keep your Laravel application aligned with the latest conventions and features.
This month focuses on adopting modern Blade Directives such as @auth, @empty, @env, @error, and @session. These streamline otherwise longer uses of the common @if directive.
Before merging, you should:
Checkout the shift-2026-02 branch
Review all pull request comments for additional changes
Revert the change from <?php tags to @php directives for Livewire Volt components. This change deviates from the documented standard for Volt, which uses <?php to define the component class.
// In a Livewire Volt component file like `resources/views/livewire/addon/show/⚡comments-tab.blade.php`
@php
declare(strict_types=1);
useApp\Models\Addon;
useLivewire\Component;
newclassextends Component
{
// ... component logic ...
}
@endphp
@placeholder
<div>...</div>
@endplaceholder
After:
// In a Livewire Volt component file like `resources/views/livewire/addon/show/⚡comments-tab.blade.php`<?phpdeclare(strict_types=1);
useApp\Models\Addon;
useLivewire\Component;
newclassextends Component
{
// ... component logic ...
};
?>
@placeholder
<div>...</div>
@endplaceholder
Suggestion importance[1-10]: 8
__
Why: The suggestion correctly identifies that the refactoring to @php violates the standard convention for Livewire Volt components, affecting the vast majority of files in this PR and contradicting the framework's documented patterns.
The action failed due to syntax errors in Blade template files during the formatting/linting process:
- resources/views/livewire/⚡comment-component.blade.php (line 235): Syntax error with $this->commentable::class. The ::class syntax is not being parsed correctly in the Blade template context.
- resources/views/livewire/admin/⚡visitor-analytics-stats.blade.php (line 92): Invalid body indentation level for a heredoc/nowdoc syntax. The closing HTML; delimiter has incorrect indentation (expecting at least 8 spaces).
- resources/views/pages/admin/⚡visitor-analytics.blade.php (line 317): Syntax error with $event->visitable::class. Similar to the first error, the ::class syntax is not being parsed correctly in the Blade template.
The process exited with code 2, indicating these parsing errors prevented successful completion.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is an automated pull request included with your Shifty Plan. It contains curated refactors to keep your Laravel application aligned with the latest conventions and features.
This month focuses on adopting modern Blade Directives such as
@auth,@empty,@env,@error, and@session. These streamline otherwise longer uses of the common@ifdirective.Before merging, you should:
shift-2026-02branchIf you do not wish to adopt these refactors, you may simply close this pull request and delete its branch.