We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@ray is not detected in HTML/Blade templates
Describe the bug
The @ray directive is not being detected in .blade.php templates, even though the ray() function is correctly detected in standard PHP files.
To Reproduce
Given the following examples:
✅ PHP file (example.php) – ray() is detected correctly:
ray('This works in PHP');
❌ Blade file (example.blade.php) – @ray is not detected:
@ray('This is not detected')
Expected Behavior
Duster should recognize and properly lint @ray in Blade templates, just like it does for ray() in PHP files.
Additional Context
The @ray directive is a Blade shortcut for ray(), and it should be treated similarly when linting Blade files.
Would you like me to add anything else to this? 🚀
The text was updated successfully, but these errors were encountered:
Same goes for @dump().
@dump()
Sorry, something went wrong.
No branches or pull requests
@ray is not detected in HTML/Blade templates
Describe the bug
The @ray directive is not being detected in .blade.php templates, even though the ray() function is correctly detected in standard PHP files.
To Reproduce
Given the following examples:
✅ PHP file (example.php) – ray() is detected correctly:
ray('This works in PHP');
❌ Blade file (example.blade.php) – @ray is not detected:
@ray('This is not detected')
Expected Behavior
Duster should recognize and properly lint @ray in Blade templates, just like it does for ray() in PHP files.
Additional Context
The @ray directive is a Blade shortcut for ray(), and it should be treated similarly when linting Blade files.
Would you like me to add anything else to this? 🚀
The text was updated successfully, but these errors were encountered: