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
I'm not sure this is the way to go, chatgpt gave this solution, and it seems to be working again.
But this was quite some gymnastic for me, it would have helped if somehow debugbar had given me some insight.
You can close this issue however you see fit. Just wanted to share my found. I'm sure this could be obvious for senior devs, but I could not have figured out without your debug snippet and chatgpt
P.S. I end up making the Enum BackedEnum, as Laravel & Other Laravel packge depend and use BackedEnum
The text was updated successfully, but these errors were encountered:
@barryvdh Hi, I just had the same error as This, I found one cause which is reproducible.
Laravel 11 fresh install.
using jetstream
ubuntu 24.04
php8.4.1
nginx
RouteGroupEnum
using RouteGroupEnum::ADMINISTRATION as group attribute messes up debugbar:
phpdebugbar.addDataSet(, "X9e9f63880c3a1639bbcd79e4c852fa02");
if I use string type eneum it works, even if I use any other object/model class even new stdClass() it works.
Debuging
using your suggestion to find out the decode error I tried:
output: Non-backed enums can't be serialized by json_encode
Possible fix
Well it is not an issue with the bebugbar per say, rather how json_decode works.
So, keeping my Enum non-baked yet still providing json_encode way to serialze
I'm not sure this is the way to go, chatgpt gave this solution, and it seems to be working again.
But this was quite some gymnastic for me, it would have helped if somehow debugbar had given me some insight.
You can close this issue however you see fit. Just wanted to share my found. I'm sure this could be obvious for senior devs, but I could not have figured out without your debug snippet and chatgpt
P.S. I end up making the Enum BackedEnum, as Laravel & Other Laravel packge depend and use BackedEnum
The text was updated successfully, but these errors were encountered: