The @ Error Control Operator is no longer suppressing errors in Blade templates

[warmwhisky]

• Laravel Version: 9.29.0
• PHP Version: 8.1
• Database Driver & Version: Mysql 8

Description:

The @ Error Control Operator is no longer suppressing errors in Blade templates

Steps To Reproduce:

Use the @ sign before a variable. <input type="hidden" name="user_id" value="{{ @$user->id }}">
I could change it to {{ isset($user) ? $user->id : '' }} but wondered if something had changed or been deprecated?

[rodrigopedra]

Can you share the error? Just tested on a fresh install just changing the welcome.blade.php template to:

<input type="hidden" name="user_id" value="{{ @$user->id }}">

and no error was thrown and the output is as expected (an <input> tag with empty value attribute).

As I didn't pass any variables to the view, it should error by no $user variable been defined, right?

Also, as a tip, since PHP 8 you can do this instead:

<input type="hidden" name="user_id" value="{{ $user?->id }}">

which, in my opinion, is clearer.

[rodrigopedra]

Well, I tried running sail locally and I can't still reproduce the error. Might be something specific to your install. You can try reinstalling sail on this project. Or try in a different machine if you have one available.

If it still fails, I guess you will have to assess error per error... and I unfortunately can't help with all of them.

On this last snippet I would refactor it to use the new-ish @selected() blade directive:

@foreach($countries as $country)
    <option value="{{$country->alpha_2_code}}" @selected($shippingAddress?->delivery_country_code == $country->alpha_2_code)>
        {{$country->en_short_name}}
    </option>
@endforeach

https://laravel.com/docs/9.x/blade#additional-attributes

Sorry for not founding the root cause. It is working fine here. Good luck =)

[warmwhisky]

Thanks for all of your input and for all of the new blade directives. I will try reinstall Sail and see what happens.

I am back on my Windows drive now and tested exactly the same environment and there is no error :/

[rodrigopedra]

You're welcome! My pleasure to help. Have a nice day =)

[warmwhisky]

On Monday, I first tried Ubuntu using a repo i'd been using in Windows 10 and Docker. Initially I had a lot of issues getting the correct Meilisearch version with docker and may have caused an issue with updating some of the packages. Its a maybe, but with a fresh repo install and knowing how to get the correct version of Meilisearch installed I no longer have the issues with @ and I have a few new blade directives to work with. Thanks!

[warmwhisky]

Well that did not last long. After a reboot I am back to @ not working again.

Something very strange is going on here.